@demonio669 said in Simplify3d 4.0.1 gcode causing Duet to mess up:
@ElmoC, I have this start gcode for Simplify, hope it work for you
T0
M140 S[bed0_temperature] ; set bed temp no wait
M104 S[extruder0_temperature] ; set extruder temp no wait
M106 S0
G28 ; home all axes
M116 ; wait all temps
M98 P/macros/CleanNozzle ; clean the nozzle
Not familiar with the M116 command. Will look into that. Thanks.
Well, while I did get it to work a couple times, when I went back and performed the steps here https://duet3d.com/wiki/Using_mesh_bed_compensation, the bed only moves away from the nozzle. I tried Z at 5, 10,15, and 20, all with the same results. 
EDIT: I restarted the printer and homed all axis. I then moved Z to 10, deployed the probe, and tried G30 S-1 again. This time it worked. So one of those commands in the steps is causing the issue. Will see if I can figure out which one.
EDIT 2: It seems the problem is with the M208 Z-3 command. This is setting the maximum Z travel to -3. I believe the command should be M208 Z-3 S1 to change the minimum Z travel.
And I can't upload again.
FTP also fails.
Adding a different access point allowed me to send a job from PrusaSlicer. Will have to see how long this will work.
So after flashing the firmware via BOSSA and updated the WiFi firmware via the PanelDue. Rebuilt the /www directory (note, the DuetWebControl.bin file is not in the release file), I was able to get the web interface back up. Need to try and send a file to it next.
UPDATE: When I try testing the connection for PrusaSlicer, the web interface gets knocked off (Failed to maintain connection) and asks for the password. PrusaSlicer reports the test was successful.
UPDATE 2: Still unable to upload files. Going to try to put a different AP on for the printer to use.
@jay_s_uk As far as I know I don't. It had been working fine but then problems started without making any changes to the config.g file. Next time I have the card out, I will check to be sure.
UPDATE: I checked and it is set to make the OUTPUT look like Marlin, which it has always been set to. Nothing about emulation of Marlin.
@dc42 When trying to update via USB through Ponterface, I get this...
Connecting...
RepRapFirmware for Duet 2 WiFi/Ethernet Version 2.05 dated 2019-12-13b1
Executing config.g...FTP is enabled on port 21
TELNET is enabled on port 23
Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 265C.
Done!
Printer is now online.
>>>M115
SENDING:M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.05 ELECTRONICS: Duet WiFi 1.02 or later + DueX5 FIRMWARE_DATE: 2019-12-13b1
>>>M997 S0
SENDING:M997 S0
[ERROR] Can't read from printer (disconnected?) (SerialException): call to ClearCommError failed
[ERROR] Can't write to printer (disconnected?) (SerialException): WriteFile failed ([Error 22] The device does not recognize the command.)
[ERROR] Can't write to printer (disconnected?) (SerialException): WriteFile failed ([Error 22] The device does not recognize the command.)
[ERROR] Can't write to printer (disconnected?) (SerialException): WriteFile failed ([Error 22] The device does not recognize the command.)
[ERROR] Can't write to printer (disconnected?) (SerialException): WriteFile failed ([Error 22] The device does not recognize the command.)
[ERROR] Disconnecting after 4 failed writes.
Disconnected.
@dc42 When I was able to connect, it was -67 I believe. Since that message, things have gotten worse. I tried updating via Ponterface and it reports it can't write to the printer. The PanelDue still works and I can transfer files by writing directly to the card so I have been able to print. Going to try reflashing the board in a bit.
@jay_s_uk Tried a new card. Same issue.
This started out as a little annoyance, but now it has become a major problem. I can't get any files to transfer to my Duet Wifi. I had been sending files via PrusaSlicer but recently, those started to fail all the times. I then started using the Upload G-Code File button in the web interface. That was working for a bit, but now all files fail at different parts of the upload. I then tried using FileZilla to transfer files, but it fails too. So now I have no way of sending any files to my printer. I haven't tried pulling the SD card and transferring directly because the card is hard to access. I can't even upload new firmware. And now, after trying to update the firmware, I can't even access the web interface.
@dc42 This is almost a year old, but I am now having this issue. I cannot upload files to my Duet WiFi from PrusaSlicer any more, but was in the past. I have changed routers and seeing that 1.21 had issues with some routers, I'm thinking it may be similar. It also fails when using the Upload button in the web interface. It doesn't fail at the same location.
How do you do a WireShark trace?
Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet WiFi 1.02 or later + DueX5
Firmware Version: 2.03 (2019-06-13b2)
WiFi Server Version: 1.23
Web Interface Version: 1.22.6
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03 running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DGM-917DA-G4MS8-6J1F2-3S06R-T9THB
Used output buffers: 3 of 24 (8 max)
=== RTOS ===
Static ram: 25680
Dynamic ram: 94148 of which 416 recycled
Exception stack ram used: 320
Never used ram: 10508
Tasks: NETWORK(ready,524) HEAT(blocked,1236) DUEX(suspended,156) MAIN(running,3748) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:07:10 ago, cause: software
Last software reset at 2020-01-14 17:21, reason: User, spinning module GCodes, available RAM 10372 bytes (slot 0)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 6.0ms, max retries 0
MCU temperature: min 34.6, current 34.8, max 35.6
Supply voltage: min 24.2, current 24.3, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Driver 5: standstill, SG min/max not available
Driver 6: standstill, SG min/max not available
Driver 7: standstill, SG min/max not available
Driver 8: standstill, SG min/max not available
Driver 9: standstill, SG min/max not available
Date/time: 2020-01-14 17:28:29
Cache data hit count 1688952282
Slowest loop: 8.35ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
Movement lock held by null
http is idle in state(s) 0
telnet is idle in state(s) 0
file is idle in state(s) 0
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 81.74ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
I will look into that more, but it didn't seem to address the bigger problem of the Duet getting an IP address from the router, but not responding. I am wondering if it may be a heat issue. After leaving the printer off last night, I was able to connect up with it and get a print job started. The printer had been running several days doing some large jobs (10+ hours). I have been thinking of redoing the way the board is mounted so this incident might just move that to a higher priority.