Search Results (Searched for: recommended hardware)
- langdons
- langdons
Today 20:05 - Today 20:07
Replied by langdons on topic Recommended New Install of LinuxCNC coming from EMC2 and Ubuntu 10.4
Recommended New Install of LinuxCNC coming from EMC2 and Ubuntu 10.4
Category: Installing LinuxCNC
Older hardware generally needs an oldish OS.
An OS 10 years younger than the hardware seems to be a good rule of thumb.
www.linuxcnc.org/iso/ubuntu-10.04-linuxcnc3-i386.iso
www.linuxcnc.org/iso/linuxcnc-2.7.14-wheezy.iso
An OS 10 years younger than the hardware seems to be a good rule of thumb.
www.linuxcnc.org/iso/ubuntu-10.04-linuxcnc3-i386.iso
www.linuxcnc.org/iso/linuxcnc-2.7.14-wheezy.iso
- Aciera
10 May 2025 16:14 - 11 May 2025 19:17
Replied by Aciera on topic Planning to Retrofit a Mazak Integrex200Y Mill-Turn Machine
Planning to Retrofit a Mazak Integrex200Y Mill-Turn Machine
Category: Advanced Configuration
Here is the promised sim config:
To test:
1. unzip
2. 'halcompile --install' the enclosed 'mazak_integrex_200y_kins.comp'
3. start 'mazak-integrex-200y' config and run the preloaded gcode program
If you have any questions, which is likely, just ask.
Text from the enclosed README file:
To test:
1. unzip
2. 'halcompile --install' the enclosed 'mazak_integrex_200y_kins.comp'
3. start 'mazak-integrex-200y' config and run the preloaded gcode program
If you have any questions, which is likely, just ask.
Text from the enclosed README file:
Experimental simulation of a 5axis Mill/Turn machine (eg MAZAK Integrex 200Y)
Implemented Gcodes:
- 'G67 B': Moves the B-axis to the 'B'-word position and activates 'HALF TCP Lathe' mode.
- 'G68 B (X Y Z)': Moves the B-axis to the 'B'-word position then defines and activates a work plane perpendicular the this current tool orientation with the origin at the current WCS (optionally offset by any [X,Y,Z]-Words). This will change WCS to 'G59' where the transformed work offset values have been written to (ie the prior values stored in G59 will be lost!).
- 'G68.1 (X Y Z)': Defines and activates a work plane perpendicular the the current tool orientation with the origin at the current WCS (optionally offset by any [X,Y,Z]-Words). For change to WCS see 'G68'
- 'G69': Cancels the work plane set by 'G68' and (currently) switches back to 'G54'.
NOTES:
- This config defines the work-spindle as '$0' and the tool-spindle as '$1'. Example: 'M19 $1 R90' will orient the tool-spindle to 90°. (For real hardware it is recommended to use the spindle encoder-position instead of using 'spindle.1.orient-angle'.)
- 'HALF/FULL TCP MILL/LATHE' modes include tracking of tool-spindle rotation.
- 'HALF TCP MILL/LATHE' modes do not track the work spindle rotation, this is intended behavior.
- 'FULL TCP MILL' mode will track all rotations.
- Tool-offsets must only be changed in 'Identity' mode as it may cause sudden joint movements otherwise.
- Lathe tools must only be used in 'Identity' or 'HALF TCP Lathe' mode.
- Mill tools must only be used in 'HALF/FULL TCP Mill' or 'TWP' mode.
- Due to easier abort handling we currently restrict the use of twp to G54 as LinuxCNC seems to revert to G54 as the default system.
Abort behavior can be handled by using a subroutine defined in the ini file under [RS274NGC]ON_ABORT_COMMAND'.
- The TWP remap code in this config does not implement virtual rotations (ie no optional 'R' word).- langdons
- langdons
21 Mar 2025 15:52 - 21 Mar 2025 15:55
Replied by langdons on topic Hardware advice
Hardware advice
Category: Computers and Hardware
"www.omc-stepperonline.com/ys-series-3-ax...ower-supply-3-clys90
* Given the age of the steppers, many people are stating that they are likely weak - due to the age of their magnets and the type of magnets they used."
Also, while the stuff from stepper online looks nice and has nice aviation connectors, it has 3 switching power supplies.
Linear (Huge and heavy) are generally recommended because they are better suited to the spikey, noisy, intermitten current draw that stepper drivers exhibit, though either will do.
What magnets?
I'm 99.9% sure stepper motors have no permanent magnets.
Anyways, that can't be true; stepper motors are brushless.
Brushless motors should not, and generally do not, wear out.
* Given the age of the steppers, many people are stating that they are likely weak - due to the age of their magnets and the type of magnets they used."
Also, while the stuff from stepper online looks nice and has nice aviation connectors, it has 3 switching power supplies.
Linear (Huge and heavy) are generally recommended because they are better suited to the spikey, noisy, intermitten current draw that stepper drivers exhibit, though either will do.
What magnets?
I'm 99.9% sure stepper motors have no permanent magnets.
Anyways, that can't be true; stepper motors are brushless.
Brushless motors should not, and generally do not, wear out.
- rainbowkoala49
- rainbowkoala49
24 Feb 2025 06:31 - 24 Feb 2025 06:42
Which combination of mesa cards should I use? was created by rainbowkoala49
Which combination of mesa cards should I use?
Category: Driver Boards
I have an existing SBZ 130 i want to retrofit by keeping the original motors+drives, the motors all (3 axis and spindle) are AC 3PH servos with integrated 2 pole resolvers (6 wires - sin, cos, excitation pairs) for their feedback, aside from that I have about 42 inputs and 36 outputs as per the machines original schematics, but I might not use every single one. Moreover, I also want to add a separate rotary milling head for chamfers at different angles later down the line, so how would I go about adding/changing the combination of mesa cards.
The same machine I've seen a successful retrofit using combination of 6i25 7i77 7i70 7i71 7i74, but that system all the motors had absolute encoders
Mine is slightly different model (1998, mine is 2001) and I was recommended from a different person to go with 6i24 (do i need 6i24-16 or 25 and whats the difference??), 7i49 for the resolvers and controlling the drives with 10v analog, but would this work? I'm a complete beginner to this field so I'd like to know before purchasing any hardware. Moreover, do I need the other cards as well? (7i70 7i71 7i74) I understand the first two are for extra I/O digitals but im not sure what the 7i74 does, if someone can explain I would greatly appreciate it.
Edit : I just found out that the 6i24 has about 70 I/O pins, I think that covers my need so I dont need the extra 7i70 and 7i71 right?
The same machine I've seen a successful retrofit using combination of 6i25 7i77 7i70 7i71 7i74, but that system all the motors had absolute encoders
Mine is slightly different model (1998, mine is 2001) and I was recommended from a different person to go with 6i24 (do i need 6i24-16 or 25 and whats the difference??), 7i49 for the resolvers and controlling the drives with 10v analog, but would this work? I'm a complete beginner to this field so I'd like to know before purchasing any hardware. Moreover, do I need the other cards as well? (7i70 7i71 7i74) I understand the first two are for extra I/O digitals but im not sure what the 7i74 does, if someone can explain I would greatly appreciate it.
Edit : I just found out that the 6i24 has about 70 I/O pins, I think that covers my need so I dont need the extra 7i70 and 7i71 right?
- cakeslob
- cakeslob
18 Jan 2025 00:57
The drivers are made specifically for the RPi3/4 and 5, so they dont use spidev and wont work with other sbc. It wont work on a PC with TPM unless someone makes some kind of hardware driver. If you dont want to use an Rpi, you can try out the remora ethernet board
Replied by cakeslob on topic recommended controller board
recommended controller board
Category: General LinuxCNC Questions
but a Raspi 5 combined with Remora is an option. This uses an SPI bus to communicate with a microcontroller that does the step generation, but it still needs a low latency communication channel to exchange data with a servo thread. Apparently it's untested or not supported to attempt to use an SPI bus from another SBC then the Raspi 5.
SPI is supposed to be unavailable on regular PC's, but as far as I know it's often available on the TPM module, together with the LPC bus. But I have not seen any hint of LinuxCNC being able to work with those communication channels.
The drivers are made specifically for the RPi3/4 and 5, so they dont use spidev and wont work with other sbc. It wont work on a PC with TPM unless someone makes some kind of hardware driver. If you dont want to use an Rpi, you can try out the remora ethernet board
- User_paulvdh_42
- User_paulvdh_42
17 Jan 2025 21:06
Replied by User_paulvdh_42 on topic recommended controller board
recommended controller board
Category: General LinuxCNC Questions
I'm also pretty new regarding LinuxCNC, and in the process of orienting for the direction to control my machine.
A quick search:
duckduckgo.com/?t=h_&q=Unimat+SL100+&iax=images&ia=images
SL1000 (with three zero's) is a hobby level lathe.
Do you already have a PC for controlling your machine?
LinuxCNC needs a specially crafted OS with a real time kernel and quick I/O capabilities, because it does all calcualtions on the PC side. If you want to use USB, something like GRBL may be more appropriate. With GRBL, you send the G-code to a microcontroller, and the microcontroller does all the real time stuff. This makes the communication between the PC and the controller very tolerant of timing issues, the PC also does not need to meet real time performance, and any PC can be used. Have a look at the GrblHAL project, where you can choose from quite a lot of different microcontroller families.
For LinuxCNC
Parallel ports are mostly obsolete as PC hardware, but there are still motherboards where an LPT port is available on an internal header, but does not have a connector on the outside of the PC.
The lowest cost option (except the 2nd hand PC from the attic) for LinuxCNC is probably one of those SBC's I once had a working machine with machinekit on a Beaglebone Black, but it was headless and X-forwarding over SSH was atrociously slow (about a 2Hz display update rate. In the meantime Machinekit has mostly died too, but a Raspi 5 combined with Remora is an option. This uses an SPI bus to communicate with a microcontroller that does the step generation, but it still needs a low latency communication channel to exchange data with a servo thread. Apparently it's untested or not supported to attempt to use an SPI bus from another SBC then the Raspi 5.
SPI is supposed to be unavailable on regular PC's, but as far as I know it's often available on the TPM module, together with the LPC bus. But I have not seen any hint of LinuxCNC being able to work with those communication channels.
A quick search:
duckduckgo.com/?t=h_&q=Unimat+SL100+&iax=images&ia=images
SL1000 (with three zero's) is a hobby level lathe.
Do you already have a PC for controlling your machine?
LinuxCNC needs a specially crafted OS with a real time kernel and quick I/O capabilities, because it does all calcualtions on the PC side. If you want to use USB, something like GRBL may be more appropriate. With GRBL, you send the G-code to a microcontroller, and the microcontroller does all the real time stuff. This makes the communication between the PC and the controller very tolerant of timing issues, the PC also does not need to meet real time performance, and any PC can be used. Have a look at the GrblHAL project, where you can choose from quite a lot of different microcontroller families.
For LinuxCNC
Parallel ports are mostly obsolete as PC hardware, but there are still motherboards where an LPT port is available on an internal header, but does not have a connector on the outside of the PC.
The lowest cost option (except the 2nd hand PC from the attic) for LinuxCNC is probably one of those SBC's I once had a working machine with machinekit on a Beaglebone Black, but it was headless and X-forwarding over SSH was atrociously slow (about a 2Hz display update rate. In the meantime Machinekit has mostly died too, but a Raspi 5 combined with Remora is an option. This uses an SPI bus to communicate with a microcontroller that does the step generation, but it still needs a low latency communication channel to exchange data with a servo thread. Apparently it's untested or not supported to attempt to use an SPI bus from another SBC then the Raspi 5.
SPI is supposed to be unavailable on regular PC's, but as far as I know it's often available on the TPM module, together with the LPC bus. But I have not seen any hint of LinuxCNC being able to work with those communication channels.
- Hakan
- Hakan
05 Jan 2025 09:08
Replied by Hakan on topic First time configuring ethercat
First time configuring ethercat
Category: EtherCAT
There isn't a stepconf or pncconf equivalent for ethercat so what I do is to configure the machine using one of these tools and then replace the connection to hardware. Editing by hand. Can be a bit of a handful for a first tine linuxcnc project.
Here is what other people do, including a link to rodw's example ethercat config. forum.linuxcnc.org/ethercat/51016-what-d...recommended-hardware
Here is what other people do, including a link to rodw's example ethercat config. forum.linuxcnc.org/ethercat/51016-what-d...recommended-hardware
- blazini36
- blazini36
03 Jan 2025 22:46
Alot of miniPCs expose Intel UART on GPIO headers. I've gotten it to run at reasonably high baud rates but I've only actually used it at standard baud rates. You're pretty much on point about SPI though I2C does get used in alot of cabled applications, Every HDMI cable has I2C in it. It's pretty easy to convert UART to RS422 with just a transceiver IC so that's not a big deal, not sure if using UART for this has any real benefits being there is no RT component but that's one of the things I was hoping to try out as I'd think it'd be just as easy to setup with Arduino-Connector.
I pretty much dropped what I was doing with Arduino-Connector because the lag on the Python side was intolerable. I just looked at the git issues and somebody figured out that it was just due to some serial timeout settings so I'll probably start messing with it again. One problem is I wasn't thrilled about the way the matrix keyboard setup worked and I would up redesigning my key panel to use I2C IO expanders to use with something else that didn't get finished. Now I'm just hoping someone can get support for I2C IO into Arduino Connector so I can try that. I don't think it would be difficult, but I don't do much code myself.
Replied by blazini36 on topic Arduino IO Expansion
Arduino IO Expansion
Category: Show Your Stuff
I actually mentioned this before as you would think as much legacy is built into LinucCNC someone would have worked on an RT serial component. I know Andy replied something along the lines of "I was wondering the same thing" but didn't offer much insight.I guess SPI would tie you to an arm platform or trying to bit bang from the host PC.
SPI is not recommended for long distance runs (its only really meant to board comms), even 6 or so inches can be unreliable when approaching MHz speeds. Seen this when experimenting with a Mesa 7c81.
Serial can use differential signals if there is noise, SPI differential signals can play havoc with timing at speeds.
And in reality unless you have a real hardware serial port, the serial comms is USB (at the host PC), doesn't run in realtime......in fact there is no realtime serial driver for Linuxcnc.
Alot of miniPCs expose Intel UART on GPIO headers. I've gotten it to run at reasonably high baud rates but I've only actually used it at standard baud rates. You're pretty much on point about SPI though I2C does get used in alot of cabled applications, Every HDMI cable has I2C in it. It's pretty easy to convert UART to RS422 with just a transceiver IC so that's not a big deal, not sure if using UART for this has any real benefits being there is no RT component but that's one of the things I was hoping to try out as I'd think it'd be just as easy to setup with Arduino-Connector.
I pretty much dropped what I was doing with Arduino-Connector because the lag on the Python side was intolerable. I just looked at the git issues and somebody figured out that it was just due to some serial timeout settings so I'll probably start messing with it again. One problem is I wasn't thrilled about the way the matrix keyboard setup worked and I would up redesigning my key panel to use I2C IO expanders to use with something else that didn't get finished. Now I'm just hoping someone can get support for I2C IO into Arduino Connector so I can try that. I don't think it would be difficult, but I don't do much code myself.
- Cant do this anymore bye all
03 Jan 2025 09:01
Replied by Cant do this anymore bye all on topic Arduino IO Expansion
Arduino IO Expansion
Category: Show Your Stuff
I guess SPI would tie you to an arm platform or trying to bit bang from the host PC.
SPI is not recommended for long distance runs (its only really meant to board comms), even 6 or so inches can be unreliable when approaching MHz speeds. Seen this when experimenting with a Mesa 7c81.
Serial can use differential signals if there is noise, SPI differential signals can play havoc with timing at speeds.
And in reality unless you have a real hardware serial port, the serial comms is USB (at the host PC), doesn't run in realtime......in fact there is no realtime serial driver for Linuxcnc.
SPI is not recommended for long distance runs (its only really meant to board comms), even 6 or so inches can be unreliable when approaching MHz speeds. Seen this when experimenting with a Mesa 7c81.
Serial can use differential signals if there is noise, SPI differential signals can play havoc with timing at speeds.
And in reality unless you have a real hardware serial port, the serial comms is USB (at the host PC), doesn't run in realtime......in fact there is no realtime serial driver for Linuxcnc.
- Cant do this anymore bye all
01 Jan 2025 12:49
Replied by Cant do this anymore bye all on topic LinuxCNC on Raspberry Pi 5
LinuxCNC on Raspberry Pi 5
Category: Installing LinuxCNC
You coming at this arse about. Which makes me wonder if this is for academic purposes, a potential commercial endeavor or a tech blog.
First one decides on the type of cnc machine they want to build, then they choose the controller to suit.
The simplest entry point for one who has no plan for their actual "cnc machine" would be.
A Lenovo M73e tower, preferably with an i5, the appropriate MB to Parallel Port cable ( there's some trickery with the cable that enables the PP hardware) and a generic Parallel Port breakout board. I've recommended this combination as I know it works, I have tested it with a lathe for basic functionality. I actually found this machine on the side of road with a celeron processor, which I swapped out for an i5 (3470 I think) and an SSD from the "useful box".
What people want is something that will run their hardware (their cnc machine be it a plasma cutter, lathe, mill router, laser tube profiler, PnP machine, cnc soldering machine) at a price point they can afford. As you can guess this is quite an expansive list.
First one decides on the type of cnc machine they want to build, then they choose the controller to suit.
The simplest entry point for one who has no plan for their actual "cnc machine" would be.
A Lenovo M73e tower, preferably with an i5, the appropriate MB to Parallel Port cable ( there's some trickery with the cable that enables the PP hardware) and a generic Parallel Port breakout board. I've recommended this combination as I know it works, I have tested it with a lathe for basic functionality. I actually found this machine on the side of road with a celeron processor, which I swapped out for an i5 (3470 I think) and an SSD from the "useful box".
What people want is something that will run their hardware (their cnc machine be it a plasma cutter, lathe, mill router, laser tube profiler, PnP machine, cnc soldering machine) at a price point they can afford. As you can guess this is quite an expansive list.
- dbtayl
- dbtayl
17 Nov 2024 22:34 - 17 Nov 2024 22:39
Replied by dbtayl on topic Strange motion offsets in one direction on one axis
Strange motion offsets in one direction on one axis
Category: General LinuxCNC Questions
1. Entirely plausible
2. Yes. The point of those was to highlight the noise seen is very high frequency, and seemingly unlikely to cause steps
3. Spindle is a BT30 taper with a manual drawbar- no ATC/belleville washers/pull studs/etc. End mill is held in a Nikken SK10 collet holder torqued to 35~40 ft-lbs, which is the recommended value. Tools are changed with an impact driver on the drawbar.
4. I should definitely re-run the code and see if I can reproduce. Haven't wanted to spend the time/material doing so, but I've wasted enough other time on this to dwarf both costs. I'll rerun both with the same tools originally used and also with a different one. May or may not have time to do that today.
5. I put an indicator on the tool and pushed on it. I can get it to deflect ~0.0005 (5 tenths) before I don't really want to push on it any harder. Seems to apply going any direction.
6. So climb vs conventional? I've thought about this, but the pocket was roughed with an adaptive/HSM toolpath, which started in the center of the pocket- so the cutter is roughing -Y to +Y on the +X side of the pocket, and +Y to -Y on the -X side. Correct me if my logic is wrong here, but if cut direction were the problem, wouldn't you expect to see issues in (eg) the +X+Y and -X-Y quadrants instead of the -Y half?
Grounding: One ground loop snuck in (shielded cable with shield connected at both ends), though disconnecting that has no impact on noise I can see. Will fix it anyway.
Beyond that, I wouldn't rule ground issues out, but am not seeing an obvious issue. The entire cabinet is aluminum and grounded. It's not a single point due to eg the filters, PSUs, and spindle drive all grounding through their chassis. The axis motors have a completely isolated supply (transformer-based)- as far as they're concerned, the world is the isolated 65V and a couple opto-couplers. The 24V and 5V negatives are all tied to a single bus bar- which is NOT ground. A multimeter shows an open circuit between 24V negative and the enclosure. The machine body has no dedicated ground, but is grounded indirectly via the spindle motor. The axis motor bodies are electrically connected to the machine, but that's isolated from their power supply.
Spindle drive has all the recommended filtering. I deviated slightly from the recommendations by omitting fuses on the logic power, replacing the contactor with an SSR, and placing said SSR before all the filtering, though I don't see an issue with that. Pictures show datasheet drawing and the schematic of how my machine is wired.
Noise is much better when motors are disabled- got it on my to-do list to see what's the root causes there. Guess is the spindle drive, but need to verify. No ferrites on anything at the moment- and no mention of them in the DYN4 (spindle) nor ClearPath (axis) manuals. Not to say they wouldn't help, just that the manuals don't call them out as important. The PSUs are MeanWell units, so at least not no-name. SOP is to not buy dubious PSUs- they can cause too many problems and take out too much valuable hardware to be worth the risk. Not to mention noise, as you say.
2. Yes. The point of those was to highlight the noise seen is very high frequency, and seemingly unlikely to cause steps
3. Spindle is a BT30 taper with a manual drawbar- no ATC/belleville washers/pull studs/etc. End mill is held in a Nikken SK10 collet holder torqued to 35~40 ft-lbs, which is the recommended value. Tools are changed with an impact driver on the drawbar.
4. I should definitely re-run the code and see if I can reproduce. Haven't wanted to spend the time/material doing so, but I've wasted enough other time on this to dwarf both costs. I'll rerun both with the same tools originally used and also with a different one. May or may not have time to do that today.
5. I put an indicator on the tool and pushed on it. I can get it to deflect ~0.0005 (5 tenths) before I don't really want to push on it any harder. Seems to apply going any direction.
6. So climb vs conventional? I've thought about this, but the pocket was roughed with an adaptive/HSM toolpath, which started in the center of the pocket- so the cutter is roughing -Y to +Y on the +X side of the pocket, and +Y to -Y on the -X side. Correct me if my logic is wrong here, but if cut direction were the problem, wouldn't you expect to see issues in (eg) the +X+Y and -X-Y quadrants instead of the -Y half?
Grounding: One ground loop snuck in (shielded cable with shield connected at both ends), though disconnecting that has no impact on noise I can see. Will fix it anyway.
Beyond that, I wouldn't rule ground issues out, but am not seeing an obvious issue. The entire cabinet is aluminum and grounded. It's not a single point due to eg the filters, PSUs, and spindle drive all grounding through their chassis. The axis motors have a completely isolated supply (transformer-based)- as far as they're concerned, the world is the isolated 65V and a couple opto-couplers. The 24V and 5V negatives are all tied to a single bus bar- which is NOT ground. A multimeter shows an open circuit between 24V negative and the enclosure. The machine body has no dedicated ground, but is grounded indirectly via the spindle motor. The axis motor bodies are electrically connected to the machine, but that's isolated from their power supply.
Spindle drive has all the recommended filtering. I deviated slightly from the recommendations by omitting fuses on the logic power, replacing the contactor with an SSR, and placing said SSR before all the filtering, though I don't see an issue with that. Pictures show datasheet drawing and the schematic of how my machine is wired.
Noise is much better when motors are disabled- got it on my to-do list to see what's the root causes there. Guess is the spindle drive, but need to verify. No ferrites on anything at the moment- and no mention of them in the DYN4 (spindle) nor ClearPath (axis) manuals. Not to say they wouldn't help, just that the manuals don't call them out as important. The PSUs are MeanWell units, so at least not no-name. SOP is to not buy dubious PSUs- they can cause too many problems and take out too much valuable hardware to be worth the risk. Not to mention noise, as you say.
- LabOuest
- LabOuest
17 Nov 2024 14:06 - 17 Nov 2024 14:37
Replied by LabOuest on topic Remora - ethernet NVEM / EC300 / EC500 cnc board
Remora - ethernet NVEM / EC300 / EC500 cnc board
Category: Computers and Hardware
Yeah, I was running a youtube video in the background but still, you're right, it's quite high.
I thought that this could be a possible cause so I've already made all of the recommended changes to the bios.
Thank you for the heads up on the core isolation, I must have misunderstood Talla83's video.
I will try to better understand kernel settings, unfortunately, there's isn't a lot of information about my dell optiplex 3020m.
Pinging the EC500 gives a latency between 0.130 and 0.25ms.
I'm trying to narrow down the possible causes, do you experience about the same ethernet latency as I do ?
EDIT: Using Halshow I can get so more debug information:
I thought that this could be a possible cause so I've already made all of the recommended changes to the bios.
Thank you for the heads up on the core isolation, I must have misunderstood Talla83's video.
I will try to better understand kernel settings, unfortunately, there's isn't a lot of information about my dell optiplex 3020m.
Pinging the EC500 gives a latency between 0.130 and 0.25ms.
I'm trying to narrow down the possible causes, do you experience about the same ethernet latency as I do ?
EDIT: Using Halshow I can get so more debug information:
- remora.read.time is between 5 to 700 000
- remora.update-freq.time is between 4-700
- remora.write.time is 5 to 800 000
- jkaminski
- jkaminski
15 Nov 2024 20:27 - 15 Nov 2024 20:30
Replied by jkaminski on topic Position vs Velocity mode
Position vs Velocity mode
Category: EtherCAT
Hi!
@zmrdko :
thank to you and other experienced users in this thread for educating other folks and providing invaluable linuxcnc knowledge. I have some follow up questions on one of your posts:
- Would you mind sharing which z390 motherboard manufacturer / series do you have that allowed you to achieve 2.3us latency?
- What Intel PCIe Ethernet card did you choose? I saw that in this thread: gitlab.com/etherlab.org/ethercat/-/issues/104 they recommended "cheap realtek 100mb/s" ethernet card.
- Did you go with intel integrated graphics?
- IIRC, you (or maybe other user?) mentioned that with newer kernel the performance dropped from 8kHz (at 4.19rt) to 4kHz.
- Were there any other factors that positively affected performance besides the servo thread latency to get 8kHz? (e.g. ethernet roundtrip was quick)
- Have you measured how long does it take to execute your HAL components in each control cycle?
- Is there some other computer hardware that you leaned about and would be eager to try out with EtherCAT?
I hope this is not too much off-topic. Please correct me if there is a better form to ask these questions.
Thank you for your consideration,
Regards, Jakub
@zmrdko :
thank to you and other experienced users in this thread for educating other folks and providing invaluable linuxcnc knowledge. I have some follow up questions on one of your posts:
- Would you mind sharing which z390 motherboard manufacturer / series do you have that allowed you to achieve 2.3us latency?
- What Intel PCIe Ethernet card did you choose? I saw that in this thread: gitlab.com/etherlab.org/ethercat/-/issues/104 they recommended "cheap realtek 100mb/s" ethernet card.
- Did you go with intel integrated graphics?
- IIRC, you (or maybe other user?) mentioned that with newer kernel the performance dropped from 8kHz (at 4.19rt) to 4kHz.
- Were there any other factors that positively affected performance besides the servo thread latency to get 8kHz? (e.g. ethernet roundtrip was quick)
- Have you measured how long does it take to execute your HAL components in each control cycle?
- Is there some other computer hardware that you leaned about and would be eager to try out with EtherCAT?
I hope this is not too much off-topic. Please correct me if there is a better form to ask these questions.
Thank you for your consideration,
Regards, Jakub
- 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
- rebelx
- rebelx
25 Oct 2024 11:49
LinuxCNC on Intel Clear Linux was created by rebelx
LinuxCNC on Intel Clear Linux
Category: Installing LinuxCNC
I have been playing with the "Clear Linux" distro for a while, and I am truly impressed by its blazing fast performance. Clear Linux is an open source project from Intel, and it is highly optimized for Intel platforms, although most of these optimizations also apply to AMD platforms.
From its website clearlinux.org : "Clear Linux OS is an open source, rolling release Linux distribution optimized for performance and security, from the Cloud to the Edge, designed for customization, and manageability."
Clear Linux (CL) works with software packages that are called Bundles. A Bundle is in a way similar to a Flatpak, as it includes all the dependencies and the bundle is thoroughly tested to work on any Clear Linux system. When a package is not available yet as a Bundle, it is also possible to compile software from source, but the recommended way to install a new application is by submitting a package-request, after which the request will be reviewed by the CL team and eventually assigned to a CL resource for creating and maintaining a new bundle for that application.
I have been trying to compile LinuxCNC on Clear Linux, but ran into too many dependency issues that could not easily be resolved as many libraries are not available on Clear Linux yet, and compiling them all one by one is a very time consuming job. As I think that it would be a very interesting case to have a dedicated LinuxCNC bundle created for CL that will allow a "one click" installation of LinuxCNC on Clear Linux, I submitted a package-request to the CL team earlier this week and I am very happy to see that it has already been assigned to an experienced Intel developer who is also active in several CNC communities. I hope this may result in an easy way to install LinuxCNC on Clear Linux and I am very curious to see if any of their performance optimizations may be beneficial to LinuxCNC. I think it could provide a secure and stable way to run LinuxCNC on modern hardware platforms moving forward.
My CL package-request can be found here: github.com/clearlinux/distribution/issues/3197
Please share your thoughts on this.
From its website clearlinux.org : "Clear Linux OS is an open source, rolling release Linux distribution optimized for performance and security, from the Cloud to the Edge, designed for customization, and manageability."
Clear Linux (CL) works with software packages that are called Bundles. A Bundle is in a way similar to a Flatpak, as it includes all the dependencies and the bundle is thoroughly tested to work on any Clear Linux system. When a package is not available yet as a Bundle, it is also possible to compile software from source, but the recommended way to install a new application is by submitting a package-request, after which the request will be reviewed by the CL team and eventually assigned to a CL resource for creating and maintaining a new bundle for that application.
I have been trying to compile LinuxCNC on Clear Linux, but ran into too many dependency issues that could not easily be resolved as many libraries are not available on Clear Linux yet, and compiling them all one by one is a very time consuming job. As I think that it would be a very interesting case to have a dedicated LinuxCNC bundle created for CL that will allow a "one click" installation of LinuxCNC on Clear Linux, I submitted a package-request to the CL team earlier this week and I am very happy to see that it has already been assigned to an experienced Intel developer who is also active in several CNC communities. I hope this may result in an easy way to install LinuxCNC on Clear Linux and I am very curious to see if any of their performance optimizations may be beneficial to LinuxCNC. I think it could provide a secure and stable way to run LinuxCNC on modern hardware platforms moving forward.
My CL package-request can be found here: github.com/clearlinux/distribution/issues/3197
Please share your thoughts on this.
Time to create page: 8.539 seconds