109
edits
Equipment/Staubli/gdmux: Difference between revisions
From London Hackspace Wiki
→Challenges
m (Mentar moved page Project:Staubli Robot Arm/g-code interpreter to Equipment/Staubli/g-code interpreter: Staubli is permamently installed and working so is part of space's infrastructure now) |
JonRussell (talk | contribs) |
||
| 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 | ||
** I vote we write the GCode interpreter on a separate microcontroller board, which then spits out V+ MOVE commands to the CS7 over a serial port. There are lots of existing open source GCode interpreters (like this one https://github.com/grbl/grbl) which run on Arduino and RPi, and are written in C/C++. Writing it in V+ will be painful :-) Also, we could interface the feed motors, steppers, etc, directly to the microcontroller, rather than trying to drive them with the CS7 GPIO - Jon. | |||
* Choose whether or not to implement arc motion as per G03 and G02. i.e. To use [http://www1.adept.com/main/KE/Data/v%20plus/V%20Language%20User/Locations5.html procedural motion] or not: | * Choose whether or not to implement arc motion as per G03 and G02. i.e. To use [http://www1.adept.com/main/KE/Data/v%20plus/V%20Language%20User/Locations5.html procedural motion] or not: | ||
<code> | <code> | ||
