New firmware 1.20 Release Candidate 2 - please try it!

deckingman

Thanks Ian, it's clear that RRF is sending the wrong information. It's using the number of visible axes where it should be using the number of total axes. I'll fix it in RC4.

Oh. Does that mean it is co-incidental with my creating the additional U and V axes? I have to say that I don't usually take much notice of the extruder drive position, otherwise I would have spotted it sooner.

Apologies to Chris. Hope he didn't spend too much time chasing this "Red Herring".

Camalot977

What am i doing wrong ?
I installed the 1.20RC3 and webserver
but lost wifi signal ?

SENT: M115
READ: FIRMWARE_NAME: RepRapFirmware for Duet WiFi FIRMWARE_VERSION: 1.20RC3 ELECTRONICS: Duet WiFi 1.0 FIRMWARE_DATE: 2017-12-16

dc42

Which firmware version were you upgrading from?

dc42

@deckingman:

@dc42:

Thanks Ian, it's clear that RRF is sending the wrong information. It's using the number of visible axes where it should be using the number of total axes. I'll fix it in RC4.

Oh. Does that mean it is co-incidental with my creating the additional U and V axes? I have to say that I don't usually take much notice of the extruder drive position, otherwise I would have spotted it sooner.

Yes. If you send M584 P5 to make the additional axes visible, I think the extruder positions will magically correct themselves.

Gosu

@dc42:

@Gosu:

i updated from RC1 to RC2 then it stopped running with wifi and i used the new www file to fix the problem

now i can only control my printer via wifi for 5 minutes(with constant disconnects) and i was able to start a print
but the printer stopped beeing able to connect via webhost
only seldomly beeing able to connect

i would love to post my current version but it wont let me connect
its FW RC2
Wifi Beta10 i believe
and RC3 Webclient

Did you install DuetWiFiFirmware twice as recommended in the upgrade notes?

Yes i did and it works for a few seconds but i just connected wanted to set the temp then it disconnected and doesnt let me connect again

6:34:03 PMDisconnected.
6:32:41 PMConnection established!
6:32:40 PMPage Load complete!

I restarted the Duet and i was able to connect
then i disconnected while i was doing autocalibration

Again another restart!

this time i was quick !!!

6:46:57 PMEndstop adjustments X-0.26 Y0.61 Z-0.35, tilt X0.00% Y0.00%
Diagonal 291.060, delta radius 144.058, homed height 380.282, bed radius 200.0, X 0.829°, Y 0.399°, Z 0.000°

File 0:/gcodes/Step_1_-Single-Wall_Box.gcode selected for printing
6:46:56 PMM32 0:/gcodes/Step_1-_Single-Wall_Box.gcode
Calibrated 6 factors using 13 points, deviation before 0.248 after 0.105
6:45:41 PMConnection established!
6:45:41 PMPage Load complete!

The Print itself looks good but i cannot connect with the printer so i cannot see the status nor do anything with my printer except restarting or waiting for the print to finish..

after the restart it works for a certain ammount of time
i have restarted the device and reconnected
then i have set bed temperature 1 minute later it was dead and didnt respond to pings while still heating to temperature and beeing responsive with a cable and pronterface

the disconnects are making using the printer almost impossible

I reinstalled the Firmwares
I started by reuploading both bins on the SD connecting the Printer with Pronterface and then Installing the Firmware first then the Wifiserver

it worked for 5 minutes then the same problems appeared

deckingman

@dc42:

Yes. If you send M584 P5 to make the additional axes visible, I think the extruder positions will magically correct themselves.

Confirmed. Sending M584 P5 makes the 20.0mm value magically jump two places to the left from D2 to D0. With the U and V axes visible, any commanded extrusion amount increments the position for the correct drive, Thanks.

Camalot977

@dc42:

Which firmware version were you upgrading from?

1.1.9 something

strips

Flashing RC3 yesterday wifi seemed to work properly and worked a few seconds after power up now and then this:

[...]
Recv: Error retrieving WiFi status message
Recv: Error retrieving WiFi status message
Recv: Error retrieving WiFi status message
Recv: Error retrieving WiFi status message
Recv: Error retrieving WiFi status message
Recv: Error retrieving WiFi status message
Recv: Error retrieving WiFi status message
[...]

Wifi debug does not give me any more info. Web server is dead.

M999 resets and I get connected to wifi:

Recv: FIRMWARE_NAME: RepRapFirmware for Duet WiFi FIRMWARE_VERSION: 1.20RC3 ELECTRONICS: Duet WiFi 1.0 + DueX5 FIRMWARE_DATE: 2017-12-16
Recv: ok
Recv: Wifi module is connected to access point Tomato24, IP address 192.168.1.111

