Wifi/Web Console issues

[Shaun]

@shaun m552 s0
ok<LF>WiFi module started<LF>
m115#
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.03 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2019-06-13b2<LF>ok<LF>

[Shaun]

@shaun === Diagnostics ===<LF>RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03 running on Duet WiFi 1.02 or later<LF>Board ID: 08DGM-9T6BU-FG3SN-6J9F4-3SD6R-TUZHF<LF>Used output buffers: 1 of 24 (1 max)<LF>=== RTOS ===<LF>Static ram: 25680<LF>Dynamic ram: 93244 of which 0 recycled<LF>Exception stack ram used: 304<LF>Never used ram: 11844<LF>Tasks: NETWORK(ready,548) HEAT(blocked,1236) MAIN(running,4256) IDLE(ready,160)<LF>Owned mutexes:<LF>=== Platform ===<LF>Last reset 00:02:42 ago, cause: software<LF>Last software reset at 2019-08-26 16:36, reason: User, spinning module GCodes, available RAM 6564 bytes (slot 1)<LF>Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0440f000 BFAR 0xe000ed38 SP 0xffffffff Task 0xffffffff<LF>Error status: 0<LF>Free file entries: 10<LF>SD card 0 detected, interface speed: 20.0MBytes/sec<LF>SD card longest block write time: 0.0ms, max retries 0<LF>MCU temperature: min 31.9, current 32.9, max 33.0<LF>Supply voltage: min 1.7, current 1.7, max 1.8, under voltage events: 0, over voltage events: 0, power goo<Warning: Maximal number of bytes per line exceeded! Check the end-of-line settings or increase the limit in the advanced terminal settings.>

[Shaun]

OK

So today ive started all over. literally clean slate. I am now able to get the wifi connected pretty quickly, the webconsole is responding nicely. only 1 problem... When i remove the board after shutting down Yat and powering it by the printer the wifi doesnt come back on. No blue light.

Ive had to actually edit the config.json to get this far. now from my eye everythign looks right.

