Posts made by Robocop

Hi, I am working on a product that uses delta mode, but I need to turn off the homing requirement. This would allow for manual (joystick) control for initial movements.

I am aware of M564 H0 and how this doesn't work for delta printers. But is there a way around this?

TIA.

Cnc lathe using Duet as controller

https://forum.duet3d.com/topic/16992/cnc-lathe-using-duet-as-controller

Proxxon MF70 mill with Duet3d...

https://www.youtube.com/watch?v=W22amYrSY4Y

https://www.youtube.com/watch?v=0TquDX9Drjc

New Duet3d v3 PCB

https://www.youtube.com/watch?v=W6U-u0wBdfQ

Hi, I don’t have any experience with using a duet board for a lathe, but I am considering that at the moment. I’m looking at buying a lathe that is quite small and has CNC capability, and I need a control board to drive the stepper motors. The lathe comes with mountings for nema 23 motors. As another person commented, the duet should have no problem driving the motors, the question is rather whether the software that generates the G code can generate the G code that is compatible with the duet board. If I find any other information, I’ll post it on the forum here.

@dc42 The M555 command seems to work, but behaves in a strange way. For example, if I send a G0 X10, it will reply with "Z_move_comp"..... and then "ok"..... why Z?

An alternative is to send a command (and perhaps get an "ok" depending upon the command), then send an M400 and await an "ok" reply to the M400 command.

tHANKS SO MUCH FOR THAT -- i SEARCHED AND FOUND NOTHING SO THAT IS REALLY HELPFUL !!!

wHOOPS, CAP LOCK IS ON

I really could use a "Command finished acknowledgement" so that I know when a command has been completed. I am using several Duets on a project that requires me to know when a move command has completed. The "ok" reply is not suitable as it is not sent upon completion of the command but rather it is send some time around the beginning of when the command is being executed. Is there such a command or method for achieving this please? Thanks in advance !

Okay, thanks, so no problems supplying 24V to the Duet and using 3V steppers?

Hi, I have a 24V PSU and looking to purchase 3V stepper motors. Is this a good idea, or should I be looking at 24V motors (or 12V motors). I understand the controller chips are current controlled, thus the waters are a bit murky..... Thanks.

Oh, I should have added to that..... is the screen resistive or capacitive touch-sensitive? Hopefully the latter.....

Hi guys, a couple of questions about the 4.3" Panel Due.....

1. If I was to require the screen to be rotated into portrait orientation, can the GUI be told to follow suit?
2. If we want to custom programming the Panel Due (we are not using it for a 3D printer) then how difficult is this and is there high quality documentation showing how to draw the GUI and do the necessary comms with the Duet motherboard?

Thanks, Rob

@dc42 Perfect -- I will place an order for one ASAP. Does documentation for the async bit rates and G-code commands come with the Duet PCB?

Thanks dc42 ! The PanelDue seems to be the best option then.

Are you able to point me to any documentation relating to the PanelDue hardware interface and serial comms? Is it simply an async SCI port on the SAM uController? Will I need to use the ribbon cable box-header?

Sorry, I am new to the Duet devices, so not quite sure where to start.

Thanks in advance.

As an alternative, I could use the 2-wire async port (URXD0, UTXD0) that is designed to connect to the PanelDue touchscreen...

https://duet3d.dozuki.com/Wiki/Connecting_an_LCD_control_panel#Section_Connecting_a_PanelDue

Does this serial port use pure G-code or is there some other protocol being used to communicate? I'm thinking that we could plug our module onto that 4-wire (incl. power) port and use pure G-code to do everything.

I will be interested to see how you go with the mods. Some pics of prints of small objects would be appreciated

Re: i2c and external hardware

Hi. We have a simple hardware module (single PCB with a few buttons and things + an i2c interface). We want to use our PCB to send and receive G-code commands and data to and from a Duet board.

We don't want to do anything too complicated -- just move a few motors and read some basic status info from the Duet. Is this capability already implemented in the Duet firmware, and thus a simple exercise to get working, or do we need to modify firmware and ugly things like that?

Ideally I would like to simply plug in our PCB and have full G-code command capability. Here's hoping.....

Thanks in advance,

Rob