Duet WiFi Access Point setup problems

aidar

If it isnt typo, then change your IP address. 192.186.2.100 is known static IP of some server and shouldnt be used by anyone else. You probably want to use 192.168.2.100

AKLiving

@aidar said in Duet WiFi Access Point setup problems:

If it isnt typo, then change your IP address. 192.186.2.100 is known static IP of some server and shouldnt be used by anyone else. You probably want to use 192.168.2.100

I changed it to 192.168.2.100. This did not change the problem I'm having.

AKLiving

@dc42 said in Duet WiFi Access Point setup problems:

Try connecting a PC or laptop to the Duet via USB, running YAT or Pronterface. Send M111 S1 P14 to enable WiFi debugging. Then try sending the M552 S2 command (from USB or PanelDue, it doesn't matter). If it fails to start up as an access point, let us know what debug messages if any it sends to the PC.

Here are my current network settings after the changes recommended:
; Network
M550 P"TronxyX5SA" ; Set machine name
M552 S2 ; Enable as an access point

And the report from YAT when enabling WiFi debugging. I'm not sure what the M596 warning is about. I don't have that command in my config.g

RepRapFirmware for Duet 2 WiFi/Ethernet Version 2.02(RTOS) dated 2018-12-24b1<LF><LF>Executing config.g...Warning: M596 command is not supported<LF>Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 606C.<LF><LF>Done!<LF>RepRapFirmware for Duet 2 WiFi/Ethernet is up and running.
m511 s1 p14
M511 command is not supported<LF>ok<LF>
M111 S1 P14
Debugging enabled for modules: WiFi(14)<LF>Debugging disabled for modules: Platform(0) Network(1) Webserver(2) GCodes(3) Move(4) Heat(5) DDA(6) Roland(7) Scanner(8) PrintMonitor(9) Storage(10) PortControl(11) DuetExpansion(12) FilamentSensors(13) Display(15)<LF>ok<LF>
M552 S2
ok<LF>WiFi reported error: Failed to start access point<LF>WiFi module is idle<LF>
M552 S2
ok<LF>WiFi reported error: Failed to start access point<LF>WiFi module is idle<LF>
M552 S2
ok<LF>WiFi reported error: Failed to start access point<LF>WiFi module is idle<LF>
M552 S2
ok<LF>WiFi reported error: Failed to start access point<LF>WiFi module is idle<LF>
M552 S2
ok<LF>WiFi reported error: Failed to start access point<LF>WiFi module is idle<LF>
M552 S2
ok<LF>WiFi module is providing access point TronxyX5SA, IP address 192.168.2.100<LF>

dc42

OK, leave it with me - I'm having problems starting AP mode too.

AKLiving

@dc42 Thank you. Just let me know if you need me to try anything else. The Duet WiFi is so much superior and configurable to what I had I'll live with my current process of hitting my macro a few times for now. With the awesome Paneldue at least I don't have to connect USB to send commands.

dc42

@AKLiving, please try installing DuetWiFiServer.bin version 1.23beta1 from https://www.dropbox.com/s/gkb6rulcayiqjcm/DuetWiFiServer.bin?dl=0 and let me know whether it fixes the problem.

If you need to use YAT to get debug info, go to Settings->Text settings and set the line ending to <LF>. That will result in better formatting of the debug info.

AKLiving

@dc42
After 2 reboots it is now working. It allows me to have 2 devices connected at the same time too! (iPhone and laptop with win10) I’ll cycle it a few more times on Monday and let you know how it’s going.

dc42

Thanks, I'll wait to hear from you again.

AKLiving

@dc42 It has been working without a single failure to connect. Thank you very much.

dc42

Thanks for the feedback. I included this version of DuetWiFiServer with the RRF 2.03beta1 release. So anyone else having the same problem can pick it up from the 2.03beta1 release area.

supermarioprof

@dc42 said in Duet WiFi Access Point setup problems:

Thanks for the feedback. I included this version of DuetWiFiServer with the RRF 2.03beta1 release. So anyone else having the same problem can pick it up from the 2.03beta1 release area.

I'm having similar problems with AP mode:
on every reboot
I need to open Pronterface,
force M552 S0,
force M552 S2 a few times (normally 3),
than AP mode goes on and everything works.

I'm on latest stable, 2.02.
I also tried to add
M552 S0
G4 S5
M552 S2
in config.g, thinking it may be a question of time to wake up for AP mode. No joy.

So:

should I update to 2.03beta1 or 2.03beta2?
should I update DuetWifiServer.bin only, or Duet2CombinedFirmware.bin too?

My config.g and SETNETWORK macro attached
thanks!

0_1551155432746_config.g
0_1551155466497_SETNETWORK.txt

dc42

If you want to stay on firmware 2.02 then you can just upgrade DuetWiFiServer to version 1.23beta.

supermarioprof

@dc42 thanks!
I installed DuetWifiServer.bin AND Duet2CombinedFirmware.bin, 2.03beta1 (I installed before reading your answer!),
kept
M552 S0
G4 S5
M552 S2
and now access point mode works good!