The copy in the samples folder will do no harm, but it is out of date so you may as well delete it.

sorry… forgot to update

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

Thanks for that,
I have solved the problem by installing 1.9 and ensuring that it runs and then updated to 1.92.

The problem was probably mine, trying to update a few steps at a time.

I'm glad you got it working. If anyone does need to use G92 with an axis position outside the M208 limits, I suspect it can be done by sending M564 S0 before the G92 command to suspend axis limits, and M564 S1 afterwards to restore them; but I haven't tested this.

Yeah, I ended upgrading from 1.18 to 1.19 but didn't realize there was a 1.19.2. Upgraded that and figured out I had to read the release notes on 1.19. Y was reversed. Also there are a few other issues now with the probe I am working out.

After going through all the guides it all appears to be in order

It was a reversed endstop connector.

Silly me for assuming that the 3-pack of endstops would have all 3 sets of cable wired the same at the board connector 🙂 One connector set was different than the other two which caused the issue.

Ok wow I totally missed doing the M552 S0 first!

Wifi module is connected to access point xxx!, IP address 192.168.1.187

Thanks - its on the network again!

That value is nice and low, so it looks like excessive step pulse rate isn't a factor.

Yes. The PID parameters are calculated from the M307 heater model parameters.

The usb pins are not available on any other connectors, but you could connect the wires from a usb cable to other points on the board i.e the diode and the resistors that the socket was connected to. Alternatively, you could connect a USB to serial converter to the PanelDue connector and use that.

Yeah, you can check the version of duet firmware installed on the WiFi. If it <1.19 then use the upgrading to 1.19 Instructions to get it to 1.19

I think it is 1.0
I bought it late last year

Just used P"". Did the trick 🙂

That did it DC… thank you very much!

It's normal for the COM port to disappear while the main firmware is being updated. It should reappear about 30 seconds later when the upgrade completes. However, there is some sort of bug in Windows 10 that sometimes causes it to ignore the USB port that a Duet was connected to after a firmware upgrade. When it happens to me I either change to a different port, or if I am using a USB hub, disconnect and reconnect the hub.

Ok, removing the G1 Z-999 S1 has resolved it. Thanks!

@Willy510:

@SuperJETT:

Did we lose the ability to edit an existing macro with 1.19?

I haven't been able to since the upgrade.

I can check the box next to one but don't see a delete or edit option. Clicking the name pulls up the confirmation dialog asking if I want to run it or not.

Also since the 1.19 update, when I scroll down in Chrome to look at time estimates/etc, within 2 seconds it updates something at the top and resets the scroll back to the top.

Hover over the name of the macro and right click and you'll see a menu popup to edit and delete

Ah, thanks. Not sure it's very intuitive but I'll go with it.

Welcome.

Yes, see https://duet3d.com/wiki/Filaments.