Advanced Search

If you get probe tripped error during slow proving it's usually a sign that you might need to add the debounce component to your halfile and then recalibrate the probe in Probe Basic.

Yes shure.
I try to run servo in csp, i see one big problem - moror jumping on re-enable.

I try to dual ethercat-stepper, lol ok all enabled first motor running good - when i try to rotate shaft motor not showing feedback. second axis showing normal. first axis good run - second axis max spedd 500rpm if more motor jumping.

nvm, i found myself solution in axis/pyvcp example

Does GTK_Vismach exist, or has anyone attempted to embed Qt_Vismach into a GTK window?

andypugh wrote:

Which version of Linux, LinuxCNC and psng are you using?

I have done some work on psng to adapt it for Gtk3 / Python3 on Debian 12+
However, on my test machines, whilst it loads without errors, there are no graphics visible in the embedded tabs.

I'm curious, Why aren't people working on the version in linuxcnc?
github.com/LinuxCNC/linuxcnc/tree/master...n-panels/versa-probe

That brings up a couple questions?

1. if the encoders have differential outputs, why in the 7I33 jumpered for single-ended (TTL) inputs

2. Leaving the TTL option enabled, can you check that grounding the INDEX+ input (encoder disconnected)
changes the state of the hal index pin (hm2_7i80.0.encoder.00.input-index for X)

You should have the servo drives switched on when you start linuxcnc.
That way linuxcnc can make them go up and down as required, and change cia402 states as required.
There is an "enable" pdo you connect to joint.amp-power-on or something like that, to enable the drive.

I think what's happening when you switch on the drives is the ethercat master spots new things on the net and
scans the bus and does some setup things for the new devices. This interrupts the cyclic operation
and I would think all slaves exits op mode for a second or two, until ethercat master is ready and the slaves
can be brought up again.

So, don't switch on and off power of the drives while active in linuxcnc.

There is another method to extract the sii firmware, modify it and then flash it back. This method is permanent.

I have a solid state relay OMRON G3PE 525B, for what I know it will not need flywheels

I forgot to mention this happen only if the first slave is connected (EK1100 --> First slave --> second slave --> etc... )
if EK1100 --> disconnect --> second slave --> etc... it doesn't blackout.

so my guess is that it's not an electrical or EMI issue, but something software side

Does that relay have a diode in parallel with the coil?
Mind the polarity.
Relays are inductors and as such create a lot of interference when switched on and off.

I don't know exactly what happen inside linuxcnc but I'm having this issue :  Ethercat issue video
at LCNC startup I power on the servos via a relay and the the whole Beckhoff modules blackout in LCNC but stays on physically, the lights don't even flash. 
This causes the first and second servos (sometimes the third) to not be set as operative.
If you want to try out yours I had to setup on HAL this to turn on halshow at startup: loadusr halshow
Any guess?

I don't get it. I meant they removed the software from the product page, now it's elsewhere..
If you mean they are crap quality, wich ethercat servos you suggest at this price point?

replace x with your servo/spindle index

net s-vel-cmd <= spindle.0.speed-out
net s-vel-cmd => cia402.x.velocity-cmd

You will need csp mode 0 :

setp cia402.5.csp-mode 0
setp cia402.5.pos-scale 1

Not a lot to go on. Where are you assigning a value to what parameter, where are you trying to access it and what happens when you do?
Usually best to give a short example of what you are trying to do and describe what is not working as expected.

I have tryed both, unfortunately #!/usr/bin/env bash makes no difference. Also halcmd show signal s-index-zero-for-ATC stays false. I also tryed to call M100 from a remapped M19 but it's totally ignored, meanwhile the same sintax for similar commands like M10 or M21 works fine.

UPDATE: somehow in toolchange.ngc M1xx doesn't work, just hang the M6Tx called BUT I noticed it works inside the subroutines called by toolchange.ngc, like M10 (remapped) so I temporarly solved.  What it could be the cause?