Topics created by Via

I'm glad you got it working!

@Phaedrux said in Duet 3 standalone not starting:

How's this?

https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3?revisionid=HEAD#Section_Running_in_standalone_mode

Excellent, It's the simple small things like this that are make or break at times, this small addition will help others from enduring similar time consuming frustrations in the future.

@dc42 is there a way to properly "flush" the memory on thoses boards ?
I have been working on that issue for couples of weeks now on different setups and boards configuration and it seem to happen more and more often on most of them. I wonder if it could be caused by a bad sector or a bug and because of that spot it just happen more and more. (Sorry for my english here, Im french .. trying to explain clairly..)

Everytime I update/flash the firmware it seem to crash faster too.

At the moment Im down to testing different sd cards, maybe I got some fakes/cheaper cards causing the issue too.

Also important point: the setups I have who never been updated (some benchmarks and extruders tester) dont have that issue. Yet..

@dc42 Thanks for reply, sorry didn't pay attention to the times on there I just looked at last reset reason.

As a test I did a 6 hour print yesterday of a random thingiverse download (moon lamp) which I thought would be good as a torture test, this printed completely with no issues.

So going back to this part I checked and verified OK in Openscad and re-rendered and sliced again, exactly same settings as yesterdays test with same filament and temperatures. This has just failed again 1 hour into print (never fails at same point) this time M122 (below) shows last reset reason as watchdog (and time matches with failure this time).

I am at a total loss, the Raspberry Pi (4B) is powered seperately with a 3amp supply I have another one so will swap out with that tomorrow just to see if that makes any difference.

If I can provide any further diagnostics please let me know.

M122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.1.1 running on Duet 3 MB6HC v0.6 or 1.0 (SBC mode) Board ID: 08DJM-956L2-G43S4-6J9FA-3S86T-1B5LD Used output buffers: 1 of 40 (13 max) === RTOS === Static ram: 154604 Dynamic ram: 163060 of which 44 recycled Exception stack ram used: 360 Never used ram: 75148 Tasks: NETWORK(ready,1972) HEAT(blocked,1188) CanReceiv(suspended,3820) CanSender(suspended,1488) CanClock(blocked,1436) TMC(blocked,68) MAIN(running,4512) IDLE(ready,76) Owned mutexes: === Platform === Last reset 00:11:26 ago, cause: watchdog Last software reset at 2020-06-06 13:56, reason: User, spinning module LinuxInterface, available RAM 75132 bytes (slot 3) Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task MAIN Error status: 0 MCU temperature: min 30.4, current 30.6, max 32.8 Supply voltage: min 13.0, current 13.1, max 13.1, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.0, current 12.0, max 12.1, under voltage events: 0 Driver 0: standstill, reads 22931, writes 0 timeouts 0, SG min/max not available Driver 1: standstill, reads 22932, writes 0 timeouts 0, SG min/max not available Driver 2: standstill, reads 22929, writes 2 timeouts 0, SG min/max not available Driver 3: standstill, reads 22929, writes 2 timeouts 0, SG min/max not available Driver 4: standstill, reads 22931, writes 0 timeouts 0, SG min/max not available Driver 5: standstill, reads 22932, writes 0 timeouts 0, SG min/max not available Date/time: 2020-06-07 22:51:20 Slowest loop: 4.04ms; fastest: 0.21ms === Storage === Free file entries: 10 SD card 0 not detected, interface speed: 37.5MBytes/sec SD card longest read time 0.0ms, write time 0.0ms, max retries 0 === Move === Hiccups: 0(0), FreeDm: 375, MinFreeDm: 375, MaxWait: 0ms Bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves: 1, completed moves: 1, 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 === GCodes === Segments left: 0 Movement lock held by null HTTP* is ready with "M122" in state(s) 0 Telnet is idle in state(s) 0 File is idle in state(s) 0 USB is idle 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 Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 0.47ms; fastest: 0.01ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions HTTP sessions: 0 of 8 - Ethernet - State: disabled Error counts: 0 0 0 0 0 Socket states: 0 0 0 0 0 0 0 0 === CAN === Messages sent 2117, longest wait 0ms for type 0 === Linux interface === State: 0, failed transfers: 0 Last transfer: 19ms ago RX/TX seq numbers: 58505/22212 SPI underruns 0, overruns 0 Number of disconnects: 0 Buffer RX/TX: 0/0-0 === Duet Control Server === Duet Control Server v3.1.1 Code buffer space: 4096 Configured SPI speed: 8000000 Hz Full transfers per second: 32.26

@Flex3D said in Duet3 - firmware update with RPi:

t must be a usb 3 Hub with quick charge function

duet doesn't support usb3 nor quick charge, but depending on what is connected to the duet most usb ports should be able to power it (disconnect any displays if you think you have a power issue)

@Flex3D said in Duet3 - firmware update with RPi:

I just followed the instructions and gave it a Reset with a jumper on erase. Any else i could do?

if you didn't get a serial port before or after trying the reset jumper then there isn't much left to do.

@Flex3D said in Duet3 - firmware update with RPi:

Can't I run it from its own Micro SD with its firmware and remove the Pi?

not if the firmware erase was successful, then it will need flashing; if you had created your own topic I might not have suggested erasing the firmware based on the output of one of the earlier posts.
new problem, new topic, please.

@Via said in Blown driver:

50/50 if I will attempt to replace or just leave how is

If you have hot air and a 2nd printer whose hotbed you can use to preheat the board it shouldn't be too bad. The Z driver is a little extra tricky with less physical clearance around the chip, still possible to shield the surrounding parts but a vacuum pickup helps a lot to pick up the bust driver. On the other hand if you can re-purpose it as is then enjoy the Duet3:)