Advanced Search

Not exactly sure what this is all about, but
1. RPI is not a good choice anymore, there were several hardware versions of RPI5 with many issues
2. There is a ready made image for RPI5 that works out of the box
3. SPI does/did not work at all on RPI5, but Scot has done some work on it so by now it probably works
4. To expensive for what it is
and personally (after buying 3 of RPI3)
5. having a very small SBC controlling a big machine is ...
6. to damn weak for comfortable use
7. to much hoops to jump just to get things working, so utmost respect for whoever made the images
8. for the same price a good used PC or laptop can be bought, and everything works.
-
As for making user experience better, utmost respect, see with ScotA if he needs help with SPI

7i84 has two separate V-Field power supply inputs, so it should be easy to have one set at 24V and the other at 5V, granted everything has the same ground/0V.
Not sure that affects the inputs, but it does outputs as far as i can recall i have one such setup i did many years ago, so a bit fuzzy on details.
Either way, the 4 inputs should work as is with 5V when set to MPG mode, again if i recall correctly.

I ran a couple of tests this morning to see if I could figure out why the velocity started working OK. These two scope captures are both at 200 RPM, running the same threading program. It shows me that 10 teeth is not adequate for some operations, and that I should modify the spindle with a new gear with more teeth. I'm thinking I'll do 180 teeth/rev. It'll take me a while to make the modifications.

I don't expect this to fix the original problem of threads not aligning at different speeds, but it should fix the slightly varying thread pitch..

HAL using: net spindle-position encoder.0.position => spindle.0.revs



HAL using: net spindle-position encoder.0.position-interpolated => spindle.0.revs



 

The scale is odd because you have the .00035 scale factor (so the full scale value (to get PWM=1) is 2857 )

Do you need the scale component? Eliminating it and setting the output scale to 24000 would certainly
simplify debugging.

With the existing scaling, setting the output scale (and max output) to 8.4 should be about right:

MAX_OUTPUT = 8.4
OUTPUT_SCALE = 8.4
OUTPUT_MIN_LIMIT = 1.75
OUTPUT_MAX_LIMIT = 8.4

But why would you do that?

MAX_OUTPUT = 24000.0
OUTPUT_SCALE = 24000
OUTPUT_MIN_LIMIT = 5000
OUTPUT_MAX_LIMIT = 24000

and no scale component is 100% easier to understand


 

Thank you cornholio.

I'm looking to cut wood for building boats.

If I run into issues doing the above well, I earned a living doing Unix driver and kernel work a while ago; I would like to contribute now if I could. I have experience with a number of device driver debugging and kernel development techniques.

Let me get some hardware and software in. Again, if there is a certain feature that doesn't work that should work, let me know.

Thanks,
Tom Alborough