Posts made by lelynch

@oozeBot Thanks for the suggestion. That's a nice little adapter but would not have helped in this case. I will have to remember it for the future though. I have my problems solved now. It was all a matter of space available on that side of the board. The issue was that the side of the housing that the RJ11 is on only had about 5mm of space to the side of another housing next to it. I wasn't able to make the mainboard housing any smaller but was able to redesign and print the the second housing so it left more room available.

@Herve_Smith I considered it, but wasn't looking to void the warranty since it is fairly new still. It turned out that is wasn't as bad as it seemed and I was able to reprint the housings to add some extra room around the RJ11 connector area.

@dc42 Thank you, but that's beyond my current knowledge level and would likely take me longer to learn than just changing and printing new housings to open up this area to the RJ11 port. It would've been helpful to have had something in the documentation that stated that it was for future expansion and that it could not be used for the main CAN bus.

@jay_s_uk Thank you for the information. Guess I have some work ahead of me.

I recently purchased a 1LC Toolboard and wanted to connect using the smaller CAN 0 connector on the 6HC v1.02 due to the limited space around the mainboard. I finally found in another post that this was not used for the main CAN bus. What is it used for then? There is no documentation for it that I can find. I'm going to have to do a major re-engineering of my housing to use the RJ-11 connector if I can't use it.

I purchased a PT100 daughterboard from a reseller just over a week ago and had issues when installing it today on a Mini 5+. I already have one on my 6HC board so I set it up the same way. Attached a known good PT100 sensor and got nothing. Tried the second connection and got nothing there either. After verifying I had not made any connection or configuration errors, I removed it from the Mini 5+ and figured I'd try it with the 6HC board since it already has one working in it. I attached the PT100 sensor from the Mini 5A+ to the daughterboard in the 6HC and that worked. I swapped out the working daughterboard in the 6HC with the new one and again got nothing on either channel. I put the original back in the 6HC and no problems. Has to be a bad daughterboard and can get a warranty exchange, correct?

@Phaedrux I received the replacement board Thursday and installed it yesterday. After a couple prints of about 3 to 4 hours each, it's working well. The prints have come out better looking than before also and I've made no changes to the configuration. Thank you for your help!

@phaedrux Email was sent with all information and online form has been filled out and a copy received. Thanks again for the help.

@phaedrux Thank you. I can deal with a week without having to put something else together to get by.

@phaedrux Thank you. I'll get all that going when I get home from work tonight. How long do you think this process will take before I have the replacement in hand? I've been printing some things for my wife's business and I'm behind now.

@dc42 @T3P3Tony I hope you are the ones to tag. I'm really needing someone that works for Duet3D to help with this issue and determine if I need a warranty replacement or something else. The website said this forum was where to go. I've been down for a week now trying to resolve this after no issues at all for the last 3 months since install. I've posted the results of M122, my config.g file and my override file. So far I've had a few suggestions to check what seems like basic stuff but no real help. Anything I've done has not helped and just results in the same error of MemoryProtectionFault. Thank you.

@fcwilt I am a very technical person but I have had less than a year experience in total with 3D printing so thanks for your suggestions. I am learning a lot as I go. I did try running the M98 P"config.g" this evening when I saw your question and it did not come back with any errors. My config-override.g has very little in it but I've posted it below. I have been running along fine with no issues since February when I got the MB6HC board. I swapped out my cheap thermistor for an E3D PT100 and a temp sensor daughterboard on 6/5/2021 and tuned the heater. Was still running fine until about 5 days ago when this stopping mid-print started happening.

; config-override.g file generated in response to M500 at 2021-06-05 09:15
; This is a system-generated file - do not edit
; Heater model parameters
M307 H0 R0.417 C218.158:218.158 D1.57 S1.00 V23.6 B0
M307 H1 R2.924 C127.890:127.890 D5.25 S1.00 V23.7 B0
; Workplace coordinates
G10 L2 P1 X0.00 Y0.00 Z0.00
G10 L2 P2 X0.00 Y0.00 Z0.00
G10 L2 P3 X0.00 Y0.00 Z0.00
G10 L2 P4 X0.00 Y0.00 Z0.00
G10 L2 P5 X0.00 Y0.00 Z0.00
G10 L2 P6 X0.00 Y0.00 Z0.00
G10 L2 P7 X0.00 Y0.00 Z0.00
G10 L2 P8 X0.00 Y0.00 Z0.00
G10 L2 P9 X0.00 Y0.00 Z0.00
M486 S-1

