inconsistent behavior - duet wifi on latest beta
-
I'm running beta 2.0(RTOS) (2018-06-05b3). This board is being move from a machine I'm decommissioning onto my delta.
I'm having some config trouble. In troubleshooting it, I've found the board behaves strangely. Sometimes, config.g is deleted from the card for no reason. When this happens, any undelete tool can bring it back undamaged. Usually, config.g.bak survives, but it doesn't contain anything recent. Sometimes, tool fan and fan 2 are linked, and sometimes they are treated as separate fans. Sometimes, the delta homing flys off the plate and into a pillar, sometimes it probes normally.
Here's a video showing some of the behaviors.
https://youtu.be/SzCLU_PVHoUEdit: here are my configs....
config.g
; Configuration file for Duet WiFi (firmware version 1.20 or newer)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Wed Jul 25 2018 20:40:36 GMT-0400 (EDT); General preferences
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves
M555 P0 ; Set firmware compatibility to look like native output;*** The homed height is deliberately set too high in the following - you will adjust it during calibration.
M665 R134 L217 B115 H292 ; Set delta radius, diagonal rod length, printable radius and homed height
M666 X0 Y0 Z0 ; Put your endstop adjustments here, or let auto calibration find them; Network
M550 PRanKossel ; Set machine name
M552 S1 ; Enable network
;*** Access point is configured manually via M587
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet; Drives
M569 P0 S0 ; Drive 0 goes backwards
M569 P1 S0 ; Drive 1 goes backwards
M569 P2 S0 ; Drive 2 goes backwards
M569 P3 S0 ; Drive 3 goes backwards
M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
M92 X80 Y80 Z80 E3000 ; Set steps per mm
M566 X1200 Y1200 Z1200 E1200 ; Set maximum instantaneous speed changes (mm/min)
M203 X600000 Y600000 Z600000 E600000 ; Set maximum speeds (mm/min)
M201 X1500 Y1500 Z1500 E1500 ; Set accelerations (mm/s^2)
M906 X1200 Y1200 Z1200 E1200 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S10 ; Set idle timeout; Axis Limits
M208 Z0 S1 ; Set minimum Z; Endstops
M574 X2 Y2 Z2 S1 ; Set active high endstops; Z-Probe
M558 P4 H5 F120 T6000 ; Set Z probe type to switch and the dive height + speeds
G31 P600 X0 Y0 Z14.7 ; Set Z probe trigger value, offset and trigger height
M557 R115 S20 ; Define mesh grid; Heaters
M305 P0 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 0
M143 H0 S120 ; Set temperature limit for heater 0 to 120C
M305 P1 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 1
M143 H1 S260 ; Set temperature limit for heater 1 to 260C; Fans
M106 P2 S1 I0 F500 ; Set fan 2 value, PWM signal inversion and frequency.
M106 P1 S1 I0 F500 H1 T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on; Tools
M563 P0 D0 H1 F2 ; Define tool 0
G10 P0 X0 Y0 Z0 ; Set tool 0 axis offsets
G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C; Automatic saving after power loss is not enabled
; Custom settings are not configured
bed.g
; bed.g
; called to perform automatic delta calibration via G32
;
; generated by RepRapFirmware Configuration Tool on Wed Jul 25 2018 20:40:36 GMT-0400 (EDT)
M561 ; clear any bed transform
G28 ; home all towers
; Probe the bed at 3 peripheral and 0 halfway points, and perform 3-factor auto compensation
; Before running this, you should have set up your Z-probe trigger height to suit your build, in the G31 command in config.g.
G30 P0 X0 Y114.9 H0 Z-99999
G30 P1 X99.51 Y-57.45 H0 Z-99999
G30 P2 X-99.51 Y-57.45 H0 Z-99999
G30 P3 X0 Y0 H0 Z-99999 S3
; Use S-1 for measurements only, without calculations. Use S4 for endstop heights and Z-height only. Use S6 for full 6 factors
; If your Z probe has significantly different trigger heights depending on XY position, adjust the H parameters in the G30 commands accordingly. The value of each H parameter should be (trigger height at that XY position) - (trigger height at centre of bed)homedelta.g
; homedelta.g
; called to home all towers on a delta printer
;
; generated by RepRapFirmware Configuration Tool on Wed Jul 25 2018 20:40:36 GMT-0400 (EDT)
G91 ; relative positioning
G1 S1 X999 Y999 Z999 F6000 ; move all towers to the high end stopping at the endstops (first pass)
G1 X-5 Y-5 Z-5 F1800 S2 ; go down a few mm
G1 S1 X10 Y10 Z10 F360 ; move all towers up once more (second pass)
G1 Z-5 F6000 ; move down a few mm so that the nozzle can be centred
G90 ; absolute positioning
G1 X0 Y0 F6000 ; move X+Y to the centre -
I would suggest doing a full backup and format of the SD card just to make sure it's working properly.
The SD card association has a formatter that will format it properly for the card type.
https://www.sdcard.org/downloads/formatter_4/Do you have a spare card you can test?
-
Before I transferred the board I did wipe the card with the SD formatter tool and completely redid it. It used to erase itself on my old machine too but once I got the config where I liked it and left it alone, it stopped happening, so I thought it was a firmware bug.
-
Can you grab a M122 diagnostic the next time it happens? Might shed some light.
-
@mentaluproar said in inconsistent behavior - duet wifi on latest beta:
Before I transferred the board I did wipe the card with the SD formatter tool and completely redid it.
After you rebuilt the card and put it in a Duet... did you issue the M commands to update firmware in both the Duet and the WiFi module? Or equivalent?
Shot in the dark here... but I'm wondering if there is somehow an incompatibility between what is running in flash on the controllers vs. something on the card. Maybe.
-
No. I thought the firmware did little more than load what was in the card to memory. What are those M codes?
-
M997 S0:1U date firmware modules 0 and 1. This should be what you want for a Duet WifiS0 - main firmware
-
Older releases filename was sys/RepRapFirmware.bin (Duet) or sys/DuetWiFiFirmware (Duet WiFi).
-
Latest releases, filename is /sys/Duet2CombinedFirmware.bin
-
File sys/iap.bin (Duet) or sys/iap4e.bin (Duet WiFi) must also be present.
1 - web server firmware
- Filename sys/DuetWiFiServer.bin (Duet WiFi only)
Latest released binary files Here: https://github.com/dc42/RepRapFirmware/releases I do recommend the very latest releases, I'm running them on a couple of different Detlas, no issues.
.
AFTER you do those upgrades, you may also want to refresh DWC (Duet Web Control), just to be sure. Upload the whole zip file (don't unzip) through the Settings>General>Upload web stuff. https://github.com/chrishamm/DuetWebControl/releases
-
-
@danal said in inconsistent behavior - duet wifi on latest beta:
M997 S0:1
Error: M997: File DuetWiFiServer.bin not found
interesting....
-
reinstalled firmware. probing still crashes into tower. config.g has not disappeared yet so far.
-
Sometimes, the delta homing flys off the plate and into a pillar, sometimes it probes normally
I assume you mean probing, not homing. If you have old deployprobe.g and retractprobe.g files in /sys on the SD card, delete them.
-
no probing files. I must have configured something wrong. delta tries to probe larger than the bed.
-
I'm dumb. I made a typo in the M665 line.
-
config.g disappeared again. Twice. I can undelete it every time without a problem. Given how FAT32 works, I'm thinking something in the firmware is telling it to delete the file.
-
@mentaluproar said in inconsistent behavior - duet wifi on latest beta:
config.g disappeared again. Twice. I can undelete it every time without a problem. Given how FAT32 works, I'm thinking something in the firmware is telling it to delete the file.
Which firmware and DWC versions are you using?
I don't think the current firmware and DWC versions ever delete config.g. When you edit it in DWC and save it, I think it first deletes config.bak if it exists, then renames config.g to config.bak, then uploads the new config.g. Or chrishamm may have implemented it another way, such as uploading to config.new first and then doing a double rename. Either way, if the process fails you should still have the old config.g renamed to config.bak.
-
config.bak is generally there. I think it has vanished before too but I can't remember.
-
its just disappeared for me too. this is not the first time. Also having problems opening the DMS file to restore the bak.
-
@kungfueinstein said in inconsistent behavior - duet wifi on latest beta:
its just disappeared for me too. this is not the first time. Also having problems opening the DMS file to restore the bak.
When it disappeared, were you editing it and trying to save it? Or was it after you uploaded a new file to /gcodes?
How many files do you have in the /sys folder? There is a limit to how many files in a folder the firmware can return to DWC. Although this normally affects only the /gcodes folder, it could affect /sys if you have a lot of files in it.
-
I've only had the files necessary for operation in the sys folder. I only ever notice config.g isn't there when I go to edit it. Sometimes I'll realize I forgot to do something after it goes to reboot the board, so I'll wait, then go back to system editor and see the file is gone.
I don't know if this is relevant, but if I reload the page (like if it's on a tab and my mac has to reload the tab because I was doing lots of other things) the board will repeat the last few instructions sent to it. Even if it is printing, it will interrupt the print to home and calibrate. This happens every time on safari, and a little less frequently on firefox.
Basically, once it's all dialed in, the board works great, but interacting with it in any way leads to unpredictable results. Still nowhere near as bad as octoprint though.
