1. Home
  2. Categories
  3. Firmware installation
  4. Can't access wifi

Can't access wifi

  • jens55

    I screwed my wifi setup today. I was trying to move the Duet to a different network and somehow managed to f$^% things up 😞

    At this point, neither the old IP network nor the new network registers the duet as connected based on the "connected devices" lists on either.

    No problem said I (HAH, jinxed it right there!), did a bit of digging and added the following lines to my config.g (memory card removed from duet and inserted in computer)

    m552 s0 ; take AP out of reset, just in case
    m588 s"*"; forget all previous access point info
    m589 s"---------" P"-------------" i00.00.00.00 ; set new access point with no network address defined

    I have replaced the actual ssid and password with dashes here.
    The only thing I am iffy on is specifying the ip address in the very last line - the system is supposed to get the ip number from the network DHCP server.

    Well of course nothing happens and the printer doesn't seem to connect to anything and I can't get to the web interface because it's not connected.
    Based on the lights on the duet, all seems well. The wifi module blinks once.

    A hint on how to proceed would be appreciated !

    0 bearer 1 Reply
  • bearer

    @jens55 said in Can't access wifi:

    m589 s"---------" P"-------------" i00.00.00.00 ; set new access point with no network address defined

    that should probably be M587 or have an actual IP defined with something like I"192.168.10.1" but not sure how well it works from config.g

    and if you do want M589 and the duet to be an accesspoint you'll need a M552 S2 instead of M552 S1 after it.

    0
  • jens55

    It might be - I haven't managed to figure out the subtle differences (if any) between M587 and M589. Both warn me not to use them in config.g

    I will give M587 a try.

    I used I00.00.00.00 (note, no quotation marks) based on what the duet returned to M587 or 589 when it was still working.

    0 bearer 1 Reply
  • bearer

    @jens55 said in Can't access wifi:

    I haven't managed to figure out the subtle differences (if any) between M587 and M589.

    M587 is to connect to an AP, M589 is to provide an AP for you computer to connect to.

    (note, no quotation marks)

    not mandatory until RRF3 i think, so I just add them for good measure.

    0
  • jens55

    Ah, interesting, didn't know that the duet wifi could provide it's own access point. Cool

    Thanks, I will try M587

    Hmmm, there are no quotation marks in the gcode reference and I am running RRF3 ... I will add the quotation marks.

    0 bearer 1 Reply
  • bearer

    @jens55 said in Can't access wifi:

    Hmmm, there are no quotation marks in the gcode reference and I am running RRF3 ... I will add the quotation marks.

    I could well be wrong on that account, but here is somewhere qoutes are required for RRF3 and not RRF2 at least.

    edit: And for M587 you don't need to use I"0.0.0.0" to get a DHCP lease, only to override a previous static IP, as you used M588 S"*" that should render that a moot point.

    0
  • jens55

    No dice with switching to M587
    I will try and remove the "i" bit

    0
  • jens55

    Oh crap ... left the dashes in the config.g file .... it's been a rough day 🙂
    will try again!

    0
  • bearer

    Haha, the I shouldn't be a problem, but removing it would remove any doubt about qoutes, thats why I mentioned it.

    what i should have typed:
    m589 s"---------" P"-------------" i00.00.00.00
    should be either
    M587 S"---------" P"-------------" ;Connects to SSID --------
    M552 S1
    or
    M589 S"---------" P"-------------" I"196.168.10.1" ;Creates SSID ----- and offers DHCP addresses in 192.168.10.0/24
    M552 S2

    0
  • jens55

    Still no joy 😞

    0
  • bearer

    Do you have a panelDue? if so create a macro and run that from the screen.

    if not, create a trigger and attach it to an endstop and then have the wifi code in that?

    edit: or usb and serial terminal is also good and interactive.

    0
  • jens55

    No I don't but just came up with another thought - I will need to give the M587 a letter salad in order to preserve the case of the letters.
    Here goes nothing .... crossing fingers ....

    0 bearer 1 Reply
  • bearer

    @jens55 said in Can't access wifi:

    I will need to give the M587 a letter salad in order to preserve the case of the letters.

    I was under the impression that was only needed for something like ponterface which translates all g-code to upper case? Still using ' to force them lowercase should work regardless of serial or config file methinks. I just seem to recall there is something preventing it from enabling the wifi module until after config.g is done. (maybe M552 S0 takes care of that idk)

    0
  • jens55

    Yes, I was under the same impression ....
    and the rest of the config.g includes an M552S1

    and

    No dice, that would have been too easy ....

    0
  • jens55

    Time to pack it in for the night. Maybe some other people will chime in overnight.
    Thanks for your help!

    0
  • bearer

    That ***** me off... so I tried on a board here.

    Think the second G4 is redundant, but uncomment if it still doesn't work. Confirmed working from config.g even though its baaaaaad mojo.

    M552 S-1
