Advanced Search

That's all great insights and recommendations, thanks guys. And yes, bidirectional translation can skew a signal pretty quick (long traces/wires == parasitic capacitance). Sensitive. Perhaps not ideal for motion control board.

You guys experimented with modern digital isolators yet? Worth looking into or... stick to the medieval optos?

I added the 8168 DKMS driver, added r8168.aspm=0 r8168.eee_enable=0 pcie_aspm=off loglevel=3 to kernel settings and removed the no longer appropriate "hardware-irq-coalesce-rx-usecs 0" from interfaces.

I ran it a bunch yesterday and never saw the error so I have high hopes this was the problem.

Thanks once again for your help Pete!

tommylight wrote:

Aaaaahhh paperless offices ... that never came. That was the promise made by e-mail .
Yes, print screen works on most distros, although XFCE used by LinuxCNC version of Debian did not work but it had screenshot in the main menu somewhere.

I pushed the prtsc button on the keyboard and it works

Aciera wrote:

I used the latest I could find
Just to be on the same page
Did you use this one:
 

from here:
linuxcnc.org/downloads/

yes and it just gave me the same problems, after this i tried the one Rodw put on google drive and it did everything it was supposed to do

I used the one rodw put on google drive
I had the same issues with the one on the linuxcnc download page
MANY THX TO RODW !!!

One thing to check with bi-directional chips is the drive, some are only recommended for short distance over pcb tracks, not generally recommended for driving signals over long wires.

I think I actually managed to get a nice install.
tomorrow will know for sure... there were some hickups but after trying to get linuxcnc installed on my system I realize that I had a crash-course in trouble-shooting and I learned a lot about the terminal while trying...
I remember that twincat in the early days also was a wildcard.
fingers crossed for tomorow.
I will make a post of all my adventure when I will get the plasma table running... with everything in detail so noobs like me don't have to go thru the torture

For IO on my boards I used the method Mesa does, FET bus switches with pull up resistors on the “world side”. Granted a bob or other driver is required to interface to the “outside world”, but you have free reign over whether a individual pin is an input or output.
As the original intention was to use Mesa firmware I wanted to be able to interface with their DB25 daughter cards.
Also it quick way to convert an existing parallel port setup. Get the firmware config as needed with riogui, flash the FPGA and plug the existing parallel port bob in and off you go. No changes required to the existing wiring.
Anyway that’s just my take, I know it’s not 100% perfect.

your case just reminded me again that the name should also be fixed at some point

---

lsf0108pwr looks good, I have to remember it

but at the moment i don't know what exactly it's for, opto inputs don't need it and for step/dir outputs it might be too weak.
PMOD is usually 3.3V

maybe for some universal IO's

And remove the "IPV4 addressierung........"

Yes I understand, but I already have some machines with Debian 10 and I have no problems. Wanting to continue with Debian 10, which is the most stable Kernel of the 4.x series.
Is it possible to use the 5.x kernel?

Thanks

OT - In the context and spirit of "IN & OUT" here's a cool 8-ch part ya fpga boyz may find useful. Considering the cost per-IO on fpgas, it's occasionally advantageous to have them bidirectional on their equally expensive hardware. Example below: 

 

meister wrote:

Does anyone have a better name?

1. LinuxCNC-RIO <

---

2. RIO
3. RIOCORE
4. Really Important OS

The enclosure was spontaneous and meant to illustrate the end goal for the protruded 90deg connectors. Just sketched a rectangle with 4 tabs, extruded it, cut off around the solids and branded it RIOCORE without thinking half-a-second (<-- birth defect). Really did took 3min from start to screenshot. ps. I'll admit I kinda like this RIOCORE though... sounds hardcore as it is! 

Thanks for pointing out. Yes I have not set these.

Just Added these in ini file. And it worked.
Thanks a lot. I was struggling for this for so long.

Is it possible /etc/default/irqbalance is not being used and thus not reaching our lcnc_irqbalancepolicy.sh file? I don't understand how that process is supposed to work...