Posts made by rhidgbak

Hi,

Setting the tolerence (SXX) in the M558 command to a negative value currently forces the average to be used (and give a warning--not an error.)

However, this does not seem to be respected when doing mesh grid probing. (works fine for G28 homing etc.) When mesh grid probing after setting "M558 ... S-0.2", it stops and reports an error.

Can this functionality be respected by the grid probing (i.e., setting tolerance in the M558 to a negative value and NOT have an error stop the mesh grid process)?

Looking at the source, it looks like the two situations are handled differently.

I seem to get really good results from by BLtouch using z-probe averaging (on a Marlin machine) so I'd like to do this with my duet3d wifi.

Thanks in advance for considering.....

@dc42 Yes. It does not show up at all (no COM or LPT ports at all on one machine--even when 'hidden' devices were enabled to be shown.) Also no unknown devices on either machine.

I was hoping to avoid erasing the firmware... but since the 1.7v looks to be back-feeding... I'll give it a try. Thanks for you help.

@mudcruzr Yes. Tried 3 different ones.

Hello,

I'm having a problem with a new, out of the box Duet 2 Wifi, v1.04 board. Basically, I can't connect via USB. I've tried multiple USB cable, two windows machines (10 & 7), and a linux machine. None recognize that the Duet is plugged in to USB. No components (except USB) are connected. I was trying to do a 1st time Wifi setup, but couldn't talk to the board at all.

Both the 5V LED and 3.3V LED are lit. The Vin LED is dark. Nothing but USB connector is plugged into board.

Checking the voltages, I got 3.3 V on 3.3; 4.3 on 5V, and (surprisingly!) 1.7V on Vin at the green terminal connector.

No parts feel like they are getting hot. Processor and wifi are above room temp, but not hot--can leave my finger on them indefinitely.

Can anybody help me or does the board have to be exchanged?

Thanks!