u/FitBroccoli19

I'm trying to figure out whether this can be done entirely within SimHub using its scripting/formula capabilities.

My controller is an STM32 running FreeJoy. I have multiple 12-position rotary switches connected to it. It behaves as an absolute switch: each position corresponds to a separate joystick button, and the button for the current position stays permanently pressed.

So essentially:

• Position 1 = Button 1 held
• Position 2 = Button 2 held
• ...
• Position 12 = Button 12 held

I'd like SimHub to treat this as if it were a normal incremental rotary encoder.

For example:

• 4 → 5 = CW
• 5 → 6 = CW
• 5 → 8 = 3 x CW
• 5 → 4 = CCW
• 1 → 12 = CCW
• 12 → 1 = CW

Since the current position is always held, SimHub could also determine the initial position when it starts without generating an input. It would then only need to remember the previous position and compare it against the new one whenever the switch moves.

Ideally I'd like to end up with two SimHub events/actions, CW and CCW per rotary switch, which I can map like the outputs of a normal encoder.

I specifically want to solve this inside SimHub. I don't want to modify the FreeJoy firmware or move all devices to a new microcontroller, because on Arduino i solved this already.

From what I've seen in the past, i would not be surprised if there is a way to create these 2 new virtual inputs based on that logic.

Has anyone done something similar, or is there a good way to create these CW/CCW events per a defined set of 12 inputs? I can work with JavaScript and have the feeling i am just one nudge away from knowing where t start.

Thank you for anything that leads me in the right direction!

Whoever needs to read this, this may be very specific use case i am in, but i am currently running 160TB in 12 HDDs + 1 Parity, filled to 95% capacity and after some days of rearranging files lowered my power draw significantly.

The files on there are very different from Backups, Media, OpenCloud, Personal Projects etc. BUT over time you notice patterns in your use time at different times of the day/week or in usage like: if i am using THIS share i am not working on content in THAT share.

I started probably like everyone else, running High Water distribution, not limiting drives and just collecting data.

(i know about split level, but it sadly falls apart quick, because split levels is ignoring remaining space rule per drive and you will run into out of storage errors, despite other drives on the same share would have space. Accounting for that does need even more prediction and knowledege about your current and future usage)

Now i consolidated and limited most of my shares content to specific drives and this ultimately resulted in 8 of 12 drives are basically off for 2/3 of the day, when before it was 11/12 running 24/7 just because everything was so scattered.

This is not news to veterans and if you know beforehand how your usage is, but if it is like on my system that grew over 2-3 years and got the occasional new HDD you will find yourself with the back to the wall and have to find time to invest the effort to restructure.

I am glad i did and from monitoring it for 2 weeks i cut the operating costs in electricity in half.

I wont get into how good or bad it is running disks 24/7 or have them start once in 2 days, thats a rage bait for another day.

Since day 1 i have connection issues when trying to send a print to the U1 from SnOrca. Latest version everywhere.

Its often taking outrageous long on the following screen

​And will end in this suddenly.

​This can happen multiple times in a row and i just try again until it works.

But when it works it then works basically instantly. So everytime i see the orange button and crawling progress i already know that this will fail. Does not matter if its a 60MB Gcode or 2 MB.

In the meantime after i selected the printer in the dropdown i also get little "Timeout" notifications at the bottom while still being connected to the printer, which i know because a few seconds after that "Timeout" it finishes syncing filaments an i can proceed.

My P1S in the same wireless network standing right next to the U1 had no such issue in 2 years, regardless of the network mode.