It appears that, at least some of my, problems may have been attributable to the sd card that came with the DuetWifi.
In trying to install the latest firmware, and failing, I discovered a bunch of corrupt directory entries on the sd card. It continued to give me problems even after a full format so I have replaced it.
The Duex isn't detected when coming back from a reset (stop, reset button, or reset after config upgate. It takes a powercycle to bring it back.
I upgraded DWC to 1.22b3 and it looks like that took care of the disconnects.
I don't recall what version DuetWiFiServer. This was a new board and as soon as I verified it was working ok I upgraded the firmware. This is my 3rd Duet (2nd Duex) so it's not the first time I've upgraded Duet firmware.
DWC retries are set at 5.
A couple other thing I notice since upgrading. When I try moving the head via the paneldue it takes ~20 seconds from the time I press the button until the printer responds. From the DWC there's ~5 seconds delay.
And when I tell it to home it often only moves part way and then stops. I have to home 2-3 times before it actually completes the homing. It's configured for sensorless homing at 50% current.
The only other error I get is:
Error: Can't open 0:/sys/oem.json to read, error code 4
Debugging doesn't indicate any problems. I tried unplugging the Duex and the problem persists.
It's also not seeing the Duex5 at times...
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.01(RTOS) running on Duet WiFi 1.02 or later
Board ID: 08DGM-95BNL-MGPSN-6J1F6-3S86J-T0XRX
Used output buffers: 1 of 20 (11 max)
=== RTOS ===
Static ram: 28476
Dynamic ram: 96704 of which 36 recycled
Exception stack ram used: 320
Never used ram: 5536
Tasks: NETWORK(ready,328) HEAT(blocked,1248) MAIN(running,3540)
Owned mutexes:
=== Platform ===
Last reset 00:05:03 ago, cause: software
Last software reset at 2018-07-31 18:04, reason: Unknown, spinning module Platform, available RAM 5188 bytes (slot 2)
Software reset code 0x00b0 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80f BFAR 0xe000ed38 SP 0x200054ac Task 0x4e49414d
Stack: 00445809 0043a80a 2100f000 00000000 00000000 3edb6db7 b7b4d800 3e178897 3e1cd04f 41700000 3e3a4134 3e639cb6 3e9251c9 3c9bf4f7 00000000 00000000 00000000 00000000 00000000 80000010 0043a809 20002bb0 0043ab1b
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 27.0, current 28.0, max 28.1
Supply voltage: min 13.8, current 13.9, max 14.1, under voltage events: 0, over voltage events: 0
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
Date/time: 2018-07-31 18:09:16
Slowest loop: 6.09ms; fastest: 0.08ms
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 240, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Stack records: 2 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: 165.58ms; fastest: 0.08ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
DuetWifi 1.03
Duex5 0.7
Upgraded from 1.20beta6
Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet WiFi 1.02 or later
Firmware Version: 2.01(RTOS) (2018-07-26b2)
WiFi Server Version: 1.21
Web Interface Version: 1.21.2-dc42
Now I often get communications errors and the ui disconnects. It takes a minute or more before it will connect again. A continuous ping doesn't indicate any dropped packets and my AP doesn't show any drops in the wifi connection.
.
Possibly a webUI bug because the x stop IS working but its status is not being updated n the webUI (under settings > machine properties).
I did a complete rebuild/upgrade of my printer and have run into a snag with the X endstop.
Both the X and Y endstops are the same (sainsmart optical), wired the same and configured the same.
The Y endstop works fine.
On power up they both show (in the web interface) not hit, as they should.
If I trigger the X stop it shows hit.
If I untrigger the X stop it stays hit. If I unplug the X stop completely it stays hit.
The led on the endstop turns on/off as it should.
Any ideas?
[[language]]
M574 X1 Y1 S1
Duet Ethernet 1.0 + DueX5
1.19beta11 (2017-07-25)
If you want regular leds on your display panel you could probably use photoresistors to turn them on and off.
No, I guess I missed that part.
Though I did comment out all the commands in those files before hand because I wan't using them