Hi
I am trying to use a RAMPS 1.4 for the extrusion commands. My question is how to customize the DI and DOs in the post-processor such that the extruder speed commands are sent through robot IOs. Also, is it possible to IE connector, or should I use General IO ports?
Thanks
I assume you can program the the board using G-code. You should be able to customise your post processor to trigger the correct events (such as Digital Outputs) for your 3D printer, which allows you to control your extruder.
(03-11-2024, 08:51 AM)Albert Wrote: I assume you can program the the board using G-code. You should be able to customise your post processor to trigger the correct events (such as Digital Outputs) for your 3D printer, which allows you to control your extruder.
Thank you. I got the R30iB post processor and tried to implement the lines in. It seems the post processor is not running. I am not getting any signal on my DO. (Using SetDo command). Should I add extruder Python code in roboDK design tree as well?
04-05-2024, 09:54 PM (This post was last modified: 04-07-2024, 09:36 AM by Albert.)
Sure.
I tried to use the GUI and the following project file. I could move the robot as it shown in the project file, but the IO is not working.
Where should I add the IO code? I need to control extruder speed using 8-bit digital from DO[109] to DO[116]. And using DO[101] for extruder ON/OFF, DO[102] for direction, DO[103] for the hot end, and DO[104] for the hotbed.
I am using a RAMPS 1.4 to drive the extruder.
Although the robot is connected, I don't know how to send IO commands. It seems I cannot use post processor for that, right?
There are 2 different ways to run the simulated program on your real robot:
Using the post processor, which will generate a program file for your robot controller.
Using the driver, which will send the instructions to the real robot controller, but one at a time.
Drivers are not as easy to customize as post processors.
You actually shared a custom version of the post processor (but I removed it as it contains confidential source code from RoboDK for that post processor). Did your custom post processor work?
(04-06-2024, 05:15 PM)Albert Wrote: There are 2 different ways to run the simulated program on your real robot:
Using the post processor, which will generate a program file for your robot controller.
Using the driver, which will send the instructions to the real robot controller, but one at a time.
Drivers are not as easy to customize as post processors.
You actually shared a custom version of the post processor (but I removed it as it contains confidential source code from RoboDK for that post processor). Did your custom post processor work?
As you mentioned, I could get the robot moved using RoboDK GUI, which I guess is the driver.
My post processor was not working. (My robot has Karell and FTP. )
The post-processor has no error but cannot link to the robot to move it. I generated Python code by right-clicking on the program generated in GUI, then tried to either send it to a robot or generate it on my PC. I got the output code, which was not working(no error, but not working).
Do you have any resources, like a sample that works for the Fanuc robot, that I can use to develop mine?
If you need more help to customize your post processor it is better if you contact us: https://robodk.com/contact
Thanks again,
Can I trigger extruder calls using the driver? Can I have a Python code similar to the macro example available(Extruder.py), but instead of using tcp/ip, send 8bit words to CRMA 58/59 for speed control?
