Duet 2 Wifi IoT module is disappointing
-
@TLAS It's surrounded by aluminium extrusion (It's a Core XY machine with the board mounted at the back) and the printer is sitting on top of a metal box, but it isn't fully enclosed. I guess the environment / background noise might also have its part to play.
-
@Joel said in Duet 2 Wifi IoT module is disappointing:
I replaced the module with an ESP-07S which has an external antenna connection. No issues since doing that.
Did you need to do any firmware update or just a hardware swap and the duet takes care of the rest?
Also, what gcode upload speed to you get from the duet web UI?
-
@zapta said in Duet 2 Wifi IoT module is disappointing:
Did you need to do any firmware update
need to flash the new module, but this is done like any other wifi firmware update (except it can't be done from DWC, you'll need serial console, PanelDue or a prepared trigger)
-
Just wanted to add that I have seven Duet 2 Wifi's in operation at the moment on printers that run almost 24/7 and have never had connectivity issues. All worked fine even when I was using the crappy router from my ISP and they all work fine with the Ubiquity set up I have now.
-
@Dz I have 4 duet2wifi 1.0.4 boards and never had any issues with wifi..I have them running over a year now...and no issues at all! Nevertheless to say that maybe one board is not performing 100% out of 1000 boards doesn't mean that the duet boards are not ok...
-
I made tonn of devices with integrated ESP8266 module and I can say
- most of the ones with external antenna don't have connectivity issues
- ~10% of "closed" modules have some type of hardware issues, in some of the cases it can be solved by baking the module, but mostly they are throwables
- firmware is unsecure, as already mentioned
- biggest issue is dev tools / SDK, if you build in your own app into the module it can come into many "undesired" states due to bugs in firmware and sdk. Happened more than once that valid app just never get control back from the wifi blob due to bug there
None of these issues I have seen, should affect duet2wifi, except maybe the antenna part, but I went myself with ethernet version 'cause I'd never run a "serious machine" with esp8266. I, for example, have 2 teartime printers with esp8266 and they don't work most of the time. IMHO ESP8266 is ok for sensors and stuff that you don't care too much if stop working, but not as main connectivity option for a device you want to use. ESP32 so far looks much better but my experience is limited (made under 20 devices so far and while they never had any issues it's still early to say).
@Dz what I dont get is after "has 20+ years in enterprise systems and datacenters" you went with wifi option for printer??? irrelevant what module was used
-
@arhi said in Duet 2 Wifi IoT module is disappointing:
teartime
not sure if typo or pure gold, but i like it.
(edit: incidentally try sending continuous ping packets to the printers and see if they become more stable, worked a treat on mine, may have to be the same host) -
@bearer That'll be all those UP printers making people cry, then... https://www.tiertime.com/
Ian
TronXY X5S with Duet 3 MB6HC and Roto toolboard : Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : Polargraph with Duet 2 WiFi
-
@droftarts oh, I have one, with a part-time Duet2Maestro; going full time as soon as I have the slicer dialed in:)
-
@bearer not a typo, but I have to say you are the first one to notice in years
@droftarts oh yes
TT printers are mechanically very decent (I do have three different ones) and that extruder, while weirdly simple, works wonder for high temp materials. TT ABS is printed at 270C and other high temp filaments also work very good; especially if you do my simple mod for the extruder
( thing:2509563 ). This is not a PLA printer, but why would you want to print PLA on such small bed anyhow.Anyhow that guy "tinyfab" made those nice CPU board replacements so you can run smoothieware on them. I don't use WiFi on them at all since I changed cpu and I'm using smoothieware+octoprint combination and they work awesome
Original slicer for TT printers was actually very good, in front of all open source slicers at the time and also way better than kislicer, simplify3d and other commercial ones. Unfortunately they lost the source of that one and recreated "studio" from scratch. Studio is not very good, but do make these printers bit more versatile allow for variable temperature and few other options.
But we went too much off topic. They do use ESP8266 (the variant with small wire antenna) and there's a lot of users complaining about them not working correctly. Good thing is that you don't need connection for the printer to run, their slicer sends the precompiled file to the printer and printer just executes the stepper commands set in that file so the only thing connection is used is for monitoring.
-
@arhi Yes. I have a smarthome with many dozens of connected wifi devices, including cameras, motions sensors, temp sensors, windows sensors, vibration sensors, etc. I am not a "wired Ethernet or nothing guy",
for enterprise systems, yes, No wifi of any kind on datacenter or enterprise systems except to provide wifi connectivity for employees. For home items, wireless is mature enough to be relied upon for most items. I run zigbee and z-wave devices on my smart things hub, and use Alexa routines to automatically tune light on/off, light colors, dimming, etc based on movement, time of day, weather and ambient light. My system also senses if people are home based on their phone present or not and performs routines accordingly, or arms cameras and sensors to keep home secure and alert on certain conditions.As for the Duet, I have solved my issues by enabling FTP and using Filezilla to upload gcodes. If the ESP module has to re-handshake during the upload, Filezilla resumes the transfer elegantly, instead of the web control simply ending the transfer and sending a fail message. This my gcode upload times from ~15-30m to ~1-2 minutes.
So for anyone experiencing wifi upload issues in the web interface, just use FTP instead and then start the cgode file in the web interface. Problem is solved.
-
@Dz I'd call that "technology enthusiast"
nice that you solved the issue with FTP
-
@Dz said in Duet 2 Wifi IoT module is disappointing:
This my gcode upload times from ~15-30m to ~1-2 minutes.
Does this fast upload go through the disappointing esp8266?
