Search Results (Searched for: raspberry)
- 7strideR
18 Nov 2024 05:46 - 18 Nov 2024 07:06
Replied by 7strideR on topic Linux CNC powered Ethercat Mill Retrofit
Linux CNC powered Ethercat Mill Retrofit
Category: EtherCAT
Hi thanks,
I am trying to get a quote on the EL-8, which is a more expensive/new version but I have seen them work on LinuxCNC through a Raspberry Pi.
I am a little scared to set these up though as there is not much info on doing this from what I've seen. As I also don't have much experience here especially when it comes to the setting up the drives addresses and communication.
I am trying to get a quote on the EL-8, which is a more expensive/new version but I have seen them work on LinuxCNC through a Raspberry Pi.
I am a little scared to set these up though as there is not much info on doing this from what I've seen. As I also don't have much experience here especially when it comes to the setting up the drives addresses and communication.
- spumco
- spumco
15 Nov 2024 20:16
Replied by spumco on topic LinuxCNC for lathe questions
LinuxCNC for lathe questions
Category: General LinuxCNC Questions
I won't comment on GUI choice(s) here - those are personal preferences. Regarding your other 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.
- Yes, LCNC has "ELS" capability. Not in a turn-key configuration, but there's no reason you can't set LCNC up to act like your ELS. All the elements are present: spindle encoder + Z-axis positioning motor + configurable logic.
- Yes. And LCNC already has a "DRO" mode. See linuxcnc.org/docs/devel/html/gui/mdro.html
- You can read my long-winded post here:
forum.linuxcnc.org/27-driver-boards/5160...i-buy?start=0#292576
- I'm not an expert, but I think the absolute cheapest Mesa combination to get an FPGA card (required) and 3 axis/spindle encoder inputs & step/dir outputs is a 7i92 (any variant) and a 7i85s. You'd still need something else for IO, but that depends on your particular setup.
- If your IO needs are moderate, a 7i96s and 7i85s would get you the IO and keep packaging to two (vs three) boards.
- Based on very little personal experience, Rpi's usually have decent to very good latency and potentially not-so-good user-interface response. i.e. 'laggy' if using a power-hungry GUI. If you are using Mesa hardware you don't have to worry about latency with an Rpi.
- I've got an Rpi5 and while I'm not using it (right now), it was just fine when I tested it with LCNC and Probe Basic (no interface lag).
- Lathe GUI - any GUI is fine except Axis.
- 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.
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.
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
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.
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.
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
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)
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
13 Nov 2024 01:21
Replied by tommylight on topic Raspberry PI4, MESA 7I96S problems
Raspberry PI4, MESA 7I96S problems
Category: General LinuxCNC Questions
Me too !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.

