@jay_s_uk

Thanks for the guidance! It was out of date.

@dc42 said in CAN connectivity: Duet 3 MB6HC to EXP3HC:

@kroybal this will most likely be resolved by updating the bootloader on the 3HC.

This resolved my issue, when I updated the firmware and forgot to do the bootloader as well.

Appreciate the help!

I haven't seen any information on resellers/forum posts about the duet magnetic filament monitor. Although I did see that someone was attempting to make a DIY which I must confess, I have considered doing the same.

Preferably I would rather purchase two, Is there any ETA as to when they will be restocked?

@MikeS said in Jerk Control M566:

Seeing that it is a professional commercial printer i won't say that requirements are not met and also you should really come in contact with the manufacturer to, at least, get the basic configuration they use for this machine.

Well I got a hold of Aon finally, apparently they're updating their calling system. Anyways, the support team said that the M1 model is mostly a prototype for proof of concept. There are issues with the model, and there are success stories with it as well. They lined me up to talk to the machine's designer so I can get some answers on its anatomy. The support agent does not know a whole lot about their legacy machine, but she does know that the set screws used to tension the toolhead to the belt wiggle loose over time and that was one of the design updates they did going into the M2 model. That said I'm going to tighten screws where I can and see if they help control it from shifting. But based on the nature of the shifts it doesn't stand out as being mechanical slipping as much as it could be configuration.

We'll see. I am just happy to have talked to an Aon team member.

@jrockland said in CAN connectivity: Duet 3 MB6HC to EXP3HC:

@kroybal hmm but why 15 ? If you have just a 6hc+3hc shouldnt it be address to 1 ? Or im missing something here

Addressing is arbitrary right? I certainly do not have tons of boards and channel 1 is free but I found it easiest to just flip them all to on in one motion instead of trying to be precise with flipping one switch.

Edit: Not totally arbitrary, but no right or wrong answer as long as its logical

I wasn't present to witness the cause of failure during the update that erased/corrupted its firmware. Which would be interesting to know and of course it was the temp's last day here at the lab (I am sure he feels bad , good kid).

If anyone knows what could cause a firmware flash to render a board unresponsive I would be interested to know.

However, I followed the erasing procedure and and using Bossa I was able to flash the most up to date firmware. Wired the machine up and printed a benchy boat just fine. Which makes this a resolved topic.

Thanks!

I have updated the firmware for the MB and TB's to the recent release about a week ago, that said I can rewire somethings and see what results it'll produce. I am still waiting to hear back from the machine's designer to ID the motors so that I can specify current ratings in the config.

@fcwilt @Phaedrux Thanks for the clarification guys. I got filaments!

@fcwilt

The support team over at AON have been really delaying getting back to me. However, my boss went ahead and ordered a duet EX3HC. The results were excellent right out of the gate. All of the layer shifted existed on the x-axis which at the time was powered by low current channels . At any rate, I have new issues to uncover and fix but for now I will call this a victory. I will start a new thread in regards to complications I face with the expansion board.

Thanks for everyones help and suggestions, ultimately it led to discovering a trivial mistake.

UPDATE:

@jay_s_uk & @Phaedrux

I got the switches running. I will probably just recognize only one of the redundant switches, since they seem to be coplanar and serve no obvious purpose. I am working with some juiced up motors for the z-axis and the only reason I can think of for redundant switches in to be safe not to damage the machine in the event of a signal failure.

I could post a photo if you are interested however, doesn't seem to be necessary at this point!

Thanks for your help.

I am building a IDEX printer with an X & U axis driven by their own 1HCL boards. I installed 17E1K-07 Motors.

The issue I am hoping to resolve is that I keep getting:

Warning: Driver 41.0 warning: tuning failed
Warning: Driver 41.0 new tuning error(s): The measured motion was inconsistent.
Warning: Driver 40.0 warning: tuning failed
Warning: Driver 40.0 new tuning error(s): The measured motion was inconsistent.

in the console as a result of homing sequence. I have played with different maneuvers. i.e. the required ones as listed in the table.

I have also adjusted the M569.1 TX parameter from 1 & 2 (pretty sure its shaft mounted however)

Additionally, when I use the closed-loop plugin (latest version), my recorded data is always:

Sample,Timestamp,Measured Motor Steps,Target Motor Steps

0,0.04,3.04,-248.09

1,0.11,3.04,-248.09

2,0.18,3.04,-248.09

3,0.24,3.04,-248.09
(You can assume the rest.....)

config.g

