Thank you for your previous reply and guidance regarding the RS-422 interface
on the 7i76 and the suggestion to use an external RS-485 transceiver.
That explanation was very helpful.

I am currently using the 7i92_7i76x2d_2pwm bitfile, and I have reviewed the
IDROM configuration using mesaflash.

From the IDROM, StepGen 5, 6, and 7 are mapped to P1 DB25 pins
1/14, 2/15, and 3/16. These step generators are unused in my system.

I would like to ask whether it would be possible to replace StepGen 5–7
with two additional QCount modules (Quad-A, Quad-B, and Quad-IDX),
using those same I/O pins.

If this is feasible and acceptable from a resource standpoint,
would you be willing to provide a custom bitfile with this change?

Thank you again for your time and for your continued support.

So I find out 3 different Linuxcnc o.s later that I should just settle with 2.9.4 because the cards were new versions “2025” mesa boards…. 2weeks of wrestling with a combination of ip address, firmware,software, etc I’m at a complete stalemate. Really wish I would have just went the g540 route, I was able to flash the firmware. Same firmware I downloaded off of mesas site 7i92tm software. Onto a usb drive loaded onto desktop move the file over to desktop it’s already unzipped so I go in and tell the terminal which combo I have “ 7i92tm_7i76u. I believe the file ends with x1pd.bin? If I’m not mistaken. Anyways, Wrestled with the flash “spelling “ supposedly for about 3 days. Finally got it flashed. Now when I go in pncconf in the pin config setup/card discovery picks up a combo of “7i92 internal data”no tm” next box down shows the combo 7i92 with 7i76. Kool! But in the pinout only the tb4 tb5 tb6 terminals show. 7i76u “2025” step dir goes on tb2 and tb3, only it’s like they don’t exist and now im thinking about just being a chef 

Hi everybody,

I have a small doubt which I hope you all can clarify.

For my z-rot-point calibration,
In my case I think the z-rot point is the distance between z-machine-zero position to the primary rotary axis pivot point (in my case A-axis pivot point) is the z-rot-point value i.e.as shown in screenshot 1: The vector from the origin of the machine coordinate system to point A on the first rotation axis of the table is set as the rotary table position in the machine coordinate system.

Similarly for z-offset in screenshot 2: When the rotation axes for controlling the table are all at 0 degrees, the vector from point A to point B on the second rotation axis of the table is set as the intersection offset vector in the machine coordinate system.

if tell me whether what I have done is correct or not.
Because I went through many threads in the forum but in most cases the rotary point of A-axis is at higher level(in Z-axis term) then the bed(C-axis rotary point) and in my case it is opposite.



 

Yes it does, if I jog the axis it will change. It doesnt seem to be realted as to how far I jog, the axis just has to move, even 0.1mm

The scurve is present now in linuxcnc master, download from GitHub and build, or use the latest .deb files

With many thanks to Grandixximo and 杨阳 we now have an experimental
S-curve / finite-jerk trajectory planner for testing.

For those that build from source just look for the new v2.10.0-pre1 tag.

Others can download debs from github for the next 90 days:
x86 / bookworm  github.com/LinuxCNC/linuxcnc/actions/run...artifacts/5056097663
x86 / trixie github.com/LinuxCNC/linuxcnc/actions/run...artifacts/5056161668
ARM64 / bookworm github.com/LinuxCNC/linuxcnc/actions/run...artifacts/5056139840
ARM64 / trixie github.com/LinuxCNC/linuxcnc/actions/run...artifacts/5056124080

Make no mistake, this is experimental, there are no guarantees that
these won't break your machines. The first user already hit the hard
stops when homing (too-low max jerk setting)
With the jerk setting it is probably best to start high and reduce, as
infinite jerk is closer to current behavior.

If you run these you are volunteering to be a guinea-pig.
magazine.punch.co.uk/image/I0000NOWOOdkXT_k

Life has got more complicated. With proper kernel tuning, latency can be better with Debian 13. I am in the process of publishing a second video about this on YouTube. Please refer to my channel.  www.youtube.com/@MrRodW
The yet to be published video should be watched before the current one.

If you zero again, does the small values stay the same?

Rhe formatting of the message is screwing it up.
Just make a short new message with the images

 

Hi,

I can seem to add the attachments, both less than 1M. Click add image, I can then see it, and press insert.

attachments didn't come though.

 Hi,I have been using linxcnc 2.4 for quite some time and though it would be a good idea to upgrade to the latest qtdragon_hd version. I did a completely fresh install using LinuxCNC 2.9.8

andypugh wrote:

Do you _need_ RTAI? What is your latency with preempt-rt?


 

I confess that RT version 2.92 worked well for me, even using LPT with around 25000 latency. However, when I saw Debian 13, I believed I could achieve the same result, but the latency is extremely high, reaching 150 on the same PC that had 25000 latency with Debian 12. That's when I tried RTAI and got these errors. I'm trying to find another PC following Tommylight's advice in an attempt to get some answers.