Advanced Search

techav.net/post/664846828623298560/point...etary-parallel-ports

Not sure what the easiest path is here but I see a couple options:

1. With pncconf, make a normal step/dir 7I76E configuration and a normal 7I77 configuration and merge them

2. Use pncconfs discover option

You are awesome! Thank you!

That was the final thing stopping me from continuing the retrofit.

After increasing the FERROR and MIN_FERROR in the ini I have tuned the X axis. I will get the Y and Z today.

now that we have checked my firmware, how do I blend my hal file for the step and direction on the 7i76e

I tried this but I got an error like
./my-mill.hal:57: Pin 'somePin' does not exist

This is not correct syntax to connect two pins in hal:
Correct syntax is (<= and => are optional and are only to improve readability)

Hello to all.
I'm trying to build a custom GUI with pyqt5 for raspberryPi 5.
My linuxCNC version is 2.9.3, python version is 3.11.2.

I wanted to watch a input pin status whenever it changes.
I create a net in my hal file.
After I created this net, I can see the pin and its changing logic from hal show with axis GUI.
I examined the qtplasmac_sim_handler.py and tried to make connections as on it.

Here is my custom GUI's handler file
with this setup I cant see any changes. It only fires one time "Changed", and after that there is no information...

My guide qtplasmac_sim_handler.py did like I was...

What is my fault?

Basically the issue is that the RPI4 Ethernet interface is connected via USB
and USB is not suited for real time.

For a RPI4 I would use a SPI interfaced device, The RPI5 (or most PCs) are fine with Ethernet
LinuxCNC motion controllers because their Ethernet hardware are not USB devices.

Tutorial 19



JT

vidgabor@gmail.com wrote:

No. It's an 3 axis mini milling machine, with three steppers. I use step-dir interfaces.
 

Hi This email address is being protected from spambots. You need JavaScript enabled to view it.,

Have you managed to get it to work, please? I am asking because I am thinking of trying out the same set up. I have a Raspberry Pi 4B with 8 GB and real-time kernel. I have not bought a MESA 7I96S yet. But I am planning too.

Thank you and best regards,

...behai.

Yes, I was in a rush and was focusing more on the duty cycle. According to the manual of my driver, EN is 5V and Step and Dir will be pulled to ground.
 

Aciera post=313997 userid=25994Hm, as I understand it, this does _not_ give us multi thread gcode execution as that would require multiple parallel motion planners in the same linuxcnc instance. A single instance of linuxcnc cannot interpolate more than one tool path at the same time.

I could be wrong, but given the current API that linuxcnc is written on top of, this would likely require very deep work into the core of linuxcnc. AFAICT there are no tools in the API that can synchronize the threads for instance. Also the code appears to be heavily written for serial execution. What would probably need to happen otomh is that the api would need a way to have each thread run independently with a centrally controlled memory management cache to synchronize the various threads. so you would have a trajectory planner " all required code to execute motion" for each new instance of a aixs and have it run in it's own thread and then a central trajectory planner would keep the various thread in sync. 

at that point, it would probably make sense to port to a mulithreaded api that has c and c++ tools for this kind of work. Texias Instruments RTOS for there microcontrollers has this kind of capabiliy. Any newer x86 can do this easily if it is multicore. I am not super familiar with the ROTS version of the linux kernel that just sa release. But yes a multithreaded pi would be required bare minimum.

tool size was different until after the G43 H2 line which prompts for inserting tool 2.

That command does NOT prompt for 'inserting tool 2', that command activates TLO with offset values defined in the tool table for tool #2.

If you are not using TLO in linuxcnc anyway then I would recommend setting freecad up so it does not output GCODE that activates TLO. This way there are no surprises whatever offset values you have in your tooltable.

Why did the behaviour change?

Probably not the answer you want but most likely due to operator error.

Why are you getting -4V on the scope?
Are the probes reversed?

I removed the level shifter and connected the Tang directly to the Break out Board. Good news, it works. Then I measured at the drives and I get a nice 50% duty cycle. However, the motors still stall. And depending on where I stop, the Tang is sending Step Signals even without any movement. The motor just make sound.