Duet Wifi / DHCP / Windows = PITA 2 find after pwr cycle …



  • I dont leave my printer on when Im not using it … so it power cycles quite a bit for decent periods of time - which I imagine exceeds the printers DHCP lease settings? I havent yet been able to get into the guts of my cable company supplied router to set a reserved IP by MAC address ...

    I thought I had a nifty little system worked out where Id ping a few known IP's on the network via Command Promp C;> ping 192.168.blah....

    Then C:>arp -a and it would typically show me ALL dhcp IP's ... I see the kids and phones and my laptop etc - but NOT the printers IP - I have to keep pinging and hoping to eventually find it.

    This is wasteful efforts and surely there is a better way to locate the device on the DHCP network vs. launching YAT and the usb cable and issuing a M552 ...

    Would love some ideas on this ... Assume I cant get into the router atm ...



  • I can't imagine running a network without having control over the router.

    I don't know of any easy way to solve your problem through configuration.

    1. Get into your router. Even cable company router are usually accessible. You're probably not the first person to want to do so. Google will likely turn up what you need.
    2. Add your own access point that you can control so that the Duet has something to connect to. Reserve it an address, or get Bonjour working so that http://duet.local works.



  • I use Fing, an app on my phone to locate devices in my network. It always finds the Duet.


  • administrators



  • can you set an IP for the Duet that you know is clear on the router?



  • So I left the printer on over night after it completed a print at 2am… Was half asleep and forgot. Came home to run some prints Printer still on... but DWC cannot connect, Find My Duet android app Cannot locate ... recycle power to system several times ... and so the idiotic cycle of the Duet not connecting to the wifi router starts all over again ... this time, I dont have my laptop down here and the new dedicated pc tasked to the printing is out of the reach of the printer and the USB cables length ...

    I really dont understand wth is going on with this ...



  • @T3P3Tony:

    Try this:

    https://play.google.com/store/apps/details?id=com.chham.FindMyDuet

    this app finds nothing … why would the board shut off wifi / connectivity ?



  • This section - as came by default … is at the END of the config.g file ..

    ;---------------------------
    ; Network
    ;---------------------------
    M550 PZaribo 220 MK3 ; Set machine name
    M551 PPWD ; Set password
    M552 S1 ; Enable network
    M587 S"SSID" P"PWD" ; Configure access point. You can delete this line once connected
    M586 P0 S1 ; Enable HTTP
    M586 P1 S0 ; Disable FTP
    M586 P2 S0 ; Disable Telnet



  • well it appears name with a space are problematic … should have know better from ages of fussing with networks and stuff - but it kinda should be spelled out - its been a while and folks can be rusty ...


  • administrators

    If you want to use a name with a space in it, you will probably need to enclose the name in double quotes:

    M550 P"Zaribo 220 MK3" ; Set machine name



  • @dc42:

    If you want to use a name with a space in it, you will probably need to enclose the name in double quotes:

    M550 P"Zaribo 220 MK3" ; Set machine name

    Well I have modified the machine name to contain NO spaces … however I still am having absurd challenges connecting this board to the wifi. I have a laptop and an Intel NUC - both of which have absolutely NEVER had a problem connecting to the wifi here. They are sitting within 5 feet of the printer.

    Sadly laptp is getting new OS installed and its closest to the printer and the damn usb cable for YAT sessions ... Nuc is too far away.

    I really need this issue resolved for good. I thought the machine name was the fix as it temporarily seemed to do the trick ... I thought perhaps 1.21RC3 was maybe part of it too. Left the machine to print overnite and when I got to it this morning, no mas wifi. I cant keep rebooting the Cable Modem trying to get the printer to connect on the 2.4Ghz channel [ as a way to rule out that issue ] Ive got 5 other people on the network and cable shows being recorded via coax etc … Im typing this on the NUC connected to the 2.4gh channel - so i know its working. The wifi radio and code on my Duet wifi IS NOT.

    Could I buy a Pi and use it as the access point ? So for printing the Duet never connects to the broadband wifi / lan router that the ret of the home uses and I can use this NUC and DWC thru the Pi to manage the printer?



  • use the I Parameter at the end of your M587 to lock in a free IP on your network such as

    M587 S"SSID" P"PWD" I192.168.0.14 ; Configure access point. You can delete this line once connected

    Doing this means it will always appear on the same IP just make sure the one you use is available and if the Router is set to give the full range of address to dhcp you may want to pick one that is high in the range.


  • administrators

    Also I suggest you upgrade at least DuetWiFiServer.bin to 1.21RC4 or 1.21RC5. These versions use a new SDK from the manufacturer of the WiFi chip, which seems to have resolved some issues. The previous revision, that we had to adopt to get the fix for the KRACK vulnerability, seems to have compatibility issues with some brands of wifi access point.



  • @Dougal1957:

    use the I Parameter at the end of your M587 to lock in a free IP on your network such as

    M587 S"SSID" P"PWD" I192.168.0.14 ; Configure access point. You can delete this line once connected

    Doing this means it will always appear on the same IP just make sure the one you use is available and if the Router is set to give the full range of address to dhcp you may want to pick one that is high in the range.

    TY sir … I shall give this a try as well ... i thought Id have to login to router and reserve the IP to be able to use this parameter ...



  • @dc42:

    Also I suggest you upgrade at least DuetWiFiServer.bin to 1.21RC4 or 1.21RC5. These versions use a new SDK from the manufacturer of the WiFi chip, which seems to have resolved some issues. The previous revision, that we had to adopt to get the fix for the KRACK vulnerability, seems to have compatibility issues with some brands of wifi access point.

    OK… TY for this update.

    As a small related sidebar note: The wifi chip and board are currently visible whilst in operation. I can see the BLUE led next to the wifi chip illuminated in solid/non blinking format - when the wifi is working and connected to my router. [ which btw it is now - after all have gone to bed for the eve and dvr is done and a reboot of modem router ] When I see it blinking or not illuminated - I know its not connecting. Sorry if this sounds obvious, but is that the ONLY thing that LED is telling me ? Someone else commented the other day that - that LED is not actually an indicator for this.

    TY



  • It sounds like you have a very congested network. When you said DVR, do you mean to say you have a television service that uses the same ethernetwork as your data transmissions? I've noticed that if my laptop is streaming a youtube video near my printer I can lose connection to the DWC.

    Have you considered switching the Duet to access point mode and connecting to it directly rather than having it connect to the network? This might not help if the wireless bands are being saturated though. If that's the case maybe try some channel hopping.

    I've used a program similar to this one in the past to map out wireless deadzones and pick a channel that isn't heavily used by my neighbours.

    https://www.netspotapp.com/wifi-network-monitor.html


  • administrators

    @SputnikOC3d:

    As a small related sidebar note: The wifi chip and board are currently visible whilst in operation. I can see the BLUE led next to the wifi chip illuminated in solid/non blinking format - when the wifi is working and connected to my router. [ which btw it is now - after all have gone to bed for the eve and dvr is done and a reboot of modem router ] When I see it blinking or not illuminated - I know its not connecting. Sorry if this sounds obvious, but is that the ONLY thing that LED is telling me ? Someone else commented the other day that - that LED is not actually an indicator for this.

    In recent versions of the WiFi firmware, the blue LED blinks slowly when trying to connect, and goes solid blue when connected.

    Have you worked through https://duet3d.dozuki.com/Wiki/WiFi_disconnections_and_AJAX_timeout_errors, in particuar checked what signal strength the Duet registers?

    There is a known issue if TCP/IP connections from the Duet get terminated abnormally too many times, however a fix is in progress.



  • With cox cable - they bring in video movies / cable tv and broadband [ 300 MB ] in on a single coax cable and feed it into a cable / modem that splits the broadband internet and cable tv signals. The MODEM is also an ethernet and wifi router specific to the service. If i need to reboot the wifi "router" - it is also rebooting the cable modem. Cable modem feeds to the cable box [ via coax ] and dvr recorder / cable tv manager. So the point is - if the fam is watching shows, has some recording, and or gaming - if I shut down the wifi router - Im shutting down the dvr in the background / the currently watched shows AND any ethernet or wifi internet connectivity.

    The real issue here is … My NUC / My Dell Laptop / 3 Apple laptops / 5 iphones / one Note5 android phone and assundry of wifi connecting devices can all at most ALL times seamlessly connect and function on this wifi router ... THE ONLY device that has connectivity issues is my Duet.

    i will research more info on Access Point mode - is that what it is called ? what would I search the doczuki for ? who knew this even existed? LOL



  • @dc42:

    @SputnikOC3d:

    As a small related sidebar note: The wifi chip and board are currently visible whilst in operation. I can see the BLUE led next to the wifi chip illuminated in solid/non blinking format - when the wifi is working and connected to my router. [ which btw it is now - after all have gone to bed for the eve and dvr is done and a reboot of modem router ] When I see it blinking or not illuminated - I know its not connecting. Sorry if this sounds obvious, but is that the ONLY thing that LED is telling me ? Someone else commented the other day that - that LED is not actually an indicator for this.

    In recent versions of the WiFi firmware, the blue LED blinks slowly when trying to connect, and goes solid blue when connected.

    Have you worked through https://duet3d.dozuki.com/Wiki/WiFi_disconnections_and_AJAX_timeout_errors, in particuar checked what signal strength the Duet registers?

    There is a known issue if TCP/IP connections from the Duet get terminated abnormally too many times, however a fix is in progress.

    Thank you for your reply …

    Yes I did go thru several of the pertinent items on that page [ or a similar page ] i cannot recall exactly now there's been soooo many items Ive worked thru. Yes - the signal db strength was @ -72 .. well im nt sure of the number then +/- 72 but it was 72 … which I thought ahhh ha - thats it - but yet another user on Duet FB group indicates his is worse and that is lenty good to work ... AND yet .... My NUC and Laptop sit here - as the crow flies - within a few feet of the printer ... nary a wifi connectivity issue.

    • WiFi -
      Network state is running
      WiFi module is connected to access point
      Failed messages: pending 0, notready 0, noresp 0
      WiFi firmware version 1.21RC3(28b1)
      WiFi MAC address 2c:3a:e8:0b:00:c2
      WiFi Vcc 3.40, reset reason Turned on by main processor
      WiFi flash size 4194304, free heap 16376
      WiFi IP address 192.168.0.10
      WiFi signal strength -71dBm, reconnections 0, sleep mode modem
      Socket states: 2 0 0 0 0 0 0 0
      === Expansion ===

  • administrators

    If/when you lose wifi connectivity, if it is an issue with the Duet then rebooting the Duet or sending M552 S-1 followed by M552 S1 (from USB or PanelDue) will resolve it. If instead you need to reboot your router, then the fault lies with your router.


 

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