yes this is a requirement now. nonstandard modules require a virtual environment (venv) in a folder. Google python venv

Pid maxoutput limits in the positive and negative direction. So, you can set maxoutput to 1.0 and it will limit the output in the range of 1.0 to -1.0

I'm not sure what it would take to prevent windup below 0.

For what its worth, one thing that has bit me in the past in trying to tune PID and lots of troubles with windup: slow vfd accel/decel. If the PID is tuned to respond faster than the ramp time of the VFD, that'll wind it up.

Also, a hal limit1 component might be in order to prevent sending a negative voltage to the vfd analog input, some kinds smoke when they get negative signals.

Bob has 5v using usb.
I'm only working with 5v now to get step/dir outputs working.
I will connect the 12v supply to run the spindle.

I've started wiring and testing my custom RIO board and everything is looking good so far.

Is there any option to have a watchdog on the outputs? So if the computer crashes or loses connection the outputs will turn off?

Also are there any examples anywhere of controlling a spindle VFD over modbus with RIO?

This can be done with 5 7I84U outputs and 6 7I84U inputs in conjunction
with the matrix_kb component

If you expect to press more than one switch at a time
you need to add one diode per switch

I'm pretty sure there are examples of this on the forum so a
search for "7i84" and "matrix" might find something...

Hello Folks, 

I searched, but not much came about multiplexing the IO on a 7I84U or other mesa card. My panel will have 28 push buttons, 3 pots and one MPG. I could wire everything to the 7I84U, but with a 5x6 matrix I can mux all the switches, saving IOs. 

How can this be done? Examples would be much appreciated.

Greetings  

Also note that the pre-installed firmware on a 7I97T fully supports the standard analog and digital I/O
You typically only need different firmware if you have an added parallel daughtercard

Analog output problems are most likely a hal file or tuning/polarity issue
 

sure it does support .ngc

my s-curve blending is comparable to the current TP, there is some loss, but it is unavoidable, but not in mills or more range.

I think a custom hal component will be the ticket for this ram control. I envision a glade user interface, separate reusable custom components for each backstop axis, and a custom component for the Y axis (upper beam height control.)

Different brands of press brakes would get their own  Y axis component, due to complicated variations in hydraulic configurations among the different makes and models.

Bend programs will be loaded in the python userspace gui app as a list of dictionaries containing positions for every single axis for the machine.

Stage two of my dream will be to write a python based app allowing the user to enter dimensions and angles, then create the bends file that the press gui can load.

Attached preliminary work, don't try running this one, it is incomplete yet.

I am wanting to write a couple of simple python3 scripts to automate some functions in LinuxCNC using the python linuxcnc module to send NML messages. I did this several years ago for another project and it was very successful. In this new application I am using a pi5 8GB with a Mesa 7i96s running Trixie 2.9.7. The basic installation is working well and the CNC is operating great so far (without any python automation). 

I am a little confused about using python on Debian Trixie. When I try to install a package I get errors and the terminal prompts that I should use a virtual environment for python and packages. If I do this, will my python scripts still connect to the running instance of LinuxCNC? Please help me understand the basic structure for using python on the Trixie OS with LinuxCNC.

Thank you,
HH

If you will test it .. please share some visual results before and after{for example scope printscreen) .. We are all interested in your pr I think !

thanks

I think there is much more to do and to finish because there are great jitters during running cloud of point... it can not approximate it and the computations last too much time(sometime mills and more) to finish ...

for signle G2 G3 it is working well ... 

I have talked with Michel, he said, he ends with lcnc and tp at all ... 

Now it is on us ...

The PR has been merged to linuxcnc-ethercat I have some testing modifications which I have not been able to test yet, will update here after I test myself, might be another PR before everything is proper.

I run M130 in the terminal every time and the error persists.