Firmware 2.0RC6 and 1.21.1RC6 released

Donpi

Hi,
I think I found a little bug.
(However I'm not sure it'is caused by the new release.)

It start the load filament macro on Tool 0, and when i see that this was not the correct macro, I shuted down the Duet.
When powered up again. I can no more right click on Tool 0 to use the filament macro.

Tool 1 keep working right.

Bye.

SM3D

@dc42 - As I mentioned yesterday, I could not find my old files in DWC but all the files are present when I access the card via panel due. I am at work so I will clear the cache and reinstall the duet web control when I get back home today.

I think somebody mentioned in other thread about fan sliders. I also have the same problem - I am able to slide the fan control by holding the left mouse button but when I leave the button the slider bounces back to previous value. If I start clicking step by step in small increments 5% each time, it works.

Cheers,
Vasan

dc42

@zerspaner_gerd said in Firmware 2.0RC6 and 1.21.1RC6 released:

Unfortunately, I still have an unstable DWC connection.

It will show "pending" for a long time (about 2 seconds), then "failed" and from then on DWC will not be updated anymore.

The WiFi code hasn't changed between 1.21 and 2.0. As your WiFi signal strength is quite low, I suspect there may have been a change in your WiFi environment - in which case, reverting to firmware 1.21 will show the same problem (if the change in the environment is still present).

Are you able to reconnect DWC after the error? Have you increased the AJAX retry count in DWC from the default of 1?

boldnuts

Just ran a 10 hour print with 2.0RC6 with no issue's to report on my Duet Ethernet P3 Steel.

dc42

@sm3d said in Firmware 2.0RC6 and 1.21.1RC6 released:

@dc42 I updated my firmware just now to 2.0RC6 and it wiped many of my .gcode files. Moreover, I could upload .gcode files without any error but I could not find them in the interface. I also cannot create a folder. Any suggestions?

Cheers,
Vasan

The number of GCode files in a single folder that can be displayed by DWC is lower than before. This was required to fix other issues. So I suspect that the files are all there, just not being displayed. Likewise the new folder you created. The workaround is to move some files into subfolders. If you can't see any subfolders in DWC, you may have to move the SD card to a PC to do this. Alternatively, use the backup facility in DWC to backup the files that you can see, then delete them; then you should be able to see the other files.

I'll add this to the upgrade notes.

dc42

@donpi said in Firmware 2.0RC6 and 1.21.1RC6 released:

Hi,
I think I found a little bug.
(However I'm not sure it'is caused by the new release.)

It start the load filament macro on Tool 0, and when i see that this was not the correct macro, I shuted down the Duet.
When powered up again. I can no more right click on Tool 0 to use the filament macro.

Tool 1 keep working right.

Bye.

Does reloading DWC fix this?

Donpi

@dc42

Sorry but what is DWC ?

dc42

Duet Web Control.

resam

@dc42 regarding the number of gcode files per folder and moving them into subfolders:

I think there is no g-code to move or rename a file on the SD card.
M30 deletes a file - but thats about it...

DWC has rr_move and rr_mkdir and rr_delete.
Would be nice to add this to the Firmware wishlist.

Looking through https://reprap.org/wiki/G-code, it seems no other firmware supports this either...
All the "good" numbers around M20-M30 that do things with the SD card are already taken.

Donpi

@dc42 Haha ok

Totaly powering of the Duet does nothing.
But maybe i have a cache problem.
I'll try tonight.

wilriker

Just finished a 3:45h print successfully with no issues apart from warping - but that is clearly not a problem of the Duet.

zerspaner_gerd

@dc42 said in Firmware 2.0RC6 and 1.21.1RC6 released:

@zerspaner_gerd said in Firmware 2.0RC6 and 1.21.1RC6 released:

Unfortunately, I still have an unstable DWC connection.

It will show "pending" for a long time (about 2 seconds), then "failed" and from then on DWC will not be updated anymore.

Are you able to reconnect DWC after the error?

