Advanced Search

@mobiusToast
Did you have any issues with the Drives sometimes not homing at all? Or them jumping at the end of the home procedure with ER87?

I think Wikipedia will explain balanced signal better than me:  en.wikipedia.org/wiki/Balanced_line . I made a small pcb that uses DS90LV/DS90LT line transceiver to turn the SPI into a balanced signal, and one at the end of the line that turn it back to an TTL SPI signal.

For the TMC5160, if you use the Remora-STM32F4xx-PIO or Remora-STM32H7xx-PIO, you'll have the possibility to configure your drivers via SPI. If you prefer to use my library, it would benefit from some changes; mainly removing the read/write functions that aren't needed and just make a configure and status check function. But you could try to use it without changes for a test, as the driver won't accept any SPI command related to internal ramp if the SPI mode isn't activated by a jumper on your board.

The host address of 10.10.10.11 is fine, it must be different than the FPGA card
(but in the same subnet)

A failed HM2 registration usually means dropped packets, so there is something marginal
with the Ethernet connection.

What does:

sudo chrt 99 ping -i .001 -c 60000 -q 10.10.10.10

report?

(it will run 1 minute before printing statistics)
 

tommylight post=341431 userid=17274

[EMCMOT]
EMCMOT = motmod
COMM_TIMEOUT = 1.0
BASE_PERIOD = 46872
SERVO_PERIOD = 1000000

Your base period is set at 46872, strange for sure, but i am pretty sure LinuxCNC will round it to something divisible from 1000000. Set it to 50000.

 

Será que estou inserindo valores incorretos para o Jitter Máximo do Período Base ao configurar uma máquina no Assistente de Configuração do Motor de Passo?

Does nobody have an idea or suggestion regarding the problems with my plans?
Lathes are probably rebuilt far less often than milling machines, unfortunately.


Well, in the meantime I continued working on the control cabinet. I had already planned the layout in CAD, and the effort put into that really pays off here.
First, I printed and attached a template, center-punched the holes and cut the threads, then cut the cable ducts and DIN rails to length and mounted them. A very pleasant, almost calming kind of work.
After that, I pre-wired everything and installed it in the cabinet. I also equipped the lid with a gas spring, and added a cable duct underneath the control cabinet.








 


 

did you turn on power to the Mesa card before starting linuxcnc?

yep, first thing I tried (a lot of times I got an error then I realized I forgot to switch on the machine)


Whats does the command:
ip a
report?
What happens if you:
ping 10.10.10.10

This is what I get with "ip a" and giving a ping:


eth0 is my second network card, I use it to reach my NAS, my LAN and the WEB
eth1 is the integrated network card, used by Mesa

giving the ping 10.10.10.10 I get response from Mesa
I just don't understand why eth1 report IP 10.10.10.11, when my hal file is set 10.10.10.10, and ping to 10.10.10.10 works.

BTW, after these tests I tried to start LinuxCNC, I get again an error message, but this time no mention about the MAC (is correctly reported), now the error is about HM2 registration:

Sorry aber English gehts schneller:
You can search the web for the gcode file, or you can download trial version of LightBurn and generate the code, then use LinuxCNC to test with it.
Most LightBurn code will run on LinuxCNC, and if it does not at least it complains about it so editing and removing offending lines should always work.

Can you post your .ini file as well?

Your base period is set at 46872, strange for sure, but i am pretty sure LinuxCNC will round it to something divisible from 1000000. Set it to 50000.
Still i do not think that is the main issue, it seems your PC has some strange and huge excursions in latency, so, did you disable in BIOS:
turbo
speed step
power saving options
TPM if any
PCI-E aggressive power saving (no idea what name is used in some boards)
C states
etc.
Be as it may, for that PC and since you need RTAI, use the Wheezy ISO as is, granted you do not need any missing features from it.
You can download and test Wheezy without installing it, see how that works out.

