Firmware update woes. Duet3

Demi

Oh, whoops. I may have jumped the gun. I ran with Bearers instructions, followed with an update/upgrade. Now returning:

pi@duet3:~ $ sudo apt list duetcontrolserver -a
Listing... Done
duetcontrolserver/unstable,now 1.3.2 armhf [installed,automatic]
duetcontrolserver/unstable 1.3.1 armhf
duetcontrolserver/unstable 1.3.0 armhf
duetcontrolserver/unstable 1.2.5.0 armhf
duetcontrolserver/unstable 1.2.4.0 armhf
duetcontrolserver/unstable 1.2.3.1 armhf
duetcontrolserver/unstable 1.2.3.0 armhf
duetcontrolserver/unstable 1.2.2.1 armhf
duetcontrolserver/unstable 1.2.2.0 armhf
duetcontrolserver/unstable 1.2.1.0 armhf
duetcontrolserver/unstable 1.2.0.0 armhf
duetcontrolserver/unstable 1.1.0.5 armhf
duetcontrolserver/unstable 1.1.0.4 armhf
duetcontrolserver/unstable 1.1.0.3 armhf
duetcontrolserver/unstable 1.1.0.2 armhf
duetcontrolserver/unstable 1.1.0.1 armhf
duetcontrolserver/unstable 1.1.0.0 armhf
duetcontrolserver/unstable 1.0.4.1 armhf
duetcontrolserver/unstable 1.0.4.0 armhf
duetcontrolserver/unstable 1.0.3.5 armhf
duetcontrolserver/unstable 1.0.3.3 armhf
duetcontrolserver/unstable 1.0.3.2 armhf

Restarting.

Danal

Our instructions looked different but did the same things. Your status looks GOOD

A Former User

@Danal said in Firmware update woes. Duet3:

but did the same things

almost; but chrishammn never confirmed or denied if stable and unstable list should co-exist after not too long ago asking someone to remove the stable list.

Danal

Once everything is back up, just for fun, try this from the Pi ssh session

echo "m115" | sudo /opt/dsf/bin/CodeConsole

Mine returns:

FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.01-RC7 ELECTRONICS: Duet 3 MB6HC v0.6 or 1.0 FIRMWARE
_DATE: 2020-04-14b3

and the fact that it returns anything indicates the Pi and the Duet are connected.

Danal

@bearer said in Firmware update woes. Duet3:

@Danal said in Firmware update woes. Duet3:

but did the same things

almost; but chrishammn never confirmed or denied if stable and unstable list should co-exist after not too long ago asking someone to remove the stable list.

Ah, very interesting. Should we update the documentation in the "getting started"?

A Former User

@Danal said in Firmware update woes. Duet3:

Should we update the documentation in the "getting started"?

i re-read it after his comment, and i guess it could be interpreted as either or, and the rest of us missed that. (but i suspect english is not the native language for me nor the author of the text so ymmw). however adding the key in both scenarios would indicate one or the other. if the text were to be changed replacing all the key stuff with wget -qO - https://pkg.duet3d.com/duet3d.gpg | sudo apt-key add - would probably be worth while as well.

clarifying if it is an issue and making the instructions clearer would probably be a good thing in any case.

Danal

@bearer said in Firmware update woes. Duet3:

but i suspect english is not the native language for me nor the author of the text so ymmw)

I joke, and I repeat JOKE, that I am not a native English speaker.

I was born in a small town in TX, and the grain of truth behind that joke is that I really did take some tutoring at a point long after college, in my mid-career, so that I could speak accent-less, grammatically correct, English when I need to in business situations. It did seem to unlock some advancement that was lagging a bit.

But what REALLY cured my TX accent, and made me sound neutral american, was living in the Greater London Area (New Barnet) for about a year.

Demi

It works!!! Good LORD. Im sure glad you were all here to help me, I would have never gotten there but I still have the ethernet issue.

So, I pull the card out of the Pi. Put it in the Duet3, plug in the ethernet. It doesnt join the network. I plug in USB and connect via Pronterface.