Then 15-20 seconds later without doing anything is crashes again with lots of "Recv: Error retrieving WiFi status message"

This is a new one for me.

dc42

@strips, please follow the instructions at https://www.duet3d.com/forum/thread.php?pid=32944#p32944.

strips

David, that is what I did.

Connected to DuetWifi by USB (octoprint in bigbox). The M111 S1 P14 really does not give my anything after it failed. I need to try again and enable before it fails to see if I get anything before.

strips

Funny… not changing anything today everything works

So I have to call this one off for the moment

dc42

Please try the new 1.20RC4 and DWS 1.20RC1 that I have just released.

BMMal

The Machine Properties tab is not reporting the motor currents in RC4 or RC3. Not sure about earlier versions. Could be a DWC thing too I suppose?

justine.haupt

@dc42:

…
1. Use M140 H0:2:3:4 to configure multiple bed heaters, instead of M140 P0 H0, M140 P1 H3 etc.
...
Thoughts?

That sounds very good to me.

T-Printer

Hi I still a lot of problems to Connect, to my DuetWifi board, is just go on and off.
I Have install the new 1.20RC4 and DWS 1.20RC1, but NO, the only drifrence from RC3 I can see, is it now only reconnect once, the it say WiFi reported error: Timed out while trying to connect to ….

This is from Pronterface, and running a M111 S1 P14
Connecting...
Printer is now online.
WiFi reported error: Lost connection, auto reconnecting

M111 S1 P14
SENDING:M111 S1 P14
Debugging enabled for modules: WiFi(14)
Debugging disabled for modules: Platform(0) Network(1) Webserver(2) GCodes(3) Move(4) Heat(5) DDA(6) Roland(7) Scanner(8) PrintMonitor(9) Storage(10) PortControl(11) DuetExpansion(12) FilamentSensors(13)
WiFi reported error: Timed out while trying to connect to Nordbygaard
WiFi: sleep enable,type: 2
WiFi: sl
WiFi: scandone
WiFi: usl
WiFi: state: 5 -> 0 (0)
WiFi: rm 0
WiFi: pm close 7
WiFi: del if0
WiFi: usl
WiFi: mode : null

Any ide, what this can be?

Dougal1957

Don't understand why you installed a release candidate rather than the full release one https://www.duet3d.com/forum/thread.php?id=3817

T-Printer

Just to try is, because the full release do the same on and off. Now I an´m back to the full release.
From Pronterface:
SENDING:M111 S1 P14
Debugging enabled for modules: WiFi(14)
Debugging disabled for modules: Platform(0) Network(1) Webserver(2) GCodes(3) Move(4) Heat(5) DDA(6) Roland(7) Scanner(8) PrintMonitor(9) Storage(10) PortControl(11) DuetExpansion(12) FilamentSensors(13)
WiFi: bcn_timout,ap_probe_send_start
WiFi reported error: Lost connection, auto reconnecting
WiFi: ap_probe_send over, rest wifi status to disassoc
WiFi: state: 5 -> 0 (1)
WiFi: rm 0
WiFi: pm close 7
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 6
WiFi: cnt
WiFi:
WiFi: connected with Nordbygaard, channel 7
WiFi: dhcp client start…
WiFi: pm open,type:2 0
WiFi reported error: Timed out while trying to connect to Nordbygaard
WiFi: sleep enable,type: 2
WiFi: sl
WiFi: scandone
WiFi: usl
WiFi: state: 5 -> 0 (0)
WiFi: rm 0
WiFi: pm close 7
WiFi: del if0
WiFi: usl
WiFi: mode : null

To connect aging, I have to power off / on.

strips

On RC4 now and so far so good! Running through levelling and calibration routines because of a rebuild.

o_lampe

Maybe a bit late to claim an issue with RC4 now that it is officially released.
I have some G1 or G0 moves in the end code of the slicer to park the effector at X0 Y0 Z160.
These moves get misinterpreted by DWC and it always shows layer count 799. Thereby the estimated print duration based on
layer time x #layers is totally wrong too.
I tried G0 and G1 moves, both with same result.
If DWC would check for moves which include an extrusion, it would detect the last relevant layer.

Sorry, if that has been posted earlier, I'm not a regular visitor here…

dc42

That's a well-known issue. The solution is put a comment starting with ;E or ; E at the end of the G0 or G1 command line that does that movement.