Sorry I’ve been quiet for a while — I had to put the project on hold for some time, but I’ve just come back to it and I’m now moving it into production. It should be available within about two weeks.A new operating mode has been added, and in my case it works extremely well (I have my own CNC controller, so I can do whatever I want). It doesn’t require any data processing, because it receives the ready-to-use height directly from the sensor. This option might be useful for others in the future as well.The only drawback is that the output is a universal open-collector type, which isn’t a standard interface. However, I designed a simple circuit that converts the open-collector signal into a standard RS-485 signal. I calculated it, built it, tested it, and measured it — and it works perfectly. Over several hours of operation, not a single bit was lost on an unshielded cable (just a regular twisted-pair Ethernet cable) over a distance of more than 300 meters in an industrial environment. That exceeded my expectations.

 



 


CONVERTER SIMULATION

3 changes should be done in the hal file:

1. Set the PWM rate to 48 KHz

2. Set offset mode true for all PWM channels:

setp hm2_5i24s.0.pwmgen.0N.offset-mode true
Where "N" is the channel number

This is critical or the analog output will be wrong

3. Set dither mode true for all PWM channels:
hm2_5i24.0.pwmgen.0N.dither true
 This will increase the Analog resolution from 12 bits full scale to 15 bits full scale

Note that this requires firmware with PWMGen version 1 if the 5I24 firmware
does not have version 1 PWMGens, I will update it.

Note that you may need to change the PWM scale so you have the desired
negative feedback (control) rather than positive feedback (runaway)

I hope I got it right this time.

Thank you so much for your reply, friend. I'd like to know if you have any contacts I could reach if I need help. I'm from Paraguay, and your help would be invaluable. Thanks again, friend.
# Generado por stepconf 1.1 en Thu Jan 15 10:49:41 2026
# Si realiza cambios en este archivo, serán
# sobrescrito cuando ejecuta stepconf nuevamente
loadrt [KINS]KINEMATICS
loadrt [EMCMOT]EMCMOT base_period_nsec=[EMCMOT]BASE_PERIOD servo_period_nsec=[EMCMOT]SERVO_PERIOD num_joints=[KINS]JOINTS num_spindles=[TRAJ]SPINDLES
loadrt hal_parport cfg="0 out"
setp parport.0.reset-time 5000
loadrt stepgen step_type=0,0,0,0
loadrt plasmac

addf parport.0.read base-thread
addf stepgen.make-pulses base-thread
addf parport.0.write base-thread
addf parport.0.reset base-thread

addf stepgen.capture-position servo-thread
addf motion-command-handler servo-thread
addf motion-controller servo-thread
addf plasmac servo-thread
addf stepgen.update-freq servo-thread

# ---PLASMA INPUT DEBOUNCE---
loadrt dbounce names=db_breakaway,db_float,db_ohmic,db_arc-ok
addf db_float servo-thread
addf db_ohmic servo-thread
addf db_breakaway servo-thread
addf db_arc-ok servo-thread

# ---JOINT ASSOCIATED WITH THE Z AXIS---
net plasmac:axis-position joint.2.pos-fb => plasmac.axis-z-position

# ---PLASMA INPUTS---
# ---all modes---
net plasmac:float-switch => db_float.in
net plasmac:breakaway => db_breakaway.in
net plasmac:ohmic-probe => db_ohmic.in
net plasmac:ohmic-sense-in => plasmac.ohmic-sense-in
# ---modes 0 & 1
net plasmac:arc-voltage-in => plasmac.arc-voltage-in
# ---modes 1 & 2
net plasmac:arc-ok-in => db_arc-ok.in
# ---mode 2
net plasmac:move-up => plasmac.move-up
net plasmac:move-down => plasmac.move-down

# ---PLASMA OUTPUTS---
# ---all modes---
net plasmac:ohmic-enable <= plasmac.ohmic-enable
net plasmac:scribe-arm <= plasmac.scribe-arm
net plasmac:scribe-on <= plasmac.scribe-on