Connecting...
Printer is now online.
>>>M122
SENDING:M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.01-RC7 running on Duet 3 MB6HC v0.6 or 1.0
Board ID: 08DJM-956L2-G43S4-6J9DD-3SJ6M-TB6AG
Used output buffers: 4 of 40 (4 max)
=== RTOS ===
Static ram: 154580
Dynamic ram: 161588 of which 24 recycled
Exception stack ram used: 308
Never used ram: 76716
Tasks: NETWORK(ready,2084) HEAT(blocked,1196) CanReceiv(suspended,3824) CanSender(suspended,1484) CanClock(blocked,1432) TMC(blocked,216) MAIN(running,4540) IDLE(ready,80)
Owned mutexes:
=== Platform ===
Last reset 00:05:00 ago, cause: power up
Last software reset at 2020-04-16 10:52, reason: User, spinning module GCodes, available RAM 76640 bytes (slot 0)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x04432000 BFAR 0x00000000 SP 0xffffffff Task 0x4e49414d
Error status: 0
[ERROR] Error status: 0

Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 33.9, current 42.7, max 42.7
Supply voltage: min 24.2, current 24.3, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.2, max 12.3, under voltage events: 0
Driver 0: standstill, reads 24921, writes 14 timeouts 0, SG min/max 0/0
Driver 1: standstill, reads 24922, writes 14 timeouts 0, SG min/max 0/0
Driver 2: standstill, reads 24923, writes 14 timeouts 0, SG min/max 0/0
Driver 3: standstill, reads 24923, writes 14 timeouts 0, SG min/max 0/0
Driver 4: standstill, reads 24927, writes 11 timeouts 0, SG min/max 0/0
Driver 5: standstill, reads 24927, writes 11 timeouts 0, SG min/max 0/0
Date/time: 1970-01-01 00:00:00
Slowest loop: 1.95ms; fastest: 0.15ms
=== Move ===
Hiccups: 0(0), FreeDm: 375, MinFreeDm: 375, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== Heat ===
Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is ready with "M122" in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 1.95ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 0 of 8
- Ethernet -
State: disabled
Error counts: 0 0 0 0 0
[ERROR] Error counts: 0 0 0 0 0

Socket states: 0 0 0 0 0 0 0 0
=== CAN ===
Messages sent 1201, longest wait 0ms for type 0
=== Linux interface ===
State: 0, failed transfers: 0
Last transfer: 93602ms ago
RX/TX seq numbers: 0/1
SPI underruns 0, overruns 0
Number of disconnects: 0
Buffer RX/TX: 0/0-0

Ethernet disconnected seems like the key entry here.
Send:

M552 S1

And BAM, everything works! If I restart I have to reconnected and do it all over again to get ethernet (stand alone) working. I tried putting the M552 S1 in config.g but it doesnt enable ethernet.

Danal

If you run with the card in the Duet, you will need the ether plugged into the duet, and the enable command.

I'd actually run with the card in the Pi, and the ethernet physically plugged into the Pi. That should just "come up and work". Default is DHCP, there are tons of Pi tutorials around on how to make it static, if you wish. EDIT: Also, if you want unique hostnames for the printers, change it on the Pi. Again, lots of Pi examples out there.

And/or, you could forgo the ether completely, and run WiFi on the Pi. This is a Pi only option (the board does not have wifi). In your environment, I'm sort of thinking you will stick to ether.

Danal

And CONGRATULATIONS and WOO HOO!!

By the way, you should never have to bossa or change feeds or anything again. From this point forward, it really is the two 'apt' commands.

Demi

@Danal said in Firmware update woes. Duet3:

If you run with the card in the Duet, you will need the ether plugged into the duet, and the enable command.

Yep thats exactly what I have setup. Card in the Duet, Duet hooked to ethernet, M552 S1 as the first line in config.g. Does not reconnect after restart. I think I might be leading us down an "XY problem here".

The whole reason for all of this is that M401 and any probe related macros dont work when I am connected through the pi. If I run the macros with M98, they work fine. If i run the commands that are in deployprobe.g, it works like a champ. IF on the other hand, I am in stand alone mode, then the M401 and G30 codes all work correctly. They just dont through the pi. Now thats not a big deal, if I can run in standalone mode, but as of now I cant, because it defaults to disabling the ethernet, and adding it to config.g doesnt seem to do anything.

