Advanced Search

yes exactly, a sequence of gcode linked to the buttons on the gui
with cycle stop and error message in case something goes wrong

Hello All,

New 7i97T last year and only just got time to work in it.  I'm new to linuxcnc and mesa boards and would appreciate advice on this setup.
CR7 and CR8 switch off so FPGA initialisation is fine
Ping 192.168.1.121 works fine and green user LEDs count ethernet packets correctly
Response of Mesaflash version 3.4.9
mesaflash --device 7I97T --addr 192.168.1.121 --readhm
=  'No 7i97t board found'
 
Response of MesaCT version 2.1.7
= 'Device found at 192.168.1.121 is not a Mesa Board'

I am thinking the board should be more revealing than this and wanted to check before proceeding with linuxcnc setup.
Thanks tom

 

The images provided are not generic Debian images, as generic Debian didn't support overlays.
The images we build are custom images based on Debian repo but with kernel sources from the RPi-Linux github.

The output I gave was showing that the hal_gpio driver does indeed work, the first line is loading the driver with the GPIO config as per the man page for the driver. Yes it was the current image, with the 6.12 series kernel & Linuxcnc 2.9.4.

By macro you mean it's just a gcode sequence?

Pardon me for not posting the errormessage encountered.
I was using hal_pi_gpio since I was under the impression from the forum that it is recommended for new projects.
Under "known bugs" on the man page it says:
*
At the moment (2023-07-16) this driver only seems to work on Raspbian as the generic Debian image does not set up the correct interfaces in /dev/gpiomem and restricts access to the /sys/mem interface.
*
The error message I got was related to access to /sys/mem. Since it was a known bug I did not save and post the error-message but instead tried going the Raspbian route.


I'm not sure what to make of your output from halrun but do you mean that you are successfully using GPIOs on a Rpi5 with hal_gpio and the downloaded "standard" img?
I'm not sure where I picked up that hal_pi_gpio was the way to go but if it works with hal_gpio I suppose that is the way to go. Thoughts?