net xstep => parport.0.pin-02-out
setp parport.0.pin-02-out-reset 1
net xdir => parport.0.pin-03-out
net ystep => parport.0.pin-04-out
setp parport.0.pin-04-out-reset 1
net ydir => parport.0.pin-05-out
net zstep => parport.0.pin-06-out
setp parport.0.pin-06-out-reset 1
net zdir => parport.0.pin-07-out
net y2step => parport.0.pin-08-out
setp parport.0.pin-08-out-reset 1
net y2dir => parport.0.pin-09-out
#qtplasmac doesn't use a spindle: net spindle-cw => parport.0.pin-14-out
#qtplasmac doesn't use a spindle: net spindle-pwm => parport.0.pin-16-out
net xenable => parport.0.pin-17-out
net estop-ext <= parport.0.pin-10-in

setp stepgen.0.position-scale [JOINT_0]SCALE
setp stepgen.0.steplen 1
setp stepgen.0.stepspace 0
setp stepgen.0.dirhold 35000
setp stepgen.0.dirsetup 35000
setp stepgen.0.maxaccel [JOINT_0]STEPGEN_MAXACCEL
net xpos-cmd joint.0.motor-pos-cmd => stepgen.0.position-cmd
net xpos-fb stepgen.0.position-fb => joint.0.motor-pos-fb
net xstep <= stepgen.0.step
net xdir <= stepgen.0.dir
net xenable joint.0.amp-enable-out => stepgen.0.enable

setp stepgen.1.position-scale [JOINT_1]SCALE
setp stepgen.1.steplen 1
setp stepgen.1.stepspace 0
setp stepgen.1.dirhold 35000
setp stepgen.1.dirsetup 35000
setp stepgen.1.maxaccel [JOINT_1]STEPGEN_MAXACCEL
net ypos-cmd joint.1.motor-pos-cmd => stepgen.1.position-cmd
net ypos-fb stepgen.1.position-fb => joint.1.motor-pos-fb
net ystep <= stepgen.1.step
net ydir <= stepgen.1.dir
net yenable joint.1.amp-enable-out => stepgen.1.enable

setp stepgen.2.position-scale [JOINT_2]SCALE
setp stepgen.2.steplen 1
setp stepgen.2.stepspace 0
setp stepgen.2.dirhold 35000
setp stepgen.2.dirsetup 35000
setp stepgen.2.maxaccel [JOINT_2]STEPGEN_MAXACCEL
net y2pos-cmd joint.2.motor-pos-cmd => stepgen.2.position-cmd
net y2pos-fb stepgen.2.position-fb => joint.2.motor-pos-fb
net y2step <= stepgen.2.step
net y2dir <= stepgen.2.dir
net y2enable joint.2.amp-enable-out => stepgen.2.enable

setp stepgen.3.position-scale [JOINT_3]SCALE
setp stepgen.3.steplen 1
setp stepgen.3.stepspace 0
setp stepgen.3.dirhold 35000
setp stepgen.3.dirsetup 35000
setp stepgen.3.maxaccel [JOINT_3]STEPGEN_MAXACCEL
net zpos-cmd joint.3.motor-pos-cmd => stepgen.3.position-cmd
net zpos-fb stepgen.3.position-fb => joint.3.motor-pos-fb
net zstep <= stepgen.3.step
net zdir <= stepgen.3.dir
net zenable joint.3.amp-enable-out => stepgen.3.enable

net estop-out <= iocontrol.0.user-enable-out
net estop-ext => iocontrol.0.emc-enable-in

net tool-number <= iocontrol.0.tool-prep-number
net tool-change-loopback iocontrol.0.tool-change => iocontrol.0.tool-changed
net tool-prepare-loopback iocontrol.0.tool-prepare => iocontrol.0.tool-prepared

Publicación de PCW=341375 ID de usuario=481¿Qué puerto paralelo se ha desconectado?

¿Puedes compartir tus jarchivos hal/ini? 

File Attachment:

File Name: CNCLINUX.txt
File Size:4 KB

File Attachment:

File Name: CNCLINUX.txt
File Size:4 KB

Dear PCW,

thank you for the answers. Good one!

I will make sure to setup the 7176 in all safe states. I think also maybe to upgrade to two limit switches per axsis instead of just one. Right now it is only one per axis and for the wire cutter i had anyways two per axis planned.

The enable and disable part: Probably I should just leave it then right now and when I encounter a situation where it does add function or value, its easy to upgrade.

So in generally, thanks. I will update with diagrams and images as soon as possible.