M552 S0 ; take AP out of reset, just in case
G4 S1
M588 S"*"; forget all previous access point info
;G4 S1
M587 S"---" P"---" 
M552 S1
    1
  • bearer

    (Culprit was something in the lines of failed to bring wifi out of reset code -7 or something like that, which showed up on the serial port and paneldue.

    oh, found the serial terminal still open, will add output in case people go searching.

    WiFi module started                                                             
M587: Failed to add SSID to remembered list                                     
Turn off the current WiFi mode before selecting a new one                       
Error: Failed to initialise WiFi module, code -7

    Next time grab a usb cable:))

    0
  • jens55

    Thanks, I will give it a try tomorrow morning.
    Interesting about adding dwell times - I would have never thought about that but it makes sense ! I will also try with and without M552 S-1 as I am thinking that S0 should be ok ... but don't know for sure.
    If I do grab a usb cable and even plug it in on both ends, then what? Do I load a terminal program ? I am running Linux btw. Never tried that before.

    0 bearer droftarts 3 Replies
  • bearer

    @jens55 said in Can't access wifi:

    ! I will also try with and without M552 S-1 as I am thinking that S0 should be ok

    some wifi modules say failed to add network bad format or something like that; the S-1 is just a potential safeguard against that, it won't hurt at least.

    0
  • bearer

    @jens55 said in Can't access wifi:

    Do I load a terminal program ? I am running Linux btw.

    yeah, screen, minicom or picocom should work.

    do dmesg | tail to see what /dev/tty* device the new serial port is called. Probably something like /dev/ttyUSB0 or /dev/ttyAMA0 depending on your distro and the angle of the moon.

    0 jens55 1 Reply
  • droftarts
    Moderator

    @jens55 what firmware version? There’s a bug in early RRF3 versions that doesn’t save the password. Use latest 3.01 RC4. M552 S-1 turns off Wifi, so you can’t add SSID, needs to be in idle mode S0. Though turning off, then idle mode, before sending SSID and password can help.

    Ian

    1
  • jens55

    I am running RRF 3.01-RC3
    When hooking up via USB I get something in the line of "no known network found" so I am assuming I have to go to RC4.
    SInce I can't update through DWC, which files do I need to put onto the memory card directly to do the upgrade ?

    Edit: I copied Duet2CombinedFirmware.bin over to the memory card but there was no change.

    Edit 2: serial port running M587 seems to report no networks found so maybe the upgrade to RC4 did not complete ?

    0
  • jens55

    @bearer , thanks for the instructions re connecting USB - worked great. Still not up and running but I am sure that's just the RC4 upgrade.
    Thanks again for all your help!

    0 droftarts 1 Reply
  • droftarts
    Moderator

    @jens55 it was fixed in 3.01 RC1, so it’s not that. Sounds like non-alphanumeric characters in SSID or password is the most likely issue, but have had a couple of problems with new router hardware. See this other thread: https://forum.duet3d.com/topic/14993/cannot-connect-duet-wifi-to-new-wifi-router/50

    Also, check how serial comms are set up https://forum.duet3d.com/topic/12649/m587-ssid-contains-character/2?_=1584716082602

    There was also a thread about Linux using non-standard codes for some characters, but I think it was the same thread as in the above paragraph.

    Finally, if the SSID is hidden, you need to specify it when enabling networking, eg M552 S1 S"ssid"

    Ian

    0
  • jens55

    While I normally like a challenge, this is getting hard on my forehead and the drywall from too much bashing my head against the wall.
    I still can't see the device in my 'connected devices' list on either network
    I have now changed the network to be visible.
    There is a tiny bit of good news, the serial connection now gives me:
    failed trying to connect to "-----" , wifi module is idle

    As I said, I have one non alphanumeric character in the password, a period ..... ?????

    Edit: the ssid it is trying to connect to is the correct ssid

    0 bearer 1 Reply
Log in to reply
 
Unless otherwise noted, all forum content is licensed under CC-BY-SA