Advanced Search

Yes, iov2 has been removed in master.
Simple cases (like yours seems to be) can be handled by a ngc remap for M6 while more complex situations can be handled by a python remap of M6 and or T.

If you just need a safety interlock you might be able to simply add some hal logic that inhibits the relevant output pins until certain conditions are met.

That error report still refers to the 'pid.s.do-pid-calcs' not being found. Maybe you attached the wrong file?

Yes, exactly. But do you know of any example configs or even discussions on how to implement a homing origin switch? I don't think I have found any.

I didn’t think the J1900 had hyper threading. I didn’t see it but I will look agian.

In BIOS hyperthreading must be disabled, and TPM also.
And in case you find "aggressive link management" regarding PCI-E, also disable.

I went through the google dock and enlisted the help of ChatGPT and this is what I did and the results.

• CPU: Intel Celeron J1900 @ 1.99GHz (4 cores)
• Kernel: 6.3.0-rt11-linuxcnc (upgraded from 6.1.0)
• NIC: Realtek RTL8111/8168/8411 (using r8168-dkms driver 8.051.02)
• Power Supply: Switched to a more stable supply from the plasma table

What I Did:

1. Installed the 6.3.0-rt11-linuxcnc kernel.
2. Installed and configured the r8168-dkms driver.
3. Disabled EEE on the NIC (r8168.EEE=0).
4. Set kernel boot parameters:

isolcpus=1,2,3 nohz_full=1,2,3 rcu_nocbs=1,2,3 pcidle.max_cstate=1 processor.max_cstate=1 idle=poll


5. Assigned IRQ 91 (NIC) to CPU core 1.
6. Set all CPUs to performance governor (persistent in rc.local).
7. Confirmed BIOS settings: C-states disabled, Turbo Boost off, EIST off.

 

I can't say I've seen crashes in Master, any more details?

Not OK, notice the red/blue vertical lines on both sides of the histogram, those are excursions outside the visible area that do not show unless explicitly requested, so
latency-histogram --nobase --sbinsize 1000 --show
will show those excursions.
Although it just might be usable for Mesa, but i would not risk it.

What version of linuxcnc?

That is OK for a Mesa card and about where mine ran for years. I'll try and remember to look at my brix tonight.
Did you do the cpu affinity?

Hi, 

I have a touch probe that requires an additional activation signal prior to probing. I've mapped motion.digital-out-00 to the pin and would like to know the best way to add M64 P0 before probing and M65 P0 after. Should that be added to each probe routine, or would it be better to use a macro for that functionality? I'm using Qtdragon_hd and Versaprobe.   

Thank you

I have a STM32H753ZI development board and would like to install remora, would that be possible?

I isolated the cores today and ran the test. Still need to do the kernel upgrade.  

FYI: Based on memory and a quick look, it appears the default and maximum velocity and acceleration variables (4 total) have an added "LINEAR" in the name for 2.9.4. This is from comparison of the TRAJ section for 2.9.4 and TRAJ and AXIS in 2.7.14 documentation.  The 2.9.4 document does mention some additional variables that carry over from the conversions involving scale aspects.

iov2 seems to removed from master..
I have manual tool change that is connected to an output pin that releases the tool(hydraulic) so spindle must inhibited from running when this is activated
also when spindle runs tool change must inhibited
Both inhibitions must be done for safety reasons.

How to do this ?