- Cant do this anymore bye all
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.
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
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?
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
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.
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
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.
Replied by behai on topic Raspberry PI4, MESA 7I96S problems
Raspberry PI4, MESA 7I96S problems
Category: General LinuxCNC Questions
Hi This email address is being protected from spambots. You need JavaScript enabled to view it.,No. It's an 3 axis mini milling machine, with three steppers. I use step-dir interfaces.
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
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:
Error report created by /usr/lib/tcltk/linuxcnc/show_errors.tcl:
Print file information:
RUN_IN_PLACE=no
LINUXCNC_DIR=
LINUXCNC_BIN_DIR=/usr/bin
LINUXCNC_TCL_DIR=/usr/lib/tcltk/linuxcnc
LINUXCNC_SCRIPT_DIR=
LINUXCNC_RTLIB_DIR=/usr/lib/linuxcnc/modules
LINUXCNC_CONFIG_DIR=
LINUXCNC_LANG_DIR=/usr/lib/tcltk/linuxcnc/msgs
INIVAR=inivar
HALCMD=halcmd
LINUXCNC_EMCSH=/usr/bin/wish8.6
LINUXCNC - 2.8.4
Machine configuration directory is '/home/pi/linuxcnc/configs/plasma'
Machine configuration file is 'plasma.ini'
INIFILE=/home/pi/linuxcnc/configs/plasma/plasma.ini
VERSION=1.1
PARAMETER_FILE=metric_parameters.txt
TASK=milltask
HALUI=halui
DISPLAY=gmoccapy
COORDINATES=XYYZA
KINEMATICS=trivkins coordinates=XYYZA kinstype=BOTH
Starting LinuxCNC...
Starting LinuxCNC server program: linuxcncsvr
Loading Real Time OS, RTAPI, and HAL_LIB modules
Starting LinuxCNC IO program: io
Starting HAL User Interface program: halui
twopass:invoked with <> options
twopass:found ./plasma.hal
twopass:found ././plasmac/plasmac.tcl
twopass:found ./plasma_connections.hal
Starting TASK program: milltask
Starting DISPLAY program: gmoccapy
task: main loop took 0.141396 seconds
task: main loop took 2.166802 seconds
33554435
41943043
37748739
35651587
39845891
31457283
44040195
Unexpected realtime delay on task 0 with period 1000000
This Message will only display once per session.
Run the Latency Test and resolve before continuing.
(0, ' = ', '/usr/bin/gmoccapy')
(1, ' = ', '-ini')
(2, ' = ', '/home/pi/linuxcnc/configs/plasma/plasma.ini')
Entry = trivkins
Entry = coordinates=XYYZA
found the following coordinates xyyza
Entry = kinstype=BOTH
**** GMOCCAPY GETINIINFO ****
Number of joints = 5
5 COORDINATES found = xyyza
('Fount double letter ', )
joint 0 = axis x
joint 1 = axis y0
joint 2 = axis y1
joint 3 = axis z
joint 4 = axis a
{0: 'x', 1: 'y0', 2: 'y1', 3: 'z', 4: 'a'}
**** GMOCCAPY GETINIINFO ****
[KINS] KINESTYPE is trivkins
Found kinstype=BOTH but using trivkins
It is not recommended to do so!
Will use mode to switch between Joints and World mode
hopefully supported by the used <<trivkins>> module
**** GMOCCAPY GETINIINFO ****
No MAX_RAPID_OVERRIDE entry found in [DISPLAY] of INI file
Default settings 100 % applied!
**** GMOCCAPY GETINIINFO ****
Preference file path: /home/pi/linuxcnc/configs/plasma/Plasma.pref
**** GMOCCAPY GETINIINFO ****
No DEFAULT_SPINDLE_SPEED entry found in [DISPLAY] of INI file
**** GMOCCAPY INFO ****
**** no valid probe config in INI File ****
**** disabled tool measurement ****
**** GMOCCAPY INFO ****
**** Entering make_DRO
axis_list =
**** GMOCCAPY INFO ****
**** Entering make ref axis button
('Filepath = ', '/usr/share/gmoccapy/images/ref_all.png')
('Filepath = ', '/usr/share/gmoccapy/images/ref_0.png')
('Filepath = ', '/usr/share/gmoccapy/images/ref_1.png')
('Filepath = ', '/usr/share/gmoccapy/images/ref_2.png')
('Filepath = ', '/usr/share/gmoccapy/images/ref_3.png')
('Filepath = ', '/usr/share/gmoccapy/images/ref_4.png')
('Filepath = ', '/usr/share/gmoccapy/images/unhome.png')
**** GMOCCAPY INFO ****
**** Entering make touch button
**** GMOCCAPY INFO ****
**** Entering make jog increments
**** GMOCCAPY INFO ****
**** Entering make jog button
**** GMOCCAPY INFO ****
**** Entering make joints button
**** GMOCCAPY INFO ****
**** arrange JOINTS button
Found 10 Joints Button
**** GMOCCAPY INFO ****
**** Entering make macro button
found 0 Macros
**** GMOCCAPY INFO ****
**** arrange DRO
4
**** GMOCCAPY INFO ****
**** Place in table
**** GMOCCAPY INFO ****
**** get DRO order
**** GMOCCAPY INFO ****
**** arrange JOG button
less than 6 axis
**** GMOCCAPY INFO ****
**** no audio available! ****
**** PYGST libray not installed? ****
**** is python-gstX.XX installed? ****
**** GMOCCAPY INFO ****
**** Entering init gremlin ****
Kinematics type changed
('_set_enable_tooltips = ', True)
**** GMOCCAPY INFO ****
**** No virtual keyboard installed, we checked for <onboard> and <matchbox-keyboard>.
**** GMOCCAPY INFO: Gcode.lang found ****
**** GMOCCAPY GETINIINFO ****
Wrong entry [DISPLAY] CYCLE_TIME in INI File!
Will use gmoccapy default 150
**** GMOCCAPY INFO : inifile = /home/pi/linuxcnc/configs/plasma/plasma.ini ****:
**** GMOCCAPY INFO : postgui halfile = postgui.tcl ****:
Jog Pin Changed
x+
Jog Button released = x+
Jog Pin Changed
x-
Jog Button released = x-
Jog Pin Changed
y+
Jog Button released = y+
Jog Pin Changed
y-
Jog Button released = y-
Jog Pin Changed
z+
Jog Button released = z+
Jog Pin Changed
z-
Jog Button released = z-
Jog Pin Changed
a+
Jog Button released = a+
Jog Pin Changed
a-
Jog Button released = a-
Jog Pin Changed
0+
Jog Button released = 0+
Jog Pin Changed
0+
Jog Button released = 0+
Jog Pin Changed
1+
Jog Button released = 1+
Jog Pin Changed
1+
Jog Button released = 1+
Jog Pin Changed
2+
Jog Button released = 2+
Jog Pin Changed
2+
Jog Button released = 2+
Jog Pin Changed
3+
Jog Button released = 3+
Jog Pin Changed
3+
Jog Button released = 3+
Jog Pin Changed
4+
Jog Button released = 4+
Jog Pin Changed
4+
Jog Button released = 4+
IDLE
1 2
MANUAL Mode
RUN
IDLE
ntb_button_switch_page
('on button home clicked = ', 'ref_all')
('Hal Status not all homed', '0124')
('Hal Status not all homed', '124')
('Hal Status not all homed', '12')
('Hal Status not all homed', '2')
Combi DRO all homed
Combi DRO all homed
Combi DRO all homed
Combi DRO all homed
hal status motion mode changed
Hal Status all homed
ntb_button_switch_page
Jog Button pressed = y-
Jog Button released = y-
Jog ButtShutting down and cleaning up LinuxCNC...
task: 9501 cycles, min=0.000150, max=2.166802, avg=0.010410, 2 latency excursions (> 10x expected cycle time of 0.010000s)
hm2: loading Mesa HostMot2 driver version 0.15
hm2_eth: loading Mesa AnyIO HostMot2 ethernet driver version 0.2
hm2_eth: 10.10.10.10: INFO: Hardware address (MAC): 00:60:1b:16:86:c3
hm2_eth: discovered 7I96S
hm2/hm2_7i96s.0: Low Level init 0.15
hm2/hm2_7i96s.0: Smart Serial Firmware Version 43
hm2/hm2_7i96s.0: 51 I/O Pins used:
hm2/hm2_7i96s.0: IO Pin 000 (TB3-01): InM Input Module #0, pin in0 (Input)
hm2/hm2_7i96s.0: IO Pin 001 (TB3-02): InM Input Module #0, pin in1 (Input)
hm2/hm2_7i96s.0: IO Pin 002 (TB3-03): InM Input Module #0, pin in2 (Input)
hm2/hm2_7i96s.0: IO Pin 003 (TB3-04): InM Input Module #0, pin in3 (Input)
hm2/hm2_7i96s.0: IO Pin 004 (TB3-05): InM Input Module #0, pin in4 (Input)
hm2/hm2_7i96s.0: IO Pin 005 (TB3-06): InM Input Module #0, pin in5 (Input)
hm2/hm2_7i96s.0: IO Pin 006 (TB3-07): InM Input Module #0, pin in6 (Input)
hm2/hm2_7i96s.0: IO Pin 007 (TB3-08): InM Input Module #0, pin in7 (Input)
hm2/hm2_7i96s.0: IO Pin 008 (TB3-09): InM Input Module #0, pin in8 (Input)
hm2/hm2_7i96s.0: IO Pin 009 (TB3-10): InM Input Module #0, pin in9 (Input)
hm2/hm2_7i96s.0: IO Pin 010 (TB3-11): InM Input Module #0, pin in10 (Input)
hm2/hm2_7i96s.0: IO Pin 011 (TB3-13/TB3-14): SSR #0, pin Out-00 (Output)
hm2/hm2_7i96s.0: IO Pin 012 (TB3-15/TB3-16): SSR #0, pin Out-01 (Output)
hm2/hm2_7i96s.0: IO Pin 013 (TB3-17/TB3-18): SSR #0, pin Out-02 (Output)
hm2/hm2_7i96s.0: IO Pin 014 (TB3-19/TB3-20): SSR #0, pin Out-03 (Output)
hm2/hm2_7i96s.0: IO Pin 015 (TB3-21/TB3-22): OutM Output Module #0, pin Out-04 (Output)
hm2/hm2_7i96s.0: IO Pin 016 (TB3-23/TB3-24): OutM Output Module #0, pin Out-05 (Output)
hm2/hm2_7i96s.0: IO Pin 017 (TB1-02/TB1-03): StepGen #0, pin Step (Output)
hm2/hm2_7i96s.0: IO Pin 018 (TB1-04/TB1-05): StepGen #0, pin Direction (Output)
hm2/hm2_7i96s.0: IO Pin 019 (TB1-08/TB1-09): StepGen #1, pin Step (Output)
hm2/hm2_7i96s.0: IO Pin 020 (TB1-10/TB1-11): StepGen #1, pin Direction (Output)
hm2/hm2_7i96s.0: IO Pin 021 (TB1-14/TB1-15): StepGen #2, pin Step (Output)
hm2/hm2_7i96s.0: IO Pin 022 (TB1-16/TB1-17): StepGen #2, pin Direction (Output)
hm2/hm2_7i96s.0: IO Pin 023 (TB1-20/TB1-21): StepGen #3, pin Step (Output)
hm2/hm2_7i96s.0: IO Pin 024 (TB1-22-TB1-23): StepGen #3, pin Direction (Output)
hm2/hm2_7i96s.0: IO Pin 025 (TB2-02/TB2-03): StepGen #4, pin Step (Output)
hm2/hm2_7i96s.0: IO Pin 026 (TB2-04/TB2-05): StepGen #4, pin Direction (Output)
hm2/hm2_7i96s.0: IO Pin 027 (TB2-07/TB2-08): Encoder #0, pin A (Input)
hm2/hm2_7i96s.0: IO Pin 028 (TB2-10/TB2-11): Encoder #0, pin B (Input)
hm2/hm2_7i96s.0: IO Pin 029 (TB2-13/TB2-14): Encoder #0, pin Index (Input)
hm2/hm2_7i96s.0: IO Pin 030 (TB2-16/TB2-17): IOPort
hm2/hm2_7i96s.0: IO Pin 031 (TB2-18/TB2-19): IOPort
hm2/hm2_7i96s.0: IO Pin 032 (internal): IOPort
hm2/hm2_7i96s.0: IO Pin 033 (internal): SSR #0, pin AC Ref (internal) (Output)
hm2/hm2_7i96s.0: IO Pin 034 (P1-01): IOPort
hm2/hm2_7i96s.0: IO Pin 035 (P1-02): IOPort
hm2/hm2_7i96s.0: IO Pin 036 (P1-03): IOPort
hm2/hm2_7i96s.0: IO Pin 037 (P1-04): IOPort
hm2/hm2_7i96s.0: IO Pin 038 (P1-05): IOPort
hm2/hm2_7i96s.0: IO Pin 039 (P1-06): IOPort
hm2/hm2_7i96s.0: IO Pin 040 (P1-07): IOPort
hm2/hm2_7i96s.0: IO Pin 041 (P1-08): IOPort
hm2/hm2_7i96s.0: IO Pin 042 (P1-09): IOPort
hm2/hm2_7i96s.0: IO Pin 043 (P1-11): IOPort
hm2/hm2_7i96s.0: IO Pin 044 (P1-13): IOPort
hm2/hm2_7i96s.0: IO Pin 045 (P1-15): IOPort
hm2/hm2_7i96s.0: IO Pin 046 (P1-17): IOPort
hm2/hm2_7i96s.0: IO Pin 047 (P1-19): IOPort
hm2/hm2_7i96s.0: IO Pin 048 (P1-21): IOPort
hm2/hm2_7i96s.0: IO Pin 049 (P1-23): IOPort
hm2/hm2_7i96s.0: IO Pin 050 (P1-25): IOPort
hm2/hm2_7i96s.0: registered
hm2_eth: in hm2_eth_reset
hm2_eth: HostMot2 ethernet driver unloaded
hm2: unloading
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments
Debug file information:
Note: Using POSIX realtime
/usr/bin/gmoccapy:312: GtkWarning: Invalid icon size 48
self.widgets.window1.show()
(gmoccapy:1107): GtkSourceView-CRITICAL **: 19:40:04.973: gtk_source_language_manager_set_search_path: assertion 'lm->priv->ids == NULL' failed
Unexpected realtime delay on task 0 with period 1000000
This Message will only display once per session.
Run the Latency Test and resolve before continuing.
/usr/lib/python2.7/dist-packages/gmoccapy/notification.py:168: GtkWarning: Invalid icon size 48
self.popup.show()
/usr/bin/gmoccapy:5248: GtkWarning: Invalid icon size 48
gtk.main()
[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
python2: ../../src/xcb_io.c:263: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
/usr/bin/linuxcnc: line 896: 1107 Aborted $EMCDISPLAY -ini "$INIFILE" $EMCDISPLAYARGS $EXTRA_ARGS
1054
1103
Stopping realtime threads
Unloading hal components
Note: Using POSIX realtime
Info report created by linuxcnc_info:
The file: /tmp/linuxcnc_info.txt
can be posted to a forum or a web site like:
pastebin.com
in order to provide information about the linuxcnc
system and configuration.
Date: Mon 11 Nov 2024 07:44:27 PM EET
UTC Date: Mon 11 Nov 2024 05:44:27 PM UTC
this program: /usr/bin/linuxcnc_info
uptime: 19:44:27 up 5 min, 2 users, load average: 1.00, 1.22, 0.64
lsb_release -sa: Raspbian Raspbian GNU/Linux 10 (buster) 10 buster
which linuxcnc: /usr/bin/linuxcnc
pwd: /home/pi/linuxcnc/configs/plasma
USER: pi
LOGNAME: pi
HOME: /home/pi
EDITOR:
VISUAL:
LANGUAGE:
TERM: dumb
COLORTERM:
DISPLAY: :0.0
DESKTOP: LXDE-pi
display size: 1200x1280 pixels (318x339 millimeters)
PATH: /usr/bin:/home/pi/linuxcnc/configs/plasma/bin:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games
uname items:
nodename -n: raspberrypi
kernel-name -s: Linux
kernel-vers -v: #1 SMP PREEMPT RT Fri Jan 1 21:15:16 GMT 2021
machine -m: armv7l
processor -p: unknown
platform -i: unknown
oper system -o: GNU/Linux
/proc items:
cmdline: coherent_pool=1M 8250.nr_uarts=0 cma=64M bcm2708_fb.fbwidth=1200 bcm2708_fb.fbheight=1280 bcm2708_fb.fbswap=1 smsc95xx.macaddr=DC:A6:32:F7:46:81 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty1 root=PARTUUID=fdc20b50-02 rootfstype=ext4 elevator=deadline fsck.repair=yes isolcpus=3 idle=poll rootwait quiet splash plymouth.ignore-serial-consoles cfg80211.ieee80211_regdom=LT
model name: ARMv7 Processor rev 3 (v7l)
cores:
cpu MHz:
parport:
serial:
Versions:
gcc: gcc (Raspbian 8.3.0-6+rpi1) 8.3.0
python: Python 2.7.16
git: git version 2.20.1
git commit: NA
tcl: 8.6
tk: 8.6
glade: not_in_PATH
glade-gtk2: not_in_PATH
linuxcnc_var all:
LINUXCNCVERSION: 2.8.4
LINUXCNC_AUX_GLADEVCP: /usr/share/linuxcnc/aux_gladevcp
LINUXCNC_AUX_EXAMPLES: /usr/share/linuxcnc/aux_examples
REALTIME: /etc/init.d/realtime
RTS: uspace
HALLIB_DIR: /usr/share/linuxcnc/hallib
dpkg -l '*linuxcnc*':
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===============-============-============-=====================================================================
un linuxcnc <none> <none> (no description available)
un linuxcnc-doc <none> <none> (no description available)
ii linuxcnc-doc-en 1:2.8.4 all motion controller for CNC machines and robots (English documentation)
un linuxcnc-sim <none> <none> (no description available)
ii linuxcnc-uspace 1:2.8.4 armhf motion controller for CNC machines and robots
Thank you
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!
Error report created by /usr/lib/tcltk/linuxcnc/show_errors.tcl:
Print file information:
RUN_IN_PLACE=no
LINUXCNC_DIR=
LINUXCNC_BIN_DIR=/usr/bin
LINUXCNC_TCL_DIR=/usr/lib/tcltk/linuxcnc
LINUXCNC_SCRIPT_DIR=
LINUXCNC_RTLIB_DIR=/usr/lib/linuxcnc/modules
LINUXCNC_CONFIG_DIR=
LINUXCNC_LANG_DIR=/usr/lib/tcltk/linuxcnc/msgs
INIVAR=inivar
HALCMD=halcmd
LINUXCNC_EMCSH=/usr/bin/wish8.6
LINUXCNC - 2.8.4
Machine configuration directory is '/home/pi/linuxcnc/configs/plasma'
Machine configuration file is 'plasma.ini'
INIFILE=/home/pi/linuxcnc/configs/plasma/plasma.ini
VERSION=1.1
PARAMETER_FILE=metric_parameters.txt
TASK=milltask
HALUI=halui
DISPLAY=gmoccapy
COORDINATES=XYYZA
KINEMATICS=trivkins coordinates=XYYZA kinstype=BOTH
Starting LinuxCNC...
Starting LinuxCNC server program: linuxcncsvr
Loading Real Time OS, RTAPI, and HAL_LIB modules
Starting LinuxCNC IO program: io
Starting HAL User Interface program: halui
twopass:invoked with <> options
twopass:found ./plasma.hal
twopass:found ././plasmac/plasmac.tcl
twopass:found ./plasma_connections.hal
Starting TASK program: milltask
Starting DISPLAY program: gmoccapy
task: main loop took 0.141396 seconds
task: main loop took 2.166802 seconds
33554435
41943043
37748739
35651587
39845891
31457283
44040195
Unexpected realtime delay on task 0 with period 1000000
This Message will only display once per session.
Run the Latency Test and resolve before continuing.
(0, ' = ', '/usr/bin/gmoccapy')
(1, ' = ', '-ini')
(2, ' = ', '/home/pi/linuxcnc/configs/plasma/plasma.ini')
Entry = trivkins
Entry = coordinates=XYYZA
found the following coordinates xyyza
Entry = kinstype=BOTH
**** GMOCCAPY GETINIINFO ****
Number of joints = 5
5 COORDINATES found = xyyza
('Fount double letter ', )
joint 0 = axis x
joint 1 = axis y0
joint 2 = axis y1
joint 3 = axis z
joint 4 = axis a
{0: 'x', 1: 'y0', 2: 'y1', 3: 'z', 4: 'a'}
**** GMOCCAPY GETINIINFO ****
[KINS] KINESTYPE is trivkins
Found kinstype=BOTH but using trivkins
It is not recommended to do so!
Will use mode to switch between Joints and World mode
hopefully supported by the used <<trivkins>> module
**** GMOCCAPY GETINIINFO ****
No MAX_RAPID_OVERRIDE entry found in [DISPLAY] of INI file
Default settings 100 % applied!
**** GMOCCAPY GETINIINFO ****
Preference file path: /home/pi/linuxcnc/configs/plasma/Plasma.pref
**** GMOCCAPY GETINIINFO ****
No DEFAULT_SPINDLE_SPEED entry found in [DISPLAY] of INI file
**** GMOCCAPY INFO ****
**** no valid probe config in INI File ****
**** disabled tool measurement ****
**** GMOCCAPY INFO ****
**** Entering make_DRO
axis_list =
**** GMOCCAPY INFO ****
**** Entering make ref axis button
('Filepath = ', '/usr/share/gmoccapy/images/ref_all.png')
('Filepath = ', '/usr/share/gmoccapy/images/ref_0.png')
('Filepath = ', '/usr/share/gmoccapy/images/ref_1.png')
('Filepath = ', '/usr/share/gmoccapy/images/ref_2.png')
('Filepath = ', '/usr/share/gmoccapy/images/ref_3.png')
('Filepath = ', '/usr/share/gmoccapy/images/ref_4.png')
('Filepath = ', '/usr/share/gmoccapy/images/unhome.png')
**** GMOCCAPY INFO ****
**** Entering make touch button
**** GMOCCAPY INFO ****
**** Entering make jog increments
**** GMOCCAPY INFO ****
**** Entering make jog button
**** GMOCCAPY INFO ****
**** Entering make joints button
**** GMOCCAPY INFO ****
**** arrange JOINTS button
Found 10 Joints Button
**** GMOCCAPY INFO ****
**** Entering make macro button
found 0 Macros
**** GMOCCAPY INFO ****
**** arrange DRO
4
**** GMOCCAPY INFO ****
**** Place in table
**** GMOCCAPY INFO ****
**** get DRO order
**** GMOCCAPY INFO ****
**** arrange JOG button
less than 6 axis
**** GMOCCAPY INFO ****
**** no audio available! ****
**** PYGST libray not installed? ****
**** is python-gstX.XX installed? ****
**** GMOCCAPY INFO ****
**** Entering init gremlin ****
Kinematics type changed
('_set_enable_tooltips = ', True)
**** GMOCCAPY INFO ****
**** No virtual keyboard installed, we checked for <onboard> and <matchbox-keyboard>.
**** GMOCCAPY INFO: Gcode.lang found ****
**** GMOCCAPY GETINIINFO ****
Wrong entry [DISPLAY] CYCLE_TIME in INI File!
Will use gmoccapy default 150
**** GMOCCAPY INFO : inifile = /home/pi/linuxcnc/configs/plasma/plasma.ini ****:
**** GMOCCAPY INFO : postgui halfile = postgui.tcl ****:
Jog Pin Changed
x+
Jog Button released = x+
Jog Pin Changed
x-
Jog Button released = x-
Jog Pin Changed
y+
Jog Button released = y+
Jog Pin Changed
y-
Jog Button released = y-
Jog Pin Changed
z+
Jog Button released = z+
Jog Pin Changed
z-
Jog Button released = z-
Jog Pin Changed
a+
Jog Button released = a+
Jog Pin Changed
a-
Jog Button released = a-
Jog Pin Changed
0+
Jog Button released = 0+
Jog Pin Changed
0+
Jog Button released = 0+
Jog Pin Changed
1+
Jog Button released = 1+
Jog Pin Changed
1+
Jog Button released = 1+
Jog Pin Changed
2+
Jog Button released = 2+
Jog Pin Changed
2+
Jog Button released = 2+
Jog Pin Changed
3+
Jog Button released = 3+
Jog Pin Changed
3+
Jog Button released = 3+
Jog Pin Changed
4+
Jog Button released = 4+
Jog Pin Changed
4+
Jog Button released = 4+
IDLE
1 2
MANUAL Mode
RUN
IDLE
ntb_button_switch_page
('on button home clicked = ', 'ref_all')
('Hal Status not all homed', '0124')
('Hal Status not all homed', '124')
('Hal Status not all homed', '12')
('Hal Status not all homed', '2')
Combi DRO all homed
Combi DRO all homed
Combi DRO all homed
Combi DRO all homed
hal status motion mode changed
Hal Status all homed
ntb_button_switch_page
Jog Button pressed = y-
Jog Button released = y-
Jog ButtShutting down and cleaning up LinuxCNC...
task: 9501 cycles, min=0.000150, max=2.166802, avg=0.010410, 2 latency excursions (> 10x expected cycle time of 0.010000s)
hm2: loading Mesa HostMot2 driver version 0.15
hm2_eth: loading Mesa AnyIO HostMot2 ethernet driver version 0.2
hm2_eth: 10.10.10.10: INFO: Hardware address (MAC): 00:60:1b:16:86:c3
hm2_eth: discovered 7I96S
hm2/hm2_7i96s.0: Low Level init 0.15
hm2/hm2_7i96s.0: Smart Serial Firmware Version 43
hm2/hm2_7i96s.0: 51 I/O Pins used:
hm2/hm2_7i96s.0: IO Pin 000 (TB3-01): InM Input Module #0, pin in0 (Input)
hm2/hm2_7i96s.0: IO Pin 001 (TB3-02): InM Input Module #0, pin in1 (Input)
hm2/hm2_7i96s.0: IO Pin 002 (TB3-03): InM Input Module #0, pin in2 (Input)
hm2/hm2_7i96s.0: IO Pin 003 (TB3-04): InM Input Module #0, pin in3 (Input)
hm2/hm2_7i96s.0: IO Pin 004 (TB3-05): InM Input Module #0, pin in4 (Input)
hm2/hm2_7i96s.0: IO Pin 005 (TB3-06): InM Input Module #0, pin in5 (Input)
hm2/hm2_7i96s.0: IO Pin 006 (TB3-07): InM Input Module #0, pin in6 (Input)
hm2/hm2_7i96s.0: IO Pin 007 (TB3-08): InM Input Module #0, pin in7 (Input)
hm2/hm2_7i96s.0: IO Pin 008 (TB3-09): InM Input Module #0, pin in8 (Input)
hm2/hm2_7i96s.0: IO Pin 009 (TB3-10): InM Input Module #0, pin in9 (Input)
hm2/hm2_7i96s.0: IO Pin 010 (TB3-11): InM Input Module #0, pin in10 (Input)
hm2/hm2_7i96s.0: IO Pin 011 (TB3-13/TB3-14): SSR #0, pin Out-00 (Output)
hm2/hm2_7i96s.0: IO Pin 012 (TB3-15/TB3-16): SSR #0, pin Out-01 (Output)
hm2/hm2_7i96s.0: IO Pin 013 (TB3-17/TB3-18): SSR #0, pin Out-02 (Output)
hm2/hm2_7i96s.0: IO Pin 014 (TB3-19/TB3-20): SSR #0, pin Out-03 (Output)
hm2/hm2_7i96s.0: IO Pin 015 (TB3-21/TB3-22): OutM Output Module #0, pin Out-04 (Output)
hm2/hm2_7i96s.0: IO Pin 016 (TB3-23/TB3-24): OutM Output Module #0, pin Out-05 (Output)
hm2/hm2_7i96s.0: IO Pin 017 (TB1-02/TB1-03): StepGen #0, pin Step (Output)
hm2/hm2_7i96s.0: IO Pin 018 (TB1-04/TB1-05): StepGen #0, pin Direction (Output)
hm2/hm2_7i96s.0: IO Pin 019 (TB1-08/TB1-09): StepGen #1, pin Step (Output)
hm2/hm2_7i96s.0: IO Pin 020 (TB1-10/TB1-11): StepGen #1, pin Direction (Output)
hm2/hm2_7i96s.0: IO Pin 021 (TB1-14/TB1-15): StepGen #2, pin Step (Output)
hm2/hm2_7i96s.0: IO Pin 022 (TB1-16/TB1-17): StepGen #2, pin Direction (Output)
hm2/hm2_7i96s.0: IO Pin 023 (TB1-20/TB1-21): StepGen #3, pin Step (Output)
hm2/hm2_7i96s.0: IO Pin 024 (TB1-22-TB1-23): StepGen #3, pin Direction (Output)
hm2/hm2_7i96s.0: IO Pin 025 (TB2-02/TB2-03): StepGen #4, pin Step (Output)
hm2/hm2_7i96s.0: IO Pin 026 (TB2-04/TB2-05): StepGen #4, pin Direction (Output)
hm2/hm2_7i96s.0: IO Pin 027 (TB2-07/TB2-08): Encoder #0, pin A (Input)
hm2/hm2_7i96s.0: IO Pin 028 (TB2-10/TB2-11): Encoder #0, pin B (Input)
hm2/hm2_7i96s.0: IO Pin 029 (TB2-13/TB2-14): Encoder #0, pin Index (Input)
hm2/hm2_7i96s.0: IO Pin 030 (TB2-16/TB2-17): IOPort
hm2/hm2_7i96s.0: IO Pin 031 (TB2-18/TB2-19): IOPort
hm2/hm2_7i96s.0: IO Pin 032 (internal): IOPort
hm2/hm2_7i96s.0: IO Pin 033 (internal): SSR #0, pin AC Ref (internal) (Output)
hm2/hm2_7i96s.0: IO Pin 034 (P1-01): IOPort
hm2/hm2_7i96s.0: IO Pin 035 (P1-02): IOPort
hm2/hm2_7i96s.0: IO Pin 036 (P1-03): IOPort
hm2/hm2_7i96s.0: IO Pin 037 (P1-04): IOPort
hm2/hm2_7i96s.0: IO Pin 038 (P1-05): IOPort
hm2/hm2_7i96s.0: IO Pin 039 (P1-06): IOPort
hm2/hm2_7i96s.0: IO Pin 040 (P1-07): IOPort
hm2/hm2_7i96s.0: IO Pin 041 (P1-08): IOPort
hm2/hm2_7i96s.0: IO Pin 042 (P1-09): IOPort
hm2/hm2_7i96s.0: IO Pin 043 (P1-11): IOPort
hm2/hm2_7i96s.0: IO Pin 044 (P1-13): IOPort
hm2/hm2_7i96s.0: IO Pin 045 (P1-15): IOPort
hm2/hm2_7i96s.0: IO Pin 046 (P1-17): IOPort
hm2/hm2_7i96s.0: IO Pin 047 (P1-19): IOPort
hm2/hm2_7i96s.0: IO Pin 048 (P1-21): IOPort
hm2/hm2_7i96s.0: IO Pin 049 (P1-23): IOPort
hm2/hm2_7i96s.0: IO Pin 050 (P1-25): IOPort
hm2/hm2_7i96s.0: registered
hm2_eth: in hm2_eth_reset
hm2_eth: HostMot2 ethernet driver unloaded
hm2: unloading
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments
Debug file information:
Note: Using POSIX realtime
/usr/bin/gmoccapy:312: GtkWarning: Invalid icon size 48
self.widgets.window1.show()
(gmoccapy:1107): GtkSourceView-CRITICAL **: 19:40:04.973: gtk_source_language_manager_set_search_path: assertion 'lm->priv->ids == NULL' failed
Unexpected realtime delay on task 0 with period 1000000
This Message will only display once per session.
Run the Latency Test and resolve before continuing.
/usr/lib/python2.7/dist-packages/gmoccapy/notification.py:168: GtkWarning: Invalid icon size 48
self.popup.show()
/usr/bin/gmoccapy:5248: GtkWarning: Invalid icon size 48
gtk.main()
[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
python2: ../../src/xcb_io.c:263: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
/usr/bin/linuxcnc: line 896: 1107 Aborted $EMCDISPLAY -ini "$INIFILE" $EMCDISPLAYARGS $EXTRA_ARGS
1054
1103
Stopping realtime threads
Unloading hal components
Note: Using POSIX realtime
Info report created by linuxcnc_info:
The file: /tmp/linuxcnc_info.txt
can be posted to a forum or a web site like:
pastebin.com
in order to provide information about the linuxcnc
system and configuration.
Date: Mon 11 Nov 2024 07:44:27 PM EET
UTC Date: Mon 11 Nov 2024 05:44:27 PM UTC
this program: /usr/bin/linuxcnc_info
uptime: 19:44:27 up 5 min, 2 users, load average: 1.00, 1.22, 0.64
lsb_release -sa: Raspbian Raspbian GNU/Linux 10 (buster) 10 buster
which linuxcnc: /usr/bin/linuxcnc
pwd: /home/pi/linuxcnc/configs/plasma
USER: pi
LOGNAME: pi
HOME: /home/pi
EDITOR:
VISUAL:
LANGUAGE:
TERM: dumb
COLORTERM:
DISPLAY: :0.0
DESKTOP: LXDE-pi
display size: 1200x1280 pixels (318x339 millimeters)
PATH: /usr/bin:/home/pi/linuxcnc/configs/plasma/bin:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games
uname items:
nodename -n: raspberrypi
kernel-name -s: Linux
kernel-vers -v: #1 SMP PREEMPT RT Fri Jan 1 21:15:16 GMT 2021
machine -m: armv7l
processor -p: unknown
platform -i: unknown
oper system -o: GNU/Linux
/proc items:
cmdline: coherent_pool=1M 8250.nr_uarts=0 cma=64M bcm2708_fb.fbwidth=1200 bcm2708_fb.fbheight=1280 bcm2708_fb.fbswap=1 smsc95xx.macaddr=DC:A6:32:F7:46:81 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty1 root=PARTUUID=fdc20b50-02 rootfstype=ext4 elevator=deadline fsck.repair=yes isolcpus=3 idle=poll rootwait quiet splash plymouth.ignore-serial-consoles cfg80211.ieee80211_regdom=LT
model name: ARMv7 Processor rev 3 (v7l)
cores:
cpu MHz:
parport:
serial:
Versions:
gcc: gcc (Raspbian 8.3.0-6+rpi1) 8.3.0
python: Python 2.7.16
git: git version 2.20.1
git commit: NA
tcl: 8.6
tk: 8.6
glade: not_in_PATH
glade-gtk2: not_in_PATH
linuxcnc_var all:
LINUXCNCVERSION: 2.8.4
LINUXCNC_AUX_GLADEVCP: /usr/share/linuxcnc/aux_gladevcp
LINUXCNC_AUX_EXAMPLES: /usr/share/linuxcnc/aux_examples
REALTIME: /etc/init.d/realtime
RTS: uspace
HALLIB_DIR: /usr/share/linuxcnc/hallib
dpkg -l '*linuxcnc*':
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===============-============-============-=====================================================================
un linuxcnc <none> <none> (no description available)
un linuxcnc-doc <none> <none> (no description available)
ii linuxcnc-doc-en 1:2.8.4 all motion controller for CNC machines and robots (English documentation)
un linuxcnc-sim <none> <none> (no description available)
ii linuxcnc-uspace 1:2.8.4 armhf motion controller for CNC machines and robots
Thank you
- PCW
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.
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.
Time to create page: 1.698 seconds