Advanced Search

Short update on that, Hannes. 
While in auto mode and running a program it doesn't show F: nor S:
It does react on Feed+/- and Speed+/- but only on displayed values in the HMI, not the pendant display.
In Man mode it shows F: and S: in the way one expect.

@Hakan:
Strange. Mine doesn't show anything. But it's an LHB04B-6 TX V3 (Wired version)
As much as I read, it should work the same, but might be not.

Starting with -Ha and commenting out github.com/LinuxCNC/linuxcnc/blob/master...whb04b-6/usb.cc#L209 it shows:

out 0x06fefdfe801800bc 060e0800161e0200 06008069006e0000
out size 24B hdr 0xfdfe dom 0xfe status 0x80 coord1 +0024.3772 coord2 +0008.7702 coord3 -0002.0000 feed 0105 spindle feed rate 00110

So it seams the values are sent. Might be my device has a different firmware. With Mach3, I tried already and I didn't see any value. I will try again with Mach4.

According to github, that's a part of the feb 15 2025 commit:

-  hal_bit_t *request_cia402_homing;   // output requests homing (connect to cia402.n.home)
-  hal_bit_t *is_cia402_homing;        // input verifies custom homing (connect to cia402.n.stat_homing)
-  hal_bit_t *cia402_homing_finished;  // input from servo drive after homing (connect to cia402.stat_homed)
+ hal_bit_t *request_custom_homing;   // output requests homing (connect to cia402.n.home)
+ hal_bit_t *is_custom_homing;        // input verifies custom homing (connect to cia402.n.stat_homing)
+ hal_bit_t *custom_homing_finished;  // input from servo drive after homing (connect to cia402.n.stat_homed)

So if your example is older than this and that you compiled the comp from source, yes you have to use the current name. And if HAL tells you the pin doesn't exist, then it very likely doesn't exist.

The specs they list for that mini control box makes me think it is a servomotor amplifier. I see ratings of 48VDC 42A max and 48VDC 104A max on several models of the control box shown at your second link.

Interesting possibilities.

So is it normal? As i remember from my old PC there were mm shown... and G21 is mm, right?

 Hallo zusammen, ich habe NativeCam auf meinem System installiert, jedoch läuft es bei mir bisher nicht wie erwartet. Konkret: Im Verfahrbereich / Geometry Tab sehe ich beim Ändern der Geometrie keine Änderungen. Wenn ich ein neues Werkstück hinzufüge, wird nicht einmal die Blockform angezeigt. Ich kann zwar Code erstellen, aber sobald ich diesen starten will, erscheint immer der Fehler: Word O gesuchtbzw. der G-Code scheint generell einen Fehler zu verursachen. Ich habe bereits geprüft, dass die Installation abgeschlossen ist, konnte den Fehler jedoch nicht finden. Hat vielleicht jemand von euch ähnliche Probleme gehabt oder kennt eine Lösung für dieses Verhalten? Jede Hilfe oder jeder Hinweis wäre super! Vielen Dank schonmal!



Hi everyone, I have installed NativeCam on my system, but it is not working as expected. Specifically: In the motion/geometry area, I don’t see any changes when I modify the geometry. When I add a new workpiece, the block form is not displayed at all. I can generate the code, but when I try to start it, I always get the error: Word O expected or the G-code seems to cause an error in general. I’ve verified that the installation completed successfully, but I haven’t been able to identify the problem. Has anyone experienced similar issues or knows a solution for this behavior? Any help or advice would be greatly appreciated!
 

The wiring does not look right to me, Don't those drives have differential inputs?

If they are differential, the 7I95 Step/Dir connections are wrong.

The cables I use are standard CAT5e patch cords, 1.5m long and the excess length is in loops.

The topology is as follows - one cables from the computer is connected to the first servo drives and all the others are daisy chained.

About the name of pin that @3404gerber mentioned. I was thinking if should I change the pin name from 'cia' to 'custom' but you have a working configuration with 'cia' in the name. Why should it be different with my cia402 home component? Perhaps, the name was updated after you got it working.

I checked on the drive side and it looks clean as well.

You are welcomed, always.
Be mindful of the wiring and shielding, since your machine was working fine, i doubt you have interfernce from VFD/spindle as they do produce a lot of EMI, so try to arrange spindle and high voltage wiring as far from low power/signal wiring, also use ferrite beads on the spindle motor wires near the VFD.

Apparently not, despite having the same model.
The one you linked has motors on all axis and ballscrews, the one here from explanation has a single motor and a gearbox to switch between axis.
Can you post some pictures of the machine?

Parametric gcode, numbers are at the top.

OK sounds nice.
I also didn`t think that this cards realy break.
So i will test this card on my new mill if it`s ready and hope it will work in a new envirement.

Thanks Tommy 

jblanscett wrote:

We have also looked at the signals from an oscilloscope and are getting nice clear step waves.

Check at the drive side.

Jensner wrote:

So it's a new experience that MESA cards can also break down sometimes. 
 

No they do not break, at least none of over 70 or 80 or more i have in daily use, they never break, never fail, in over 15 years.
Most of them are on huge industrial machines, some on plasma machines that are the worst environment regarding EMI, i have Mesa 7i92 wired through 6 meters of cable to plasma source with no BOB, directly to Mesa inputs, etc etc.
They always, always fail due to miss wiring or lack of proper shielding/grounding.