Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login
    1. Home
    2. BjornH
    • Profile
    • Following 0
    • Followers 0
    • Topics 3
    • Posts 21
    • Best 0
    • Controversial 0
    • Groups 0

    BjornH

    @BjornH

    0
    Reputation
    1
    Profile views
    21
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    BjornH Unfollow Follow

    Latest posts made by BjornH

    • RE: Serious error/fault with firmware or am I new to something?

      @fcwilt Board: Duet 3 Mini 5+ (Mini5plus)
      Firmware: RepRapFirmware for Duet 3 Mini 5+ 3.3RC2 (2021-05-11)
      Duet WiFi Server Version: 1.26

      posted in Duet Hardware and wiring
      BjornHundefined
      BjornH
    • Serious error/fault with firmware or am I new to something?

      Hello.
      Long run programming my duet mini 5+ I stumbled over a weird thing.

      When I was probing I accidentally sent the code g30 s1 instead of g30 s-1 making my printer freeze. No homing working or no command, the machine acted like all home was homed but nothing would move no more. Machine would just run it course then say it didn't work.

      By sending the command G30 s1- i unfroze the machine.

      Is this something known to the community or one time problem???

      posted in Duet Hardware and wiring
      BjornHundefined
      BjornH
    • RE: Duet3 mini 5+ faulty card

      @t3p3tony email has been sent.

      posted in General Discussion
      BjornHundefined
      BjornH
    • RE: Duet3 mini 5+ faulty card

      homing.png @t3p3tony

      undefined

      So i did upload and reinstall 3.3 from DWC, tried homing after. See picture, nothing happens when homing. I sent M122 after reinstalling. Your 3. option do not work i already tried this, what happens is that i double click reset it connects to the computer but after 5 sec it disconnect or if i drag the files the mount freezes.

      New M122
      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: DXGUZ-U196U-D65J0-40KMN-1Y03Z-RKST9
      Used output buffers: 3 of 40 (24 max)
      === RTOS ===
      Static ram: 102724
      Dynamic ram: 106340 of which 156 recycled
      Never used RAM 31628, free system stack 130 words
      Tasks: NETWORK(ready,15.0%,264) HEAT(notifyWait,0.0%,307) Move(notifyWait,0.1%,305) CanReceiv(notifyWait,0.0%,941) CanSender(notifyWait,0.0%,371) CanClock(delaying,0.0%,340) TMC(notifyWait,0.3%,115) MAIN(running,83.8%,426) IDLE(ready,0.0%,29) AIN(delaying,0.8%,273), total 100.0%
      Owned mutexes: WiFi(NETWORK)
      === Platform ===
      Last reset 00:04:03 ago, cause: software
      Last software reset at 2021-10-31 20:34, reason: User, GCodes spinning, available RAM 31628, 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
      MCU revision 3, ADC conversions started 243911, completed 243911, timed out 0, errs 0
      Step timer max interval 808
      MCU temperature: min 37.2, current 37.6, max 37.9
      Supply voltage: min 23.8, current 23.8, max 23.8, under voltage events: 0, over voltage events: 0, power good: yes
      Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/4/4, gc cycles 0
      Driver 0: position 25200, assumed not present
      Driver 1: position 25200, assumed not present
      Driver 2: position 4000, assumed not present
      Driver 3: position 0, assumed not present
      Driver 4: position 0, assumed not present
      Driver 5: position 0, assumed not present
      Driver 6: position 0, assumed not present
      Date/time: 2021-10-31 20:38:19
      Cache data hit count 452273392
      Slowest loop: 4.24ms; fastest: 0.11ms
      === Storage ===
      Free file entries: 10
      SD card 0 detected, interface speed: 22.5MBytes/sec
      SD card longest read time 3.5ms, write time 0.0ms, max retries 0
      === Move ===
      DMs created 83, maxWait 143770ms, bed compensation in use: none, comp offset 0.000
      === MainDDARing ===
      Scheduled moves 2, completed moves 2, 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 1321, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 17 (min 17), ts 734/0/0
      Tx timeouts 0,0,734,0,0,587 last cancelled message type 4514 dest 127

      === Network ===
      Slowest loop: 199.72ms; fastest: 0.06ms
      Responder states: HTTP(2) 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 1
        WiFi firmware version 1.26
        WiFi MAC address d8:bf:c0:14:e6:36
        WiFi Vcc 3.30, reset reason Power up
        WiFi flash size 2097152, free heap 24480
        WiFi IP address 192.168.50.149
        WiFi signal strength -37dBm, mode 802.11n, reconnections 0, sleep mode modem
        Clock register 00002002
        Socket states: 0 0 0 0 0 0 0 0
      posted in General Discussion
      BjornHundefined
      BjornH
    • RE: Duet3 mini 5+ faulty card

      @t3p3tony any response?

      posted in General Discussion
      BjornHundefined
      BjornH
    • RE: Duet3 mini 5+ faulty card

      @t3p3tony From YAT only USB === Diagnostics ===<LF>RepRapFirmware for Duet 3 Mini 5+ version 3.3 (2021-06-15 21:46:11) running on Duet 3 Mini5plus WiFi
      (standalone mode)<LF>Board ID: DXGUZ-U196U-D65J0-40KMN-1Y03Z-RKST9<LF>Used output buffers: 1 of 40 (12 max)<LF>=== RTOS ===<LF>Stat
      ic ram: 102724<LF>Dynamic ram: 106308 of which 12 recycled<LF>Never used RAM 34660, free system stack 170 words<LF>Tasks: NETWORK
      (ready,12.6%,264) HEAT(notifyWait,0.0%,307) Move(notifyWait,0.1%,338) CanReceiv(notifyWait,0.0%,941) CanSender(notifyWai
      t,0.0%,371) CanClock(delaying,0.0%,340) TMC(notifyWait,0.0%,124) MAIN(running,85.5%,426) IDLE(ready,1.0%,29) AIN(delayin
      g,0.8%,273), total 100.0%<LF>Owned mutexes: WiFi(NETWORK) USB(MAIN)<LF>=== Platform ===<LF>Last reset 00:00:22 ago, cause: power
      up<LF>Last software reset at 2021-10-22 16:29, reason: User, GCodes spinning, available RAM 31628, slot 2<LF>Software reset co
      de 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a<LF>Error st
      atus: 0x00<LF>MCU revision 3, ADC conversions started 22476, completed 22476, timed out 0, errs 0<LF>Step timer max interval 7
      52<LF>MCU temperature: min 27.2, current 29.9, max 30.1<LF>Supply voltage: min 1.1, current 1.3, max 1.4, under voltage events
      : 0, over voltage events: 0, power good: no<LF>Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0
      /0/0, gc cycles 0<LF>Driver 0: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, w
      rites 0, timeouts 0, DMA errors 0<LF>Driver 1: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifc
      nt 0, reads 0, writes 0, timeouts 0, DMA errors 0<LF>Driver 2: position 0, ok, SG min/max not available, read errors 0, wri
      te errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0<LF>Driver 3: position 0, ok, SG min/max not available, re
      ad errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0<LF>Driver 4: position 0, ok, SG min/max n
      ot available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0<LF>Driver 5: position 0,
      ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0<LF>Driver
      6: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA
      errors 0<LF>Date/time: 2021-10-22 21:15:44<LF>Cache data hit count 44194745<LF>Slowest loop: 3.80ms; fastest: 0.11ms<LF>=== Storage
      ===<LF>Free file entries: 10<LF>SD card 0 detected, interface speed: 22.5MBytes/sec<LF>SD card longest read time 3.1ms, write ti
      me 0.0ms, max retries 0<LF>=== Move ===<LF>DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000<LF>=== M
      ainDDARing ===<LF>Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA stat
      e -1<LF>=== AuxDDARing ===<LF>Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0],
      CDDA state -1<LF>=== Heat ===<LF>Bed heaters = 0 -1, chamberHeaters = -1 -1<LF>=== GCodes ===<LF>Segments left: 0<LF>Movement lock held
      by null<LF>HTTP is idle in state(s) 0<LF>Telnet is idle in state(s) 0<LF>File is idle in state(s) 0<LF>USB is ready with "m122" in
      state(s) 0<LF>Aux is idle in state(s) 0<LF>Trigger is idle in state(s) 0<LF>Queue is idle in state(s) 0<LF>LCD is idle in state(s) 0
      <LF>SBC is idle in state(s) 0<LF>Daemon is idle in state(s) 0<LF>Aux2 is idle in state(s) 0<LF>Autopause is idle in state(s) 0<LF>Code
      queue is empty.<LF>=== CAN ===<LF>Messages queued 199, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync del
      ay 0, free buffers 17 (min 17), ts 112/0/0<LF>Tx timeouts 0,0,111,0,0,86 last cancelled message type 30 dest 127<LF><LF>=== Netwo
      rk ===<LF>Slowest loop: 10.76ms; fastest: 0.00ms<LF>Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sess
      ions<LF>HTTP sessions: 1 of 8<LF>- WiFi -<LF>Network state is active<LF>WiFi module is connected to access point <LF>Failed messages: p
      ending 0, notready 0, noresp 0<LF>WiFi firmware version 1.26<LF>WiFi MAC address d8:bf:c0:14:e6:36<LF>WiFi Vcc 3.31, reset reason
      Power up<LF>WiFi flash size 2097152, free heap 26376<LF>WiFi IP address 192.168.50.149<LF>WiFi signal strength -51dBm, mode 802.
      11n, reconnections 0, sleep mode modem<LF>Clock register 00002002<LF>Socket states: 0 0 0 0 0 0 0 0<LF>ok<LF>

      posted in General Discussion
      BjornHundefined
      BjornH
    • RE: Duet3 mini 5+ faulty card

      @t3p3tony === 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: DXGUZ-U196U-D65J0-40KMN-1Y03Z-RKST9
      Used output buffers: 3 of 40 (13 max)
      === RTOS ===
      Static ram: 102724
      Dynamic ram: 106308 of which 12 recycled
      Never used RAM 34660, free system stack 170 words
      Tasks: NETWORK(ready,14.5%,260) HEAT(delaying,0.0%,307) Move(notifyWait,0.1%,284) CanReceiv(notifyWait,0.0%,941) CanSender(notifyWait,0.0%,371) CanClock(delaying,0.0%,340) TMC(notifyWait,0.3%,116) MAIN(running,83.5%,426) IDLE(ready,0.8%,29) AIN(delaying,0.8%,273), total 100.0%
      Owned mutexes: WiFi(NETWORK)
      === Platform ===
      Last reset 00:00:30 ago, cause: power up
      Last software reset at 2021-10-22 16:29, reason: User, GCodes spinning, available RAM 31628, slot 2
      Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
      Error status: 0x00
      MCU revision 3, ADC conversions started 30622, completed 30622, timed out 0, errs 0
      Step timer max interval 1487
      MCU temperature: min 24.4, current 27.8, max 27.9
      Supply voltage: min 23.9, current 24.1, max 24.2, 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 49600, assumed not present
      Driver 1: position 0, assumed not present
      Driver 2: position 0, assumed not present
      Driver 3: position 0, assumed not present
      Driver 4: position 0, assumed not present
      Driver 5: position 0, assumed not present
      Driver 6: position 0, assumed not present
      Date/time: 2021-10-22 21:14:02
      Cache data hit count 58840567
      Slowest loop: 4.88ms; fastest: 0.11ms
      === Storage ===
      Free file entries: 10
      SD card 0 detected, interface speed: 22.5MBytes/sec
      SD card longest read time 3.8ms, write time 0.0ms, max retries 0
      === Move ===
      DMs created 83, maxWait 20640ms, bed compensation in use: none, comp offset 0.000
      === MainDDARing ===
      Scheduled moves 8, completed moves 8, 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 273, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 17 (min 17), ts 153/0/0
      Tx timeouts 0,0,152,0,0,119 last cancelled message type 4514 dest 127

      === Network ===
      Slowest loop: 9.93ms; fastest: 0.00ms
      Responder states: HTTP(2) 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 d8:bf:c0:14:e6:36
        WiFi Vcc 3.31, reset reason Power up
        WiFi flash size 2097152, free heap 24240
        WiFi IP address 192.168.50.149
        WiFi signal strength -45dBm, mode 802.11n, reconnections 0, sleep mode modem
        Clock register 00002002
        Socket states: 4 0 0 0 0 0 0 0

      From webcontrol

      posted in General Discussion
      BjornHundefined
      BjornH
    • Duet3 mini 5+ faulty card

      I need some feedback/help and sorting out the problem so i can fix the card or possibly get a new one.

      Here is the story/problem:
      Card been laying in the box until the wiring and completion off whole printer, then i have connected the whole thing and programmed the code to match the setup. The setup is a 3 axis Z, with the extra drive expansion on the duet 3 mainboard.

      Printer finished its first print perfectly no problem, but when i tried changing the filament i noticed the stepper motors did not respond to the commands in webconsole, neither homing. The printer works like normal, but it does not show drivers 5,4,3,2,1,0 in M122 command. I also notice that STATUS is blinking slow red. I take the card out after reading that i can flash it with usb with new firmware(3.3), double clicks reset to get into bootload after about 5 sec light disapear and when i try put new files into bootload the whole thing crashes.
      I have been reading about possible CPU fault, wich is super rare. I have checked whole thing for possible burns or faults, and card looks like new. Changed both fuses to see if that helped.

      I uploaded my code so you can see, but i also tried loading standard code from RRF config to see if something was faulty. Even if i start card with or without SD card the mainboard blinks red status light.

      Hope to get some quick respons, and service as i would really like to use my printer after 2 months of research and wiring/putting together again.

      Best regards

      tpre0.g tpost0.g tfree0.g stop.g sleep.g retractprobe.g resurrect.g resume.g pause.g homez.g homey.g homex.g homeall.g deployprobe.g config.g bed.g

      posted in General Discussion
      BjornHundefined
      BjornH
    • RE: Duet 2 wifi. Bltouch sometimes doesn't work

      https://forum.duet3d.com/topic/20333/bltouch-oddity/10?_=1613996928642

      Please read this. I have finally found the problem.

      It was not the cable after all but the Z min pin on the bl touch had come loose. Check the bltouch, i have original one yet i feel they are really cheaply made. The soldering had come loose on the pin on the z min on the probe(constantly giving me reading errors, red lights and z-probe 1000 red error reading

      posted in General Discussion
      BjornHundefined
      BjornH
    • RE: Bltouch oddity

      @TampaPrinter I have not corrected my fault yet, since i have to dissasemble my extruder. I belive the problem lays in the pins (dupont) connection to the bltouch as they are not thight enough

      posted in General Discussion
      BjornHundefined
      BjornH