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

Posts made by Marshal

  • RE: Cura vase mode settings for funnel

    Okay, so it worked by using two parts.
    I had to "merge" them first, to align them and after break the created group, to assign different settings.
    funnel_3 (Telefon).png

    Thanks @cosmowave

    Needing the lip, I do not know 🤡
    Its like you said, all you see is with a lip.

    Problem with bottom layers is, that it would either have them all the way, so closed funnel, or if set to 0 remove them, there would be no bottom layer for the lip either.

    posted in 3D Printing General Chat
    undefined
    Marshal
    25 Aug 2022, 18:58
  • Cura vase mode settings for funnel

    Hi all,

    I am trying to print a funnel in vase mode, but I fail in setting the write values in Cura 5.1.0.
    Attempt 1:
    Funnel build in freecad (basically a pipe with a collar).
    funnel_1 (Telefon).png

    When trying to slice this version in vase mode, it will generate two walls, one inner, one outer wall.
    funnel_1_sliced (Telefon).png
    It seems logical to me, since there are "two" outer surfaces.

    Attempt 2:
    keep the funnel solid:
    funnel_2 (Telefon).png

    This will be fine except the bottom layer is closeing of the funnel
    funnel_2_sliced (Telefon).png

    Is there a way to have the result from attempt 2, but with open bottom side?

    Thank you

    posted in 3D Printing General Chat cura vase
    undefined
    Marshal
    25 Aug 2022, 13:11
  • RE: Temperature wrong after fitting PT1000

    Hi,

    which firmware are you running? Something is off with Beta 3.4.7, causing lower temperature readings, at least at room temperature. I have not tested the effect at high temperatures.

    Maybe check here:
    3-4-0b7-firmware-update-changes-1lc-temp

    posted in Tuning and tweaking
    undefined
    Marshal
    24 Dec 2021, 23:24
  • RE: [3.4.0b7] Firmware update changes 1LC temp

    @dc42
    No issue with bed thermistor here:

    M308 S0 P"0.temp0" Y"thermistor" T100000 B4725 C7.06e-8
    
    posted in Beta Firmware
    undefined
    Marshal
    21 Dec 2021, 12:14
  • RE: [3.4.0b7] Firmware update changes 1LC temp

    @dc42 I know that feeling 😉

    i case you are wondering.
    going back to 3.4.0b7 will come up with low temperature again.

    m122 b20
    Diagnostics for board 20:
    Duet TOOL1LC rev 1.0 or earlier firmware version 3.4.0beta7 (2021-12-16 12:25:01)
    Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
    Never used RAM 3648, free system stack 2788 words
    Tasks: Move(notifyWait,0.0%,153) HEAT(notifyWait,0.2%,115) CanAsync(notifyWait,0.0%,65) CanRecv(notifyWait,0.0%,76) CanClock(notifyWait,0.0%,65) TMC(delaying,3.0%,57) MAIN(running,91.8%,351) IDLE(ready,0.0%,40) AIN(delaying,4.9%,142), total 100.0%
    Last reset 00:00:47 ago, cause: software
    Last software reset time unknown, reason: AssertionFailed, available RAM 4592, slot 1
    Software reset code 0x0120 ICSR 0x00000000 SP 0x20003cac Task   Freestk 130 bad marker
    Stack: 00000544 00023174 00019cb5 20003044 00016e33 20003044 00016505 20000ed0 00000000 00000001 0000828d 200071c8 200071c8 200071e0 00000000 20000f50 000116b3 00022530 000225e8 00021c40 00019c55 200071c8 200071c8 20000f50 00008405 200071d8 000009c6
    Driver 0: pos 0, 419.2 steps/mm,standstill, SG min 0, read errors 0, write errors 1, ifcnt 24, reads 23875, writes 12, timeouts 0, DMA errors 0, CC errors 0, steps req 0 done 0
    Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
    Peak sync jitter 4/9, peak Rx sync delay 579, resyncs 0/1, no step interrupt scheduled
    VIN voltage: min 24.2, current 24.2, max 24.3
    MCU temperature: min 29.2C, current 31.4C, max 31.4C
    Last sensors broadcast 0x00000002 found 1 65 ticks ago, 0 ordering errs, loop time 0
    CAN messages queued 919, send timeouts 0, received 437, lost 0, free buffers 37, min 37, error reg 0
    dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
    Accelerometer: none
    I2C bus errors 4509, naks 4509, other errors 4509
    

    beta7.png

    posted in Beta Firmware
    undefined
    Marshal
    19 Dec 2021, 19:58
  • RE: [3.4.0b7] Firmware update changes 1LC temp

    @dc42 Hi,
    for me beta7+1 fixed the issue.
    (theres a small typo in your post - 3. Send M121 B#)

    config.g - not changed

    M308 S1 P"20.temp0" Y"thermistor" T100000 B4725 C7.06e-8
    

    [3.4.0b7]:

    M122 B20
    Diagnostics for board 20:
    Duet TOOL1LC rev 1.0 or earlier firmware version 3.4.0beta7 (2021-12-16 12:25:01)
    Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
    Never used RAM 3648, free system stack 2788 words
    Tasks: Move(notifyWait,0.0%,153) HEAT(notifyWait,0.2%,115) CanAsync(notifyWait,0.0%,65) CanRecv(notifyWait,0.0%,76) CanClock(notifyWait,0.0%,65) TMC(delaying,3.0%,57) MAIN(running,91.8%,351) IDLE(ready,0.0%,40) AIN(delaying,4.9%,142), total 100.0%
    Last reset 00:02:33 ago, cause: software
    Last software reset time unknown, reason: AssertionFailed, available RAM 4592, slot 1
    Software reset code 0x0120 ICSR 0x00000000 SP 0x20003cac Task   Freestk 130 bad marker
    Stack: 00000544 00023174 00019cb5 20003044 00016e33 20003044 00016505 20000ed0 00000000 00000001 0000828d 200071c8 200071c8 200071e0 00000000 20000f50 000116b3 00022530 000225e8 00021c40 00019c55 200071c8 200071c8 20000f50 00008405 200071d8 000009c6
    Driver 0: pos 0, 419.2 steps/mm,standstill, SG min 0, read errors 0, write errors 1, ifcnt 24, reads 10980, writes 12, timeouts 0, DMA errors 0, CC errors 0, steps req 0 done 0
    Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
    Peak sync jitter 5/8, peak Rx sync delay 213, resyncs 0/0, no step interrupt scheduled
    VIN voltage: min 24.2, current 24.2, max 24.3
    MCU temperature: min 33.2C, current 35.9C, max 35.9C
    Last sensors broadcast 0x00000002 found 1 97 ticks ago, 0 ordering errs, loop time 0
    CAN messages queued 3054, send timeouts 0, received 1386, lost 0, free buffers 37, min 37, error reg 0
    dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
    Accelerometer: none
    I2C bus errors 4509, naks 4509, other errors 4509
    
    M308 S1
    Sensor 1 type Thermistor using pin 20.temp0, reading 13.5, last error: success, T:100000.0 B:4725.0 C:7.06e-8 R:2200.0 L:0 H:0
    

    Readings:
    beta7.png

    [3.4.0b7+1]:

    M122 B20
    Diagnostics for board 20:
    Duet TOOL1LC rev 1.0 or earlier firmware version 3.4.0beta7+1 (2021-12-18 13:47:42)
    Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
    All averaging filters OK
    Never used RAM 3648, free system stack 2788 words
    Tasks: Move(notifyWait,0.0%,153) HEAT(notifyWait,0.2%,115) CanAsync(notifyWait,0.0%,65) CanRecv(notifyWait,0.0%,76) CanClock(notifyWait,0.0%,65) TMC(notifyWait,3.0%,57) MAIN(running,91.8%,341) IDLE(ready,0.0%,40) AIN(delaying,4.9%,142), total 100.0%
    Last reset 00:04:12 ago, cause: software
    Last software reset time unknown, reason: AssertionFailed, available RAM 4592, slot 1
    Software reset code 0x0120 ICSR 0x00000000 SP 0x20003cac Task   Freestk 130 bad marker
    Stack: 00000544 00023174 00019cb5 20003044 00016e33 20003044 00016505 20000ed0 00000000 00000001 0000828d 200071c8 200071c8 200071e0 00000000 20000f50 000116b3 00022530 000225e8 00021c40 00019c55 200071c8 200071c8 20000f50 00008405 200071d8 000009c6
    Driver 0: pos 0, 419.2 steps/mm,standstill, SG min 0, read errors 0, write errors 1, ifcnt 51, reads 60503, writes 11, timeouts 0, DMA errors 0, CC errors 0, steps req 0 done 0
    Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
    Peak sync jitter 4/9, peak Rx sync delay 214, resyncs 0/1, no step interrupt scheduled
    VIN voltage: min 24.2, current 24.2, max 24.3
    MCU temperature: min 37.2C, current 37.6C, max 37.6C
    Last sensors broadcast 0x00000002 found 1 137 ticks ago, 0 ordering errs, loop time 0
    CAN messages queued 4866, send timeouts 0, received 2276, lost 0, free buffers 37, min 37, error reg 50000
    dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
    Accelerometer: none
    I2C bus errors 4509, naks 4509, other errors 4509
    
    M308 S1
    Sensor 1 type Thermistor using pin 20.temp0, reading 25.5, last error: success, T:100000.0 B:4725.0 C:7.06e-8 R:2200.0 L:0 H:0
    

    Readings:
    beta7+1.png

    posted in Beta Firmware
    undefined
    Marshal
    19 Dec 2021, 11:35
  • RE: Toolboard LC1 - IO1 failed?

    @alankilian

    THX for the input, especially jumping the connector.

    With

    M409 K"endstops.sensors"
    

    I observed the input working.

    I changed my config.g from

    M574 X1 S1 P"20.io1.in" # old
    M574 X1 S1 P"^20.io1.in" # new
    

    to activate the pull up resistor.
    Like this its back working.

    Probably I have messed the line up, can't explain when or why though ...

    Thx

    posted in Duet Hardware and wiring
    undefined
    Marshal
    3 Nov 2021, 19:46
  • Toolboard LC1 - IO1 failed?

    Hi all,

    i ran into issues today with the IO1 of a tool board
    It is not working anymore.

    IO1 was configured for an optical end stop

    M574 X1 S1 P"20.io1.in"
    

    and it was working for quite some time.

    As off today the sensors is showing as triggered when it is not.
    When connecting the sensor to IO2 and changing the configuration accordingly, the sensor is working fine.

    I checked the supply voltage on IO1, it is 3.3 V.
    The optical end stop has one led which is lit up when the sensor is not triggered.
    I tried to only connect V+ and GND, in this case the led is lit and triggers when triggering the sensor.

    Maybe there is a short on the signal line? Can i check this somehow?

    Without power

    • IO1.in to V+ is shorted on the tool board
    • IO2.in to V+ is not shorted on the tool board

    Thx in advance.

    Additional info:

    M122
    === Diagnostics ===
    RepRapFirmware for Duet 3 MB6HC version 3.4.0beta5 (2021-10-12 13:53:56) running on Duet 3 MB6HC v0.6 or 1.0 (SBC mode)
    Board ID: 08DJM-956L2-G43S8-6J9D4-3SN6M-TU0UG
    Used output buffers: 1 of 40 (12 max)
    === RTOS ===
    Static ram: 151104
    Dynamic ram: 65740 of which 516 recycled
    Never used RAM 133312, free system stack 200 words
    Tasks: SBC(ready,0.4%,508) HEAT(notifyWait,0.0%,327) Move(notifyWait,0.0%,299) CanReceiv(notifyWait,0.0%,797) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,339) TMC(notifyWait,8.0%,92) MAIN(running,89.9%,921) IDLE(ready,1.6%,30), total 100.0%
    Owned mutexes: HTTP(MAIN)
    === Platform ===
    Last reset 00:02:30 ago, cause: power up
    Last software reset at 2021-11-03 15:19, reason: User, GCodes spinning, available RAM 133356, slot 2
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
    Error status: 0x00
    Step timer max interval 132
    MCU temperature: min 20.8, current 33.2, max 33.2
    Supply voltage: min 24.2, current 24.2, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
    12V rail voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0
    Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
    Driver 0: pos 0, standstill, SG min/max 0/0, reads 54840, writes 14 timeouts 0
    Driver 1: pos 0, standstill, SG min/max 0/0, reads 54840, writes 14 timeouts 0
    Driver 2: pos 0, standstill, SG min/max 0/0, reads 54840, writes 14 timeouts 0
    Driver 3: pos 0, standstill, SG min/max 0/0, reads 54840, writes 14 timeouts 0
    Driver 4: pos 0, standstill, SG min/max 0/0, reads 54840, writes 14 timeouts 0
    Driver 5: pos 0, standstill, SG min/max 0/0, reads 54843, writes 11 timeouts 0
    Date/time: 2021-11-03 15:36:59
    Slowest loop: 1.27ms; fastest: 0.04ms
    === 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 ===
    DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
    === MainDDARing ===
    Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
    === AuxDDARing ===
    Scheduled moves 0, completed 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
    Heater 1 is on, I-accum = 0.0
    === 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 1285, received 2763, lost 0, longest wait 2ms for reply type 6049, peak Tx sync delay 46, free buffers 49 (min 48), ts 754/753/0
    Tx timeouts 0,0,0,0,0,0
    === SBC interface ===
    State: 4, failed transfers: 1, checksum errors: 0
    Last transfer: 2ms ago
    RX/TX seq numbers: 4992/4992
    SPI underruns 0, overruns 0
    Disconnects: 0, timeouts: 0, IAP RAM available 0x2b7dc
    Buffer RX/TX: 0/0-0
    === Duet Control Server ===
    Duet Control Server v3.4-b5
    Code buffer space: 4096
    Configured SPI speed: 8000000Hz
    Full transfers per second: 4.19, max wait times: 28.8ms/5.3ms
    Codes per second: 0.04
    Maximum length of RX/TX data transfers: 2988/580
    
    m122 b20
    Diagnostics for board 20:
    Duet TOOL1LC rev 1.0 or earlier firmware version 3.4.0beta5 (2021-10-12 13:59:06)
    Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
    Never used RAM 3612, free system stack 2789 words
    Tasks: Move(notifyWait,0.0%,153) HEAT(notifyWait,0.3%,97) CanAsync(notifyWait,0.0%,60) CanRecv(notifyWait,0.0%,77) CanClock(notifyWait,0.0%,64) TMC(notifyWait,3.0%,57) MAIN(running,91.8%,348) IDLE(ready,0.0%,41) AIN(delaying,4.9%,142), total 100.0%
    Last reset 01:07:15 ago, cause: power up
    Last software reset time unknown, reason: AssertionFailed, available RAM 4592, slot 1
    Software reset code 0x0120 ICSR 0x00000000 SP 0x20003cac Task   Freestk 130 bad marker
    Stack: 00000544 00023174 00019cb5 20003044 00016e33 20003044 00016505 20000ed0 00000000 00000001 0000828d 200071c8 200071c8 200071e0 00000000 20000f50 000116b3 00022530 000225e8 00021c40 00019c55 200071c8 200071c8 20000f50 00008405 200071d8 000009c6
    Driver 0: pos 0, 419.2 steps/mm, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 22, reads 51870, writes 22, timeouts 0, DMA errors 0, steps req 0 done 0
    Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
    Peak sync jitter 4/9, peak Rx sync delay 215, resyncs 0/5, no step interrupt scheduled
    VIN voltage: min 23.0, current 24.3, max 24.3
    MCU temperature: min 35.8C, current 39.0C, max 41.3C
    Last sensors broadcast 0x00000002 found 1 240 ticks ago, loop time 0
    CAN messages queued 80639, send timeouts 0, received 36266, lost 0, free buffers 37, min 37, error reg 150000
    dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
    Accelerometer detected: no
    I2C bus errors 4509, naks 4509, other errors 4509
    
    posted in Duet Hardware and wiring
    undefined
    Marshal
    3 Nov 2021, 15:40
  • RE: After updating to 3.4.0beta2: faulty heater 1, -273.1C.

    Hi all,

    I updated my printer after vacation and noticed the same issue.
    I have upped the LC1 to 3.4.0beta2+2 and readings are back within expected range.

    No recalibration done yet.

    (I was not sure if there was a toolboard v1 reported or tested with the issue.)

    Diagnostics for board 20:
    Duet TOOL1LC firmware version 3.4.0beta2+2 (2021-08-21 14:16:34)
    Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
    
    posted in Beta Firmware
    undefined
    Marshal
    22 Aug 2021, 10:54
  • RE: Blobs and zits - stuttering movement

    Hi,

    I think I ran in a similar issue, I started to look into it once here: link text

    On my core xy straight lines are fine, as soon as a radius starts, the stuttering is happening.

    Firmware does not make a difference currently using latest RC2. My assumption it is an interference with the 3D-touch seems to be wrong.

    The issue seems to be there when I have start code configured in Cura. I have not tested in detail, but

    • start code including M32 —> fail
    • disabling M32 in start code or just commenting out in DWC (no other changes to guide) —> printing fine
      *Starting M32 manually prior to print and starting print after M32 has finished —> fine

    Do you have any start code active?

    Best Regards
    Marshal

    posted in Tuning and tweaking
    undefined
    Marshal
    24 May 2021, 09:20
  • RE: Bl touch "already triggered at the start of the probing move''

    @grahamexp try a

    M280 Pxxx S160
    

    or

    M280 Pxxx S60
    

    I changed my retractprobe.g to

    M280 P10 S90
    G4 P200
    M280 P10 S160
    

    yesterday due to issues with a 3DTouch

    posted in Duet Hardware and wiring
    undefined
    Marshal
    29 Apr 2021, 21:41
  • RE: Duet 3 6HC stuttering and not using up filament during print

    Hi,

    i continued testing this evening,

    • Upgrading Toolboard to 3.2.2 (all system 3.2.2) --> issue remains
    • Upgrading all to 3.3beta3 --> issue remains

    Currently i am using a 3DTouch (BLTouch clone), with 3.3beta3 i had some events, where probe was not deployed, or was triggered before touching bed. Which seemed more an issue of the sensor after the previous "touch" than anything else.

    I have extended retractprobe.g
    from:

     M280 P10 S90
    

    to:

    M280 P10 S90
    G4 P200
    M280 P10 S160
    

    I have done 3 test prints in a row now, no issue yet.
    Maybe the sensor was putting noise on Toolboar.io0.in?

    More prints will tell if it is fixed like this. Maybe a BLTouch will replace the 3DTouch soon.

    posted in General Discussion
    undefined
    Marshal
    28 Apr 2021, 18:48
  • RE: Duet 3 6HC stuttering and not using up filament during print

    @phaedrux: my bad, i have changed the LC1 due to a bad resitstor, but didn't confirm the firmware ...

    M122 B20
    Diagnostics for board 20:
    Duet TOOL1LC firmware version 3.2.2 (2021-02-11)
    Bootloader ID: not available
    Never used RAM 4108, free system stack 94 words
    HEAT 90 CanAsync 89 CanRecv 83 TMC 56 MAIN 216 AIN 64
    Last reset 00:00:16 ago, cause: software
    Last software reset data not available
    Driver 0: position 0, 430.1 steps/mm, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 23, reads 8021, writes 11, timeouts 0, DMA errors 0
    Moves scheduled 0, completed 0, in progress 0, hiccups 0
    No step interrupt scheduled
    VIN: 24.3V
    MCU temperature: min 39.1C, current 39.2C, max 39.3C
    Ticks since heat task active 97, ADC conversions started 16060, completed 16059, timed out 0
    Last sensors broadcast 0x00000002 found 1 101 ticks ago, loop time 0
    CAN messages queued 122, send timeouts 0, received 149, lost 0, free buffers 36
    

    I will test soon.

    @JamesM: M83 is called before from job to run.

    ;FLAVOR:RepRap
    ;TIME:1876
    ;Filament used: 0.562977m
    ;Layer height: 0.2
    ;MINX:177.567
    ;MINY:181.574
    ;MINZ:0.125
    ;MAXX:225.933
    ;MAXY:211.149
    ;MAXZ:52.925
    ;Generated with Cura_SteamEngine 4.9.0
    T0
    M190 S70
    M104 S240
    M109 S240
    M82 ;absolute extrusion mode
    G32
    M83 ;relative extrusion mode
    G1 F2400 E-2
    ;LAYER_COUNT:265
    ;LAYER:0
    M107
    G0 F1800 X180.77 Y185.898 Z0.125
    ;TYPE:SKIRT
    G1 F2400 E2
    G1 F1200 X181.549 Y185.164 E0.04005
    G1 X181.772 Y184.974 E0.01096
    .
    .
    .
    
    posted in General Discussion
    undefined
    Marshal
    28 Apr 2021, 07:38
  • Duet 3 6HC stuttering and not using up filament during print

    Hi all,

    I am running first prints with a newly built printer.

    For some reason I am running into an issue, where the printer is not moving smoothly and is not using filament.

    • not moving smoothly is especially visible during circles
    • not using filament, the extruder stepper is changing from extrusion to retract but is averaging at ~0

    Giving the same gcode several tries will eventually result in a working one.
    I am trying to run it down with one routine

    • power up printer
    • goto "Jobs"
    • select/start print
    • within gcode:
      -- heat up of bed / tool
      -- G32 for homing and tramming

    From M122 (see below) i am wondering, if:

    === CAN ===
    Messages queued 1976, send timeouts 0, received 4518, lost 0, longest wait 2ms for reply
    

    is ok, due to the messages in queue?
    Maybe, bad CAN connection?

    Thx in advance.

    System Details:

    Board: Duet 3 MB6HC (MB6HC)
    DSF Version: 3.2.2
    Firmware: RepRapFirmware for Duet 3 MB6HC 3.2.2 (2021-02-11)
    
    RPI 4 SBC, updates last checked today
    
    Duet TOOL1LC firmware version 3.2 (2021-01-05)
    

    M122:

    M122
    === Diagnostics ===
    RepRapFirmware for Duet 3 MB6HC version 3.2.2 running on Duet 3 MB6HC v0.6 or 1.0 (SBC mode)
    Board ID: 08DJM-956L2-G43S8-6J9D4-3SN6M-TU0UG
    Used output buffers: 4 of 40 (10 max)
    === RTOS ===
    Static ram: 149788
    Dynamic ram: 62836 of which 88 recycled
    Never used RAM 146120, free system stack 128 words
    Tasks: Linux(ready,77) HEAT(blocked,297) CanReceiv(blocked,834) CanSender(blocked,344) CanClock(blocked,352) TMC(blocked,17) MAIN(running,720) IDLE(ready,19)
    Owned mutexes: HTTP(MAIN)
    === Platform ===
    Last reset 00:06:09 ago, cause: software
    Last software reset at 2021-04-27 20:51, reason: User, Platform spinning, available RAM 146536, slot 1
    Software reset code 0x0000 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task Linu Freestk 0 n/a
    Error status: 0x00
    Aux0 errors 0,0,0
    Aux1 errors 0,0,0
    MCU temperature: min 40.0, current 41.1, max 42.1
    Supply voltage: min 24.1, current 24.2, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
    12V rail voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0
    Driver 0: position 65938, ok, reads 37397, writes 17 timeouts 0, SG min/max 0/1023
    Driver 1: position 1629, standstill, reads 37397, writes 17 timeouts 0, SG min/max 0/1023
    Driver 2: position 840, standstill, reads 37399, writes 17 timeouts 0, SG min/max 0/1023
    Driver 3: position 0, standstill, reads 37399, writes 17 timeouts 0, SG min/max 0/439
    Driver 4: position 0, standstill, reads 37399, writes 17 timeouts 0, SG min/max 0/476
    Driver 5: position 0, standstill, reads 37405, writes 11 timeouts 0, SG min/max 0/0
    Date/time: 2021-04-27 20:57:17
    Slowest loop: 183.64ms; fastest: 0.05ms
    === 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 ===
    DMs created 125, maxWait 77883ms, bed compensation in use: none, comp offset 0.000
    === MainDDARing ===
    Scheduled moves 1148, completed moves 1141, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state 3
    === 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
    Heater 0 is on, I-accum = 0.1
    Heater 1 is on, I-accum = 0.0
    === GCodes ===
    Segments left: 1
    Movement lock held by null
    HTTP* is doing "M122" in state(s) 0
    Telnet is idle in state(s) 0
    File* is doing "G1 X198.794006 Y186.348999 E0.581140" 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 1976, send timeouts 0, received 4518, lost 0, longest wait 2ms for reply type 6049, free buffers 48
    === SBC interface ===
    State: 4, failed transfers: 0
    Last transfer: 3ms ago
    RX/TX seq numbers: 13507/13507
    SPI underruns 0, overruns 0
    Number of disconnects: 0, IAP RAM available 0x2c85c
    Buffer RX/TX: 1296/2808-0
    === Duet Control Server ===
    Duet Control Server v3.2.2
    File:
    Buffered code: G1 X198.794 Y186.349 E0.58114
    Buffered code: G1 X199.36 Y186.349 E0.01883
    Buffered code: G1 X211.149 Y198.138 E0.55452
    Buffered code: G1 X211.149 Y197.572 E0.01883
    Buffered code: G1 X199.925 Y186.349 E0.52792
    Buffered code: G1 X200.491 Y186.349 E0.01883
    Buffered code: G1 X211.149 Y197.007 E0.50132
    Buffered code: G1 X211.149 Y196.441 E0.01883
    Buffered code: G1 X201.057 Y186.349 E0.4747
    Buffered code: G1 X201.623 Y186.349 E0.01883
    Buffered code: G1 X211.149 Y195.875 E0.44807
    Buffered code: G1 X211.149 Y195.309 E0.01883
    Buffered code: G1 X202.188 Y186.349 E0.42147
    Buffered code: G1 X202.754 Y186.349 E0.01883
    Buffered code: G1 X211.149 Y194.744 E0.39488
    Buffered code: G1 X211.149 Y194.178 E0.01883
    Buffered code: G1 X203.32 Y186.349 E0.36825
    Buffered code: G1 X203.885 Y186.349 E0.01879
    Buffered code: G1 X211.149 Y193.612 E0.34165
    Buffered code: G1 X211.149 Y193.047 E0.01879
    Buffered code: G1 X204.451 Y186.349 E0.31505
    Buffered code: G1 X205.017 Y186.349 E0.01883
    Buffered code: G1 X211.149 Y192.481 E0.28843
    Buffered code: G1 X211.149 Y191.915 E0.01883
    Buffered code: G1 X205.582 Y186.349 E0.26183
    Buffered code: G1 X206.148 Y186.349 E0.01883
    Buffered code: G1 X211.149 Y191.35 E0.23523
    Buffered code: G1 X211.149 Y190.784 E0.01883
    Buffered code: G1 X206.714 Y186.349 E0.20861
    Buffered code: G1 X207.279 Y186.349 E0.01879
    Buffered code: G1 X211.149 Y190.218 E0.18201
    Buffered code: G1 X211.149 Y189.653 E0.01879
    ==> 1520 bytes
    Code buffer space: 1288
    Configured SPI speed: 8000000 Hz
    Full transfers per second: 36.75
    Maximum length of RX/TX data transfers: 4454/1552
    File /opt/dsf/sd/gcodes/TXXPRO_CHEPCalibrationCube.gcode is selected, processing
    

    M122 B20

    M122 B20
    Diagnostics for board 20:
    Duet TOOL1LC firmware version 3.2 (2021-01-05)
    Bootloader ID: not available
    Never used RAM 4040, free system stack 50 words
    HEAT 86 CanAsync 85 CanRecv 83 TMC 54 MAIN 216 AIN 64
    Last reset 00:44:57 ago, cause: software
    Last software reset data not available
    Driver 0: position -9956, 430.1 steps/mm, ok, SG min/max 0/16, read errors 0, write errors 1, ifcnt 34, reads 37840, writes 21, timeouts 0, DMA errors 0
    Moves scheduled 7866, completed 7865, in progress 1, hiccups 0
    Next step interrupt due in 2517 ticks, enabled
    VIN: 23.9V
    MCU temperature: min 41.2C, current 51.3C, max 51.5C
    Ticks since heat task active 211, ADC conversions started 2686474, completed 2686473, timed out 0
    Last sensors broadcast 0x00000002 found 1 215 ticks ago, loop time 0
    CAN messages queued 32597, send timeouts 0, received 32342, lost 0, free buffers 36
    

    Screenshot DWC:
    Stuttering_001.png

    posted in General Discussion
    undefined
    Marshal
    27 Apr 2021, 20:12
  • RE: Toolboard LC1 - Temp0 with offset or wrong reading

    @dc42 I have recieved a replacement today. New board is working as expected.
    (SMD soldering is not on my stronglist 😉 )

    Thx for your support.

    posted in Duet Hardware and wiring
    undefined
    Marshal
    20 Apr 2021, 14:37
  • RE: Toolboard LC1 - Temp0 with offset or wrong reading

    @dc42 R21 seems to be in place. I checked resistance of the component and it is the same as for the pins.

    Btw. it is version 1.0

    posted in Duet Hardware and wiring
    undefined
    Marshal
    16 Apr 2021, 14:39
  • Toolboard LC1 - Temp0 with offset or wrong reading

    Hello All,

    I am setting up a new printer with my first set of Duet Hardware and RRF.
    I am using a Duet 3 and currently 1 Toolbaord LC1 without distribution board.

    Duet 3:

    Board: Duet 3 MB6HC (MB6HC)
    DSF Version: 3.2.2
    Firmware: RepRapFirmware for Duet 3 MB6HC 3.2.2 (2021-02-11)
    

    Can and power connection between Duet3 () and LC1 is up:

    M115 B121
    Duet TOOL1LC firmware version 3.2 (2021-01-05)
    

    Currently I am faceing an issue with the reading of Temp0 on the LC1.
    For testing and debugging I have configured 3 thermistors (104gt-2), 1 on the Duet3 and 2 on the LC1:

    M308 S0 P"0.temp0" Y"thermistor" T100000 B4725 C7.06e-8;
    M308 S1 P"121.temp0" Y"thermistor" T100000 B4725 C7.06e-8;
    M308 S2 P"121.temp1" Y"thermistor" T100000 B4725 C7.06e-8;
    

    The readings without connected thermistors are:

    S0 = -273,1 C
    S1 = 46.0 C
    S2 = -273,1 C
    

    Connecting a thermistor will result in:

    S0 = ~26 C
    S1 = ~163 C
    S2 = ~26 C
    

    Where 26 C is a little above room temperature and i consider as correct reading.

    So it is not realy an offset.
    Is there anything i can check or try
    I have measured the resistance between pins 1 and 2 (don't know if this is helpfull)

    LC1.Temp0 = 265 k Ohm
    LC1.Temp1 = 4,4 k Ohm
    

    Might the board/temp0 be fried?

    Thanks
    Marshal

    posted in Duet Hardware and wiring
    undefined
    Marshal
    16 Apr 2021, 13:17
Unless otherwise noted, all forum content is licensed under CC-BY-SA