Network connection problems

curieos

You're arguing the most obscure edge case type stuff I've ever seen. Who's deploying a printer in a tent? Why would someone be so concerned with cracking into a secure network to get at a 3d printer when theres all the other stuff thats probably at least 10X more interesting? What world are you living in where thats something someone would be interested in doing?

Also, why are you arguing against the duet having wifi? T3P3 has already expressed interest in making a wired duet, like a potentially drop in replacement for the ESP module. Theres already been 2 wired Duets, just be patient.

bot

Really sorry to have expressed an opinion.

I have 2 wifi's on the way, and a third in a close relative's machine as well… but I simply would have preferred to not have to rely on Wifi. What;s the big deal about that? Why am I all of a sudden an asshole for having concerns?

curieos

People addressed your concerns with pretty satisfactory answers (and sources), they offered solutions to your issues, and yet you continued to argue the same points, or you moved to increasingly more obscure scenarios. You went from expressing valid concerns to grasping for straws as to why wifi is the worst thing and its probably going to abduct your kids when you're not looking. Its starting to feel like US Bottle Rockets on the SeeMe forums again, just continuing on and on for no reason. You're not an asshole bot, I'm just tired of you beating the horse.

bot

My main concern is not nearly the security issue… it was not I who was beating the dead horse. The issue of wifi is not dead, it's a real issue. I make printers for professional use, and sometimes my clients want to buy the printers. I want to be able to offer them wired ethernet, end of story. If a client requires ethernet, they won't also enjoy the features of the duet wifi I guess, like the higher current rating on steppers. I merely entertained the discussion about security concerns because, to me, that sort of thing is interesting.

A Former User

Pronterface:

[[language]]
>>> M552 S1
SENDING:M552 S1
WiFi server starting up
DuetWiFiServer version 1.03 (ch fork)
Flash size 4194304, free RAM 32840 bytes, WiFi Vcc 3.04V, host name: duetwifi, reset reason: Turned on by main processor
WiFi server connected to access point XXXXXXX, IP=XXX.XXX.XXX.XXX, signal strength=-89dBm

Pinging works. However when I try to access the DWC I get the following crash:

[[language]]
DuetWiFiServer version 1.03 (ch fork)
Flash size 4194304, free RAM 32840 bytes, WiFi Vcc 3.03V, host name: duetwifi, reset reason: Exception
WiFi server connected to access point XXXXXXX, IP=XXX.XXX.XXX.XXX, signal strength=-89dBm

M122 didn't give much information. It could be the weak signal strength. I have no other choice…
+1 for DuetWifi AP mode.

It's a pity I still have severe wifi issues. IMHO that's the weakest part of the DuetWifi.
Thanks for any help!

dc42

Yes -89dbm is a very weak signal. One option is to install a WiFi repeater closer to the Duet than your router is. Depending on what router you have already, another option may be to get a better router, especially if your existing one doesn't have MIMO capability.

We recognise that for a minority of users, wired Ethernet is preferable to WiFi. I have spent much of today working on the firmware for the forthcoming Duet Ethernet.

lolorc

would it be possible to upgrade from wifi to ethernet ? like just replacing the esp module by an ethernet module ?

dc42

The prototype I am working with is a converted Duet WiFi. So If our plans work out as we hope, it should be possibe to convert a blue production Duet WiFi board to Ethernet. You would need a hot air desoldering too to remove the WiFi module.

A Former User

That's great news!
Would a access point mode work for the DuetWiFi if more people needed it?

I already tried some kind of repeater configuration by using an old router, which worked very well with other wifi devices. With the Duet WiFi I get the same behaviour I described above (only pinging works).

dc42

Yes we're planning to support running the Duet WiFi in access point mode.

A Former User

I took my plain DuetWifi board, a usb cable and a laptop to a brand new access point.
The signal strength is around -40dBm.
Same problem again.

Did you see my VCC reading? It's 3.04V. Could that be a problem? I saw other boards have around 3.3V.

dc42

If the Vcc really is only 3.03V then that could be a problem. However, that reading is taken by the ESP module itself, so it is only as accurate as the voltage reference in the module- which probably has a tolerance of 10% or so.

