Advanced Search

You can actually ignore all the inmux setup in the manual
and not have any inmux related statements in the configuration
string.

One of the best ways to determine the pin/parameter names is with halcmd or halshow
for example, this command in a terminal when LinuxCNC is running:

halcmd show pin hm2

Will show all hardware pins, while:

halcmd show pin *inmux*

will show all inmux pins

You can also do this with halshow, You can launch halshow from axis
with Machine --> Show Hal Configuration. The "Watch" tab of halshow
allows you to monitor pins in real time.
 

Thank you very much for the response. It was indeed the hm2_eth that I needed to change to hm2_rpspi. I also needed to change the CARD0=hm2_7c80 to CARD0=hm2_7c80.0
The next hurdle to surmount is a simple syntax issue. Terminal blocks 1 and 2 are inmux which has gone over my head. After reading the HOSTMOT2 documentation (www.linuxcnc.org/docs/html/man/man9/hostmot2.9.html) 
inmuxes have names like "hm2_<BoardType>.<BoardNum>.inmux.<Instance>". "Instance" is a two-digit number that corresponds to the HostMot2 inm or inmux instance number. There are "num_inms" or numx_inmuxs" instances, starting with 00. So if I want to use TB1 pin 7 for a "door closed" signal, following the manual, it's INPUT6. Would it be hm2_7c80.0.inmux06 ? What about activating TB2 pin 1 for INPUT COMMON 0?

hm2_eth: loading Mesa AnyIO HostMot2 ethernet driver version 0.2

You still have the Ethernet driver (hm2_eth) invoked in the hal file, you need the
RPI4 SPI driver (hm2_rpspi)

From your error report:
./CNC_V_Mill.hal:10: parameter or pin 'hm2_7c80.watchdog.timeout_ns' not found
6722
So just omit that line in the hal file and try again.

I had the idea to purchase the Mesa 7C80 board and a Raspberry Pi 4B to build my own control panel and have run head first into a severe lack of knowledge coupled with almost zero sources to find answers. I have used Raspberry Pis for other projects like media servers and 3d printer farms but I have really over extended myself on this one. I would greatly appreciate it if some of the individuals here that have successfully configured their own machines could assist me and hopefully I can build a guide so that others can learn how to configure these boards since they really do seem to be worth the investment. 
1) I downloaded the Debian image shared by user shepherps and loaded it into my Pi. www.linuxcnc.org/iso/rpi-4-debian-bookwo...23-11-17-1731.img.xz
2) I adjusted the config file in the SD card to allow SPI
3) I modified the ribbon cable purchased from Mesanet so that it was about 2 inches long.
4) I changed the Region setting to US UT8  (I was receiving errors just trying to calculate the steps in pncconf and found the answer to be this)
5) I used mesaflash to verify that the board could communicate with the Pi
6) I used pncconf to generate the 7i96d with ini substitution enabled and then changed the instance of "CARD0=7I96.0" to "CARD0=7C80.0" 
7) Changed "hm2_eth" to "hm2_rpspi" in the .hal file to change the communication driver from ethernet to SPI

To be honest I'm basically a script kiddie when it comes to Linux and Pis, I'm more of an arduino and FANUC guy so most of the other threads have gone over my head but I used to be proficient in DOS so far from intimidated by the terminal. I have attached my most recent error log to show where I'm stuck at now.

tommylight wrote:

A shot from the hip, but usually those drive/steppers will have wrong encoder wiring, would be prudent to double check.
 

Hi tommylight,

It just so turned out you were right: one of my encoder wire were loose, I tightened it on the CL57T-V41 driver and it behaves now.

This is the wiring diagram:




My References for the Wiring Diagram:

1.

From 34:14 CL57T Driver Overview.

2. help.stepperonline.com/en/article/wiring...tepper-motor-4cddqy/

The first CL57T diagram.

3. pypi.org/project/cl57t-raspberry-pi-stepper-drive/

See the table for signal pins to the Raspberry Pi 4B.

And I have learned to work the ENA+ pin: setting it to low to enable, to high to disable.

The Python code below turns the motor 1 revolution, pauses for a little then keeps on turning till Control C to stop.

If I changed [ gpio.output( ena_pin, gpio.LOW ) ] to [ gpio.output( ena_pin, gpio.HIGH ) ] the motor won't turn.

