Advanced Search

The PktUART interface is the second serial interface on TB4 pins 19..24
I don't think it needs resistors on the latest board revision, but I would
need to check that tomorrow.

If you want to use the HY_vfd component, you need to use s USB or serial
port to RS-485 adapter.

The process with the PREEMPT_RT kernel is rtapi. The one with -98 priority is the base thread and the one with -99 is the servo thread.
Some settings you could try:
Maximum Payload = Auto > to max
AMD 880 HD Audo = Enabled > Disabled
PME Wake Up From S5 = Enabled > Disabled
PS2 Keyboard PowerOn = Any Key > Disabled
Stroke Key = Wake Key > Disabled
PS2 Mouse PowerOn = Enabled > Disabled
USB Device Wake Up From S3/S4 = Enabled > Disabled
Unpopulated Links = Keep Link ON > Off

And the following kernel parameters instead:
skew_tick=1 nosmt=force kthread_cpus=0-1 irqaffinity=0-1 rcu_nocbs=2-7 nohz_full=2-7 isolcpus=2-7
intel_pstate=disable cpufreq.off=1 cpuidle.off=1 processor.max_cstate=0 idle=mwait clocksource=tsc
tsc=reliable nosoftlockup nowatchdog default_hugepagesz=1G hugepages=4 transparent_hugepage=never
threadirqs forcedeth.use_msi=0 mce=ignore_ce nmi_watchdog=0 audit=0 mitigations=off

Not a problem, hope it was helpful.

Regarding spindle orient... I'd hoped to use orient for my lathe as a 'poor-man's c-axis' once I realized that caxis.comp wasn't doing what I wanted.

I quickly realized that is orient by itself won't hold a position.  You either need a spindle brake, or you need a servo drive that is in position mode (internally).  Servo drives in velocity-mode don't necessarily hold a position rigidly, but LCNC is perfectly capable of treating a position-mode servo drive as a spindle.

LCNC can orient a plain old VFD to a pretty exact position, but that does no good if you're trying to use live tools once the spindle is in the appropriate position.

I think you're on the right track for your first steps.  Get the spindle working as well as you can, then add the orient function.  Orient is simple in concept, but tuning and nailing the position can be tricky and time-consuming.  Especially if you have a heavy spindle/chuck.

Something else to consider... your spindle encoder need not be super-high resolution for spindle/orient functions, but for eventual c-axis work the higher the resolution the better.  And that can become a rabbit-hole when trying to balance high encoder speeds with high resolution... while remaining budget friendly.

Hey chaps.

With the mesa 7i95t 7i95t_1pktv2d.bin firmware what pins are needed for rs485 spindle? Any resisters needed? I want to use the HY_vfd component to drive my vfd.

Or is a rs485 usb easier to setup? 

Thanks in advance 

Edit: The test code was removed because it was in
the wrong place, it will be restored to the correct
place later. its not a very important test.

The error was that the code accessed a RX buffer
that was not filled yet, this trashed the stack under
some circumstances, causing random garbage
in other functions.

The function miss-match is unrelated. This happens
because the PKTUART RX FIFO is not cleared before
the modbus driver starts, so may have left over characters
from the last time LinuxCNC was run, power cycle garbage
charcters etc. Its not harmful and will be fixed soon.

with update-hz 0 all work fine if set it to possitive i get
call/response function number mismatch but this didn't hurt is the known bug..
What does this code that removing it fixes the problem?

I no longer have the HPC option in my bios settings.  I'm guessing it went away when I switched to the X6 1090T processor (instead of the fx 8350).  The 1090T didn't have hyperthreading, so I'm not using it.  With the real time kernel, for some reason /sys/devices/system/cpu/smt/active isn't there, but I'm sure I don't have hyperthreading now.

I tried the core performance boost.  It seemed to work for a bit, but restarting without changing settings made it go away.  I seem to have some random really good performance every once in a while, but it isn't repeatable.  Even restarting just the latency-histogram makes it go away sometimes.

Here's one of the times it looked pretty good for awhile.
 

I also tried adding the following commands to try to help things, but it is hard to tell if they really did anything.

swap off --all
systemctl --user stop pulseaudio.socket
systemctl --user stop pulseaudio.service

I also moved the rcu_sched to processor affinity 1,2,3,4,5.  That helped until I started firefox, and I could never get it back.


I think I'm gonna just try to move foreward without getting that last bit of jitter out.  I'm consistently below 40us, which sounds like it is good enough.  (I'll come back to it if I get some motors moving.) 

Oh, and for completeness, I tried the blocking of sound modules described here:
forum.linuxcnc.org/18-computer/39371-res...th-linuxcnc?start=90

Thanks royka,
Do you happen to know the names of the base and servo processes? I see migration/0 through migration/5 and rtkit-daemon listed as RT in htop. They don't seem to increase in time though, so I'd guess they aren't being used. There are some -20 priority processes too.

I tried removing each ram module, and it seemed to work for a bit, but I'd restart the latency-histogram (without restarting anything else), and it would stop helping, so I guess really some other random thing was happening that I can't find.

I am using a cheap SSD. I tried playing around with bios settings for it, and it seems to make no difference. I don't have any CD/DVD or SD-readers.

www.rocketronics.de/shop/en/micropod1.ht...tPslSBwzVmltalID63TW

Sorry for the late response, you were right about it. I did an fresh install in english and now I can configure my card.

Driver manual can be downloaded here: en.bergerda.com/download/31.html

I checked, there is parameter P82 - Input pulse filter frequency, which default value by manual is 800, but need to check tomorrow what number is actually set!

 
 

Thanks a lot for the detailed reply. Really appreciated.

I know that this is not an official LCNC function. I was expecting this to be troublesome, but with your feedback, I might consider leaving it be for the moment.
If I find time I will try to understand ACIERA's setup and try this out.

I might just setup spindle orient function for now. This should be fairly straight forward.

Cheers,
Dave

At update-hz = 1000 the update rate will be limited by the data communication time plus the response time.
(9600 baud is about 1 ms per character so probably something like 100Hz would be the max communication rate
if the I/O device had no delays in responding to commands)
 

try this and recompile

yes this patch works..
the strange is that works very fast with update-hz 1000