Advanced Search

5I22-1.5 firmware for:

7I36 on P2 (PWM/ENC 0..3 sserial port 0 chan 0)
7I36 on P3 (PWM/ENC 4..7 sserial port 0 chan 1)
7I44 on P4 (sserial port 1 channels 0..7)


 
 

At its simplest
Then whenever the carousel.0.enable goes true, it will drive to that pocket.

All the subroutines etc are about the other things that have to happen before carousel motion, such as tool unload, spindle lift etc.

Ist ein Oszilloskop vorhanden? Falls ja, einfach ans Glasmaßstab anschließen, auf single shot stellen, Triggerspannung einstellen und die Achse joggen.
Ansonsten kannst du probieren mit dem Signal einen MOSFET und damit eine LED zu schalten (mit Diode in Serie am Gate, damit er auch geschaltet bleibt). Wenn bekannt ist, wo das Signal ist, kann man die Stelle anfahren und die genaue Spannung mit dem Multimeter messen. 

Can you start LinuxCNC from the command-line and paste the output here?

1/. The computer has a NEX 604 motherboard and uses a dual Realtek 8111E PCI Express Gigabit Ethernet chip.

2/.  

I'm guessing that the 8ms maximum tells you all that you need to know?

 

I think that this approach is probably valid, but will be necessarily comlex when building it from discrete HAL components.

You can look at the servo thread execution time with and without the added components to see if it is using a lot of CPU time, but it probably won't be.

Does Tormach include "halcompile" to create custom HAL components? If it does, then this is getting to the point where that might be worth doing.

linuxcnc.org/docs/stable/html/hal/comp.html

I always fancied the idea of being able to define limits as an STL file.
(STL because it's simple and easy to parse)

Are you basing your config on this wiki page?

wiki.linuxcnc.org/cgi-bin/wiki.pl?Simple_Remote_Pendant

Are you using the "-f" flag when loading the component?

That seems to have that effect. (But it might also be the default behaviour)

I've just put up a YouTube video with a quick demo:

unknown wrote:

Uninstall 2.9.5

Manually download the 2.9.4 deb files using gdebi.

Or 2.9.6 which has been created to fix this specific issue, but hasn't been moved onto the repository yet (I haven't been at home long enough to do it since the debs got built).

buildbot2.highlab.com/release/debian/dists/
 

"Dear friend,
I am working on retrofitting a grinding machine and I have prepared the following hardware for it: Mesa 5i22-1.5 + 2x 7i36 + 7i44 + 7i70 + 7i72 + 7i73. I would kindly like to ask if it would be possible to create firmware for this combination.
Thank you very much in advance."

It's not obvious what's wrong. Forget the 0x20xx SDOs, you are not using them, they are not mentioned in ethercat-conf.xml.

Let's look at the error message in syslogIf you look at the subindices that are listed, they agree with the documentation
 
(From teknic.com/files/downloads/ClearPath-EC_Software_Reference.pdf)
Some subindices ARE missing and I don't know why the EtherCAT master makes a big deal of that. If it needs that info or what?
I think the Invalid input configuration is a consequence of those errors but could be something else also.

Almost out of ideas, but there are two things you can try. Set configPDOS="false" or remove the option altogether.
If that doesn't help, increase debug level on the ethercat master to hopefully get some ideas on what's going wrong.for example, try to start linuxcnc and list the messages in syslog again.
Can you also show the content of sdo 0x60c2:1 and 0x60c2:2 (interpolation time) Use commandCompare with table in manual.
 

Hi  thankyou for your post.  Do you have any videos of it in action?

Clearpath should have good docs. Typically the CIA402 registers are > 6000. 
Its not a one size fits all.

There are quite a lot of optimisations required with the later kernels (Debian 12-13). I have documented them in a PDF file available here
erpx.au/shop/trixie-linuxcnc-debian-trix...tion-pdf-download-48
There is a nominal AUD $2.00 fee for this info... Sorry but it was the only way I had to store a file.
While it refers to Debian 13 Trixie, it also is applicable to Debian 12 Bookworm.

I will say that feedback from users I've received says 2 core PCs are marginal for Debian 12-13 but some have got them working with the optimisations I describe. I have never used < 4 core PC's