Config.json:
"network": {
"enabled": true,
"mac_address": "",
"name": "CR10",
"password": "",
"ssid": "Spiffy",
"ssid_password": "nicetry", (not really my password)
"dhcp": true,
"ip": "192.168.0.20",
"netmask": "255.255.255.0",
"gateway": "192.168.0.1",
"protocols": {
"http": true,
"ftp": false,
"telnet": false
}

M115:
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.03 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2019-06-13b2<LF>ok<LF>

M552 S1 is in the config.g file.
; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet

Still cannot get the wifi to online and join.

[Shaun]

@t3p3tony Are you technical support for the product?

[T3P3Tony]

@shaun said in Wifi/Web Console issues:

@t3p3tony I can only get it connected when i run YAT

M552 s0
m587 s"name" p"password"
M552 s1

Then it connects, try the web console which honestly struggles. WHen i manage to get into the settings to confirm that M552 S1 is set in the config.g it returns a "make sure your device is connected"

When i shut down and then transfer to the printer, wifi doesnt even come on. I get no blue light once i move the board.

Ive cleared the saved details and then set them using M587, i have even tried DHCP and Static details.

Can you run M122, from YAT, one the wifi is connected. It should show what the DB of the wifi signal you are getting.

When you put it in the printer, is that now in a metal enclosure, or is the printer further form the wifi router?

[A Former User]

Need to configure line endings in YAT or use another terminal btw.

when you start editing config.json its probably time to move off the web configurator and stick to only editing config.g as well; duet boards does not read config.json.

[T3P3Tony]

@Shaun I just see you have posted part of M122 above. If you set YAT to use the correct line endings you will get nicer output that wont be truncated.

Go to Terminal/Settings/Text Settings and change the EOL sequence to <LF>.

[A Former User]

(OT, when YAT is the recommended terminal, I'd change the firmware EOL to be compatible with the default settings of YAT)

[T3P3Tony]

@bearer good point, or at least send both.

[Shaun]

@t3p3tony Let me clarify, WIFI now connects when i run M552 S0 then M552 S1. Webconsole also responds pretty quickly.

When moving the board to the printer i power it without connecting it or placing it into anything. Simply laying it down in the foam from inside the shipping box. The wifi blue light doesnt even blink once.

Signal strength isnt a problem, i checked the strength many times as i use to have the Pi there without any issues.

Do you have any suggestions in getting the wifi fired up without having to send code to the board via YAT

[Shaun]

@bearer I hear you, but i only managed to get a stable connection once i added her SID and Password to Config.json so its clearly reading from it. I dont have those details in the Config.g.

[Shaun]

@t3p3tony said in Wifi/Web Console issues:

@Shaun I just see you have posted part of M122 above. If you set YAT to use the correct line endings you will get nicer output that wont be truncated.

Go to Terminal/Settings/Text Settings and change the EOL sequence to <LF>.

Noted

[A Former User]

@shaun said in Wifi/Web Console issues:

so its clearly reading from it.

No.

@shaun said in Wifi/Web Console issues:

I dont have those details in the Config.g.

yes, thats correct, after you enter the details with M587 it is stored in the wifi modules flash memory. which is part of the reason the documentations tells you not to use M587 (to store wifi details) in config.g, the wifi module is not enabled at the time config.g is executed and saving the wifi details every time would put unnecessary wear on the wifi flash memory.

[Shaun]

@bearer said in Wifi/Web Console issues:

@shaun said in Wifi/Web Console issues:

so its clearly reading from it.

No.

@shaun said in Wifi/Web Console issues:

I dont have those details in the Config.g.

yes, thats correct, after you enter the details with M587 it is stored in the wifi modules flash memory. which is part of the reason the documentations tells you not to use M587 (to store wifi details) in config.g, the wifi module is not enabled at the time config.g is executed and saving the wifi details every time would put unnecessary wear on the wifi flash memory.

OK, so could you help me figure out why the wifi is not even coming on when i power the board? At which point is M552 S0 read from Flash?

[MrsDelish]

M552 S0 = turn off networking, you do not want that in your config.g if you want networking.

config.g that contains this should connect if a ssid and pw is previously set.
; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet

gcode wiki M552

[Phaedrux]

@shaun said in Wifi/Web Console issues:

why the wifi is not even coming on when i power the board?

What is the power supply? Do the rest of the lights and everything else come on?

When it is powered by the PSU, can you connect via USB as well and send M122 with the correct YAT line endings and report what the diagnostic replies with?

[Shaun]

@phaedrux said in Wifi/Web Console issues:

@shaun said in Wifi/Web Console issues:

why the wifi is not even coming on when i power the board?

What is the power supply? Do the rest of the lights and everything else come on?

When it is powered by the PSU, can you connect via USB as well and send M122 with the correct YAT line endings and report what the diagnostic replies with?

Ill get this when i get home, PSU is as per vendor recommendations.

Red light by the USB power port, 2 more lights to the left of that. No blue wifi light.

[Phaedrux]

Understood.

With the line endings of YAT changed we will be able to see the end of the diagnostic report which contains the wifi section. Without that we're kind of blind as to what's going on.

Can you also include the contents of config.g from the /sys folder on the SD card?

That contains your current configuration and what you will be editing going forward. It can be edited from the web interface once you can get reliably connected to it. Until then it may require pulling the SD card unfortunately.

[A Former User]

@shaun said in Wifi/Web Console issues:

OK, so could you help me figure out why the wifi is not even coming on when i power the board?

Sure, when you set aside your assumptions as start doing as suggested. The output from M587 and all of the M122 output please.

[Shaun]

@bearer said in Wifi/Web Console issues:

M122

M587<CR>
M587: Failed to retrieve network list
ok
M122 <CR>
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03 running on Duet WiFi 1.02 or later
Board ID: 08DGM-9T6BU-FG3SN-6J9F4-3SD6R-TUZHF
Used output buffers: 1 of 24 (1 max)
=== RTOS ===
Static ram: 25680
Dynamic ram: 93244 of which 0 recycled
Exception stack ram used: 304
Never used ram: 11844
Tasks: NETWORK(ready,1876) HEAT(blocked,1236) MAIN(running,4184) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:00:55 ago, cause: power up
Last software reset at 2019-09-02 22:49, reason: User, spinning module GCodes, available RAM 11844 bytes (slot 3)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x04433000 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: 0.0ms, max retries 0
MCU temperature: min 26.5, current 30.2, max 30.5
Supply voltage: min 0.6, current 1.7, max 1.7, under voltage events: 0, over voltage events: 0, power good: no
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 101580001
Slowest loop: 0.16ms; fastest: 0.06ms
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
=== 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 ===
Slowest loop: 0.15ms; fastest: 0.00ms
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 disabled
  WiFi module is disabled
  Failed messages: pending 2779096485, notready 2779096485, noresp 2779096485
  Socket states: 0 0 0 0 0 0 0 0
  m552 s0
  ok
  WiFi module started
  m122
  === Diagnostics ===
  RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03 running on Duet WiFi 1.02 or later
  Board ID: 08DGM-9T6BU-FG3SN-6J9F4-3SD6R-TUZHF
  Used output buffers: 1 of 24 (10 max)
  === RTOS ===
  Static ram: 25680
  Dynamic ram: 93288 of which 0 recycled
  Exception stack ram used: 304
  Never used ram: 11800
  Tasks: NETWORK(ready,1656) HEAT(blocked,1236) MAIN(running,3768) IDLE(ready,160)
  Owned mutexes:
  === Platform ===
  Last reset 00:04:05 ago, cause: power up
  Last software reset at 2019-09-02 22:49, reason: User, spinning module GCodes, available RAM 11844 bytes (slot 3)
  Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x04433000 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: 0.0ms, max retries 0
  MCU temperature: min 30.2, current 31.6, max 31.7
  Supply voltage: min 1.7, current 1.7, max 1.7, under voltage events: 0, over voltage events: 0, power good: no
  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 461723815
  Slowest loop: 99.34ms; fastest: 0.06ms
  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
  === 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 ===
  Slowest loop: 1.22ms; fastest: 0.00ms
  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 running
  WiFi module is idle
  Failed messages: pending 0, notready 0, noresp 0
  WiFi firmware version 1.23
  WiFi MAC address 84:f3:eb:41:4e:f8
  WiFi Vcc 3.39, reset reason Turned on by main processor
  WiFi flash size 4194304, free heap 30176
  Socket states: 0 0 0 0 0 0 0 0
  ok
  m587
  Remembered networks:
  Spiffy IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0
  ok
  M587 s"Spiffy" p"Password1"
  ok
  M587
  Remembered networks:
  Spiffy IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0
  ok
  m122
  === Diagnostics ===
  RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03 running on Duet WiFi 1.02 or later
  Board ID: 08DGM-9T6BU-FG3SN-6J9F4-3SD6R-TUZHF
  Used output buffers: 1 of 24 (10 max)
  === RTOS ===
  Static ram: 25680
  Dynamic ram: 93288 of which 0 recycled
  Exception stack ram used: 304
  Never used ram: 11800
  Tasks: NETWORK(ready,1656) HEAT(blocked,1236) MAIN(running,3756) IDLE(ready,160)
  Owned mutexes:
  === Platform ===
  Last reset 00:05:15 ago, cause: power up
  Last software reset at 2019-09-02 22:49, reason: User, spinning module GCodes, available RAM 11844 bytes (slot 3)
  Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x04433000 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: 0.0ms, max retries 0
  MCU temperature: min 31.4, current 32.3, max 32.4
  Supply voltage: min 1.7, current 1.7, max 1.7, under voltage events: 0, over voltage events: 0, power good: no
  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 602028484
  Slowest loop: 0.33ms; fastest: 0.06ms
  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
  === 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 ===
  Slowest loop: 0.14ms; fastest: 0.00ms
  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 running
  WiFi module is idle
  Failed messages: pending 0, notready 0, noresp 0
  WiFi firmware version 1.23
  WiFi MAC address 84:f3:eb:41:4e:f8
  WiFi Vcc 3.39, reset reason Turned on by main processor
  WiFi flash size 4194304, free heap 30176
  Socket states: 0 0 0 0 0 0 0 0
  ok

.....