I have extended the python code mentioned in forum.linuxcnc.org/24-hal-components/145...with-graphviz#325079 in github.com/JTrantow/LCNC_HAL_to_graphviz

With these changes I can use it to get 99% of the graphviz I use to document my configurations. 

The attached CompleteConfig.svg is an example I whipped up today to help a friend setup a spindle VFD and external estop switch.

Using an online graphvix editor, I can quickly delete the subgraphs and signals that were cluttering up the spindle VFD and estop we were working on. See attached VFDandEStop.svg.

See the readme.md in github for further detail. I have run this on multiple configurations without issue. When your config is divided into multiple files, it's relatively easy to only load the portions you want to document.

When I tried to attach individual .svg files it complains about "Unable to get properties for the image."???
 

Sorry for late reply. I've have made a new rebuild of my wiring, and i would appreciate if you guys would check if everything looks correct. I will make a video of the problem if it still there, if my wiring diagram looks right. 

The unit of pos-scale is increments/distance unit, like steps/mm or steps/inch.
If you motor's encoder has 500 pulses/rev, then it is 2000 increments/rev.
With a axis movement of 5 mm/motor revolution you should set pos-scale = 2000/5 and 2000/180 respectively.
400 and 11.111

It may be possible to set the increments/rev separately from the encoders value, check the drive manual if the above doesn't match.

 

Not sure what you mean by encoder_value.
You have the cia402.x.pos-scale to work with.
Instead of mathematically figuring it out, multiply the current value with 6.5/2 = 3.25 and try again.
If you find that number matches a known relation, use that.

I think the following errors follows from the pos-scale. At least get this right first.

More text here on how to calculate pos-scale
forum.linuxcnc.org/ethercat/22346-etherc...er?start=1360#338150

db1981 wrote:

state machine from my comp is ok . 0x6 -> 0x7 -> 0x7f . Bit 2 (quickstop) is always set.

mine too, do you fix that

Did you start the motor?

Hello,
I'm trying to start the motor but it's not working, I tried via halrun and via sudo ethercat upload -p and motor enters OP, but it doesn't accept OP_STATUS, always 0, and the motor dont move, please can you help me somehow.

I have been trying to solve these problems on my own with very little headway:

When the Servo moves 2 inches, LinuxCNC registers it as ~6.5inches regardless of the encoder_scale value

joint following error when I try to jog over ~60in/min (linuxcnc units)

joint following error when try to home (probably related)

I haven't even gotten to the real configuration and am already failing :'/
Help is appreciated

1. there is no issue changing the firmware (unless you needed the 7I74)

2. 150V full scale should be OK though it may give less margin for sensing ARC OK if you don't have an
ARC OK signal from the plasma source. You can use any divider but /32 is suggested for best noise immunity
If you use /1 you must reduce the encoder filer time constant (so not suggested)

3. Yes, for 7i96s_7i74 or 7i96s_d or 7i96s_dpl firmware, the "A0" encoder input
is always on TB2 pins 7,8 (you can check by looking at the .pin files in the firmware directory)

Backlash not working anymore in LinuxCNC v2.9.x

Build my own laser CNC machine about 4 years ago, which worked fine with LinuxCNC 2.8.2.
Using an RPi 3B+, laser and 2 x L293D controllers and 28BYJ-48 steppenmotors.

After trying to update Debian to trixie the SD-card would not boot anymore, so build new one (back to Bookworm).
(Although i can get the old data from LinuxCNC of the card.)
Debian Trixie is not that RT compatible as written all over, still need an RT version to run LinuxCNC on RPI 3B+.
Pitty there is no complete RPi 3 (only 4 and 5) version of LinuxCNC available anymore?

After installing LinuxCNC v2.9.6 (on Debian Bookworm) I could not get the machine working as it did with v2.8.2.
I also changed X-axis steppenmotor with a spindle drive to make it more accurate, this works fine (backlash between 0.1 - 0.3),
but after this I still have trouble with the Y-axis (on which i did not changed anything).
Before (v2.8.2) the Y-axis had a backlash of 1.315, but now I can not get it right anymore.
It looks like the backlash is now only working in 1 direction and I do not see the backlash correction back on the motor movement.
Even if I make the backlash much bigger, just to see if is really done by the motor.
It only draws (i.e. circles) bigger, but the error stays (see IMG_4618a.JPG with BL of 1, 2 and 3)

My question is what has been changed in v2.9.x according the backlash, as I only find 'improved'.
In my case it is not improved but getting worse.
Maybe the new changes do not work with my controllers (L293D)?
And how to solve this weird issue.

Reagrds, DG 

 

Juergen
Very well done and extremely inspiring!!!
Thanks for sharing. I happen to have one of these gampads trailing around somewhere. Off searching
Greez
chris

Hi all, can someone help me with "setp cia402.x.pos-scale xxxx" value?
I've this type of motor with the same encoder: EMMB-ST-87-M-SM (X), EMMB-ST-87-M-SMB (Z1,Z2,Y1,Y2).
Z1, Z2 5mm/rev; X, Y1, Y2 180mm/rev but I don't know the correct pos-scale value.

Unser Plasmaschneider Hevy-Metal hat diese Jahr gute Dienste und schöne Ergebnisse geliefert....
Des halb haben wir uns entschlossen das THC nach zurüsten....
Erste Frage da wir damals die falsche Firmware genommen ( 7I96S_7I74 )haben gibt es ein Chaos wenn wir auf 7I96S-dpl gehen ?
Frage zum THCAD2 High isolation A-
10 V Full Scale
Wiederstände sind ok
Da der Plasmaschneider etwa 103 V beim Schneiden abgiebt was sich mit den Typenschild decktist die frage kann ich auf 150 V gehen für die Wiederstands berechnung oder sollte man auf 200 V gehen ?
Output Frequency ??Mode F/32 oder weiche für die 7I96S ?
Die Eingänge auf der 7I96S Endcoder-Stecker immer die beiden unteren wie in Beitrag 
MESA THCAD-2 - couple quick questions ?

Das war es fürs erste.

---

Our Heavy-Metal plasma cutter has served us well this year and delivered great results.... Therefore, we've decided to upgrade to the THC....
First question: Since we used the wrong firmware (7I96S_7I74) back then, will there be any problems if we switch to 7I96S-dpl?
Question regarding the THCAD2 High Isolation A-D
10V Full Scale
Resistors are OK Since the plasma cutter outputs about 103V during cutting, which matches the nameplate, the question is: Can I use 150V for the resistor calculation, or should I use 200V?
Output Frequency? Mode F/32 in the THCad 2 for the 7I96S?
The inputs on the 7I96S encoder connector are always the two lower ones, as in the post "MESA THCAD-2 - couple quick questions" ?
That's all for now.

king regard e Juergen

Thanks, I'm on the way to a solution for the drivers, what's left of the cables is clear to me, and the rest are: analog +-10v signals, one 25pin input cable, which are partly connected as soon as the machine is turned on, and partly I realized which ones are for homing and for inductive sensors from the tool. and this 25 pin output cable remains, there are a total of about 10 outputs, my plan is to activate them all manually, together, by hand out of 7i77card, to see what will happen on the other side of the machine where this TB3 (see schematic) terminal block is. the cable from the pendant remained, that is, the one  from external buttons to the controller, I mean jog, feed override, spindle override, axis select, step select, estop. I will have to find a way to activate the K1 switch, it turns on the drivers, but also to connect the estop to turn it off. My question is, do I need analog inputs for the pendant later, or could a configuration be made using buttons and potentiometers that would support mpg, potentiometers and buttons with digital inputs?