Guys, I really am sorry this is such a pain, and I cant thank you enough for all the help.

Demi

WAIT I think I understand what you are trying so desperately to get through my thick head. Just enable ethernet through SSH like you would with any other pi. Standby as I try to be less mentally compromised and give that a go.

Danal

@Demi said in Firmware update woes. Duet3:

@Danal said in Firmware update woes. Duet3:

If you run with the card in the Duet, you will need the ether plugged into the duet, and the enable command.

Yep thats exactly what I have setup. Card in the Duet, Duet hooked to ethernet, M552 S1 as the first line in config.g. Does not reconnect after restart. I think I might be leading us down an "XY problem here".

The whole reason for all of this is that M401 and any probe related macros dont work when I am connected through the pi. If I run the macros with M98, they work fine. If i run the commands that are in deployprobe.g, it works like a champ. IF on the other hand, I am in stand alone mode, then the M401 and G30 codes all work correctly. They just dont through the pi. Now thats not a big deal, if I can run in standalone mode, but as of now I cant, because it defaults to disabling the ethernet, and adding it to config.g doesnt seem to do anything.

Guys, I really am sorry this is such a pain, and I cant thank you enough for all the help.

I think you will find that all cleaned up on this release. I run all that stuff on a D3+Pi toolchanger that is passing 10,000 toolchanges at the moment (I track for wear) each of which has to do what you are describing several times.

With one caveat: Check your macros after you switch back to the Pi... even though it is the same physical SD, stand-alone and Pi have separate places they store /sys, /macros, /gcode, etc, etc.

Demi

Good lord. Okay so just to try to get up and running in stand alone, I am flashing a new SD with the Duetpi-lite.zip from:
https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_DuetPi

Putting it right in the board and seeing if I can run stand alone with ethernet.

A Former User

@Demi said in Firmware update woes. Duet3:

Good lord. Okay so just to try to get up and running in stand alone, I am flashing a new SD with the Duetpi-lite.zip from:
https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_DuetPi
Putting it right in the board and seeing if I can run stand alone with ethernet.

That image is still primarily for using the Duet3 with the Pi. To use wihtout the Pi you can use the same card but have to make sure to put config and duetwebcontrol files on the first FAT32 partition* (or simpler reformat the card so there is but one fat32 partition and put the files on there)

*) when the pi is running this is /boot

Demi

HOLY HELL! It works! I think I now know what I was doing wrong. With a fresh card, it connected straight away. As soon as I loaded my old config it wouldnt connect.....because I have the brain rot, and the old config wasnt for stand alone. YEESH. Everything works now. You guys are absolutely amazing, thank you so so much.

A Former User

@Demi said in Firmware update woes. Duet3:

the old config wasnt for stand alone

there isn't much difference afaik.

heck if you add M552 S1 and put config.g in /boot/sys/config.g and symlink it to /opt/dsf/sd/sys/config.g it should (could?) work in both the pi and the Duet3 with no furhter changes but maybe not poke the bear if its working
(and you'd need to put all the other files and dwc into /boot/www etc)

monster

May I kindly ask, in the end do we have a instructions how to do it for dummies?
I kinda got to update mine duet 3 and reading this post is scary

A Former User

@monster said in Firmware update woes. Duet3:

May I kindly ask, in the end do we have a instructions how to do it for dummies?
I kinda got to update mine duet 3 and reading this post is scary

Duet 3 or Duet 3 + Raspberry Pi? (Also probably better to make a new thread to keep it easier to follow the information later)

Danal

There are a lot of horror stories when things get out of sync. These will go away as the procedure matures and people get more used to the procedure.

But... no fear!

The real procedure is:

sudo apt update
sudo apt upgrade

With the one and only caveat that if you have multiple boards, you will need to M997 B1, B2, etc.

Other than that caveat, those two commands are really it. They will take care of everything for you.

Perhaps it is fair to say, that ONE TIME, you need to etch an SD image onto a card, and ONE TIME you need to choose whether to be on the 'stable' feed or the 'unstable' feed.

But, again, beyond those one time installation activities, it REALLY IS, those two commands.