Posts made by lodger

@phaedrux No not really . I think it was just a lose joint / bad crimp. I did not get any driver errors nothing .

So after a bit of hair pulling . I thought to myself ....It only resets when it starts to extrude.
So i powered the printer off and unpluged the exturders cable.

And she started happy printing in mid air. I quick dug out a spare stepper cable poorly tie rap it place and plug her in..Yes she is printer happy as can be.

So i did not know a crappy stepper cable can reset the duet.

@fcwilt Sorry i was thinking about the small button on the board itself. i have not wired or connected anything external

@phaedrux It looks fine . when i press it it clicks as it should. and pops out again as it should.
I dont think its the button itself..

@fcwilt I have not wired a reset in .

My printer keeps resetting and i am trying to narrow the issuse down.
My M122 says reset button has caurse it. This happens in both standalone and SBC,

Yesterday i did update to b3 firmware but have since dropped back to 3.3 stable. Before i updated the printer was fine. and i did not try to print last night , It was late and bed time !

It resets as soon as i start printing . So i have tried a old Gcode which printed fine before but same again.

Anyone got anyideas.

	M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.3 (2021-06-15 21:46:11) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: 9Y0D5-4396U-D65J0-40KM2-LF03Z-ZRMYB
Used output buffers: 3 of 40 (20 max)
=== RTOS ===
Static ram: 102724
Dynamic ram: 106152 of which 36 recycled
Never used RAM 34792, free system stack 198 words
Tasks: NETWORK(ready,11.6%,226) HEAT(notifyWait,0.0%,358) Move(notifyWait,0.1%,362) CanReceiv(notifyWait,0.0%,941) CanSender(notifyWait,0.0%,371) CanClock(delaying,0.0%,340) TMC(notifyWait,1.1%,115) MAIN(running,84.8%,412) IDLE(ready,1.6%,29) AIN(delaying,0.8%,273), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:00:14 ago, cause: reset button
Last software reset at 2021-08-25 19:52, reason: User, GCodes spinning, available RAM 34792, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU revision 3, ADC conversions started 14341, completed 14340, timed out 0, errs 0
Step timer max interval 751
MCU temperature: min 40.1, current 41.2, max 41.2
Supply voltage: min 23.9, current 24.0, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 22, reads 1273, writes 9, timeouts 0, DMA errors 0
Driver 1: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 21, reads 1272, writes 9, timeouts 0, DMA errors 0
Driver 2: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 21, reads 1272, writes 9, timeouts 0, DMA errors 0
Driver 3: position 0, standstill, SG min/max 2/2, read errors 0, write errors 1, ifcnt 21, reads 1272, writes 9, timeouts 0, DMA errors 0
Driver 4: position 0, standstill, SG min/max 2/2, read errors 0, write errors 1, ifcnt 22, reads 1272, writes 9, timeouts 0, DMA errors 0
Driver 5: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 21, reads 1272, writes 9, timeouts 0, DMA errors 0
Driver 6: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 19, reads 1272, writes 9, timeouts 0, DMA errors 0
Date/time: 2021-08-25 20:22:37
Cache data hit count 27239000
Slowest loop: 5.09ms; fastest: 0.12ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 0.5ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1, chamberHeaters = -1 -1
=== 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 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.
=== CAN ===
Messages queued 128, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 17 (min 17), ts 72/0/0
Tx timeouts 0,0,71,0,0,55 last cancelled message type 30 dest 127

=== Network ===
Slowest loop: 15.87ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
- WiFi -
Network state is active
WiFi module is connected to access point 
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.26
WiFi MAC address f4:cf:a2:70:32:3b
WiFi Vcc 3.40, reset reason Power up
WiFi flash size 2097152, free heap 25624
WiFi IP address 10.174.1.101
WiFi signal strength -60dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

@phaedrux Second that.

@dc42 Did MicroChip get back to you. Or is this all you and the teams hard work.....Just to say thank you really ..

Paul

@dc42 mine did today when i was messing about.

@lodger Seams i wrote this in a bit of a hurry and does not make much sences.....SORRY

Ok i have one of these :
https://wiki.fysetc.com/Generic_12864_Panel/

Its states its pin Compatable with the MINI 12864.

I can not seams to figure out how to get the backlight working.
This is not a RGB like the Mini and i have the Mini working fine so my config is correct for that.

I am only playing and its not inportant for me to get running . Just a bit of fun. Any Ideas

Paul

I have been playing witha ST7567 based display on my Mini5.

I have set M918 too....

