DDCSV1.1 4 Axis controller

The Shop > CNC

<< < (96/202) > >>

chriscnc:
Thank you UGV for your reply, You CNC machine is beautiful. Are you manually adding the M98 to your G code, or is the controller set up to see the M6 T command and refer it to the M98 sub? Also i see you added a slide for your ATC with 2 relays also controlled via the I/O..

Thank you for your time and info

chriscnc:
Ok Simon I think i understand what UGV is doing after a little digging

So M98 will invoke the controller to run a referenced sub routine. The sub routine is just standard G code and then is using M99 command to end the sub routine. So to stop your spindle and pause for a tool change your sub routine would be:

G53 to refer back to machine coordinates
G01 Z to a safe height
M5 to stop the spindle
G01 XYZ to your tool change position
G0 for a Pause and Cycle start
M3 to turn the spindle back on
T# G49 to reference the tool length offset from the saved table
G54 to ref back to work concordance
M99 to terminate the sub routine.

Here is what i need to understand, Mach can be told to run a VB script or M98 when it sees a M6 or ignore it, can this controller be told to run a M98 when it sees a M6 or do we need to swap out M6 commands in our code for m98.. some CAM postprocessors can be made to do this automatically, But a controller ref M6 to m98 XXXX would be awesome. Also, can the M98 be stored on the controller or needs to be added to the end of the Gcode for M98 reference. There are G and M codes for driving outputs high and low, pauses etc so a full ATC such as UGV is posable as a sub

Benedikt:

--- Quote from: chriscnc on March 16, 2017, 06:14:37 PM ---Ok Simon I think i understand what UGV is doing after a little digging

So M98 will invoke the controller to run a referenced sub routine. The sub routine is just standard G code and then is using M99 command to end the sub routine. So to stop your spindle and pause for a tool change your sub routine would be:

G53 to refer back to machine coordinates
G01 Z to a safe height
M5 to stop the spindle
G01 XYZ to your tool change position
G0 for a Pause and Cycle start
M3 to turn the spindle back on
T# G49 to reference the tool length offset from the saved table
G54 to ref back to work concordance
M99 to terminate the sub routine.

Here is what i need to understand, Mach can be told to run a VB script or M98 when it sees a M6 or ignore it, can this controller be told to run a M98 when it sees a M6 or do we need to swap out M6 commands in our code for m98.. some CAM postprocessors can be made to do this automatically, But a controller ref M6 to m98 XXXX would be awesome. Also, can the M98 be stored on the controller or needs to be added to the end of the Gcode for M98 reference. There are G and M codes for driving outputs high and low, pauses etc so a full ATC such as UGV is posable as a sub

--- End quote ---
The current version of the Pandora firmware I am working on will support on the fly postprocessing right on the controller. I was asking you all to tell me what it needs to rewrite and do to the code. It can easily replace G-codes by macros, do conditional processing, fix issues, improve accuracy, calculate tool compensation, fix inches by converting it to metric values, and so on. Feel free to suggest anything :thumbup:

chriscnc:
Wow Benendikt, that is a heck of a undertaking.... Im not familiar with pandora so i will be no help, is the goal just the front end and leaving the FPGA alone for motion? or is it a full new rewrite? Are you basing any of it off of LinuxCNC or UCcnc for motion path planning? I'm trying to just better understand how this controller works as it seems to mirror more expensive controllers functions i.e standards. Meaning if i can figure out how to write a M98 sub on this I should be able to do it on a Siemens etc as they should respond the same. Have you seen the feature set of the AU based HIND this would be a good reference for UI and features.. basically the same idea but the DDCSV is 1/4 the price and has better hardware. We could really do something with this if we can get this worked out. Thanks for all your work on this Benedikt... Im happy to help where i can and test as well

http://www.hindtechnology.com/

John Stevenson:
Problem with the HIND is it still uses everything BUT a PC and that's what we are trying to get away from, clunky monitors, keyboards and mouse.

Navigation

 Message Index

Go to full version