Advanced Search

I have translated mainly the MainWindow when I decided to test it, before putting more hours in it.
I have also tested to translate only one button "estop", the compiled .qm file had the translation inside.
 



I have also spotted difference between mine and @Franklin's .ts file. At the very beginning, the line="42" and line="43" is different. Does this means that these translations arent compatible between versions?
[/code]

Hi.  Andre Fellow Norwegian here. Is it possible to talk to you on messenger or something?

When you activate too many overlays they can interfere with each other, because some pins have multiple functions. Some can also cause extra interrupts, so remove everything that you don't need and isolcpus should be placed after extraargs:​​​​​​​

royka wrote:

That's nice, how is the latency? It might help to isolate the last 4 cores (isolcpus=2-5)if just isolating the last core is not good enough (isolcpus=5)

For spi, open /boot/armbianEnv.txt and edit the following:
overlay_prefix=rockchip-rk3399
overlays=spi-spidev
 

The latency not good actually, it's 75 us with 6*glxgears without SSH, however during this test, there was so many lags.
and with SSH it was 130 us.
and about:
overlay_prefix=rockchip-rk3399
overlays=spi-spidev
I have now this:
verbosity=1
bootlogo=true
console=both
overlay_prefix=rockchip
fdtfile=rockchip/rk3399-orangepi-4-lts.dtb
rootdev=UUID=a703d82e-8d61-4266-8b54-c10361d608ca
rootfstype=ext4
overlays=rk3318-box-cpu-hs rk3318-box-emmc-ddr rk3318-box-emmc-hs200 rk3318-box-led-conf1 rk3318-box-led-conf2 rk3318-box-led-conf3 rk3318-box-led-conf4 rk3318-box-wlan-ap6330 rk3318-box-wlan-ap6334 rk3318-box-wlan-ext rk3328-i2c0 rk3328-i2s1-pcm5102 rk3328-opp-1.4ghz rk3328-opp-1.5ghz rk3328-spi-spidev rk3328-uart1 rk3399-dwc3-0-host rk3399-i2c7 rk3399-i2c8 rk3399-opp-2ghz rk3399-pcie-gen2 rk3399-spi-jedec-nor rk3399-spi-spidev rk3399-uart4 rk3399-uhs rk3399-w1-gpio rk3566-sata2 rk3568-hk-i2c0 rk3568-hk-i2c1 rk3568-hk-pwm1 rk3568-hk-pwm2 rk3568-hk-pwm9 rk3568-hk-spi-spidev rk3568-hk-uart0 rk3568-hk-uart0-rts_cts rk3568-hk-uart1 rk3568-nanopi-r5c-leds rk3568-nanopi-r5s-leds rockpi4cplus-usb-host rockpro64-lcd
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u
isolcpus=2-5

Do I need to change it? cause the spi is there already.

 

Thanks Peter and Tommy.
All the board jumpers are set to 5i24 settings.
There are no options in bios for pcie settings unfortunately.
They're is a 1x pcie slot on the mb but neither this, nor any other slots will allow the computer to boot with the 6i24 in situ.
As a trial, I have another (Windows) machine. That machine boots fine and the card is visible in device manager.
I think for now I'm putting it down to something to do with the computer, possibly mother board related.
One last question though, is there a minimum version of linuxcnc which needs to be used to allow the computer to recognise a 6i24?? Could it be something as simple as missing drivers?? IIRC the last time I updated was about 18 months ago.
Thanks!!

Hey Tommy,

Thanks. I actually just got a response from Peter.  He gave me the same link you gave me but told me there is a firmware that already has the modifications that I need.  It's called 7i96s_pmd.bin.  So it seems that as long as I can get this to flash I should be good to go as far as listening to the PWM from the Powercore from Rack Robo goes. 

Assss long as the Mesa board can pick up a 3.3v signal on that pin.  It seems that is what the Powercore is putting out as its PWM signal. I can also ask Peter about this and worst case I can run the input into a MOSFET or something similar to up the voltage into the Mesa...

Best,
-Dylan

Hello,
I'm getting more familiar with LinuxCNC and Mesa boards, converting a Biesse Rover 13s and have a 7I96s step and direction interface along with a 7I77 analog servo interface connected via the P1 expansion connector. I also have one 7I84 I/O board connected via the TB2 sserial and all is well, I can command the outputs etc. from halshow at all the boards but I need to connect two more 7I84s. I also have the 7I94T anything I/O Ethernet card but I'm using ethernet already on the 7I96S with 10.10.10.10. Should I reset the 7I94T IP to something other than .10 and use an ethernet switch or is there another way to use multiple sserial channels from the 7I96S?

By the way I really appreciate all the others that have gone before me and made this all possible! Thanks for the help!

I was typing up a post to ask for help getting LinuxCNC 2.9.2 running on a Raspberry Pi 4 B attached to a Raspberry Pi 7 inch Touch Display, when I finally figured out the solution. Thought I'd still make the post for helping others or possibly even future me if I have to rebuild this system one day.

The Pi Touch uses DSI for connecting to a Raspberry Pi and seems LinuxCNC doesn't have the required settings enabled in the config.txt by default. Not really a surprise as its probably an unusual pairing of hardware and OS.

The solution was adding the below text to config.txt

It should work indeed when selected fully preempted. At least it worked for me until 6.11 (after patching). What's strange for me is that when it's set manually to rt prio it works

Start with
DIRSETUP = 20000
DIRHOLD = 20000
STEPLEN = 5000
STEPSPACE = 5000
And if it works, change only last two to 4000, test, 3000 etc, until you notice missed steps, then add 50% more to that, i would add 100% just to be safe.

Is the tittle OK now?

www.phoronix.com/news/Linux-6.12-Does-Real-Time
6.12 does not need patching for AMD64 according to the above, it should work with just setting the preemption to full. That needs to be tested.
The list of all architectures that have ready made debs for 6.12 RT.
packages.debian.org/search?keywords=linux-image-rt
And yes, i know patching sometimes does not work as it should, but can not recall what would cause that as last i did patching was when Linux Mint 17.n came out.
And yes, we do need evidence of it not working on AMD64 or X86_64 (there are no new kernels for X86 for quite some time).

Anyway thanks for the link, just tried the kernel from the link and that one works correctly indeed. Still a mystery for me while mine doesn't get detected, because rhey're compiled with fully preemptible (realtime) in menuconfig.

Why compiling myself? Because I use it on a pc with Fedora and an Orange Pi 5. I'll dig further into it.

If i have a maximum frequency of 500k(pps) and a minimum pulse width of 1us how do i convert those numbers into the step and direction timings of a joint that i put into my ini file?

In the other terminal you can read "PREEMPT_,RT".

In the screenshot of the whole screen (where I put the rtapi processes manually on the FIFO scheduler with rt priority) you can see from the result that it's definitely a realtime kernel, but somehow just not detected correctly since 6.12.
Do I really need to send a proof that it's the same with x86?

It's a bit annoying that the title got changed to something that attracts less attention, while it's not even limited to only that device/architecture.

Since you didn't reply on it but you did reply on other topics in this section I assumed that you didn't read it. So by trying to prevent of getting a lot of noise in this topic (didn't work) I pushed the report button.