@handyandy Hi, I have just spotted the solution to this at the end of the 'Getting Started' document. I should RTFM more!

Apologies - That does work! I was just putting Z and the line end and not Z1
Thanks alot

Hi @jay_s_uk , Thanks again... found it!

Hi, I took on board your comments about my old text editors and looked at Notepad++... I didn't like it. The GUI seems very 'home made in my shed'.
I did however find the 'Atom' editor being recommended so have also tried this. I like it a lot.
It has a really nice and modern looking GUI. It allowed me to load my whole SD card into it as a project. I could then set up my Find/Replace criteria and quickly apply them throughout the project. Brilliant.
I can now also display degree symbols correctly!
Cheers all.

@OwenD
Thanks guys. I must be dyslexic?

@Phaedrux
Sorry I misread that, here is the start.g file... start.g

@Phaedrux
Thanks for your help. Requestewd files follow... config.g Cura-end.g Cura-Start.g

Whenever I start a print I always get an error message after a couple of minutes. I select start and the program begins with a cold bed levelling routine (in start.g) then running code I have in my Cura start code it heats up the bed to 80C. I then allways get this error message...

"Error: M190: Temperature too high for heater 0" in a red box at the bottom of the display.

This comes just before it heats the nozzle to 175C and repeats the bed levelling in hot mode. Everything in config.g for the bed (110C) and nozzle (300C) max temperatures looks correct.
After the ebd levelling the rest of the program runs perfectly; bed and nozzle temperature increase to the cortrect filament settings and I generally get perfect prints.

I just don't know what causes the error message. Help please.

@droftarts Thanks for that.

Hi, I hope someone here can help with this, as it's beginning to annoy me! Everything used to work fine when using Chrome, I ran DWC from the browser with no problems. If I used Edge it would very occasionally fail to connect in a similar manner.

The only thing of note that has changed is that in late February I had a dispute with Micosoft re 365, I ended up removing that software and totally re-installing Windows 11 and all my apps.

I am now trying to re-commision my 3d printer that runs via a Duet 3 mini 5 controller and has a PanelDue display connected. There have been no changes at all since before.

My problem is that, now when I try to run DWC from the browser I constantly get the error message 'This site ca't be reached 192.168.1.102 refused to connect'. The PanelDue displays all the correct messages to say it has connected with WiFi to 192.168.1.102

Please, any help with this would be great.

Thanks for that.

Hi,
I would like to echo the value of 'heat.heaters[1].current' in the following line of code as an integer (i.e. no decimal places). Currently it always displays it with to two decimal places.

echo "Heating the nozzle to " ^ global.filamentTemp ^ ", it's currently " ^ heat.heaters[1].current ^ "°C"

It must be easy but I'm feeling a bit thick today!

@jay_s_uk Hi, I've not uploaded files here before so I hope I'm doing it right!
config.g
homex.g
homey.g
homez.g
homeall.g
Whilst you are looking at these I also can't get the PanelDue to display.
Any Ideas?

Hi, I had been getting on fine with sensorless homing with my duet3mini5 board. Both the X & Y axis were homing almost silently and ultra-repeatable with just one contact needed to work.
However, I was getting an error message with the X-axis, it came up as...
"Error: Pin name needed for switch type end stop on X-axis ". I don't understand this homex.g is identical to home.y (except X's and Y's! of course). Why is it asking for a pin name when it's sensorless ?