Nothing to be sorry about at all!
I’m worried about the next part. I figured out what the ws pin is, that’s an i2s communication not i2c. I2s is 3 wire, i2c is 2…. Off to research more
stumbled on this…I2C/SPI GPIO expander support? - Features - Klipper
Yeah it seems i2c expanders are good to go. But from looking at the jackpot it uses an i2s expander. That’s where the 3rd pin comes in and I haven’t found a way to make that work in kipper yet. Now I know nothing about i2s so can it run without the 3rd pin? Something says I doubt it but I really don’t know. Trying to read as fast as I can lol
1 Like
I can’t figure out what to use as a section header. maybe 2 will do it?
[fan] doesn’t work 
1 Like
https://www.klipper3d.org/Config_Reference.html
This page lists them all from top to bottom lol
But don’t add any heaters or thermistors yet. Once you do it will trip error till it sees the thermistor
Okay I am done for the evening, thank you for helping.
1 Like
No problem at all! Glad I was able to!
You can use just one pi. It can handle klipper host, moonraker and mainsale (and more).
For a long time I had klipper host and octoprint on ine pi. That worked mostly. But there were some dumb things that weren’t well supported by the octo-klipper plugin. Mainsail works pretty well. I do miss octoprint though…
Now I have that trio and klipper screen for the hdmi touchscreen.
For this situation I believe he has to have the second pi. The pico on the jackpot then the standard rpi running everything else.
Klipper allows multiple microcontrollers per host.
1 Like
Oh. I don’t think of the pico as a pi. I hate that raspberry made a microcontroller. My bad.
3 Likes
Yes I know. What I am saying is I don’t think the pico is enough to run the firmware and all of the other stuff at the same time. So having the firmware on the pico and his second pi attached usb will be the way he needs to run it.
lol now it makes sense. And I am just assuming that Ryan was calling it a pi. Hell we might all be talking about something different at this point lol
Its is a silly thing to be angry about before 6am. But every other pi runs linux. Now I have to say things like, “any pi can run bash (except the pico)”. They should have called it a raspberry tart or rhubarb pi or something.
4 Likes
Yes, I feel the same way. Really awesome, affordable peripheral- with the dumbest name ever.
One of the secrets of how Bart Dring and company got the ESP32 to work with the unique IO expander design is that their implementation makes use of some special hardware acceleration in the ESP32 that was built in because the limited number of onboard GPIO was a regular concern of ESP32 customers.
This is the limitation that has prevented others from implementing similar support- other microcontrollers don’t have that hardware.
The Pico microcontroller has a similar trick up its’ sleeve in the form of the PIO engine. This is unique hardware on the pico which can handle special interface definition and acceleration. The path forward for putting Jackpot board support on the pico microcontroller is, in my opinion, going to require putting the Bart style IO expansion into the PIO for acceleration.
Doing that is above my limited coding ability- but probably not above others in this community (and certainly not above the broader open source community).
Trying to bit-bang the Bart style IO expansion through a microcontroller that only has a 12Mbps USB1 interface is why there are warnings about using a GPIO expander through the pico. Using the pico’s PIO is the only way I can see to make the full functionality work.
It could, of course, be just a limit of my own imagination. But the need for a pico-specific, Bart-style IO expansion set of code seems clear to me.
2 Likes
Don’t disagree. And it’s all well above my pay grade lol. I was just looking for anything that could be helpful to Ryan trying to get it setup. I knew klipper had support for i2c but I kept seeing i2s in the jackpot info. That was throwing me off so I went searching. That 3rd needed pin is where the issue with klipper is going to be I think. It might be something simple as just adding it in there but I doubt it. The hardware can run it fine. But getting klipper to control it is going to be the hard part. I searched around the klipper forum last night and couldn’t find much about i2s and what I did find was all for screens and stuff. Hopefully it’s something simple that I just don’t know about or how to search for
1 Like
Well if nothing else that new board will let most other fluidNC board. I have no issues with that. It would be nice to show up to RMRRF running a printer on a non-biqu board. Obviously it would be way cooler if it was the jackpot.
I also thought the only issue we were going to have was the three extra drivers. I didn’t know the first three would also be an issue. Shows how very little I actually understand the jackpot.
1 Like
I thought the first 3 didn’t run though the multiplex? What issue are you having with those?
I never got them running last night. Chugging some coffee and diving deeper.
From my (very) limited understanding, we are shooting for SPI to I2S?
1 Like