1. Forum
  3. Search

Advanced Search

Search Results (Searched for: raspberry pi 3)

  • slowpoke
  • slowpoke
15 Nov 2024 14:44 - 15 Nov 2024 18:28
LinuxCNC for lathe questions was created by slowpoke

LinuxCNC for lathe questions

Category: General LinuxCNC Questions

Bunch of questions, Hopefully someone can fill in a few blanks as I formulate a plan for the lathe.

I'm using Axis for my mill and I'm completely happy with it. I'm now considering using LinuxCNC for my lathe. I definitely want to maintain manual operation capability.

Presently I have a derivative of the Clough42 ELS with feedback from the spindle and a stepper driving the leadscrew for threading. I like the simplicity of selecting various thread pitches metric and SAE electronically.
1) I don't suppose LinuxCNC has this "ELS" capability?

2) I also have DRO scales. Assuming I will use a MESA board, is it possible to connect the scales to the MESA board and use LinuxCNC as a glorified DRO without actually driving any steppers/servos?

3) Assuming for the moment I can use LinuxCNC simply as a DRO, what MESA board(s) would be a good fit for say max 3 encoder inputs and possibly up to 3 steppers later?

 I have a RaspberryPi of some sort and I might try using it for the LinuxCNC for both space and $.

4) What RaspberryPI's are likely to have acceptable latency and what versions should I avoid?

 I find the Axis GUI a good fit for my needs on the mill, what GUI is a good fit for lathe control?

Much appreciated.
 
  • AD_15
  • AD_15
15 Nov 2024 12:39
Unrecognized error -1 was created by AD_15

Unrecognized error -1

Category: General LinuxCNC Questions

Hello!!
I have implemented mesa 7c81 on spartan 6. Raspberry pi is connected with my board (spartan 6) and we implement linuxcnc on that board, everything works good here but while we run some big files after some time it shows error Unrecognized error -1 and my python scripts stop suddenly, even estop didn't work, file will run but my scripts, estop functionality stop working. Please Suggest any solution.
  • my1987toyota
  • my1987toyota's Avatar
14 Nov 2024 13:10 - 14 Nov 2024 13:12
Replied by my1987toyota on topic Please help with Nema 23 closed loop CL57T-V41 driver Microstep Switches

Please help with Nema 23 closed loop CL57T-V41 driver Microstep Switches

Category: Off Topic and Test Posts

  Well first off welcome to the wonderful world of CNC. Firstly I recommend you read through the Linuxcnc manual, that will get you
going in the right direction. I don't have direct experience with using Raspberry Pi and Linuxcnc. I usually use the Dell Optiplex 9020
and MESA boards
however I recommend using 8 micro steps for most installs. That said you can run the full gamut from full step to 200 micro step
if your driver is rated to handle it.
  Next NO you don't have to run the exact same step setting on all drivers. You could use a belt
drive for one axis, for example a Y axis at say 100 micro steps and a ball screw axis, again for example X axis at say 8 micro step.
At that point you change your step counts in you ini. file accordingly or in your software wizard either Pncconf or Stepconf.
That way you should have accurate calibrated movements on your axis.
  You will have a lot of questions along the way everyone does, so don't get discouraged by it. I would recommend you run a few
simulated setups and play with the system to see how things work before you do your build.
  Lastly keep your build as simple as possible an gradually add in more complexity later if you so desire. It helps keep the
overwhelm from getting to you. I hope this helps and good luck with your CNC endeavors.
  • behai
  • behai
14 Nov 2024 08:21
Please help with Nema 23 closed loop CL57T-V41 driver Microstep Switches was created by behai

Please help with Nema 23 closed loop CL57T-V41 driver Microstep Switches

Category: Off Topic and Test Posts

Hi,

I am trying to understand the Nema 23 closed loop CL57T driver. I have zero knowledge of CNC and stepper motors. I am learning with the objective of building my own CNC.

The manual for the driver: www.omc-stepperonline.com/download/CL57T_V4.0.pdf

The factory setting for the Microstep Switches are:

SW1 = ON, SW2 = OFF, SW3 = ON, SW4 = ON

