Firmware 1.20 released
-
Hi…
For curiosity... Examples of printers of more 3 axis?
ThanksThe ones I can remember:
IDEX printers (dual X carriages) - 4 axes (RRF treats the second X carriage as an additional axis)
Kulitorum's concrete printer - 4 axes (the 4th axis rotates the concrete extruder)
Ian (deckingman's) printer with dual CoreXY gantries - 5 axes
Various printers that split the (N) Z motors during homing, so they can be homed separately - 2 + (N) axes (one temporary axis per additional Z motor)
Someone's (sorry, I can't remember who it was) printer with dual X, dual Y and dual Z axes - 6 axes -
Chrishamm has now released DWC 1.20, so I've updated the release to include it instead of DWC 1.20 RC3.
-
So thankful for this release! Wait for thermostatic fans on power off, adjustable PWM frequency, and so much more!
Thanks!
-
I am pleased to announce the release of firmware version 1.20 at https://github.com/dc42/RepRapFirmware/releases.
…...................- Fixed the sending of motor currents to DWC
Confirmed fixed. Thanks.
-
Just wanted to say that I updated with no problems very straight forward and reconnected to my network upstairs with noproblems
and then reconnected to a different network downstairs and also here no problems. connects right away to the router every time for now. -
Just wanted to say that I updated with no problems very straight forward and reconnected to my network upstairs with noproblems
and then reconnected to a different network downstairs and also here no problems. connects right away to the router every time for now.Thanks for your feedback!
-
I've been running for a few hours now with no significant problems. Only thing I can complain about is that since 1.20 went to RC, my WiFi issues are more prevalent again. A while back I was wondering if I was running too high of a step frequency due to the Step Errors and causing some kind of under-run. Never really figured anything out about that though or if it is at all related.
[[language]] === Diagnostics === Used output buffers: 3 of 32 (15 max) === Platform === RepRapFirmware for Duet WiFi version 1.20 running on Duet WiFi 1.0 + DueX5 Board ID: 08D6M-91AST-L23S4-7JTD8-3S86K-1PX1K Static ram used: 15448 Dynamic ram used: 99992 Recycled dynamic ram: 3344 Stack ram used: 1392 current, 8440 maximum Never used ram: 3848 Last reset 03:59:41 ago, cause: software Last software reset at 2017-12-26 13:20, reason: User, spinning module GCodes, available RAM 3848 bytes (slot 0) Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0441f000, BFAR 0xe000ed38, SP 0xffffffff Error status: 2 Free file entries: 8 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest block write time: 404.0ms MCU temperature: min 26.3, current 27.7, max 28.4 Supply voltage: min 24.2, current 24.5, max 25.0, under voltage events: 0, over voltage events: 0 Driver 0: ok, SG min/max 0/787 Driver 1: ok, SG min/max 0/1023 Driver 2: standstill, SG min/max 0/1023 Driver 3: standstill, SG min/max 0/585 Driver 4: standstill, SG min/max not available Driver 5: ok, SG min/max 0/1023 Driver 6: standstill, SG min/max 0/543 Driver 7: standstill, SG min/max not available Driver 8: standstill, SG min/max not available Driver 9: standstill, SG min/max not available Expansion motor(s) stall indication: yes Date/time: 2017-12-26 17:24:08 Cache data hit count 4294967295 Slowest main loop (seconds): 0.407292; fastest: 0.000045 === Move === MaxReps: 5, StepErrors: 12803, FreeDm: 164, MinFreeDm 150, MaxWait: 4260061081ms, Underruns: 0, 1 Scheduled moves: 216447, completed moves: 216420 Bed compensation in use: none Bed probe heights: 0.000 0.000 0.000 0.000 0.000 === Heat === Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 Heater 0 is on, I-accum = 0.0 Heater 3 is on, I-accum = 0.0 === GCodes === Segments left: 1 Stack records: 3 allocated, 0 in use Movement lock held by null http is idle in state(s) 0 telnet is idle in state(s) 0 file is doing "G1 X252.578 Y56.169 E0.0484" in state(s) 0 serial is idle in state(s) 0 aux is idle in state(s) 0 daemon is idle in state(s) 0 queue is idle in state(s) 0 autopause is idle in state(s) 0 Code queue is empty. Network state is running WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 0 WiFi firmware version 1.20 WiFi MAC address a0:20:a6:16:e6:c6 WiFi Vcc 3.26, reset reason Turned on by main processor WiFi flash size 4194304, free heap 16752 WiFi IP address 10.0.0.115 WiFi signal strength -31dBm, reconnections 0, sleep mode modem HTTP sessions: 1 of 8 Socket states: 2 0 0 0 0 0 0 0 Responder states: HTTP(1) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) -
Have done a few prints now with 1.20 on a DuetEthernet/delta : No issues so far.
-
I've been running for a few hours now with no significant problems. Only thing I can complain about is that since 1.20 went to RC, my WiFi issues are more prevalent again. A while back I was wondering if I was running too high of a step frequency due to the Step Errors and causing some kind of under-run. Never really figured anything out about that though or if it is at all related.
Your MaxReps figure is low so there isn't a problem with the step rate. But I would like to investigate why you have so many step errors. Can you provide the Gcode file and your config.g file?
-
I've been running for a few hours now with no significant problems. Only thing I can complain about is that since 1.20 went to RC, my WiFi issues are more prevalent again. A while back I was wondering if I was running too high of a step frequency due to the Step Errors and causing some kind of under-run. Never really figured anything out about that though or if it is at all related.
Your MaxReps figure is low so there isn't a problem with the step rate. But I would like to investigate why you have so many step errors. Can you provide the Gcode file and your config.g file?
You can get the files from here: https://www.dropbox.com/sh/4er7llhg7vifkfu/AADv9KP6UQct_5WiclzfOFOia?dl=0
-
Haven't upgraded my firmware yet (want to finish current project before I change anything on the printer) I was looking changes I need to make to my config…
would it make more sense to start logging as custom g-code in slic3r, rather than in the config.g?
For start gcode:M929 S0 ; stop any existing logs that might be running M929 P"[input_filename_base].log" S1 ;Start logging ```and at the endM929 S0 ; Stop logging
-
Thanks! I have reproduced the step errors, both on the bench and in the simulator. I have located the reason for the vast majority of the step errors, and fixed it. The step errors are benign and should not affect print quality. I am still getting a small number of step errors reported with a different cause, and I will investigate those today.
I already found another bug that needs to be fixed in 1.20 (also present in 1.19) concerning filament sensor support, so I am planning a 1.20.1 release, which will also have the fixes for the step error reports.
-
OK then, I just today fired up my Duet Wifi on my CoreXY after many months of idle. Was mounted for a short time on m old i3 clone just for kicks. anyway, it's still running 1.8. what do I have to do to update? just get all those files? upload to SD card and then run the update like is in the Docs for 1.9? Honestly I tried the 1.9 update back then and it failed miserably. had to re set to 1.8.
Do want to update as right now the wifi won't connect every time I reboot or just fire it up for the day. I have to go and kick my computer's Wifi over the the Duet. do the 192.1.1…. then the window pops up asking for the wifi info.. select network and type in password and reboot and then it'll work,... till I have to reboot again and I'll have to go through the whole process once more. Ugg. anyway, it's late and I'm off to bed.. hoping tomorrow to be a bit better a day for it
-
One way is to upload the new DuetWiFiFirmware.bin and DuetWiFiServer.bin files WITHOUT installing them (or copy them to the SD card on a PC). Also comment out the M552 S1 command in config.g. Then connect via USB and send M997 S0 to update the main firmware. You can watch the progress on PanelDue if you have one. After a minute you should be able to reconnect via USB, then send M997 S1 to update the WiFi firmware. Then follow the "getting connected" instructions for firmware 1.19 and later on the wiki.
-
I upgraded from 1.19 to 1.20. Now my BL Touch does not work correctly. It self tests fine, but when I home z, the probe does deploy, but now my printer tries to drive the nozzle through the heat bed. It does not stop.
If I down grade to 1.19 on the firmware, do I need to downgrade the wifi server also?
-
One way is to upload the new DuetWiFiFirmware.bin and DuetWiFiServer.bin files WITHOUT installing them (or copy them to the SD card on a PC). Also comment out the M552 S1 command in config.g. Then connect via USB and send M997 S0 to update the main firmware. You can watch the progress on PanelDue if you have one. After a minute you should be able to reconnect via USB, then send M997 S1 to update the WiFi firmware. Then follow the "getting connected" instructions for firmware 1.19 and later on the wiki.
did exactly that.. Uploaded and told it not to install. Turned off the wifi, disconnected everything and brought over to computer -
plugged into USB, connect with Printrun(pronto face) type in M997 S0,.. keep getting errors.. Remove SD card and plug in direct to computer.. Can't drag and drop the file won't let me. ?? now what? -
I seriously think my WiFi module is bad. this thing has been nothing but issues, drops connection. won't reconnect 1/2 the time with out a complete power down and restart and then I always had to go in and reconfigure the network info. Every single time. did everything you stated above ad it won't work. Now I can't even get the wifi to turn back on under 1.8.
-
M552 S1
SENDING:M552 S1
WiFi module started
Error: Failed to initialise WiFi module, code -10
[ERROR] Error: Failed to initialise WiFi module, code -10or,…
M552 S0
SENDING:M552 S0
WiFi module started
Error: Failed to initialise WiFi module, code -10
[ERROR] Error: Failed to initialise WiFi module, code -10 -
That error usually means that the main firmware and wifi firmware are out of step, i.e. one is pre-1.19 and the other is 1.19 or later. So use M115 to check that your main firmware is version 1.20; then use your PC to put a fresh copy of DuetWiFiServer.bin from the 1.20 release area of github into /sys on the SD card; put it in the Duet, start the Duet, connect via USB, and send M997 S1 to install it. If/when it reports success, try M552 S1 again.
-
seems to be working.
thanks… so far anyway!! AWESOme!Connecting...
Printer is now online.m115
SENDING:M115
FIRMWARE_NAME: RepRapFirmware for Duet WiFi FIRMWARE_VERSION: 1.20 ELECTRONICS: Duet WiFi 1.0 FIRMWARE_DATE: 2017-12-23
Disconnected.
Connecting...
Printer is now online.
M997 S1
SENDING:M997 S1
Trying to connect at 230400 baud:
success
Erasing 4096 bytes...
Erasing 233472 bytes...
Uploading file...
5% complete
10% complete
15% complete
20% complete
25% complete
30% complete
35% complete
40% complete
45% complete
50% complete
55% complete
60% complete
65% complete
70% complete
75% complete
80% complete
85% complete
90% complete
95% complete
Upload successful
M552 S1
SENDING:M552 S1
WiFi module started
Wifi module is connected to access point ####, IP address #######