M918 P2 E4 F2000000 in my config.g.

The display is working but is very dull. How can i turn the brightness up ??

Not contrast !

Is it set by the voltage 3.3v not 5v ???

This is not a RGB display !

Thanks Paul

Forget all that... Its the back light not working......

What did you set in your config.g. IE did you set your colours ?

M918 P2 E4 F2000000 ; configure direct-connect display
M150 X2 R255 U255 B255 S3 ; set all 3 LEDs to white

Afternoon,

Sorry to say i have had undervolt again. This time network fully locked up. and i had to plug in a keyboard and monitor to get the M122 off . So sorry about the txt file

M122.txt

Web page ,SSH and remote desktop fully stopped.

@droftarts When DC42 ask on Saturday I also printed the same file without issue .

I have been printing around the clock up till Tuesday. Again without issue. There is just no patten.

I have one of the first batch of boards, and on a earlier firmware (dont ask what one).
I am sure i had this happen in standalone mode. So since Tuesday i have been printing non stop trying to prove this.

I have to say though i am getting bloody sick of all these massive 3dbenchy boats lying around my living room. lol

@ukwebb Have you tried the beta DC24 posted above.

I was only thinking yesterday if its posible to get the PD interface running on a touchscreen. ie make it HTML based and point the screen to that not DWC.
Way above my skill level but a idea.

@dc42 Mornings.

The print completed . with no under voltage triggers at all. I will try print something else and report if i get any more problems

@dc42 Hi,

Yes it was a print. I will just put the kettle on and update and print. It was a 10 hour print so i may not get back to you till tomo.

Edit:: I have updated and run a Similator of the same file. Without problems !
Just running the print now .

I have come down this morning to find a stalled print. Here is my M122,

m122

=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.2.2 running on Duet 3 Mini5plus WiFi (SBC mode)
Board ID: XJDX9-1296U-D65J0-40KMJ-4K03Z-7J6X6
Used output buffers: 1 of 40 (18 max)
=== RTOS ===
Static ram: 98732
Dynamic ram: 95844 of which 64 recycled
Never used RAM 50576, free system stack 122 words
Tasks: Linux(ready,99) HEAT(blocked,297) CanReceiv(blocked,947) CanSender(blocked,358) CanClock(blocked,362) TMC(blocked,75) MAIN(running,476) IDLE(ready,20) AIN(blocked,264)
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 17:19:34 ago, cause: software
Last software reset at 2021-03-19 15:58, reason: User, none spinning, available RAM 50808, slot 1
Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0400f000 BFAR 0xe000ed38 SP 0x00000000 Task Linu Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
Supply voltage: min 0.0, current 24.2, max 24.3, under voltage events: 2, over voltage events: 0, power good: yes
Driver 0: position 16355, standstill, SG min/max 0/428, read errors 0, write errors 1, ifcnt 223, reads 13005, writes 43, timeouts 17110, DMA errors 0, failedOp 0x71
Driver 1: position 2458, standstill, SG min/max 0/410, read errors 0, write errors 1, ifcnt 223, reads 30107, writes 43, timeouts 7, DMA errors 0, failedOp 0x6f
Driver 2: position 63048, standstill, SG min/max 0/44, read errors 0, write errors 1, ifcnt 189, reads 29631, writes 32, timeouts 494, DMA errors 0, failedOp 0x71
Driver 3: position 0, standstill, SG min/max 0/30, read errors 0, write errors 1, ifcnt 188, reads 29889, writes 32, timeouts 235, DMA errors 0, failedOp 0x01
Driver 4: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 155, reads 30130, writes 27, timeouts 0, DMA errors 0
Driver 5: position 0, assumed not present
Driver 6: position 0, assumed not present
Date/time: 2021-03-20 09:18:05
Cache data hit count 4294967295
Slowest loop: 178.10ms; fastest: 0.08ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 0.0MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 11368610ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 190766, completed moves 190766, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1, chamberHeaters = 2 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is doing "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.
=== CAN ===
Messages queued 561364, send timeouts 561361, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 15
=== SBC interface ===
State: 4, failed transfers: 0
Last transfer: 3ms ago
RX/TX seq numbers: 42328/42328
SPI underruns 0, overruns 0
Number of disconnects: 0, IAP RAM available 0x10eec
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.2.2
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 36.40
Maximum length of RX/TX data transfers: 5108/1664.

Is it worth running some heaters duing a simulation. To give the PSU some load.
During a print my VIN can jump up and down a few points of a volt. But during a sim . She is bang on 24.2v and dont move.