On the SBC side of the house. I had an idea to write a X Window app that is basically the PD layout. People may argue why not just run DWC? But in my mind this app would basically be the PD and screen for the SBC at the same time. and not connect via network but direct to OS&DSF. Basically klipper screen concept for RRF+SBC makes obtaining a touchscreen for your RRF printer really easy hardware wise.
I think this a great idea but lack the skill to actually make it haha. I'm useless that way 
@honeycris I think you be better off replacing the fuse with the same size that blew. Then move that 800W bed onto its own external mosfet and power line.
@shifu87 The issue is when the motors are not powered the can free spool and the weight of that 360mm bed can make one side or the other drop. Anti backlash nuts help with this but its not a 100% fix. Also when you power the motors back on they will jump to the nearest step. Over time this drift will make your bed not level to the x axis anymore and you have to manually correct it. With two Z controllers you can let your probe and a macro just fix it for you from time to time.
@fcwilt Yep Thanks for the help Put my settings inside the loop like you have. Works perfectly.
I got it... I love it when a plan comes together... Found the correct GPIO pin:
#68 located in device /dev/gpiochip1
thanks for putting up with my noise everyone
If you have one of these SBC's feel free to hit me up if you run into issues.
@nurgelrot Nope. Don't use this one either It cools the board but causes it to drop below 4.6V from time to time... Who would think it so hard to find active cooling that works. Guess I'll wire a Noctua 40mm 5v right of my 5v PSU. Was hoping to not have to do that but since no one can make simple fan that doesn't block the header or screw up the voltage...
@reflexlab Well other only time I've seen it suck in Connecting like that and my config was right I had Tx -> Tx and Rx -> Rx rather than having them crossed so the PD and board couldn't actually hear each other. If that's not it try reflashing the Firmware on the PD at that point your sorta out of options.
Oh and just confirm you're plugged in IO.0 on the duet right? Or are you trying to use the ribbon cable?
Also looks like you might be on <v3 firmware on PD based on the location of the "." between the numbers. if your on firmware V3 on the Duet you probably want to update the firmware on the PD anyway. Don't know what the compatibility is between version but everything current is usually the best way to go.
@phaedrux said in Ask user to set bed temperature before bed mesh probing:
M291
How about writing a conditional macro placed the start gcode in your slicer to load a low|medium|high heightmap based on printing temp?...
Not that it's perfect and will require some changes from your config. But : https://github.com/Nurgelrot/RatRig-VCore-3-Configs/
I suggest you joining the RatRig Discord server. the Duet channel there has a few people to help with that specific printer.
@fart_plume Right. That's correct. they only receive data during a print. should switch to :
Pulse-type filament monitor on pin io4.in, enabled, sensitivity 7.000mm/pulse, allowed movement 50% to 200%, check every 15.0mm, no calibration data
while printing. I cant remember what condition they collect calibration data under... if in doubt cut the filament.
I have 2 PanelDues v3 (fysetc version) running the new 3.3 release of the paneldue firmware. When using the Dark Theme1 The Home buttons don't always update their color to indict that the axis are homed. Also the Progress bar on the Status page for a print doesn't update - never fills in as the print progresses. Did something change in a config I can update or anything else I'm doing wrong? Or is this something that got missed?
@keyz182 Man both myself and my browser's search function are blind.... okay well i set it the way i should have it through dumb luck. I can live with that.
Okay using a different 1.7b pcb and v1 mechanical parts I was able to show that its the mechanical side of the sensor that's causing the error. Probably the housing... so Not much anyone can do here to help I'll just have to make a better housing. Thanks for letting me ramble
@thebiologist Shouldn't
M92 X160.00 Y160.00 Z8000.00 E873.08
That be Z1600 for 32 microstepping? Not sure I always just use 16 and interpolation.
Most model displays in the control screen of printers are just preview images created by the slicer. That I think could be implemented in a redesigned PD. But live rendering? I would not want this. Massive waste of resources in your control screen (even if it was technically possible). If you really what this, do it via DWC and the Gcode viewer plugin on a tablet display don't burden the Panel Due.
I used to struggle with the PD's UI. You see other products and they look really cool and at first glance the PD looks so dated. Then I actually print something and realize that everything I really need to see is on the PD and is easy to read. Actually elegant in its efficiency.
@war4peace Sure you can't find a similar spec fan in 24v? that will cut your amps and will all be connected to the same power so less chance of something going wrong wiring voltage right from VIN(or the PSU supplying VIN rather)and signal to an OUT.
Okay Solved. Housing had the magnet too close. I shimmed it with 5 layers of 20# paper. that got the agc up to 112 and the mag down to 128 and its giving reliable readings. Going to modify SLT that I already fixed the screw hole size on to make ~.5mm more space for the magnet when using resin
Here is my known good working very well ender 5 plus configs for you to pick over and see if something jumps out. I have converted to Direct Drive with a .9 stepper on the bondtec extruder and I have tweaked my endstops to give me a bit more bed space. Just to be aware.
bed.g
config.g
homeall.g
homex.g
homey.g
homez.g
Hope this helps you find your gremlins.
@Nurgelrot UPDATE @gloomyandy helped me identify someplaces where the macro could make better use of available stack space by loading some local varables with some expression results rather than parsing it all in one go. Fixed the problem. He specualated that in the Mini5+ and even some of the STM32F4xx boards that stack space was already pretty low in 3.4.6 and 3.5 pushed it over for this particular use case. Something for people to keep an eye on.
@knutselsmurf The centered "." between the numbers tells me you on <=1.24. Flash your PD up to 3.2.x... as see if that helps.