LinuxCNC + Orange Pi (allwincnc)

Hey Ninja! 

The CPU can be locked on the armbian-config tool. Select the same clock for min and max and the governor as performance.

Also, edit your /boot/armbianEnv.txt and add this to the end of it:
On your INI file, you have to add the option to ignore if the machine was homed or not, since you don't have the switches/sensors wired yet. It can be done by adding this to the TRAJ section:
I'm still having some issues. So please, report your test results here! Thanks.

I use the encoder funtion to connect the MPG Jog wheel.
Not the one for feedback.
I'm not sure the SOC board have enough CPU power to do the real encoder close loop stuff.

These aren't for H3. Our boards use the Mali 400, which should be working with the already installed Lima drivers out of the box. Unfortunately it seems to be not performing as expected. I read somewhere that the older proprietary Mali drivers could reach 300+ fps in glxgears. Unfortuantely it only works in very ancient kernels.

Cncninja wrote:

Should I use this to install from that page, or do I need a variant for ARM?

apt install mali-t76x-x11-driver
apt install mali-t76x-wayland-driver
apt install mali-t76x-fbdev-driver

 

What's the armbian version you are using?

envyvan wrote:

I use the encoder funtion to connect the MPG Jog wheel.
Not the one for feedback.
I'm not sure the SOC board have enough CPU power to do the real encoder close loop stuff.

Hi Dolence,

I currently runing with Armbian_21.02.3_Orangepipc_buster_current_5.10.21_xfce

I'm asking because Michael wrote this on Russian forum:

In general, H3 is no longer supported normally. For in the uboot (bootloader) code, developers are constantly muddying up various new items that interfere with the work with the coprocessor.

I wanna know which Armbian version you guys are using with your working H3 boards. Which version is the latest supported or known to work with the current version of this project?

Why I mentioned that we need our own u-boot branch for this project since those devs usually could care less about real time. We could ask them to stop stomping all over the memory space for the ARISC if that is the real issue. They might not even be aware of anyone using them.

I used to write firmware for x86 (BIOS, coreboot, etc) and work with u-boot. I am actually more comfortable with firmware than writing applications in abstract languages. i prefer 1's and 0's.

I only running this project on Armbian_21.02.3 and seems like it works just fine with me.
I will keep work with it until most of the function has been test.
A notice issue is halui would cause a warning, but seem like every thing run normal.

Hi Dolence
I am running
Armbian_21.02.3_Orangepiplus2e_buster_current_5.10.21_xfce_desktop
on an Opi+2e, with HDMI output and logitec wireles usb kbd & mouse
from a SanDisk 32G sd card ( class A )
I use isolcpus=1,2,3 idle=poll
I am using Lima video ( thru no effort on my part, it was automatic)
I am running Lichuan LCDA357H/ LC57H38 stepservos right now in a test rig
at 1588rpm with 1/4 step and 100 acceleration. Trying for faster, but have occasional amp faults that i havent figured out yet.
My setup is not ready for real use use yet. The OPi is running fine tho.
tomp