@phaedrux No, I have never had a USB cable connected except at initial install.

@chrishamm I went back and ran the same file on simulate and that ran without an issue.

@chrishamm On the way home tonight, I bought a brand new micro SDHC card and replaced that to rule it out. Then I upgraded to v3.3.0 as requested. Started a print and it stopped again in mid-print as if it was sent a reset just like before. M122 shows "Last software reset at 2021-06-16 20:58, reason: MemoryProtectionFault mmarValid daccViol". Latest M122 full print attached. No other changes were made besides the firmware upgrade and the micro SD card change.

M122.txt

@chrishamm Thank you. I'll give that a try and report my results.

If it helps, this originally was an Ender 3 printer but it's been heavily upgraded. The last of which was the Duet3 6HC mainboard and then adding the daughter card to change to a PT100 temp sensor on the hotend. The sensor change was a couple weeks ago.

Not sure where to post this based on the category names. I have a DUET 3 6HC that I bought from Matter Hackers in March of this year. I have been running along fine since then as a standalone setup. Now in the last couple days it has started stopping mid-print as if it was reset. So far I have removed the SD card, copied my files, formatted it and then put them back. Still stopping. Tonight I had it upload the firmware files hoping it may re-flash them. Still stopping. The latest from M122 is below and shows "MemoryProtectionFault iaccViol". This is 3 times I have ran M122 after it has stopped although it has stopped more before I learned about M122. Twice has shown the Memory Protection Fault and once it said "HardFault undefInstr". Do I have a hardware problem and it needs replaced or something else? I'd appreciate any help to get it working again.

6/15/2021, 8:00:07 PM M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.2.2 running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-956L2-G43S8-6J1F6-3S46R-KU2YD
Used output buffers: 1 of 40 (11 max)
=== RTOS ===
Static ram: 149788
Dynamic ram: 93648 of which 44 recycled
Never used RAM 115352, free system stack 192 words
Tasks: NETWORK(ready,201) ETHERNET(blocked,110) HEAT(blocked,300) CanReceiv(blocked,927) CanSender(blocked,371) CanClock(blocked,358) TMC(blocked,51) MAIN(running,1119) IDLE(ready,19)
Owned mutexes:
=== Platform ===
Last reset 00:00:28 ago, cause: software
Last software reset at 2021-06-15 19:59, reason: MemoryProtectionFault iaccViol, none spinning, available RAM 115352, slot 1
Software reset code 0x4172 HFSR 0x00000000 CFSR 0x00000001 ICSR 0x00400004 BFAR 0x00000000 SP 0x2045ff70 Task MAIN Freestk 67434 ok
Stack: 20419a84 2041e16c 2041fe28 2041e168 20419a20 0046afc9 2041e168 8001000e 2041a9b8 204276c0 ecf52af9 2045c238 2042d96c 204276c0 0000ed0e 00424dc3 2042d97c 00000000 2041a9b8 00000000 00000000 00427fcf 00000008 2042a45c 2043a380 0046afc9 2041a35c
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
MCU temperature: min 38.8, current 39.4, max 39.5
Supply voltage: min 23.8, current 23.8, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.1, max 12.1, under voltage events: 0
Driver 0: position 0, standstill, reads 31481, writes 14 timeouts 0, SG min/max 0/0
Driver 1: position 0, standstill, reads 31481, writes 14 timeouts 0, SG min/max 0/0
Driver 2: position 0, standstill, reads 31481, writes 14 timeouts 0, SG min/max 0/0
Driver 3: position 0, standstill, reads 31482, writes 14 timeouts 0, SG min/max 0/0
Driver 4: position 0, standstill, reads 31482, writes 14 timeouts 0, SG min/max 0/0
Driver 5: position 0, standstill, reads 31485, writes 11 timeouts 0, SG min/max 0/0
Date/time: 2021-06-15 20:00:03
Slowest loop: 2.21ms; fastest: 0.06ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 0.6ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, 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 -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 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.
=== Network ===
Slowest loop: 1.98ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(1) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 1 of 8

