In case anyone was wondering. I was able to figure it out. After hours of teardown I determined that the geometry was off on the trucks that I was using on each tower; there was too much flex and it caused an excessive amount of bowing on the arms, resulting in effector tilt that I could not see when it wasn't moving.

I did not want to go back to the SeeMeCNC trucks so I finally found the, now defunct, trick laser trucks. I searched around the internets for a while and found the cad model for them and tweaked the mounting holes to have the proper geometry for Hayden's ball-cup arms. We're back in business.

The ripple that I was seeing before is completely gone!

@dc42 That seemed to fix it. Just updating alone to 3.5 was enough to handle the filament sensor, but when I enabled the end-stop it crashed again. I had to reduce a little further so I also reduced buffer sizes for UART.

Everything works together now. Thank you for your help! I have a bunch of manual macros working now so I just need to automate it all.

I dropped back to 3.5_DEV on CANLIB and the error went away. Still get a warning but it compiles now.

@phaedrux

Sorry, I should clarify just a little more.

It works, in that, the probe deploys but it will return to the origin that I defined via G60 and probe, NOT the G30 coordinates that I specified.

I just updated so I'm running 3.4

If you decide to undertake the ERCF, hit me up. I have a few boards that I made. You can't buy just one. I also made some adjustments (manually) to the board to solve the servo issue experienced by some.

I'll post about it later in another thread once I get it a little more automated.

@EdChamberlain It's working but I've taken small breaks to build some other hardware.

The core of the SB2040 toolboard is working great. I am looking into I2C in order to add an LIS3DH accelerometer, but the I2C libs aren't wired up into the RP2040 yet.

I had a few issues with my environment and now can compile both the 3.5 code for RP2040 and Jay's branch.

Does anyone know when I2C might be ready to test on the RP2040? I'm digging around but I'm getting a little lost.

@infiniteloop Cool, thank you for that! Let me break that down a bit over the next couple days but I think it makes sense.

@oliof Good ole Forest Mimms, I had a few of his books from Radio Shack when I grew up.

I will have to check this out, I was considering something like that but was leaning towards something already manufactured. This is cool!

@rexx I'd be willing to give you a hand. I'll message you privately.

I am planning to make a few but I've been delayed by a few weeks. I may decide to just place a big order once I'm done with the first, I'll post here when I do. If you're interested send me a message and I'll direct my communication to those people interested.

@VoodooBane I don't know, I haven't seen them online for quite some time. It's pretty simple, however, to update and compile the firmware. To be honest it's been a hot minute since I touched it last.

I was looking around for someone else and either I sold them all or completely lost them in my shop

I am considering a new order of them, if I get enough interest it would push my decision up a notch.

@OwenD Haven't touched it in a hot minute, but as I recall that I had a custom firmware to handle the two steppers. Are you still looking for this?

EDIT: I found the firmware I used, it was the one originally from @Gixxerfast , you'll need to compile it: https://github.com/gixxerfast/Duet3Expansion/tree/cannedboard

@VoodooBane Hey there, sorry for the delay. I might have a couple left, let me know if you're still interested.

@Herve_Smith That works

@Herve_Smith yeah, I can see them. I was meaning that I’d like to see the cad files if you’re sharing.

@Aitor I've seen some issues with my 5+ mini disconnecting from WIFI as well. Best I can tell is it's not a problem with the config or the board itself. It's possible that there's an issue with the WIFI firmware, but I haven't narrowed it down yet. What seems to be at the root of my issues is the AP itself. I'm running EnGenius wifi around my house.

Both 2.4 and 5g bands are broadcast on a single SSID and allows for WIFI6. Very intermittent issues for the Duet boards (non sbc) in my house.

For my printers I created a special WIFI which only provides a stripped down 2.4g signal. This seems to have addressed it, so I've just forgotten about it since then

Happy to do some troubleshooting but I would certainly start by looking at your AP wifi settings, I have a hunch that it could be related to providing b/g/n/ax from the AP while providing only the 2.4b/g SSID addresses it.

Again just theory based on my experience.

@Herve_Smith I'd be interested to see what you've come up with. Always looking for ways to modify my Voron 2.4

@rjenkinsgb

You can update your code to point to these two repositories:
https://github.com/th0mpy/wizio-pico
and
https://github.com/th0mpy/framework-wizio-pico

As I recall, that's all I had to do. Let me know if that works and I can double check my DEV VM when I get home later.

@rjenkinsgb Yeah I'm around

I will need to double check but I do have a repo which does work. Give me the morning to look it over and I'll link it here.

@EdChamberlain It's working but I've taken small breaks to build some other hardware.

The core of the SB2040 toolboard is working great. I am looking into I2C in order to add an LIS3DH accelerometer, but the I2C libs aren't wired up into the RP2040 yet.

I had a few issues with my environment and now can compile both the 3.5 code for RP2040 and Jay's branch.

Does anyone know when I2C might be ready to test on the RP2040? I'm digging around but I'm getting a little lost.