Posts made by snakeibf

Got it all sorted, thank you for the link.

I am having an issue withe the Z motor continuing to lower the extruder even after the homing switch is triggered. The X and Y axes home properly and stop as they should.
I have them all set as active low and in the web interface It even shows the endstop is active when triggered. It just continues to move down anyway. I'm sure I have the correct one connected as I activated all three just to be sure. Has anyone else had this issue?

I just updated the firmware 1.21RC2 and the WiFi update using commands M997 S1 and M997 S0.

I then ran M552 S0 which gave me the response of ok <lf>I then input my SSID and password
I then sent M552 S1 and got this:
Turn off the current WiFi mode before selecting a new one<lf>ok <lf>Then I ran M552 and got the same as I was getting before:
WiFi module is being started

Next I removed the SD card and opened the sys folder and inserted a semicolon in front of M552.
I place it back into the SD slot and when I go through the procedure again to enable the wifi, enter the SSID, password and send M552 S1 again I get this:
Turn off the current WiFi mode before selecting a new one

Here is another diagnostics report:
=== Diagnostics ===
Used output buffers: 1 of 32 (1 max)
=== Platform ===
RepRapFirmware for Duet WiFi and Duet Ethernet version 1.21RC2 running on Duet WiFi 1.02 or later
Board ID: 08DAM-9K9K2-P24SD-6JKDJ-3SJ6Q-17NHJ
Static ram used: 16136
Dynamic ram used: 100488
Recycled dynamic ram: 2160
Stack ram used: 3568 current, 4576 maximum
Never used ram: 7712
Last reset 00:04:30 ago, cause: software
Last software reset details not available
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 19.1, current 21.4, max 21.7
Supply voltage: min 1.6, current 1.6, max 1.7, under voltage events: 0, over voltage events: 0
Driver 0: ok, SG min/max not available
Driver 1: ok, SG min/max not available
Driver 2: ok, SG min/max not available
Driver 3: ok, SG min/max not available
Driver 4: ok, SG min/max not available
Date/time: 1970-01-01 00:00:00
Slowest main loop (seconds): 0.099681; fastest: 0.000044
=== Move ===
MaxReps: 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: 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 ready with "M122" 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 ===
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 0 of 8

• WiFi -
  Network state is starting
  WiFi module is disabled
  Failed messages: pending 0, notready 0, noresp 0
  Socket states: 0 0 0 0 0 0 0 0
  === Expansion ===
  ok

Nothing is connected to the board and never has been, it just got it a few weeks ago and haven't been able to get it to work.</lf></lf></lf>

After downloading and reloading the firmware several times and even replacing the wifi module with a new one I had in the parts bin I still get the same response. Any ideas would be much appreciated? I'd prefer not to have to buy another board.

M552 S0
ok
M122
=== Diagnostics ===
Used output buffers: 1 of 32 (8 max)
=== Platform ===
RepRapFirmware for Duet WiFi version 1.20 running on Duet WiFi 1.0
Board ID: 08DAM-9K9K2-P24SD-6JKDJ-3SJ6Q-17NHJ
Static ram used: 15448
Dynamic ram used: 99320
Recycled dynamic ram: 4016
Stack ram used: 3576 current, 4592 maximum
Never used ram: 7696
Last reset 00:02:08 ago, cause: power up
Last software reset details not available
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 17.3, current 19.2, max 19.4
Supply voltage: min 1.6, current 1.6, max 1.6, under voltage events: 0, over voltage events: 0
Driver 0: ok, SG min/max not available
Driver 1: ok, SG min/max not available
Driver 2: ok, SG min/max not available
Driver 3: ok, SG min/max not available
Driver 4: ok, SG min/max not available
Date/time: 1970-01-01 00:00:00
Cache data hit count 143813038
Slowest main loop (seconds): 0.099625; fastest: 0.000037
=== Move ===
MaxReps: 0, StepErrors: 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: 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 ready with "M122" 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 state is starting
WiFi module is disabled
Failed messages: pending 0, notready 0, noresp 0
HTTP sessions: 0 of 8
Socket states: 0 0 0 0 0 0 0 0
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
ok

Got it mixed up with M122.

I'm getting this now when use the M552 command
M552
WiFi module is being started
ok

I am thinking it is supposed to start at some point.

When I type M112 I get this:
Emergency Stop! Reset the controller to continue.ok
I then use M552 S-1 to stop it, but when I re-enable it and use M112 again I get the same message.
I have tried powering it externally as well, but it makes no difference.

M552
WiFi module is being started
ok
M552 S0
ok
M552 S1
Turn off the current WiFi mode before selecting a new one
ok

Hello,

I have been working on getting the wifi module working for several hours. I am using the latest firmware on GitHub. When I ype M552 S0 using YAT It only says "ok" . I then use the M587 command, input my username and password and I get this:
M587: Failed to add SSID to remembered list<lf>ok <lf>When I upload the firmware to the WiFi module it seems to work, but gives me an error. about bytes per line exceeded. Any ideas? Below is the diagnostic report.

=== Diagnostics ===
Used output buffers: 1 of 32 (2 max)
=== Platform ===
RepRapFirmware for Duet WiFi version 1.20 running on Duet WiFi 1.0
Board ID: 08DAM-9K9K2-P24SD-6JKDJ-3SJ6Q-17NHJ
Static ram used: 15448
Dynamic ram used: 99120
Recycled dynamic ram: 120
Stack ram used: 3576 current, 4460 maximum
Never used ram: 11924
Last reset 00:09:37 ago, cause: power up
Last software reset details not available
Error status: 1
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 20.9, current 23.3, max 25.9
Supply voltage: min 1.3, current 1.7, max 1.7, under voltage events: 0, over voltage events: 0
Driver 0: ok, SG min/max not available
Driver 1: ok, SG min/max not available
Driver 2: ok, SG min/max not available
Driver 3: ok, SG min/max not available
Driver 4: ok, SG min/max not available
Date/time: 1970-01-01 00:00:00
Cache data hit count 765984165
Slowest main loop (seconds): 1.037297; fastest: 0.000033
=== Move ===
MaxReps: 0, StepErrors: 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: 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 ready with "M122" 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 state is starting
WiFi module is disabled
Failed messages: pending 0, notready 0, noresp 0
HTTP sessions: 0 of 8
Socket states: 0 0 0 0 0 0 0 0
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
ok</lf></lf>