; Configuration file for Duet 3 (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.1.4 on Fri Sep 04 2020 17:16:08 GMT-0600 (Mountain Daylight Time)

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

; Network
M551 P"tom"                                     ; set password
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

; Axis Definitions====>>>>>
; X = Left (on X-axis) Extruder U = Right (on X-axis) Extruder /// Y = Y-Axis /// Z = Z-Axis  

; ======={ Drives }========================================
; 0.x corresponds to main board /// 40.x corresponds 1HCL-1 /// 41.x corresponds to 1HCL-2
; X
M569.1 P40.0 T2 C20 R100 I0 D0 ;
M569.1 P41.0 T2 C20 R100 I0 D0 ;
M569 P40.0 S0 D4                                ; physical drive 0.0 goes forwards
M569 P41.0 S0 D4 ; physical drive 0.1 goes forwards
M569.6 P40.0 V1 ; Tuning maneuver
M569.6 P41.0 V1 ; Tuning maneuver
; Y
M569 P0.2 S0                                    ; physical drive 0.2 goes forwards
M569 P0.3 S1 ; physical drive 0.3 goes backwards
; Z
M569 P0.4 S0                                    ; physical drive 0.4 goes backwards
M569 P0.5 S0 ; physical drive 0.5 goes backwards

; ======={ Extruders }=====================================
M569 P0.0 S1                                    ; physical drive 1.0 goes forwards
M569 P0.1 S1                                    ; physical drive 2.0 goes forwards
M584 X40.0 Y0.2:0.3 Z0.4:0.5 U41.0 E0.0:0.1     ; set drive mapping
[REST config.g IS CLIPPED]

M122 B40 (X-Axis)

Diagnostics for board 40:
Duet EXP1HCL firmware version 3.4.1 (2022-06-01 21:14:32)
Bootloader ID: SAME5x bootloader version 2.4 (2021-12-10)
All averaging filters OK
Never used RAM 52256, free system stack 169 words
Tasks: Move(notifyWait,0.0%,108) HEAT(notifyWait,0.0%,70) CanAsync(notifyWait,0.0%,65) CanRecv(notifyWait,0.0%,79) CanClock(notifyWait,0.0%,70) TMC(notifyWait,34.5%,360) CLSend(notifyWait,0.0%,152) MAIN(running,63.7%,413) IDLE(ready,0.0%,30) AIN(notifyWait,1.7%,265), total 100.0%
Last reset 00:07:43 ago, cause: software
Last software reset data not available
Closed loop enabled: yes, pre-error threshold: 0.00, error threshold: 0.00, encoder type rotaryQuadrature, reverse polarity: no, position 243, raw count = 0, tuning mode: 0, tuning error: 0x10, collecting data: no
Control loop runtime (ms): min=0.003, max=0.028, frequency (Hz): min=11719, max=17442
Driver 0: pos -48210, 80.4 steps/mm,tuning failed, SG min 0, mspos 776, reads 24967, writes 2112 timeouts 0, steps req 57854 done 13661
Moves scheduled 5, completed 5, in progress 0, hiccups 0, step errors 0, maxPrep 60, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter -1/10, peak Rx sync delay 194, resyncs 0/0, no step interrupt scheduled
VIN voltage: min 10.9, current 12.4, max 12.5
V12 voltage: min 10.6, current 10.6, max 10.8
MCU temperature: min 31.5C, current 32.4C, max 32.4C
Last sensors broadcast 0x00000000 found 0 223 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 3776, send timeouts 0, received 4215, lost 0, free buffers 37, min 37, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 292, adv 36388/37193

M122 B41 (U-Axis)

Diagnostics for board 41:
Duet EXP1HCL firmware version 3.4.1 (2022-06-01 21:14:32)
Bootloader ID: SAME5x bootloader version 2.4 (2021-12-10)
All averaging filters OK
Never used RAM 52256, free system stack 173 words
Tasks: Move(notifyWait,0.0%,108) HEAT(notifyWait,0.0%,70) CanAsync(notifyWait,0.0%,65) CanRecv(notifyWait,0.0%,79) CanClock(notifyWait,0.0%,70) TMC(notifyWait,34.5%,360) CLSend(notifyWait,0.0%,152) MAIN(running,63.7%,409) IDLE(ready,0.0%,30) AIN(notifyWait,1.8%,265), total 100.0%
Last reset 00:09:26 ago, cause: software
Last software reset data not available
Closed loop enabled: yes, pre-error threshold: 0.00, error threshold: 0.00, encoder type rotaryQuadrature, reverse polarity: no, position 163, raw count = 0, tuning mode: 0, tuning error: 0x10, collecting data: no
Control loop runtime (ms): min=0.003, max=0.029, frequency (Hz): min=11538, max=17442
Driver 0: pos 48210, 80.4 steps/mm,tuning failed, SG min 0, mspos 520, reads 64910, writes 2112 timeouts 0, steps req 57854 done 13661
Moves scheduled 5, completed 5, in progress 0, hiccups 0, step errors 0, maxPrep 60, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter 2/14, peak Rx sync delay 196, resyncs 0/0, no step interrupt scheduled
VIN voltage: min 12.4, current 12.4, max 12.5
V12 voltage: min 10.7, current 10.7, max 10.8
MCU temperature: min 34.8C, current 35.9C, max 36.1C
Last sensors broadcast 0x00000000 found 0 103 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 4599, send timeouts 0, received 5140, lost 0, free buffers 37, min 37, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 294, adv 35836/37161

homeall.g

; ========{Change to Open Mode}========
M569 P40.0 D0 S0 ; Change X to open-mode
M569 P41.0 D0 S0 ; Change U to open-mode

; ========{Home in Open-Loop Mode}========
G91                   ; relative positioning
G1 H2 Z15 F720         ; lift Z relative to current position
G1 H1 X-595 Y-459 U595 F2400 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 H2 X10 Y10 U-10 F6000     ; go back a few mm
G1 H1 X-15 Y-15 U15 F180   ; move slowly to X and Y axis endstops once more (second pass)
G1 H1 Z-650 F360       ; move Z down stopping at the endstop
G1 H2 Z3 F360
G1 H1 Z-10 F10
G90                     ; absolute positioning
G92 Z0                 ; set Z position to axis minimum (you may want to adjust this)


; ========{Move to a Safe Location}========
G91 ; Relative Positioning
G1 Z15 F720 ; Move the Z down
G1 X50 F1000 ; Move the X away from the endstop
G1 U-50 F1000 ; Move the U away from the endstop
M400 ; Wait for previous moves to complete
G4 P500 ; Wait for the motor to settle
G90 ; Absolute Positioning;-

; ========{Turn on Closed-Loop Mode}========
; ========{Perform the Encoder Tuning}========
M569 P40.0 D4 S0 ; Change X to closed-loop-mode
M569.6 P40.0 V1 ; Perform the tuning manoeuvres for a quadrature encoder;

M569 P41.0 D4 S0 ; Change U to closed-loop-mode
M569.6 P41.0 V1 ; Perform the tuning manoeuvres for a quadrature encoder

; ========{Return to Home Location}========
G91 ; Relative Positioning
G1 X-50 F720
G1 U50 F720
G1 Z-15 F720
G90 ; Absolute Positioning

I wasn't present to witness the cause of failure during the update that erased/corrupted its firmware. Which would be interesting to know and of course it was the temp's last day here at the lab (I am sure he feels bad , good kid).

If anyone knows what could cause a firmware flash to render a board unresponsive I would be interested to know.

However, I followed the erasing procedure and and using Bossa I was able to flash the most up to date firmware. Wired the machine up and printed a benchy boat just fine. Which makes this a resolved topic.

Thanks!

@jay_s_uk Thank you for the link

Here are my results:

I am in this regime:

If the firmware has been erased the DIAG/STATUS LED will glow permanently (ie not full brightness).

And:

If neither port is shown, then the Duet may be faulty or it may not have valid firmware installed. With USB power applied, erase the firmware. Only erase the firmware if your board is completely unresponsive, or if instructed to do so by Duet3D. On older boards do this by holding down the Erase button for at least 1 second, then press the Reset button. On newer boards there is no Erase button; so fit a jumper across the Erase pins, then connect to USB for a few seconds, then disconnect from USB, remove the jumper and connect to USB again. You may have to do this a couple of times if the Duet does not appear in the Device Manager.

Kind of seems like I need to erase

I was searching the forum to see if this was a solved problem, however, I couldn't find any valuable info on my issue:

The temp here at the lab was updating the firmware such that we can have closed loop control on our encoded motors.

Our setup is for a IDEX printer consisting of a D3MB6HC + two Duet 3 Exp 1HCL. We have two 17E1K-07 motors installed into the X and U axes.

We found our prints to be failing due to layer shifts in The X direction and decided to upgrade the machine.

When the temp flashed the firmware by uploading a .zip file (Duet2and3Firmware-3.4.1.zip) to the DWC sys directory, the machine now fails to start up properly. The Panel Due shows an endless "Connecting..." and we recently purchased a new MB6HC with a fresh, factory setting SD card which upon swapping, still has no impact on the machine's ability to boot up and connect.

I am out of ideas with how to regain our machine without swapping in the new board.

@jay_s_uk

Thanks for the guidance! It was out of date.

@dc42 said in CAN connectivity: Duet 3 MB6HC to EXP3HC:

@kroybal this will most likely be resolved by updating the bootloader on the 3HC.

This resolved my issue, when I updated the firmware and forgot to do the bootloader as well.

Appreciate the help!

Update:

I got in touch with Filastruder, turns out my warranty on the board was out of date. Not a problem, I purchased another MB6HC and its still encountering the same 30seconds to 45 minute sync time with the EXP3HC board.

Both are up to date firmware wise. Could it be the oscillator on the EXP3HC? I had a few other boards installed (now have been removed) so my serial port is 15 I suspect its not a problem regarding performance, but if it is I could dial that down now I have no other boards beyond the two stated.

M122 B0
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.1 (2022-06-01 21:09:01) running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-9P63L-DJ3T8-6J1D6-3SJ6L-1A73A
Used output buffers: 3 of 40 (15 max)

M122 B15
Diagnostics for board 15:
Duet EXP3HC rev 1.01 or earlier firmware version 3.4.1 (2022-06-01 21:15:27)

@t3p3tony said in Rotating Magnetic Sensor - Keeps Pausing Printer:

@wouldstain please send a M591 D0 after the pause.

Checking my understanding here: does passing a M591 DX command display the data collected during an active print, following a pause?

I am experiencing similar issues "too little movement"...

I have a 3.x firmware and the DWC just gave me very basic description of the FM when I tried to do a M591 D1/2 command (I am not at the lab so I do not know off the top of my head which firmware I have/config settings).

But I recently installed two filament monitors to my IDEX direct drive printer. They are mounted on my custom designed/printed spool holders and false signal a pause after every 3.0mm reference length has been extruded.

My filament monitoring is very meat and potatoes default settings.

M591 D0 P3 C"io1.in" S1 R70:130 E3.0;			;Driver 0.0, rotating magnet, pinname, disabled, Low 70% High 130%, 3.0mm detection
M591 D1 P3 C"io2.in" S1 R70:130 E3.0;			;Driver 0.1, rotating magnet, pinname, disabled, Low 70% High 130%, 3.0mm detection

I guess I had some confusion on the A parameter, and the agc. Its not clear how to dial in an accurate parameter for that. Any tips?

@dc42 I do not believe I was ever put into contact with filastruder, I suppose I was awaiting a response.

At any rate, I am back simply due to the same reasons stated above. We have made do with the bug (I am actively waiting for the sync LED as we speak) but I was curious of the latest Firmware updates, I believe I checked your account and checked the latest post that I could find in regards to firmware updates was your post from January 5th, 2021.

I am currently working with RepRapFirmware for Duet 3 MB6HC 3.2.2 (2021-02-11), I will have to uncover the EXP3HC firmware once its sync'd, however likely not necessary, it is still the same (if stated above.)

Anyways, I could attempt another firmware upgrade before going through the process of an exchange.

I have been having issues with the IR filament monitor. For my printer's setup, the sensor is enclosed in an SLA printed opaque part with silicone gasketing to prevent light leaks. However, my sensor will flicker a persistent green even when there is no motion. I have had to disable FM for the past month due to the boards inconsistencies. This has persisted even after cleaning the sensor with air, and a gentle dusting with a PEC Pad ensuring the sensor is clear of dust/debris.

How does the board handle its signal output? Is it some square wave PWM signal that's producing some (I say this arbitrarily) 50% DC as its high/motion detected state and 25% low/no motion? I am trying to read into the led flickering and make sense of what is occurring behind the signal its providing to the board.

My DWC reports back over extrusion print paused and in other cases, I have experienced under extrusion where the behavior of the LED color indications: R R R R .... G
during phases of constant filament feeds.

There are parameters I can dial in such as reference length which I would imagine takes some delta of the signal output and converts signal into a length of motion required to produce the trace. I just don't see this helping my case, because I believe it is at a hardware level and not a software level.

I am digging deep into the PCB circuitry logic at this point, but I have done so because I feel like I have exhausted many of my fixes.

I haven't seen any information on resellers/forum posts about the duet magnetic filament monitor. Although I did see that someone was attempting to make a DIY which I must confess, I have considered doing the same.

Preferably I would rather purchase two, Is there any ETA as to when they will be restocked?