Now I am trying to figure out why I need 1600 to do one revolution, it is about how the DIP switches are set, I have to understand the table in the manual

Thank you and best regards,

...behai.

[
# 08/11/2024
#
# Enable by setting ENA+ pin to low. Expected: motor will run.
#
# /usr/bin/python3 nema23_04_ena_enabled.py
#
from time import sleep
import RPi.GPIO as gpio

direction_pin   = 13
pulse_pin       = 6
ena_pin         = 19
cw_direction    = 0
ccw_direction   = 1

gpio.setmode( gpio.BCM )
gpio.setup( direction_pin, gpio.OUT )
gpio.setup( pulse_pin, gpio.OUT )
gpio.setup( ena_pin, gpio.OUT )
gpio.output( direction_pin, cw_direction )

# Enable.
gpio.output( ena_pin, gpio.LOW )
# ENA pin must be ahead of DIR by at least 200ms.
sleep( 0.5 )

try:
    while True:
        print( 'Direction CW' )
        sleep( .5 )
        gpio.output( direction_pin,cw_direction )
        for x in range( 1600 ):
            gpio.output( pulse_pin, gpio.HIGH )
            sleep( 0.0001 )
            gpio.output( pulse_pin, gpio.LOW )
            sleep( 0.0001 )

except KeyboardInterrupt:
    # Disable.
    gpio.output( ena_pin, gpio.HIGH )
    gpio.cleanup()
]

 

Hello,

I was wondering, would it be of any interest to provide Gentoo ARM64 images for a few boards with PREEMPT_RT?

I don't think I have any besides a Pi 4 stashed away somewhere, but there's quite a lot of topics and messages about people getting LinuxCNC on Raspberry Pis and whatnot. What if there was a be-all and end-all solution that had Gentoo fully ready to go for LinuxCNC? Would anyone care or want this? What device(s) has/have the most interest/popularity among LinuxCNC users?

Cheers!

Joco wrote:

Okay - we found the problem and after some tests believe it is fixed. a stray full-stop ina file name pattern.

Thanks Joco!

Confirmed able to install now on stable.

Okay - we found the problem and after some tests believe it is fixed. a stray full-stop ina file name pattern.

A shot from the hip, but usually those drive/steppers will have wrong encoder wiring, would be prudent to double check.

Cant do this anymore bye all wrote:

First of all, my deepest deepest sympathies,sorry to hear you live in Melbourne, the only good thing Victoria has to other is Philip Island and the roads, airports and docks that lead out of the state.

Why aren't you using the premade image for your RPi ?

The links are on the Linuxcnc home page under downloads.
 

Good evening cornholio,

Thank you for your reply and suggestions.

I love Melbourne, except the crazy weather I have spent more than 2/3 of my life in Melbourne.

So after about 6 failed attempts ha ha ha... I found this official instructions: The Linux kernel

And I used one of the 64 bit images offered by the Raspberry Pi imager software to get my initial OS with Desktop.

Then from the instructions above, I picked out the appropriate bits to apply.

I finally succeeded:



Then, I also use a Windows utility named "Win32 Disk Imager - 1.0" to take an image of the SD card. And restore the image to another new card, I am able to boot from this new card also. Now I have an entire back up of the original card, if both cards fail at the same time, I am still covered.

Originally, I used the native dd tool to do the image backup, I could restore the image also, but it refuses to boot.

Currently, I only have a "Nema 23 Closed Loop Stepper Motor 3Nm (424.83oz.in)" and the CL57T-V41 driver.

I am learning by trying to program it using Python... I am having trouble getting it to work properly as a closed loop motor. I can get it to work as an open loop motor, we just switch on the the 6th dip switch SW6.

Thank you and best regards,

...behai.


 

I will do some snooping after work on my pi5.  Thats about 5 hrs away as of the time of this post.

Ok so used the image given by joco and that installed fine but it installed the develop version of probe basic.  On trying to switch back following the instructions on the probebasic install site when i update the source list to use stable and then do the apt-get update i get the error again.

Switch back to develop branch and able to install correctly.  

I would recommend using either one of these prebuild images for pi5:

[1] Without network manager UI
drive.google.com/file/d/14rVniZWJ7DqbIxQ.../view?usp=drive_link

or

[2] With network manger UI
drive.google.com/file/d/11XX6SdbaO0tL1Zg.../view?usp=drive_link