Problem with 1.18 to 1.19 Update



  • Yep SSID is definitely all caps and the password is correct. There was no issues using the same credentials to get the Wi-Fi working on 1.18.

    I'm pretty the problem is related to the "bad parameter" error, since the M587 command doesn't check the credential validity anyway (or so I believe…).

    Also the S1 command gets the module to attempt to connect to the network, so I'm pretty sure the credentials need to be entered under S0.



  • Yes, you are correct. You need to run M587 AFTER issuing a M552 S0.

    Is that second snippet of code in you config.g file? If it is, just comment it out for now.

    using Pronterface(or w/e) try this:

    M558 S""
    M552 S0
    M587 S"NETGEAR89" P"
    ******"
    M552 S1

    That will remove any current config, put the module idle, send the new configs, and finally initialize and hopefully connect the wifi!

    Sorry if you know all this, just going on what i have in front of me for info from your post.



  • Wrong password while trying to connect to NETGEAR89
    Wifi module is idle

    Uppercase? Log say wrong password



  • @KeeganB:

    Yes, you are correct. You need to run M587 AFTER issuing a M552 S0.

    Is that second snippet of code in you config.g file? If it is, just comment it out for now.

    using Pronterface(or w/e) try this:

    M558 S""
    M552 S0
    M587 S"NETGEAR89" P"
    ******"
    M552 S1

    That will remove any current config, put the module idle, send the new configs, and finally initialize and hopefully connect the wifi!

    Sorry if you know all this, just going on what i have in front of me for info from your post.

    All good. The second code snippet is the macro I'm running to set the network credentials, copied from the instructions in the wiki. The enable WiFi line in the config.g file is commented out.

    Unfortunately I've tried those (and several permutations) commands to set the credentials and turn on the Wi-Fi module with no success.



  • and you are 1,000,000,000,000% sure you have the case sensitivity correct in your M587 command? This is where I failed several times my first attempts.



  • @KeeganB:

    and you are 1,000,000,000,000% sure you have the case sensitivity correct in your M587 command? This is where I failed several times my first attempts.

    Yep definitely. I'm pretty sure it doesn't check if the credentials are correct when you run the M587 command anyway, so I don't think an incorrect password or SSID would cause the "bad parameter" error…



  • True. hmmmm

    Copy your M587 line here. Redact the password, but if you could someone keep it so we can see which should be caps/lower that may help.



  • @KeeganB:

    True. hmmmm

    Copy your M587 line here. Redact the password, but if you could someone keep it so we can see which should be caps/lower that may help.

    The last code snippet in my first post is the exact macro I've been using, just with the password replaced by stars. The password is definitely correct, so unless there's a syntax error in the M587 command somewhere it's probably a firmware issue I think.


  • administrators

    Pronterface forces all characters in the commands you send to upper case, including the characters in your password. It may also fail to send special characters in your password, which main explain the "Bad parameter" errors.. Therefore, do not use Pronterface to send the M587 command. Use a terminal emulator (e.g. YAT if your PC runs Windows) instead.



  • Woohoo I think I'm back up and running!

    Setting the credentials through the terminal interface seemed to work. I'm confused as to why running the macro didn't work then, I would've thought the macro would bypass the convert-to-uppercase problem?

    Thanks for the help all 🙂


  • administrators

    Yes, running the macro should have worked if you had the correct commands in it i.e. M552 S0 to enable the WiFi module, G4 … to give it time to start up, then the M587 command.


Locked
 

Looks like your connection to Duet3D was lost, please wait while we try to reconnect.