IDEX Upgrade VCore 300

I just finished connecting in everything for the IDEX upgrade on my RR4 300 and when I go into configurator, select IDEX on the 300 and walk through it shows T0 twice, not T1 - at the end I can't create the config because it doesn't know about axis 1. I checked on the pi and I can see both toolboards so not sure what's going on.
pi@Ratatoskr:~ $ lsusb
Bus 002 Device 002: ID 2109:0817 VIA Labs, Inc. USB3.0 Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 012: ID 1d50:614e OpenMoko, Inc. stm32g0b1xx
Bus 001 Device 004: ID 1d50:614e OpenMoko, Inc. stm32g0b1xx
Bus 001 Device 008: ID 04d8:e72b Microchip Technology, Inc. Beacon RevH
Bus 001 Device 010: ID 1d50:614e OpenMoko, Inc. stm32f446xx
Bus 001 Device 006: ID 046d:08e5 Logitech, Inc. HD Pro Webcam C920
Bus 001 Device 003: ID 2109:2817 VIA Labs, Inc. USB2.0 Hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
pi@Ratatoskr:~ $ lsusb
Bus 002 Device 002: ID 2109:0817 VIA Labs, Inc. USB3.0 Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 012: ID 1d50:614e OpenMoko, Inc. stm32g0b1xx
Bus 001 Device 004: ID 1d50:614e OpenMoko, Inc. stm32g0b1xx
Bus 001 Device 008: ID 04d8:e72b Microchip Technology, Inc. Beacon RevH
Bus 001 Device 010: ID 1d50:614e OpenMoko, Inc. stm32f446xx
Bus 001 Device 006: ID 046d:08e5 Logitech, Inc. HD Pro Webcam C920
Bus 001 Device 003: ID 2109:2817 VIA Labs, Inc. USB2.0 Hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
So the toolboard is recognized by the pi but ratos doesn't seem to see it?
Solution:
I'd run through the configurator again. The beacon section should absolutely get fully populated
Jump to solution
10 Replies
TheTik
TheTik2w ago
Theres something in the UI that trips people up there in the configurator but I can't remember. Try searching this discord and you should find the answer.
k1bbles
k1bblesOP2w ago
The answer was I'm an idiot and tried to reuse my old config rather than "start fresh". So I'm past that now but now klipper is complaining about "Option 'serial' in section 'beacon' must be specified" -- which is new to me (everything worked great pre-IDEX!).
TheTik
TheTik2w ago
do you have a beacon installed? Did you select Beacon as your z sensor in the configurator?
k1bbles
k1bblesOP2w ago
Yes, on T0. T1 has no sensor. Pi can see it:
Bus 001 Device 008: ID 04d8:e72b Microchip Technology, Inc. Beacon RevH
Bus 001 Device 008: ID 04d8:e72b Microchip Technology, Inc. Beacon RevH
Solution
TheTik
TheTik2w ago
I'd run through the configurator again. The beacon section should absolutely get fully populated
k1bbles
k1bblesOP2w ago
Is it possible T0 and T1 are reversed somehow? I guess I'd have to check the USB config. Nope - reconfig seemed to find it. Thank god, those parts fans are so loud until the PWM pin comes online.
TheTik
TheTik2w ago
lol, no joke
k1bbles
k1bblesOP2w ago
Well that was fun - homed all axis and both tool heads zerod along with Z, went to do a beacon calibrate and the bed crashed. My own fault, I hadn't tucked the T1 cabling into a safe place and it got caught and pulled the usb-c out which crashed everything. Trying again without the stupidity.
TheTik
TheTik2w ago
Tried and failed to find a clip of the scene from Independence Day where Jeff Goldblum says, "Yes yes, without the oops."
k1bbles
k1bblesOP2w ago
Basically yes! Words to live by. I dunno if I trust T1 to try printing with it but I think I can at least print with T0 again at this point once the beacon recalibrates. Then have to print the VAOC part that I thought would be included but, apparently, is not.

Did you find this page helpful?