Advanced Search

thanks, then I will buy a 7i77 and I solved the problem with cards:)

thank you, I made a mistake, I have 7i74 instead of what I wrote 7i44

Thank you for your efforts and the quick reply.
I will test it tomorrow.
I have also just ordered a network card:
Intel Gigabit CT Desktop Adapter 893647 Network Card EXPI9301CT 
Perhaps this will work better than the onboard network card.

VG Anton

The issue with a 7I96S+7I74 is that there's nowhere to add the second encoder
(well you could have strange 7I96S+7I74 firmware that puts one differential encoder
on the RX lines of 3 of the 7I74s RJ45 connectors)

Edit: you need three encoders: X, Z, Spindle.

You could use a 7I96S+7I85+7I83 but a 7I96S+7I77 might make more sense

A custom cable wouldn't be difficult, if not mesa has this.
store.mesanet.com/index.php?route=produc...69_71&product_id=285

sorry I made a mistake, I have 7i74 instead of what I wrote 7i44

thank you very much, I have a 7i96s , so I thought I'd use it in combination with a 7i74 i also have, so I thought about getting a 7i83, i only need it for two servo motors+ spindle, 7i83 it is cheaper variant in that case.

I have a 7i92
P1 > 7i76
P2 > 7i74 > 1 port to a 7i83 (for spindle control plus some extra "things") and another port to a 7i73

The 7i74 might be a better fit as it has a 25 pin connector that matches the 7i96s connector where as the 7i44 has a 50 pin connector, tho it wouldn't be impossible.

Yes you can do that but you might be better off
with a  7I92TM +7I77 or 7I97T

Hello, is it possible to connect these three cards, it is a plan to retrofit a lathe with siemens analog amplifiers.. ?in case it can't 7i96s+7i77 can 

Xiānshēng nǐ hǎo Delta B3L sìfú qūdòngqì méiyǒu màichōng sùdù móshì nǐ shì rúhé shǐyòng sùdù móshì shì yào xiān bǎ màichōng zhuǎnhuàn dào 10v de mónǐ sùdù fāngshì ma? Yīngyǔ shì yòng fānyì ruǎnjiàn fānyì kěnéng bùnéng zhèngquè biǎodá
展开
87 / 5,000
Hello Sir

Delta B3L servo drive does not have pulse speed mode

How do you use the speed mode? Do you need to convert the pulse to 10v analog speed mode first?

The English translation is done using a translation software, so it may not be expressed correctly

Hallo zusammen!
Ich bin immer noch in den ersten Wehen mit Debian 12, LCNC 2.9 Pre1und meiner 7i76E. Axis läuft schon mal. Aktuell habe ich folgendes Problem:

Unter Axis kann ich den Nothalt Button auf der GUI lösen, dann kann ich auch die Maschine einschalten. Soweit so schön.

Jetzt habe ich aber noch an der Maschine ein PNOZ Sicherheitsrelais mit zwei NC Pilz-Tastern in Reihe eingebunden, die (als Loop geschaltet) über den Ausgang des PNOZ auf einen Eingang input-10 gelegt, die Maschine stoppen sollen, aber nicht stromlos schalten wie ein Kollege im Beitrag forum.linuxcnc.org/42-deutsch/50957-e-st...-immer-aktiv?start=0

sich das gewünscht hatte. Das Signal estop-ext soll einfach das Gleiche auslösen wie das interne estop über die GUI.

Die entspr. Zeilen in meiner Haupt HAL sehen so aus:

net estop-ext <=  hm2_7i76e.0.7i76.0.0.input-10-not #Pin 11, dort kommt das ON Signal vom PNOZ an
# und wg der loop mit NC Kontakten muss das Signal invertiert sein.
net estop <= iocontrol.0.user-enable-out # GUI Signale
net estop => iocontrol.0.emc-enable-in

