1,068
edits
Equipment/Staubli/gdmux: Difference between revisions
From London Hackspace Wiki
m
no edit summary
mNo edit summary |
mNo edit summary |
||
| Line 4: | Line 4: | ||
===Challenges=== | ===Challenges=== | ||
* G-code standards often have tool specific inline variations. E.g. for 3D printint there's E###, which is the rate of extrusion, whereas for CNC applications there's F### which is the spindle speed. The issues arises as the CS7 controller does the motion planning and inverse kinematics, and although the controller has GPIO they are not 5v TTL and have to be controlled with [http://www1.adept.com/main/KE/DATA/V%20Plus/V%20Language%20Reference/signal_i.html awkward V+ code]. The alternative is to intercept the gcode on a separate micro-controller and either proxy the motion only g-code to the controller or alternatively | * G-code standards often have tool specific inline variations. E.g. for 3D printint there's E###, which is the rate of extrusion, whereas for CNC applications there's F### which is the spindle speed. The issues arises as the CS7 controller does the motion planning and inverse kinematics, and although the controller has GPIO they are not 5v TTL and have to be controlled with [http://www1.adept.com/main/KE/DATA/V%20Plus/V%20Language%20Reference/signal_i.html awkward V+ code]. The alternative is to intercept the gcode on a separate micro-controller and either proxy the motion only g-code to the controller or alternatively | ||
* Choose whether or not to interpolate arcs as per G03 and G02 | * Choose whether or not to interpolate arcs as per G03 and G02. i.e. the controller side interpolations would look something along the lines of: | ||
<code> | <code> | ||
DURATION 0.5 ALWAYS | DURATION 0.5 ALWAYS | ||
