New experimental firmware 1.19beta11
-
Thanks, I'll see if I can reproduce that.
-
So after updating to this firmware, my board as become completely unresponsive over night. initially it worked, but the web server kept crashing, as of this morning, the board, can not connect via wifi, or pointerface. As well as after to trying to attempt the Fallback procedure #3 I cant get the board to connect to SAM-BA.
I already followed the directions to a T
-
Does the Bossa Port appear in Device Manager after you press Erase for one second, then release it and press Reset?
Windows has a habit of disabling USB ports, so if it doesn't appear, try a different USB port or reboot Windows.
HTH David
-
Got it seems like I needed a different cable.
-
I installed 1.19 beta 11….I have something weird happening when I do a home all.....the x axis goes by the end stop switch and the x axis stalls....this does not always happen.....when I do a home on just the x axis there seems to be no problem.....the home all script I use is just calling the homex.g homey.g and homez.g files...so this shouldn't be a problem...maybe a bit of a bug
-
Read the upgrade notes, in particular the bit about deployprobe.g and retractprobe.g files.
-
new issue is with the duet not being able to find the its own access point. Though the board communicates with with my PC, and even confirms connectivity. I have no way of accessing the web server. This all worked perfectly while running firmware 1.17e
Now even after reverting back too my old firmware the duet wont seem to want to connect to the web server. Every time i look into my list of available networks the DuetWifi network shows even after ive already went through the set up. And it will keep showing the DuetWfif network as open no matter how many times i connect it to my internet network.
-
I do use a deployable bed probe so I require the two files….it is a Cartesian printer so this should not be an issue.
-
every time i try to connect my duet too my network, instead of getting an Ip address i get this
READ: DuetWiFiServer version 1.03 (ch fork)
READ: Flash size 4194304, free RAM 30544 bytes, WiFi Vcc 3.16V, host name: duetwifi, reset reason: Turned on by main processor
READ: WiFi is running as an access point with name DuetWiFiI still then have an access point for the Duet available to connect too, even after performing the procedure over multiple times times
-
new issue is with the duet not being able to find the its own access point. Though the board communicates with with my PC, and even confirms connectivity. I have no way of accessing the web server. This all worked perfectly while running firmware 1.17e
Did you do a simultaneous upgrade of the main and the WiFi firmware as described at https://duet3d.com/wiki/DuetWiFiFirmware_1.19beta ?
-
I just setup my delta with a new DuetWifi I just purchased and it has been a struggle.
I kept having JSON errors and was unable to use the web server, consistently it would switch from being in AP mode and back to being associated with my AP depending on it's mood when I would restart.
So I upgraded to 1.19beta11 following the instructions in the document. I used M997 S0:1 to do the upgrade of both firmwares.
So now it crashes with JSON shortly after opening the web page.
"× Communication Error
An AJAX error has been reported, so the current session has been terminated.
Please check if your printer is still on and try to connect again.
Error reason: SyntaxError: Unexpected token a in JSON at position 65"
So I put it back to 1.18.1 and had the same issues. I erased the firmware and reloaded using the SAM-BA tool and I upgraded to the beta again and I still have the same problems.
This is disappointing.
Firmware Name: RepRapFirmware for Duet WiFi
Firmware Electronics: Duet WiFi 1.0
Firmware Version: 1.19beta11 (2017-07-25)
Web Interface Version: 1.17+2
Web Interface by Christian HammacherNo matter what I have done has not worked as of yet.
Please help I ordered your system because it looked to be the best integrated most complete…....
-
I'm sorry to hear of your troubles. I need to see the faulty JSON response to see why it isn't working. Please can you do one of the following:
1. In Chrome press control-shift-J to get the debugging console, then try to connect. It should pause on the exception. If you go to the network tab you should find the JSON message that it couldn't parse. Please post it.
2. Load Wireshark on your PC and get a WireShark trace of the connection attempt, then post the .pcap file from Wireshark to a file sharing site and post the link to it.
Also please make your config.g file available.
-
new issue is with the duet not being able to find the its own access point. Though the board communicates with with my PC, and even confirms connectivity. I have no way of accessing the web server. This all worked perfectly while running firmware 1.17e
Did you do a simultaneous upgrade of the main and the WiFi firmware as described at https://duet3d.com/wiki/DuetWiFiFirmware_1.19beta ?
Yeah in every instance I would do a simultaneous upgrade. The duet just fails to connect to its web server.
-
And also did you copy the DWC Files into /www on the SD Card?
-
…
Error reason: SyntaxError: Unexpected token a in JSON at position 65"...By chance I just received this exact message while testing beta 12 firmware. The condition under which it happens is that the XYZ position can't be computed because it is impossible. The way I provoked it was to use very low motor currents that didn't reliably trigger the endstop switches, so that the apparent length of the homing move made by one tower created a geometrically impossible position.
I'll fix this in beta 12. In the meantime, my suspicion is that you have a delta printer, and the M665 parameters you have specified are physically impossible - in which case the problem will go away if you correct them. Please share your config.g file.
-
And also did you copy the DWC Files into /www on the SD Card?
Yes sir re Bob. But not change in allowing me to connect to the server. I'm every instance. It shows a duetwifi network. I'll connect to the network. I'll turn off then on the duet wifi connection. And then it won't connect. I'll get a message saying the duet as connected to a network with the access point name duetwifi. But not my wifi network or ip adress.
-
Please confirm that you are running DuetWiFiFirmware 1.19beta11, DuetWiFiServer 1.19 beta 10, and DWC 1.17+2, and that you have programmed your access point details as described at https://duet3d.com/wiki/DuetWiFiFirmware_1.19beta. You can verify the SSID name by sending command M587. [Edit: or perhaps you are running firmware 1.18.2 now?]
I've heard a previous case of a router blacklisting the MAC address of the Duet WiFi. In that case, resetting the router cleared the problem.
-
fixed it thanks everyone!!!
-
Thanks I have it working reliably now.
It was the config not sure what was wrong I reran the web configurator and the problem went away.
…
Error reason: SyntaxError: Unexpected token a in JSON at position 65"...By chance I just received this exact message while testing beta 12 firmware. The condition under which it happens is that the XYZ position can't be computed because it is impossible. The way I provoked it was to use very low motor currents that didn't reliably trigger the endstop switches, so that the apparent length of the homing move made by one tower created a geometrically impossible position.
I'll fix this in beta 12. In the meantime, my suspicion is that you have a delta printer, and the M665 parameters you have specified are physically impossible - in which case the problem will go away if you correct them. Please share your config.g file.
-
I'm having some quirky and unnerving behavior in 1.19beta11 when I switch tools on my diamond hot end delta. Sometimes the printer will quietly switch and sometimes it makes alarming noises while it retracts and extracts back and forth very quickly. I'm not sure why it does one or the other. My tools definitions are as follows:
; Tool definitions
M92 E60.28:60.28:60.28 ; Set extruder steps per mm
M207 S3.75 F3000 ; set firmware retraction
M563 P0 D0:1:2 H1 ; Define tool 0
G10 P0 X0 Y0 ; Set tool 0 axis offsets
G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C
M568 P0 S1 ; Enable mixing for tool 0
M567 P0 E0.90:0.05:0.05 ; Set mixing ratios for tool 0 (90%,5%,5%)
M563 P1 D0:1:2 H1 ; Define tool 1
G10 P1 X0 Y0 ; Set tool 1 axis offsets
G10 P1 R0 S0 ; Set initial tool 1 active and standby temperatures to 0C
M568 P1 S1 ; Enable mixing for tool 1
M567 P1 E0.05:0.90:0.05 ; Set mixing ratios for tool 1 (5%,90%,5%)
M563 P2 D0:1:2 H1 ; Define tool 2
G10 P2 X0 Y0 ; Set tool 2 axis offsets
G10 P2 R0 S0 ; Set initial tool 2 active and standby temperatures to 0C
M568 P2 S1 ; Enable mixing for tool 2
M567 P2 E0.05:0.05:0.90 ; Set mixing ratios for tool 2 (5%,5%,90%)
M563 P3 D0:1:2 H1 ; Define tool 3
G10 P3 X0 Y0 ; Set tool 3 axis offsets
G10 P3 R0 S0 ; Set initial tool 3 active and standby temperatures to 0C
M568 P3 S1 ; Enable mixing for tool 3
M567 P3 E0.34:0.33:0.33 ; Set mixing ratios for tool 3 (34%,33%,33%)T3 ; select tool 3 (evenly mixed)
I also seem to be having more problems with filaments jamming when I extrude single colors as opposed to evenly mixed which is working without issue.
John
