Advanced Search

Here are the .ini and .hal files.
The static IP of the RPi is 10.10.10.100 - I can ping the Mesa card from the terminal.
   

I am not sure if this is specific to qt_dragon or not.

However, when I try to rerun a tool because it broke or I need to adjust comps, the process makes me load and set tool length for each tool before it in the nc code.

I'm using versa probe and the Qt auto tool setter routine.

Is there any way to avoid changing each tool before rerunning the desired tool? Often times it's easier and quicker to just repost the single tool path as a separate program to avoid changing all the tools. I'd like to avoid that, if possible.

I'm using an RPi5 and a PCIe HAT with another NIC and some extra USB ports. Seems to work fine. It's the waveshare 27541. The setup needs the 5V 5A power supply to avoid voltage drops and hard resets. The 5V 3A power supply was not sufficient. I am using the official power supply in the control box as I had issues with other solutions. I'd also suggest a cooler for the cpu if you go this route.

From your error report:Usually means you have set the IP address on PC same as on Mesa card, the PC must have different last number for IP address, so
10.10.10.11 is OK for PC if Mesa is set at 10.10.10.10

What can you tell me about this program?

# --- Load the userspace for probe error manager ---
loadusr -Wn probe_error_mgr python3 probe_error_mgr.py

I have been running my machine in a kind of sketchy estop version, where LinuxCNC doesn´t really correlate with my physical estop hardware (which is running seperately).
Currently i am finally trying to implement feedback of my physical estop hardware (pilz estop relais that checks various inputs) into linuxCNC
Original hardware used two momentary switches connected to the main pilz relais to switch the main power on/-off. Once the machine is running i have a estop-ok signal 24V connected to my mesa inputs. 
Currently i have serious problems to synchronize GUI interface, linuxCNC and the main hardware. I have tried so many different versions of estop routing i am now totally confused what would be the best approach and like to have some directions for a new setup from scratch.
I would love to have it work like that:
- i connect my machine to power and the PC and mesahardware boots up, Estop Hardware is supplied 24V (works perfectly)
- once GUI is loaded (Gmoccapy) i press machine-on (which is currently not available to be pressed because the GUI is in estop)
- machine-on sends a 24V oneshot through mesa outputs to pilz e-stop relais, which switches on the rest of the hardware. (legacy function from the original setup)
- after a few seconds the estop hardware delivers a e-stop ok signal to linuxCNC which finally pulls the GUI estop button. halui estop is activated -> false

Main problems i have encountered so far are:
- halui estop is always actived. No matter what kind of reset functionality i have used in my main hal. 
- i can never use the GUI machine-is on button to actually start my machine. But i need to do so to recieve a estop ok signal from my hardware. So it needs to be usable before. Currently i use a jumper cable to start my machine and would love to get away with not have to implement a physical switch somewhere as the install with a big touchscreen doesn´t have anywhere to mount one.

Some direction would be much appreciated, thanks. 

I'm on 2.9.3. I'll update and see what I get.

If you call toolchange with parameter, eg.

O<toolchange>  call [1][#<toolno>]

then #2 has value of second parameter. #1 to #30  are used like that.
If you need the number of loaded tool, just use #5400.
Be aware that probing result is with current active coordinate system setting. If Z is has an offset...
Some people release from toolsetter after contact.

Thank you for all the replies, Appreciate the help though I will look through the links!
In the meantime I have a pi coming, thinking I can use usb-ethernet for non-realtime comms, though I prefer less components.

Good advice, I tend to forget there's a GUI for stuff like that.

What I did: In xfce you can go System|Synaptic Package Manager, search for Linuxcnc, mark linuxcnc-uspace. In Menu -> Package Force Version->you can select an older version -> apply.

Hi everyone,

So I have my B-axis articulated by a ballscrew, as you might have guessed, and I am having some trouble understanding kinematics and how to set this up in LinuxCNC. Below is a picture of my design, followed by a drawing of the geometry. My trouble isn't with getting the math correct, so you can ignore the math if you wish. I need help understanding how to input this into LinuxCNC. So far I have followed this tutorial,  but I have got stuck with the kinematics part. 

And the geometry

So to describe the drawing

• Line CD is a connecting rod where point C travels along the ballscrew path AB, and the path is perpendicular to the Z-axis
• Point H is a point along the path AB that is directly above point E, that is, angle BHE will always be 90 deg and the distance HE is 120mm and AH is 217mm
• Point E is the centre of the B-axis rotation 
• Point D represents where the connecting rod is connected to the B-axis assembly
• Line FG is the spindle where G is the tool tip.
• CD = 125mm
• DE = 127mm
• EG = 120mm
• HE = 120
• Angle DEF = 30.579 deg

So to find the angle of the spindle  FEH we must first find DEH and subtract DEF from it.
DEH

So if I were to write a function to find the angle of the spindle(FEH) relative to the Z-axis based on the length of AC, it would be as follows
So first, we will calculate the length CE based on the length CH
CE = sqrt(CH2 +HE2) where HE = 120
CE = sqrt(CH2 +1202)
CE = sqrt(CH2 + 14400)

Now we can calculate angle DEC and subtract angle DEF to get the angle of the spindle

COS(DEC) = (1272 + CE2 - 1252)/(2*127*CE)
COS(DEC) = (1272 + CH2 + 14400 - 1252)/(2*127*sqrt(CH2 + 14400))
COS(DEC) = (CH2 - 14904) / (254*sqrt(CH2 + 14400))                  
where CH = AC - AH = AC-217

If you are not interested in the math, please continue reading here
So if COS(DEC) = (CH2 - 14904) / (254*sqrt(CH2 + 14400))  - DEF describes the relation of the ballscrew moving to the rotation of the B-axis how do I set this up in LinuxCNC? Also, do I need to calculate the formula for the tool tip change in X-axis and Z axis based on the B-axis rotating as well, before inputting this into LinuxCNC or is this sufficient? Thank you for your help and patience

Wow, that's really cool. Unfortunately, I can't afford the UltraScale's ;(

I once tried using a miner board (S9) and wanted to use the ARM part only as an Ethernet bridge, but I ran into a few difficulties and didn't continue with it for the time being.

But what you've done there is amazing

Hi, 
I ordered a Radxa CubieA5E with a similar idea in mind; having an Ethercat motion controller accepting G-code over network. But it is too soon to say if it will work; I had a hard time having a working real-time kernel on the Radxa Zero3E, so this may take some time.

Anyway, you have one more option!
Cheers

autotune usually has a global stiffness setting. So for example with my omrons, a setting of 15 is pretty soft and would wiggle as you describe, 20 is pretty decent if you have lower dynamics, and 25-30 is super stiff tracking.

So, assuming the software is doing what its meant to do you simply might not be ably to get the stiffness you desire with your machine and motor and acceleration combination. Your machine may just have too much of an inertia load and you might need a larger servo.

Once autotuning does its basic job, and you find that its not quite as good as you'd like, you can use then "go form there" with some manual tweaking of settings. I had to do this with my Y axis with my omrons, but the x and z were "perfect" after autotuning.

I got one of these coming tomorrow for testing.