@voodoobane Youre Right! I forgot to flash the firmware to the wifi board (Doh!). Have done that now and can confirm after forgetting my wifi password a few times it is now working! I can accsess the DWC and will now assume it is fully working.

@dc42 The duet is up and running again! I never thought it would work again. Thanks a ton for the help.

I am having a slightly strange issue with the web interface though. Wherever there are SDcard contents on display it will load the contents repeatedly in the list. The lists listing things like macros or gcodes just keep growing repeating the contents of the SD card.

I only have one Gcode (test.g) and it just keeps loading it over and over as fast as it can so the list is effectively endless! See example: https://imgur.com/a/yCz6RWn

Hi, I just picked up a PINDA probe (the one Prusa uses on its printers) with the intention of using it as an NPN inductive sensor. The problem with inductive sensors is that the heat from the bed can cause the trigger point to drift somewhat and affect your measurement accuracy.

The interesting feature of the PINDA is that it has an internal thermistor to allow temperature compensation which works by adding an extra connection (4 wires instead of the usual 3). In theory the probe connector could be replaced with two separate connectors: one for the NPN inductive sensor and a second for this thermistor output allowing the sensor to be connected to the Probe port and the thermistor to be connected to a spare thermistor channel.

If this could be done is there any support for compensating probe measurement against probe temperature in RRF like the prusa printers do?

@Th0mpy How are you getting on with the FLY SB2040? I was looking at one of these due to its form factor.

@Danal Do you have a reason for that? Thats what I am actually currently using but alignment / calibration of that is a nightmare

@Danal My actual goal? Its to drive 3 motors for Z without having to buy an expansion board.

Since this is a Z axis I dont need much speed or current on the motors so I suspect it would be ok.

My z is lifted by 3 Z motors with the idea being that I can convert that to 3 independant drives later on for ABL but currently I cant afford the extra board / want to prove out the Z axis first before I go and buy another dueX.

@bearer This is for a Z axis so speed is not really my priority here. I guess it would work acceptably.

We obviously have two headers on the Z driver allowing dual Z motors (i3 style) to be connected. Is is possible to connect 3 Z motors to the one driver? If so how would you go about doing that?

Ive been playing around with G2 / G3 arc commands and I've hit an odd issue. Ive been using the command:

G3 X100.0 Y150.0 R50.0 E0.0

to try and draw an arc from from (X150.0 Y100.0) to (X100.0 Y150.0) in a circle with radius 50. In my understanding it should rotate the head around the centre point 100, 100 but in practise the centre point of rotation is off. It seems to make the circle smaller and move the centre point towards the arc segment.

If I replace the g2 command with:

G3 X100.0 Y150.0 I-50 J0 E0.0

it works perfectly.

Am I missing something here?

Hi, I just picked up a PINDA probe (the one Prusa uses on its printers) with the intention of using it as an NPN inductive sensor. The problem with inductive sensors is that the heat from the bed can cause the trigger point to drift somewhat and affect your measurement accuracy.

The interesting feature of the PINDA is that it has an internal thermistor to allow temperature compensation which works by adding an extra connection (4 wires instead of the usual 3). In theory the probe connector could be replaced with two separate connectors: one for the NPN inductive sensor and a second for this thermistor output allowing the sensor to be connected to the Probe port and the thermistor to be connected to a spare thermistor channel.

If this could be done is there any support for compensating probe measurement against probe temperature in RRF like the prusa printers do?

@bearer perhaps it is workable with that. I’ve never actually tried but can you do maths in macros? E.g. if I take 2 probe points can I calculate the orientation of the part to be milled and then set that with G10 (I think) or is that not possible.

I can’t remember the exact Gcode that the post spits out when you use the probing and I’m not at my pc right now although I think it’s something weird like P348.1.9 or similar depending on the probe macro to be used. The industrial controllers are expecting these macro calls though as they have a macro package installed on them so it’s not a standard gcode. The macros then complete their process such as touching off 2 points on an edge and then calculate the part rotation. Or probe 4 points in a bore to find a centre point.

I assume I could happily change the post however to spit out almost anything or do a find and replace on the Gcode to replace it with something duet friendly.

I’ve built 3 duet based printers now and basically refuse to use anything else because of how good it is. My next project is a CNC and I’m trying to work out what controller to use - ideally I’d like to use the duet but with external drivers. (I’d probably use the built in drivers to power auxiliary steppers around the machine or something)

One key requirement I have is to use a spindle probe for billet locating and probing in second ops (XYZC) and also using a tool setting probe to set tool length. Are these features supported in RepRap firmware?

I’d love to be able to use the fusion360 probing tools but I think these only support calls to the renishaw macros. Would it be possible to get these working on the duet?

I’m sure this question has been asked to death but I can’t find a clear answer. My understanding is the maximum step rate of the duet is 360kHz but that is only for a single motor at a time.

I’m running a CoreXY setup with 4 motors running continuously: A, B, Z, and E. My printer has a belt loop between the motor and the actual CoreXY belt paths so I can adjust the two pulleys on that loop to adjust a gearing ratio between the motor and CoreXY system and I’m looking to tune that.

What would be the maximum step rate the duet can output in this setup? Is it as simple as dividing max step rate (360kHz) by 4?

And what would be the optimal step rate? I don’t want to be running on the limit all the time so is there a value (I’ve heard 50kHz thrown around) that would be an optimal step rate for each motor?

Thanks for any help!