1. Forum
  3. Search

Advanced Search

Search Results (Searched for: raspberry pi 3)

  • behai
  • behai
12 Nov 2024 13:10
Replied by behai on topic Raspberry PI4, MESA 7I96S problems

Raspberry PI4, MESA 7I96S problems

Category: General LinuxCNC Questions

No. It's an 3 axis mini milling machine, with three steppers. I use step-dir interfaces.
 

Hi This email address is being protected from spambots. You need JavaScript enabled to view it.,

Have you managed to get it to work, please? I am asking because I am thinking of trying out the same set up. I have a Raspberry Pi 4B with 8 GB and real-time kernel. I have not bought a MESA 7I96S yet. But I am planning too.

Thank you and best regards,

...behai.
  • JackRay
  • JackRay
11 Nov 2024 19:17
Replied by JackRay on topic Mesa 7i96s connected but inputs not working

Mesa 7i96s connected but inputs not working

Category: Driver Boards

hello ,
your video explains very well the basic connections and it's very welcome because at the beginning it's not easy to understand everything. I've just bought a 7i96s to replace my SV2 card (parallel port) mainly to add position feedback for my axes (encoders). The middle and end of travel connections for my 5 axes are operational and work very well with a Raspberry pi4. Where I'm having a lot of trouble is with the connections and signals from my encoder.
I want to connect the position feedback of my B axis to the only encoder port on the board.
My encoder is type A+,B+,0V,5Vdc . But I don't understand the documentation for the Mesa 7i96s board with TX/RX 422/485 ... I have no signal feedback in the halmeter.

Could you please guide me to the right connections and signals for my configuration? If attached the configuration of my B axis in my . Hal

---closedloop stepper signals---

net b-pos-cmd <= joint.3.motor-pos-cmd
net b-vel-cmd <= joint.3.vel-cmd
net b-output => [HMOT](CARD0).stepgen.03.velocity-cmd
#net b-pos-fb <= [HMOT](CARD0).stepgen.03.position-fb
net b-pos-fb => joint.3.motor-pos-fb
net b-enable <= joint.3.amp-enable-out
net b-enable => [HMOT](CARD0).stepgen.03.enable

# ---Encoder feedback signals/setup---

setp [HMOT](CARD0).encoder.00.counter-mode 0
setp [HMOT](CARD0).encoder.00.filter 1
setp [HMOT](CARD0).encoder.00.index-invert 0
setp [HMOT](CARD0).encoder.00.index-mask 0
setp [HMOT](CARD0).encoder.00.index-mask-invert 0
setp [HMOT](CARD0).encoder.00.scale [JOINT_3]ENCODER_SCALE

net b-pos-fb <= [HMOT](CARD0).encoder.00.position
net b-vel-fb <= [HMOT](CARD0).encoder.00.velocity
net b-pos-fb => joint.3.motor-pos-fb
net b-index-enable joint.3.index-enable <=> [HMOT](CARD0).encoder.00.index-enable
net b-pos-rawcounts <= [HMOT](CARD0).encoder.00.rawcounts


# ---setup home / limit switch signals---


net b-home-sw => joint.3.home-sw-in
net b-neg-limit => joint.3.neg-lim-sw-in
net b-pos-limit => joint.3.pos-lim-sw-in

Thank you very much
  • domse
  • domse
11 Nov 2024 18:23 - 11 Nov 2024 18:24
Linuxcnc crashing randomly when pressing buttons was created by domse

Linuxcnc crashing randomly when pressing buttons

Category: General LinuxCNC Questions

Hello, so this same problem occurs on on two different machines. One is an old core 2 duo pc + mesa 7i96 with monitor, keyboard, mouse. The other one is a raspberry pi 4 + 7i96s with a vnc connection (no monitor, no mouse, no keyboard) running a plasma machine.

Randomly the program crashes when navigating the gmocappy gui. it happens while jogging in small increments, when switching to program mode, when searching for a gcode file. I'd say the raspberry crashes more often than the pc. When i manage to start a gcode file, even if it is hours long, it is stable.

i attached a report below, this time the machine was homed and the y axis was moved in small increments when it crashed.

Report:
Warning: Spoiler!


Thank you 
  • PCW
  • PCW's Avatar
10 Nov 2024 14:39
Replied by PCW on topic Raspberry Pi4B and Mesa7C80 setup for a beginner

Raspberry Pi4B and Mesa7C80 setup for a beginner

Category: Driver Boards

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.
 
  • d3m0n54in7
  • d3m0n54in7
10 Nov 2024 03:24
Replied by d3m0n54in7 on topic Raspberry Pi4B and Mesa7C80 setup for a beginner

Raspberry Pi4B and Mesa7C80 setup for a beginner

Category: Driver Boards

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?
  • PCW
  • PCW's Avatar
09 Nov 2024 14:19
Replied by PCW on topic Raspberry Pi4B and Mesa7C80 setup for a beginner

Raspberry Pi4B and Mesa7C80 setup for a beginner

Category: Driver Boards

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)
  • tommylight
  • tommylight's Avatar
09 Nov 2024 12:21
Replied by tommylight on topic Raspberry Pi4B and Mesa7C80 setup for a beginner

Raspberry Pi4B and Mesa7C80 setup for a beginner

Category: Driver Boards

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.
  • d3m0n54in7
  • d3m0n54in7
09 Nov 2024 07:51 - 10 Nov 2024 03:29
Raspberry Pi4B and Mesa7C80 setup for a beginner was created by d3m0n54in7

Raspberry Pi4B and Mesa7C80 setup for a beginner

Category: Driver Boards

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" 

File Attachment:

File Name: linuxcncreport.txt
File Size:5 KB

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.
  • behai
  • behai
08 Nov 2024 08:04
Replied by behai on topic Installing LinuxCNC 2.9 on Raspberry Pi 4B with Preempt-RT kernel

Installing LinuxCNC 2.9 on Raspberry Pi 4B with Preempt-RT kernel

Category: Installing LinuxCNC

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:


File Attachment:


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()
]

 
Displaying 811 - 819 out of 819 results.
  1. Forum
  3. Search
Time to create page: 0.737 seconds
Powered by Kunena Forum