Yes, I can immediately press on Disconnect Connect.

Have you increased the AJAX retry count in DWC from the default of 1?

I have played with this attitude something (up to 2) without change.

I suspect there may have been a change in your WiFi environment - in which case, reverting to firmware 1.21 will show the same problem (if the change in the environment is still present).

It's enough if I downgrade to DWC 1.21

Current combination:

Firmware Version: 2.0 (RTOS) RC6 (2018-05-29b4)
WiFi server version: 1.21
Web Interface Version: 1.21

No noticeable delays. (over an hour) With 1.21.1 it was between 10 seconds and a maximum of 5 minutes.

The debug mode shows the same error, only the difference is, it just continues after the error.

0_1527717963254_DWC 1.21 Debug.png

So it seems to me that the cause of DWC is not RFF, right?

@donpi said in Firmware 2.0RC6 and 1.21.1RC6 released:

I can no more right click on Tool 0 to use the filament macro.

I can confirm that, that's exactly the case with me. I already wrote it at RC5.
https://forum.duet3d.com/topic/5394/new-firmware-2-0rc5-available/74

3dmntbighker

Installed rc6 in my coreXY and so far so good. I don't have many extra goodies yet to trip it up of course.

Danal

Installed on BFD (Big Fast Delta).

Firmware Name:	RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics:	Duet WiFi 1.02 or later
Firmware Version:	2.0(RTOS)RC6 (2018-05-29b4)
WiFi Server Version:	1.21
Web Interface Version:	1.21.1

Collected Data
Warm-Up Time	Current Layer Time	Last Layer Time		Print Duration
01m 36s		09s			58s			8h 44m 53s

Estimations
Based on	Filament Usage	File Progress	Layer Time
Time Left	16h 37m 49s	22h 27m 39s	24h 54m 39s

No issues.

SM3D

@dc42 you are right. I took the SD card and made subfolders to make sure there are less than 25 files in each folder. Now I see all the files in DWC.

I did a small 1 hour print and no issues so far.

Cheers,
Vasan

timcurtis67

Just ran a 8 hr print with no issues. Running IDEX ditto printing with both heads at the same time.

Works great so far.

SM3D

@dc42 I noticed one more issue. It happened twice after 2.0RC6 upgrade (past 2 days) - whenever I update the config.g file, DWC says it cannot be updated and loses connection. It shows under system editor only config.g.bak but no config.g files.

When I shut down the printer and restart again, it cannot connect or show my tools because config.g is not present. I have to take the SD card out and rename config.g.bak to config.g to make things work again. This never happened to me in previous upgrades.

Cheers,
Vasan

Donpi

Today I tried to print with two extruder and get a strange behaviour.

I'm printing the Kisslicer Wizzard box with extruder 1 to the raft and extruder 0 to the main object.

And when the printer change from tools 1 to tool 0, the Duet switches to full steps. The print becom impossible as everthing goes 256 x faster and is 256 x bigger.

That worked at lest once with firmware 1.21.

May that help

PS : I checked the gcode after M92, M350 and M569 but fond none of them.

resam

@sm3d said in Firmware 2.0RC6 and 1.21.1RC6 released:

It shows under system editor only config.g.bak but no config.g files.
When I shut down the printer and restart again, it cannot connect or show my tools because config.g is not present. I have to take the SD card out and rename config.g.bak to config.g to make things work again. This never happened to me in previous upgrades.

I had the same thing happen to my printer once, maybe 2-3 months ago. Don't remember which FW I had back then, maybe 1.20?
So, I don't think this is a new thing.

daveidmx

After reorganizing my /sys files into subfolders (to get down below the limit so they call appear in DWC) I noticed that subfolders of /sys don't appear on DWC either. Would that be a DWC feature request, or is there firmware-side support needed too?

Is there a different way I should be doing this to maintain DWC editability of all my config files? (I can move some of them to /macros, but it wouldn't make sense for them ever to show up on the UI to be called individually. Is that what's expected, though?)