Leider ist die aktuelle Funktion so, dass ich mit dem GUI Button die Maschine freischalten kann obwohl estop-ext nicht dran hängt, also die externe Nothalt Loop mit dem PNOZ/Tastern unterbrochen ist, was gedrücktem NotHalt Taster entspricht.
Das will ich nicht. Ich möchte dass sowohl das Signal estop als auch estop-ext jeweils den Nothalt auslösen können und die Maschine aus ist und bleibt bis zum Reset der Taster UND dem GUI Button.
(nicht stromlos, wie im o.g Beitrag gewünscht, weil ich einen VFD mit NotStop Funktion habe der die Spindel augenblicklich stoppt und nicht austrudeln lässt wie bei stromlos.)

Also spannende Frage - was muss ich in der HAL ändern, damit beide estops funktionieren, aber auch beide entriegelt sein müssen um die Maschine zu starten.  (estop-ext hatte ich schon ohne Invertierung probiert - gleiches Ergebnis)

Vielen Dank für Eure Ideen und Hinweise!
Arno

I am a little confused on how to get say an IO module working. Most everything I see details the servo side of things. Also, if using Classic Ladder how to draw in the addresses?

At the end of the day, i think that it is time to start coming out of the stone age using step and direction and parallel port emulation. While far less expensive, it uses way too many BoB's and leaves way too many variables that make troubleshooting and long term support too open ended.

While I am no expert at LCNC, I am a 30 year cnc service and applications engineer with 30+ years on Fanuc as an integrator, as well as Seimens/Heidenhain. The primary focus is always on reliability with maximum cost efficiency. But, with all truly capable cnc controls to get that level of determinism you have pay more than a couple hundred bucks.

I develop industrial solutions and tend to never seek hobby level solutions. Otherwise you end up with something along the lines of Mach4 which has zero standardization and zero ability to have consistent support.

All that said, I would like to find a way to develop a team outside the normal channels to further advance the LCNC system to a more streamlined and almost canned version that allows for integrators to setup a system without weeks of tweaking around the endless versions of this and that. I suppose my idea is to create a standard fully developed LCNC system that provides the specific hardware interfaces and drivers. More or less along the same lines as Fanuc and the rest of the commercial grade products. LCNC is mature enough to handle this. At least from my perspective.

I started down the rabbit hole a year or so ago and gave up because the zero to hero factor is not practical based on the hundreds of iterations on the web. Sure customization is cool, but if as an integrator I install the system in a custom manner my client will only be able to use 1 source for support. That fails the smell test. I suspect that is the reason LCNC has never made it past the 98% hobby level system.

Thanks for the info and I look forward to chatting more. And listening to your humble advice in regards to my above statements. I think ProbeBasic was a solid start down the path of standards on the GUI side. Now a standard for a hardware setup needs to be created. Maybe even tie them together. Who knows...?

I would disable turbo-boost in the BIOS as anything that changes the CPU clock
can cause major latencies.

The interfaces file is an alternate way to setup a network connection.
to use it, you must add the required lines to the interfaces file, something like:

       auto enp1s0
       iface enp1s0 inet static
           address 192.168.1.120/24
           hardware-irq-coalesce-rx-usecs 0


The last line only makes sense if you have a Intel Ethernet chip

One way to check for this is:

dmesg | grep -i eth

(you may need sudo dmesg | grep -i eth on some systems

or

 lspci | grep -i eth

Also check that you have ethtool installed with:

man ethtool

or the " hardware-irq-coalesce-rx-usecs 0" line will not do anything

 

Hello,
AXIS has a selection box with jog increments (1, 0.1, 0.01 mm). But to select a certain value, you need the mouse.
I want to link a key on the keyboard to a value. For example, I press "Key-A" and the 0.1 mm selection is made. It's a bit like a shortcut.
I found a command to change the speed:

root_window.bind('<Key-1>',lambda event: set_feedrate(10))

This works and is exactly what I want.
Now the problem is finding the correct routine to call, set_feedrate() is for ffeed rate ... but what's the name for jog increment ?
I guess it's something like jog_increment()?
Subsidiary question: where can I find a list of functions of this type that can be called from a script?
Thanks,
Denis