Advanced Search

Hello, I built a mach 3 based plasma table using junk china parts. I am sick of dealing with problem after problem. Latest one is the board crashing and losing all usb including the mouse and keyboard. I figure it's time to upgrade and the thc integration really captivated me towards Linux cnc aswell as the freedom modify. I have never ran linux before but I am no beginner to computers and building stuff. I was looking into the mesa boards. Does anybody have any recommendations for a super reliable computer to purchase to run linux cnc in a industrial setting and any recommendations for the breakout board and thc to run a plasma table? Thanks. 

how did you solve those errors?

My base thread is getting over 100k when I run my Hal test and I keep getting a error when I start linuxcnc and it won't let me run my machine. It was working before but now it's not.

I have recently converted my mini lathe with a 7i96s. Everything is working amazingly well. 
I mostly turn plastics, brass and aluminum. While drilling plastics, namely acrylic- I need to go to a depth of 65 mm which melts the acrylic if I fail to provide coolant properly. 
I would like to add a flood coolant system to my lathe. Maybe just adding a DC motor pump to the 7i96s would serve the purpose. I have learnt that I can add an external SSR to the 7i96s outputs and driving the DC pump through the external SSR. But I am a bit unsure about the wiring (total newbie in electronics, also my fear of blowing up my 7i96s), can anyone help me with the wiring and maybe if I need something more for the electronics setup?
​

On you actionbutton (in Designer):
Select property 'indicator_status_option'
Select property 'is_homed_status'

Then set your stylesheet, though usually one would set a specific button:

I live in north ... here continuos rain these year not usual ... some disaster happens .... not a lucky year for whether here. These summer until 1.5 month ago 42°C than in 5 days we go to 18°C ... and now it rain every days with stop of 1 or 2 days than rain again.
Happy places Holland. Your plains are very beatiful. Never visit Kosovo .... before I had the boys I thought of going to visit Tommilight on  motorbike....now the motorbike has dust and it's been almost 10 years. ... life is strange .... beautiful and strange ....

When opcua compile correctly using cmakelist ... I add that features on my project, for now seems I use double version od opcua62541.h heather ... maybe ... installation process on qt is not well understand from my side. So I have multiple copy of plugin and heather in many parts.

 

spindle speed 2000-2500 rpm

meister wrote:

Hi,
very cool !!!!

for my board without oscillator, i need to run:
```
gpio mode 7 clock
gpio clock 7 5000000
```
to provide a clock signal for the FPGA


for flashing i use this script:
```
riocore/configs/IceShield/spiflash.sh
```
all as root.

LinuxCNC runs as user,
i think i use the normal LinuxCNC RPI image (bookworm)

if you use the default config with:
```
{
"type": "blink",
"pins": {
"led": {
"pin": "LED:G"
}
},
"frequency": 1.0
},
```
on of the LED's have to blink with 1Hz after flashing

to test the connection, you can also use the rio-test tool:
```
bin/rio-test riocore/configs/IceShield/config.json
```
 

It works! Thank you, the GPCKL0 gpio config was just what I needed. Linuxcnc talks to it just fine now. Also, it seems I forgot to route pin 7 to 35 on the FPGA

I'll adjust the board to route that line, dump a production outputs file and instructions for people to order it, and push it up to github along with the config once I confirm the motors and switches do what I need them to do for a standard 3 axis mill setup.

 

To add a liyttle more detail:

-> qtversaprobe.enable

reflects the state of the 'measure tool' button on the versa probe screen.
This is a manual selection button (to ignore auto probing)
It doesn't do anything unless the remap code utilizes it such as:

-> qtversaprobe.probe-loaded

true when the tool number equals the preference files entry:
ps_probe_tool = 1

It doesn't do anything unless connected to other logic such as spindle.0.inhibit.
If you have multiple signals to connect to spindle.0.inhibit, then you must use an OR logic component.
 

No homing expert, but if the search and latch velocities are in the same direction
it seem like you would always end up on the switch after homing if the home final
velocity was 0 (and it seem to be set to 0 on all joints) It also seems like to avoid
this you also need home defined.
 

Hey, I've had this issue on and off for a while and I am still trying to figure out the reason my system does this every so often:
My Y axis has 2 steppers and 2 limit switches. Y(1) being on the left, Y2 the right. When the limit switch for Y2 triggers the motor backs off the switch and (supposedly) waits for the other axis to finish finding its home.
Y(1) hits the switch, but instead of backing off it pauses for a fraction of a second then continues to push into the switch.
I hit the Estop at that point as the stepper starts skipping when it gets near the end of its travel.

Video of the switch issue


Things I've checked:
Restarting the system entirely doesn't seem to have any effect.
Wiring is all good, I can see the corresponding lights on the mesa board lighting when the switch is pressed
The switches is fine, I switched the 2 axis switches and got the same behavior
Signals are coming through according to the HAL meter with Y and Y2 home both showing true when pressed
The home offset is set for 5.00 mm for both sides, meaning the gantry should move in the negative direction (away from the switches) when correcting (and it does when it occasionally works)

Any help or suggestions would be very welcome.

 



On a side note: I'd love to know what the homing subroutine looks like, but I can't find anything online for it. Is it possible to remap it like the M6 tool change in the INI?  

Badass man, submit a pull request

Had to dig this out of their website, so they might get p.o. but here it is
literature.rockwellautomation.com/idc/gr...2098-in003_-en-p.pdf
Installation manual for the drives, do check the model and type though to be sure.
If that is the correct document, they do have step/dir inputs and use resolvers for feedback, a bit more time with the document would be needed to be sure what exactly is required for use.
One thing to makes things easier, if you know exactly what motor was wired to what drive, it would save a lot of time in tuning the drives to motors, and a lot easier later tuning in LinuxCNC.

Martin, I went true the machine original diagram followed few wires to make sure that I understand the diagram. I found out that some parts of the schematic are in Chinese and that might explain the wrong  name labels in the diagram and no comments what so ever, which is unusual for European machines. I blame the poor documentation on our far east friends.

Here what I found for drive Z (same for the rest of the drive just different numbering)

CN1 PIN 8 BRN DC24V (no sure about polarity you my need to use multimeter to determine)

CN1 PIN25 YELL #29 GOES TO OUTPUT 12.7 DRIVE READY Z (FROM PAGE 8)
 

CN1 PIN10 WHITE #192 DRIVE Z ENABLE (KA3 RELAY SEE PAGE 6)
 
 
CN1 PIN 18 RED DC 24V 

CN1 PIN 19 RED WIRE #186          Analog signal (+) assuming mislabeled output instead off input)
CN1 PIN 20 BLACK WIRE # 189     Analog signal (-) assuming mislabeled output instead off input)
These wire goes to page 16  to the current controller
 

Conclusion it looks like you have analog drives. 

Please do not take cutting pliers and dismental everything thinking its better to drive peripherals directly from mesa. I would leave the machine wiring as is. only remove the existing controller and wire mesa card to replace it. If you have wiring problems, let us know and will try to help you solve the problem. The wiring of the machine is straight forward, its just not label well.

If you want a package installation then the Buildbot is best:
buildbot2.highlab.com/

Otherwise you could build a run in place install from the source:
linuxcnc.org/docs/html/code/building-linuxcnc.html