• Ethernet -
  State: active
  Error counts: 0 0 1 0 0
  Socket states: 3 5 2 2 2 0 0 0
  === Filament sensors ===
  Extruder 0: pos 8.37, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0
  === CAN ===
  Messages queued 114, send timeouts 256, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 48

Config.g file contents

; Configuration file for Duet 3 (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Sat Mar 27 2021 11:01:02 GMT-0500 (Central Daylight Time)

; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Ender 3" ; set printer name

; Network
M552 P0.0.0.0 S1 ; enable network and acquire dynamic address via DHCP
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet

; Drives
M569 P0.0 S1 ; physical drive 0.0 goes forwards
M569 P0.1 S1 ; physical drive 0.1 goes forwards
M569 P0.2 S0 ; physical drive 0.2 goes backwards
M569 P0.3 S0 ; physical drive 0.3 goes backwards
M569 P0.4 S1 ; physical drive 0.4 goes forwards
M584 X0.0 Y0.1 Z0.2:0.3 E0.4 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E415.00 ; set steps per mm
M566 X1200.00 Y1200.00 Z24.00 E1200.00 ; set maximum instantaneous speed changes (mm/min)
M203 X9000.00 Y9000.00 Z600.00 E6000.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z100.00 E5000.00 ; set accelerations (mm/s^2)
M906 X1275 Y1275 Z1275 E500 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 S0 X-113.5:117.5 Y-117.5:116.5 Z250 ; set axis limits

; Endstops
M574 X1 S1 P"io4.in" ; configure active-high endstop for low end on X via pin io4.in
M574 Y1 S1 P"io5.in" ; configure active-high endstop for low end on Y via pin io5.in
M574 Z1 S2 ; configure Z-probe endstop for low end on Z

; Z-Probe
M950 S0 C"io7.out" ; create servo pin 0 for BLTouch
M558 P9 C"^io7.in" H5 F300 T9000 ; set Z probe type to bltouch and the dive height + speeds
G31 P25 X-26 Y0 Z1.872 ; set Z probe trigger value, offset and trigger height
M557 X-85:84 Y-78:92 S40 ; define mesh grid

; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B3950 A"Bed" ; configure sensor 0 as thermistor on pin temp1
M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0
M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S100 ; set temperature limit for heater 0 to 100C
M308 S1 P"spi.cs0" Y"rtd-max31865" A"Hotend" ; configure sensor 1 as thermistor on pin temp0
M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S300 ; set temperature limit for heater 1 to 300C

; Fans
M950 F0 C"out7" Q500 ; create fan 0 on pin out7 and set its frequency
M106 P0 S0 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"out8" Q500 ; create fan 1 on pin out8 and set its frequency
M106 P1 T45 S1 H1 ; set fan 1 value. Thermostatic control is turned on
M308 S2 Y"drivers" A"DRIVERS" ; configure sensor 2 as temperature warning and overheat flags on the TMC2660 on Duet
M308 S3 Y"mcu-temp" A"MCU" ; configure sensor 3 as thermistor on pin e1temp for left stepper
M950 F2 C"out9" Q100 ; create fan 2 on pin fan2 and set its frequency
M106 P2 H2:3 L0.25 X1 B0.3 T35:70 ; set fan 2 value

; Tools
M563 P0 D0 H1 F0 ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C

; Custom settings are not defined
M912 P0 S-3.7 ; calibration offset for MCU tempurature

; Miscellaneous
M591 D0 P6 C"io1.in" R70:125 L0.41 E10.0 S1 ; enable filament monitor
M575 P1 S1 B57600 ; enable support for PanelDue
M501 ; load saved parameters from non-volatile memory