Posts made by kroybal

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?

@dc42 I will get in touch with my boss and owner of the machine. I believe he got it from filastruder.

@dc42
IMG_2245-2.mp4

I verified the build time. Following the firmware update the reset worked my first go at it, the second go at it took about 10 seconds before the LED powered on.

The attached video is capturing the third and fourth attempt at resetting the board. I had to reduce quality and cut the video short but the fourth attempt was about 50 second connection, and I tried once more after that and it was immediate.

If firmware updates have an effect on the behavior of the LED/connection, could that be suggesting that the board has the potential to work? I have have seen an improvement, we started at the range of 10-30 minutes to connect and now we're down to the range of immediately to 50 seconds tops.

@dc42 Sure thing, I will be leaving the lab today in 15 minutes so I will likely get back to you by tomorrow. Hope that is not too much of an inconvenience.

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

Thanks. I'm sorry to hear that it is still taking a long time for the 3HC to connect. Does the LED on the 3HC start blinking rapidly as soon as it is powered up, but then take up to 45 sec before it blinks slowly to indicate CAN sync? Or does the LED remain off for up to 45 sec from power on; but having started blinking rapidly, it then establishes sync within a couple of seconds? Or something else?

The light is not on for the 45 sec duration, then flickers for about 3 seconds before syncing up with the MB.

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

I can authorise a warranty exchange of the 3HC if you wish. Unfortunately it will take some time for your board to reach me here in UK, so this won't help me to diagnose the cause in the short term.

Sure thing, do you think this issue is unique to my board or is this issue common at this time? If it is not necessary, we could hold off on exchanging the board. If the problem does persist and/or is unique to my board, then we may have to go that route . So we can eliminate the possibility of this board slipping through a crack in QA and being unfixable for my purposes.

@dc42
I updated with the new binaries and confirmed the firmware date with an M115 command on both. They both reported back 2021-02-01.

Upon restarting the boards (via toggling the power switch) the 3HC was connected in under 10 seconds. I am a fan of repetition so I tried again and now its connection time is in the bracket of 30-45s following power-up.

Certainly an improvement, however, might I suggest a message to the console stating an established connection.

Another point I would like to note is that once the board is connected my endstops are not active until I press "STOP" on my pannel Due or emergency stop via the DWC and wait for a connection. Using a software reset does not cause the 3HC to lose connection.

@dc42 I was absent from work Friday due to family reasons and do not normally work on weekends. I'll update the boards and report back to you.

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

3. What board revision is your 3HC?

For record, it is a V1.0 board

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

Which country are you in?

Central U.S.

One difference I have noticed is that my EXP3HC board flashes without sync now and does not connect to the mainboard whatsoever even after waiting over five minutes at this point.

@dc42 I have installed the updated EXP3HC and it seems like the problem is still persisting.

Here is my M122 command for both boards

1/28/2021, 10:01:52 AM === Diagnostics ===

RepRapFirmware for Duet 3 MB6HC version 3.3beta running on Duet 3 MB6HC v1.01 or later (standalone mode)

Board ID: 08DJM-956L2-G43S8-6JKD8-3S06K-9B2GD

Used output buffers: 1 of 40 (13 max)

=== RTOS ===

Static ram: 149784

Dynamic ram: 92536 of which 0 recycled

Never used RAM 108352, free system stack 200 words

Tasks: NETWORK(ready,254) ETHERNET(blocked,111) HEAT(blocked,305) CanReceiv(blocked,909) CanSender(blocked,365) CanClock(blocked,334) TMC(blocked,52) MAIN(running,1120) IDLE(ready,20)

Owned mutexes: LwipCore(NETWORK) HTTP(MAIN)

=== Platform ===

Last reset 00:00:13 ago, cause: software

Last software reset at 2021-01-28 09:57, reason: User, GCodes spinning, available RAM 108312, slot 2

Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a

Error status: 0x00

Aux0 errors 0,0,0

Aux1 errors 0,0,0

MCU temperature: min 38.6, current 40.3, max 40.5

Supply voltage: min 24.3, current 24.3, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes

12V rail voltage: min 10.8, current 12.6, max 12.8, under voltage events: 0

Driver 0: position 0, standstill, reads 10313, writes 14 timeouts 0, SG min/max 0/0

Driver 1: position 0, standstill, reads 10313, writes 14 timeouts 0, SG min/max 0/0

Driver 2: position 0, standstill, reads 10313, writes 14 timeouts 0, SG min/max 0/0

Driver 3: position 0, standstill, reads 10313, writes 14 timeouts 0, SG min/max 0/0

Driver 4: position 0, standstill, reads 10314, writes 14 timeouts 0, SG min/max 0/0

Driver 5: position 0, standstill, reads 10314, writes 14 timeouts 0, SG min/max 0/0

Date/time: 2021-01-28 10:01:53

Slowest loop: 4.11ms; fastest: 0.05ms

=== Storage ===

Free file entries: 10

SD card 0 detected, interface speed: 25.0MBytes/sec

SD card longest read time 2.3ms, 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 = 3 -1 -1 -1

Heater 0 is on, I-accum = 0.0

=== GCodes ===

Segments left: 0

Movement lock held by null

HTTP is ready with "M122 B0" 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.

=== Filament sensors ===

Extruder 0: pos 0.45, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0

Extruder 1: pos 3.66, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0

=== CAN ===

Messages queued 74, send timeouts 0, received 20, lost 0, longest wait 1ms for reply type 6018, peak Tx sync delay 493, free buffers 48 (min 47)

=== Network ===

Slowest loop: 6.40ms; fastest: 0.02ms

Responder states: HTTP(0) HTTP(0) 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: 5 2 2 2 2 0 0 0

1/28/2021, 10:02:36 AM M122 B15

Diagnostics for board 15:

Duet EXP3HC firmware version 3.3beta (2021-01-28 09:11:08)

Bootloader ID: not available

Never used RAM 155236, free system stack 0 words

Move 160 HEAT 103 CanAsync 72 CanRecv 84 CanClock 74 TMC 64 MAIN 339 AIN 260

Last reset 00:00:13 ago, cause: software

Last software reset data not available

Driver 0: position 0, 80.9 steps/mm, standstill, reads 46408, writes 16 timeouts 0, SG min/max 0/0, steps req 0 done 0

Driver 1: position 0, 80.9 steps/mm, standstill, reads 46410, writes 16 timeouts 0, SG min/max 0/0, steps req 0 done 0

Driver 2: position 0, 80.0 steps/mm, standstill, reads 46419, writes 11 timeouts 0, SG min/max 0/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 12, peak Rx sync delay 174, resyncs 0, no step interrupt scheduled

VIN: 24.4V, V12: 12.2V

MCU temperature: min 43.6C, current 43.6C, max 43.9C

Ticks since heat task active 90, ADC conversions started 13832, completed 13831, timed out 0

Last sensors broadcast 0x00000000 found 0 94 ticks ago, loop time 0

CAN messages queued 33, send timeouts 0, received 136, lost 0, free buffers 36, min 36, error reg 110067

dup 0, oos 0, bm 0, wbm 0

Very coarse statistics on my setup suggest about a 1/15 shot at lighting up upon startup, and 2 minutes light-up-and-sync time in the case of a startup failure.

Does this have to do with the crystal oscillators not powering up still or simply waiting for the signal from the boards to be in phase?

@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