If the wifi server code keeps resetting with an exception, that suggests a bug in the server code, or possibly a hardware problem. But it's hard to diagnose a crash when we can't reproduce it, especially when we are dependent on 3rd-party code and not all the source is available.

lolorc

Flash size 4194304, free RAM 32808 bytes, WiFi Vcc 3.21V, host name: duetwifi, reset reason: Exception

I can easily reproduce this by connecting to the web interface from both my computer (chromium) and my phone(firefox) and trying to move head from the machine control tab.

A Former User

You are right with the 10% tolerance.
My DMM showed 3.29V between +3.3V and GND on the ESP8266 module.

I tried different server versions:
DuetWiFiServer version 1.02 shows VCC 3.30V
DuetWiFiServer version 1.03 (ch fork) shows VCC 3.04V

The micro sd card shouldn't influence the web server. I also tried without micro sd card. No change.

@dc42: What third-party code do you mean? I only found this for the server: https://github.com/dc42/RepRapFirmware/blob/dev/src/DuetNG/DuetWiFi/Webserver.cpp

@lolorc: What's your signal strength? Does it work for you with only one device connected?

lolorc

@lolorc: What's your signal strength? Does it work for you with only one device connected?

signal strength=-54dBm
It works for me with only one device.
I guess the crashes come from too much errors and retransmissions.
It would help to get real error messages instead of "exception", I'm looking at the source at the moment, I'm wondering how I could add debug statements in DWS (https://github.com/chrishamm/DuetWiFiServer) I'm not sure i can simply add Serial.println("DEBUG: BLAH"); I guess I need to have them parsed in RRF so they get displayed on the console.

about having duetwifi working as a AP, it can be easily implemented in here : https://github.com/chrishamm/DuetWiFiServer/blob/master/src/RepRapWiFi.cpp

Have you tried to use another AP ? an android phone used as a portable hotspot for instance. (as I mention in
https://www.duet3d.com/forum/thread.php?id=455 I had weird issues with a cisco aironet 1130 AP, was working perfectly with my android phone before, now I'm testing a 1140 AP)

lolorc

@lolorc:

[
It would help to get real error messages instead of "exception", I'm looking at the source at the moment, I'm wondering how I could add debug statements in DWS (https://github.com/chrishamm/DuetWiFiServer) I'm not sure i can simply add Serial.println("DEBUG: BLAH"); I guess I need to have them parsed in RRF so they get displayed on the console.

hmmm looks like I might just have to populate ESP_COMMS to receive the Serial.println from DWS

dc42

@lolorc:

@lolorc: What's your signal strength? Does it work for you with only one device connected?

It would help to get real error messages instead of "exception", I'm looking at the source at the moment, I'm wondering how I could add debug statements in DWS (https://github.com/chrishamm/DuetWiFiServer) I'm not sure i can simply add Serial.println("DEBUG: BLAH"); I guess I need to have them parsed in RRF so they get displayed on the console.

I agree, we need at least the program address that caused the exception to be able to debug this. Unfortunately, the core library for the ESP8266 is closed source. Even if the manufacturer wanted to open-source it, the FCC won't allow that.

I do have a major rework of the DuetWiFiServer code planned. I think it will be next after implementing babystepping in firmware 1.18 and finishing support for the Duet Ethernet (which is mostly working already).

lolorc

Can you confirm if I connect to URXD1/UTXD1 (ESP_COMMS) I will get the access to the ESP serial and be able to get messages from the Serial.println in DWS to debug it ?

dc42

@lolorc:

Can you confirm if I connect to URXD1/UTXD1 (ESP_COMMS) I will get the access to the ESP serial and be able to get messages from the Serial.println in DWS to debug it ?

Yes, that should work if you match the baud rates.

lolorc

@dc42:

@lolorc:

Can you confirm if I connect to URXD1/UTXD1 (ESP_COMMS) I will get the access to the ESP serial and be able to get messages from the Serial.println in DWS to debug it ?

Yes, that should work if you match the baud rates.

it does, thanks. (115200 as stated in DWS)