Wifi/Web Console issues
-
I don't think it's disabled, I think it's trying to find an SSID and cannot, so it stops.
It's working and connecting reliably when you're powered via USB, correct?
-
If you have M552 S1 in config.g and you do not also have another M552 command in there that cancels it, then when it has finished running config.g is will do a site scan and connect to the strongest network that you have told it about via M587. So:
-
Make sure there is exactly one M552 command in config.g and it has parameter S1.
-
Retype that line in case it contains hidden characters.
-
When you start the Duet, look out for the blue LED on the WiFi module flashing.
If it tries to connect but fails, the state falls back to Idle, not Disabled. State Disabled is what you get if you never used M552 to enable the WiFi module, or if you send M552 S-1.
-
-
@phaedrux At my desk, i power cycle the board and the wifi doesnt light up. check the config and wifi disabled.
there in lies my problem.
-
Thanks for all the help, ive managed to resolve this issue myself. Nothing like recompiling the Config.g from scratch.
-
I assume you mean run through the configurator again to get a new set of configs?
It's not so complicated once you're connected. The config.g is just a plain text file with gcode commands. You can edit it right from the web interface.
-
Something i noticed which may or may not have a bearing on things, I thought that in the config.g that the network section was always generally at the start of the file, in this gents case it was well down his list.
So does the duet execute the g code in the order in which its in the file or is it irrelevant and you can put the g code in any order at all ?
-
Everything is executed line by line, be it a config file or a sliced file to print.
The order is only important for a few commands, more so in RRF3 as you have to define pins and stuff before using commands that use them etc. The wiki has some notes on the commands where the order do matter.
(But as evident in another recent thread having the network config at the top may allow you to have working network even if there is a problem further down in the config file?) -
@calvinx said in Wifi/Web Console issues:
Something i noticed which may or may not have a bearing on things, I thought that in the config.g that the network section was always generally at the start of the file, in this gents case it was well down his list.
So does the duet execute the g code in the order in which its in the file or is it irrelevant and you can put the g code in any order at all ?
Good point buddy, thought this would be something support would have noticed had they looked. I dropped the wifi into the general settings second line and all working fine. I had to emulate the code execution before it highlighted that due to errors further up it never got to executing the wifi config down the bottom.
Only spent hours and hours redoing everything. The new configuration wizard places the network settings right at the bottom. Something they might want to add further to the start of the config.g
; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"CR10" ; set printer name
M552 S1 ; enable network
M911 S10 R11 P'M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000' ; set voltage thresholds and actions to run on power loss -
@shaun said in Wifi/Web Console issues:
M911 S10 R11 P'M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000' ; set voltage thresholds and actions to run on power loss
replace
'with" -
@bearer said in Wifi/Web Console issues:
@shaun said in Wifi/Web Console issues:
M911 S10 R11 P'M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000' ; set voltage thresholds and actions to run on power loss
replace
'with"Thanks Bearer, done.
@Admins the configuration wizard sets this so you might want to double check your code.
M911 S10 R11 P'M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000' ; set voltage thresholds and actions to run on power loss
'M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000' as Bearer pointed out should look like "M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000"
-
Seems it was flagged as a bug about a week ago, there is also a more recent issue specifically detailing this issue so it'll probably be updated as soon as the guy who maintains the configuration tool sees it.
-
Good catch guys. Those wrong quotes were stopping the execution of the rest of the config.
