Cant get my nozzle close to bed at all when trying to print

[Phaedrux]

The H value in the M558 command in config.g

[Phaedrux]

@puppet172 did it work?

[Puppet172]

@phaedrux @dc42
Yeah it worked.
And another question. When i re did my G29 to have more points to be more accurate, now when ever i print it is much higher off the print bed like a couple millimeters. Why would this be happening?
Thanks

[Puppet172]

@Phaedrux @dc42

I don't think the bed level is working to well

[Phaedrux]

Yeah that's a bit too high maybe.

Can we get some more details of your printer? Print surface? Slicer settings?firmware version?

[Puppet172]

@phaedrux
Ok So my printer is massive its about 3 ft cubed and has two arms controlling the y and one controlling the x and finally 4 lead screws controlling the z. it is printing onto a piece of aluminum that is screw down to box tube then that screwed into the frame the bed is not level by itself. i have tried my best to get it level on its own but to no avail. On that aluminum sheet is 1 foot squares of PEI i bought off amazon and have pieced together to make a bed surface. i am using Cura 15.04.6 as a slicer, but have been thinking about buying Simplify 3d.

[Puppet172]

@phaedrux
Software Information
Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet WiFi 1.02 or later + DueX5
Firmware Version: 2.01beta1(RTOS) (2018-06-23b1)
WiFi Server Version: 1.21
Web Interface Version: 1.21.2-b1

[Phaedrux]

Alright, from the top, try this.

Redo your trigger height measurements but run these commands first just to eliminate any overlapping height map errors.

M561			; Disable any current bed compensation
G29 S2			; Clear mesh bed compensation perameters
G31 Z0				; Reset zprobe trigger height 

Enter your resulting trigger height into config.g, reboot, and run a G29 and post the resulting height map image.

[Puppet172]

@phaedrux @dc42
Ok before i can do that i have a problem that just started happening. When i turn on the Printer i can connect for about 5 seconds and then it does like a reset and its says HTTP Error and then i cant connect until it does like a reboot and then it happens again over and over. My setting are still the same as before and this just started happening. Is it a bug with the new update?
Thanks,
Bennett

[Phaedrux]

Does it only do a reset when you connect to the DWC?

Can you connect via usb and terminal and do a M122 command and post the results?

When you updated to 2.0 did you get all of the other files as well? DWC etc?

[Puppet172]

@phaedrux
It resets whether or not its connected online or to usb And yes i downloaded:
DuetWebControl-1.21.2-b1.zip &
Duet2CombinedFirmware.bin

and i also updated the wifi server Also

[Phaedrux]

What was the last thing you changed in config.g? Has any wiring or anything else changed?

Power down, remove the SD card, pop it into your computer, does anything show on the card? If so, make a backup of the contents. Try deleting the config.g and then renaming the config.g.bak to config.g. It automatically makes a backup whenever you save a new change.

As for the way forward, I'll have to let someone more versed in hardware problem recovery step in.

In the mean time you can try running through this: https://duet3d.dozuki.com/Wiki/What_to_do_if_your_Duet_won't_respond

[Phaedrux]

@puppet172 said in Cant get my nozzle close to bed at all when trying to print:

@phaedrux
It resets whether or not its connected online or to usb And yes i downloaded:
DuetWebControl-1.21.2-b1.zip &
Duet2CombinedFirmware.bin

and i also updated the wifi server Also

So you're saying if you disconnect everything from the board and then connect it to your computer via USB it will just continuously power cycle?

[dc42]

If it resets continuously, please try starting the Duet with the SD card removed and try to connect via USB. If that works and it no longer keeps rebooting, send M122 and post the software reset data and stack trace here so that I can diagnose the problem. Then run the commands in config.g manually one at a time to see which one causes the reset.

[Puppet172]

@dc42
Is the Software reset data and stack trace what i will get from the M122 Command?

[Puppet172]

@dc42 @Phaedrux
RepRapFirmware for Duet 2 WiFi/Ethernet Version 2.01beta1(RTOS) dated 2018-06-23b1<LF><LF>Executing config.g...Error: M587: Failed to add SSID to remembered list<LF>HTTP is enabled on port 80<LF>FTP is disabled<LF>TELNET is disabled<LF><LF>Done!<LF>RepRapFirmware for Duet 2 WiFi/Ethernet is up and running.<LF>WiFi module started<LF>WiFi module is c

[Phaedrux]

Yes. M122 is a dump of diagnostic information

[Puppet172]

@phaedrux @dc42
What commands do you mean in the config?

[Phaedrux]

@puppet172 I think he means that you should send each line of the config.g file over the USB terminal connection one at a time. If there is a command in there that is causing it to reset, you'll know when you send it.

It looks like you're getting an error on your M587 command to add an SSID. Maybe comment out that command and try again?

[Puppet172]

@phaedrux @dc42
i was able to get the M122 Command to go through but it still keeps reseting. THeres like a split second where i can get it to work but it still Resets every couple seconds