Advanced Search

Something sounds odd.
Docs on coordinates are here linuxcnc.org/docs/stable/html/gcode/coordinates.html

I wonder if the .var file is marked read only? This would prevent values from being saved.
Delete it as sometimes it gets stuffed up when setting up a new machine.

If you can't find it, check the file name in use in the ini file eg. for my QTdragon config
PARAMETER_FILE = linuxcnc.var

1. As far as I am aware the 'DIAM' value is for the radius of the tool tip on a lathe tool (ie for radius compensation G41/G42):
linuxcnc.org/docs/stable/html/lathe/lathe-user.html
To my knowledge, the values 'FRONT' 'BACK' 'ORIENT' are only used to change the tool display in the preview window.

2. Retraction of an oriented tool is quite simple:
    
    - stop program execution
    - change to MDI mode and execute 'g68.1'
    - Jog the Z axis in the positive direction

I have modified the sim config and brought the 'TWP' button back to the right hand panel. Clicking on this should now define a TWP at the current tool orientation and position.
(G68.1 X#<_x> Y#<_y> Z#<_z>).

The folder has been updated:
forum.linuxcnc.org/10-advanced-configura...hine?start=50#328156

I did check one of my known good configs with a shared home/limit before my last reply. It uses a negative latch velocity.
github.com/rodw-au/vmnmillqt/blob/main/VMNmillQT.ini#L247
(units are metric)

Latching happens so quickly its hard to see what is going on. Sometimes I've slowed homing velocities right down (to 10% or less) to troubleshoot.

Thanks for you Replay.   
I tried it. I think something is wrong.
i get the following replay:
QtPyVCP 0+unknown, Probe Basic v0+unkown
Any idea about this?

Thanks

normally yes, it will increase, and then during threading i think, there is a reset index command which turns it to 0 i think. during css operation im not sure.

did you end up getting the abz encoder? did you do the spindle.speed-in stuff? monitor that while your doing the css and see if it takes a dive while the speed is changing. the remora.sp0 signal looks exactly as i would expect though, with the speed tapering up or down as the diameter changes.

I would start with a MesaCT created configuration.

Hello,

this is just outstanding! Also thank you so much for the Fanuc  tool change example!

I could only try it out for one hour so far and I'm just amazed by the work and effort you done. Without your support, my decision of retrofitting this machine probably would be different! I also tried M19 R180. Worked flawlessly.

And as you correctly predicted i have a few questions so far:

1. Tool table:

The "Orient" and the "Diameter" for turning tools: Is it just informative, or is it used by some background calculations?

2. Tool rescue:

Assuming a drill or end mill doesn't sound right during milling and i stop the programming and want to retract it. When die B-axis is not at 0° it's quite difficult to get the tool out of a hole/pocket without braking it. A function to move the X axis at an B angle would be helpful for this.

That's it so far. I will try and implement the Fanuc tool change tomorrow and see where this will go. Again thank you so much and amazing work






 

200N = ~20.3KG ???
450LBS = over 200KG = ~2000N

Hi all, I’m planning to use a Compulab Fitlet3 as the controller PC for a LinuxCNC setup (Mesa 7i94T over Ethernet). My goal is a quiet, compact, low-latency machine with dual LAN and enough performance for a Qt UI (e.g., QtDragon or ProbeBasic), without excessive overhead. Here’s the configuration I’m considering:  

Fitlet3 configuration: 

• CPU: Intel Atom x6425E (4 cores @ 2.0 GHz base, 3.0 GHz burst, 12 W TDP)
• RAM: 8 GB DDR4 SODIMM
• Storage: 256 GB NVMe (M.2 Key-M)
• No SATA drive, no WiFi or modem
• Audio: Analog audio codec module
• I/O: Terminal block with RS-232/RS-485/GPIO
• Enclosure: Standard finned top cover (rated for 18 W)
• Thermal spec: Extended range –20°C to +70°C
• TPM: Not installed
• FACET card: FC3-LAN (adds 2× Intel i210/i225 Gbit LAN)

I plan to run the official LinuxCNC ISO with Preempt-RT, not a custom kernel or patched distro. Hence, I’m relying on the FC3-LAN FACET card for known-good Intel NICs, as the onboard Marvell NICs require kernel 5.15+ and I’d prefer to avoid that complexity.  

My questions: 

1. Has anyone here run LinuxCNC with a Fitlet3 (or similar Elkhart Lake system)?
2. Is the x6425E predictable and stable under Preempt-RT with Mesa boards over Ethernet?
3. Can anyone confirm that the following BIOS options are present and can be disabled in a AMI Inc. BIOS? 
   • Intel Turbo Boost
   • CPU C-states
   • SpeedStep (EIST)
   • CPU power management (set to Performance)

I’d also appreciate any pointers on edge cases I might be overlooking, or real-world latency results on this hardware (if available). 

Thanks in advance — I’d love to avoid going down a rabbit hole if this platform has hidden caveats. 

aeth wrote:

... I want to make a truly badass solution with Raspberry Pi...

That statement ... has issues!
Use a NUC or any small PC, not a RPI.
You should check the export regulations before jumping in, the biggest market for DIY is USA, then India, Europe is pretty far down that list. I checked for the same thing, it was not pretty. BTW, my country has the lowest tarifs for USA at 10% only! Does not fix much when sending anything there costs over 300$ for a small box.
This is not to discourage you, absolutely do try, just make sure you get informed beforehand.

Hello everyone.

I'm quite new to the topic of Mesa cards and LinuxCNC. For the past few days, I've been trying to get my Mesa 7i95T up and running. Some things are working well, I’ve loaded the firmware and configuration, and now I can communicate with my card. Encoders can also be observed on the LinuxCNC interface. Now I wanted to try running my motor for the first time, but unfortunately, I’ve been unsuccessful for a few days. When I reference all my axes and click Jog, I get the error message:
Motor 0 position error
emc/task/taskintf.cc 976: Error on joint 0, command number 108


.hal
# kinematics
loadrt [KINS](KINEMATICS)
# motion controller
loadrt [EMCMOT](EMCMOT) servo_period_nsec=[EMCMOT](SERVO_PERIOD) num_joints=[KINS](JOINTS) num_dio=8
# hostmot2 driver
loadrt hostmot2
loadrt hm2_eth board_ip=192.168.1.121 config="num_encoders=6 num_stepgens=6 sserial_port_0=00000000"
#Stepgen
loadrt stepgen step_type=0,0,0
setp hm2_7i95.0.stepgen.00.enable TRUE
# THREADS
addf [MESA](CARD0).read servo-thread
addf [MESA](CARD0).write servo-thread
addf motion-command-handler servo-thread
addf motion-controller servo-thread
# Encoder X
setp hm2_7i95.0.encoder.00.filter 1
setp hm2_7i95.0.encoder.01.filter 1
setp hm2_7i95.0.encoder.02.filter 1
# Encoder 0 -> Joint 0 (X)
net x-pos-fb hm2_7i95.0.encoder.00.position => joint.0.motor-pos-fb
#E-Stop
net estop-loop iocontrol.0.user-enable-out => iocontrol.0.emc-enable-in
# DPLL
setp hm2_7i95.0.dpll.01.timer-us 100
# joint-0 enable chain
net joint-0-index-enable <=> joint.0.index-enable
#net joint-0-index-enable <=> [MESA](CARD0).encoder.00.index-enable
net joint-0-index-enable <=> [MESA](CARD0).stepgen.00.index-enable

# Joint 0 Step Generator Settings
setp [MESA](CARD0).stepgen.00.dirsetup [JOINT_0](DIRSETUP)
setp [MESA](CARD0).stepgen.00.dirhold [JOINT_0](DIRHOLD)
setp [MESA](CARD0).stepgen.00.steplen [JOINT_0](STEPLEN)
setp [MESA](CARD0).stepgen.00.stepspace [JOINT_0](STEPSPACE)
setp [MESA](CARD0).stepgen.00.position-scale [JOINT_0](SCALE)
setp [MESA](CARD0).stepgen.00.maxvel [JOINT_0](STEPGEN_MAX_VEL)
setp [MESA](CARD0).stepgen.00.maxaccel [JOINT_0](STEPGEN_MAX_ACC)
setp [MESA](CARD0).stepgen.00.step_type 0
setp [MESA](CARD0).stepgen.00.control-type 0
setp [MESA](CARD0).stepgen.00.direction.invert_output true
# position command and feedback
net joint-0-pos-cmd <= joint.0.motor-pos-cmd
net joint-0-pos-cmd <= [MESA](CARD0).stepgen.00.position-cmd
net joint-0-pos-fb <= [MESA](CARD0).stepgen.00.position-fb
#net joint-0-pos-fb <= [MESA](CARD0).encoder.00.position
net joint.0.output => [MESA](CARD0).stepgen.00.velocity-cmd
net joint.0.output <= joint.0.vel-cmd

.ini
[EMC]
MACHINE = Mesa 7i95T XYZ
DEBUG = 0
VERSION = 1.1
[HAL]
HALFILE = /home/kacper/linuxcnc/configs/Mesa_Mini/01_main.hal
[HMOT]
CARD0=hm2_eth
[HOSTMOT2]
ETH0=192.168.1.121
[EMCMOT]
EMCMOT = motmod
COMM_TIMEOUT = 1.0
COMM_WAIT = 0.010
SERVO_PERIOD = 1000000
[MESA]
VERSION = 2.0.6
FIRMWARE = 7i95t_sdid.bin
CARD0 = hm2_7i95.0
[DISPLAY]
DISPLAY = axis
POSITION_OFFSET = RELATIVE
POSITION_FEEDBACK = ACTUAL
[TASK]
TASK = milltask
CYCLE_TIME = 0.010
[EMCIO]
EMCIO = iov2
CYCLE_TIME = 0.1
TOOL_TABLE = tool.tbl
[RS274NGC]
PARAMETER_FILE = linuxcnc.var
[KINS]
KINEMATICS = trivkins coordinates=XYZ
JOINTS = 1
[TRAJ]
AXES = 1
COORDINATES = X
LINEAR_UNITS = mm
ANGULAR_UNITS = degree
MAX_LINEAR_VELOCITY = 200

[AXIS_X]
TYPE = LINEAR
MAX_VELOCITY = 50
MAX_ACCELERATION = 100
MIN_LIMIT = -200
MAX_LIMIT = 200
[JOINT_0]
TYPE = LINEAR
HOME = 0
FERROR = 5
MIN_FERROR = 0.5
MAX_VELOCITY = 100
MAX_ACCELERATION = 200
STEPGEN_MAX_VEL = 60
STEPGEN_MAX_ACC = 120
P = 1000
I = 0
D = 0
FF0 = 0
FF1 = 1
FF2 = 0
DEADBAND = 0
BIAS = 0
MAX_OUTPUT = 10
MIN_LIMIT = -200
MAX_LIMIT = 200
STEPLEN = 1000     
STEPSPACE = 1000   
DIRSETUP = 1000    
DIRHOLD = 1000     
SCALE = 640  
start

 From a hardware perspective, everything seems to be correctly connected. Below, I’m attaching my .ini, .hal, and stepgen pins. Do you maybe have an idea where the issue could be?

Right now, my main goal is just to get the motor running. Thanks in advance for your tips and support.

I noticed when looking at encoderS0.position I'm getting no valves. Also no valves when looking at spindle.0.revs in halshow. Could this be causing the issue ? EncoderS0.phase-Z is getting the signal from one of the remora input pins(my encoder index) which both are blinking in halshow when triggered. Should I be seeing the spindle.0.revs displaying a valve in halshow?

I was recently wondering if there's a company or someone who builds 3 or 4 axis mill control boxes pre-configured with LinuxCNC. Most hobby and semi-professional machines rely on a very similar configuration with one, maybe 2 steppers per axis and it would be awesome if a properly built control box with Linux CNC was available pre-configured and off the shelf. Is anyone aware of a product like this? I know that CNC drive sells their control boxes with UCCNC and stuff like VFD, fuses, relays and stepper drivers preinstalled.
Ever since Ethercat was integrated into LinuxCNC, I want to make a truly badass solution with Raspberry Pi, hardware control panel (there's a Shenzen company producign Ethercat panels with feed/speed knobs and macro buttons!) and Leadshine CS3E closed loop stepper drivers and Delta MS300 VFD. A complete Linux CNC solution like this will cost around 2500 USD which is the price for just the Centroid Hicory mainboard + software that offers similar capabilities.
If there's nothing like this on the market and enough people are interested, I could partner with my friend in China who could help me get this stuff assembled there.

That dkms error is an error in the debian distribution, they included a raspberry package. Just delete it.Well I thought the secure boot would be an explanation but now I don't know.
Happy you can use it, anyway.

Changing the latch velocity is worth a try _but_ having the same sign on search velocity as latch velocity is valid.

In this case, The homing logic is supposed to move towards the home switch at the search velocity, and when the
home switch is detected, reverse and back off until the home switch deactivates, and then move towards the home
switch again at the latch velocity for the final home switch detection.