This "Microstep 8" factory setting requires 1600 pulses per revolution. In my Python program, if I send in 1600 pulses the motor makes one revolution: I just observed that by eyes only.

When I set the switches to "Microstep 1": SW1 = ON, SW2 = ON, SW3 = ON, SW4 = ON

Then I send in 200 pulses and the motor makes one revolution: but it runs very fast compared to "Microstep 8".

I understand the relationship between switches and pulses. PLEASE HELP WITH THE QUESTIONS:

- When we use this motor and this driver with LinuxCNC, how do we set the Microstep Switches?

- Must all drivers' Microstep Switches be set the same?

Please pardon me if the questions are ignorant, all I have currently is LinuxCNC installed for Raspberry Pi 4B. I don't have any other relevant hardware, so I can't try anything yet. I am just trying to understand the basics.

I've attempted some settings, I have a video showing the speed at different pulses:



Thank you and best regards,

...behai.
  • PCW
  • PCW's Avatar
13 Nov 2024 02:15
Replied by PCW on topic Raspberry PI4, MESA 7I96S problems

Raspberry PI4, MESA 7I96S problems

Category: General LinuxCNC Questions

Yes I had forgotten, its the RPI3 that uses USB --> Ethernet
I should know since I have run a Mesa Ethernet card from a RPI4.

 (I think some RPI4 --> Ethernet motion card users needed to increase
the servo thread period to 2 ms to get it to run reliably)
  • tommylight
  • tommylight's Avatar
13 Nov 2024 01:21
Replied by tommylight on topic Raspberry PI4, MESA 7I96S problems

Raspberry PI4, MESA 7I96S problems

Category: General LinuxCNC Questions

I was always under the impression that up to version 3 the ethernet was on the USB bus and 4 and after were on the PCIe bus.

Me too ! :)
  • Cant do this anymore bye all
  • Cant do this anymore bye all's Avatar
13 Nov 2024 01:15
Replied by Cant do this anymore bye all on topic Raspberry PI4, MESA 7I96S problems

Raspberry PI4, MESA 7I96S problems

Category: General LinuxCNC Questions

I was always under the impression that up to version 3 the ethernet was on the USB bus and 4 and after were on the PCIe bus.
  • bladekel
  • bladekel
12 Nov 2024 15:36 - 12 Nov 2024 15:39
How to connect hal pins to custom GUI? was created by bladekel

How to connect hal pins to custom GUI?

Category: Other User Interfaces

Hello to all.
I'm trying to build a custom GUI with pyqt5 for raspberryPi 5.
My linuxCNC version is 2.9.3, python version is 3.11.2.

I wanted to watch a input pin status whenever it changes.
I create a net in my hal file.
net somePin  hal_gpio.PIN33-in

After I created this net, I can see the pin and its changing logic from hal show with axis GUI.
I examined the qtplasmac_sim_handler.py and tried to make connections as on it.

Here is my custom GUI's handler file
def __init__(self, halcomp,widgets,paths):
    super().__init__()

    self.hal = halcomp self.somePinComp = self.hal.newpin('somePin', hal.HAL_BIT, hal.HAL_IN)
    self.somePinComp.value_changed.connect(lambda v: self.debugPrint("Changed"))

with this setup I cant see any changes. It only fires one time "Changed", and after that there is no information...

My guide qtplasmac_sim_handler.py did like I was...

What is my fault?
  • PCW
  • PCW's Avatar
12 Nov 2024 14:43
Replied by PCW on topic Raspberry PI4, MESA 7I96S problems

Raspberry PI4, MESA 7I96S problems

Category: General LinuxCNC Questions

Basically the issue is that the RPI4 Ethernet interface is connected via USB
and USB is not suited for real time.

For a RPI4 I would use a SPI interfaced device, The RPI5 (or most PCs) are fine with Ethernet
LinuxCNC motion controllers because their Ethernet hardware are not USB devices.
  • 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)
Displaying 661 - 675 out of 885 results.
  1. Forum
  3. Search
Time to create page: 0.672 seconds
Powered by Kunena Forum