Advanced Search

Hmm, it looks the same if i add --sserial

I now have my RPI5, just as it should be.

 

That's correct, mesaflash does not show sserial devices unless you add the --sserial command line option

In the editor i just did a mesaflash --device 7i76e --addr 10.10.10.10 --readhmid... there is just TB2/TB3, P1 and P2 visible. No TB4, 5 and 6. Somewhere there the mistake? What to do?

That  should work, if LinuxCNC is running and there have been no watchdog or other faults.

 

I think that is just a GUI message (qtDragon?). What makes you think it is due to your remap?

Hello,
As a German beginner, I am currently trying to get my Mesa7i76e up and running.
I have connected three relays to pins 17, 18, and 19 and would like to control them via Halshow. When I connect a relay directly to 24V, it activates.
In Halshow, I would say that I have set the correct pins via Set. However, no output is switched. I can switch the yellow indicator in Halshow on and off.
I hope you can help. Thank you.

Translated with DeepL.com (free version)

Probe Basic is a separate project for LinuxCNC.

Vergiss den "Parallel Hat". Es gibt seit ein paar Wochen auf Aliexpress die 7I92 oder 7I98 für sehr kleines Geld zu kaufen, vermutlich sogar billiger als das "Parallel Hat" aus den USA:
de.aliexpress.com/item/1005009563621594.html
de.aliexpress.com/item/1005009714713471.html
Die schließt du einfach an den Ethernet-Port des Raspberrys an.

Falls du nicht vor hast Glasmaßstäbe nachzurüsten, ist die 7I92 mehr als ausreichend. Die Schrittmotortreiber kannst du auch direkt an die Pins anschließen (das gilt genauso für die GPIO Ausgänge des Raspberrys, da du nur die LED im Optokoppler der Schrittmotorendstufe betreibst, wofür 3.3V mehr als ausreichend sind, also ein "Parallel Hat" völlig überflüssig).

Ich persönlich habe vor genau einer Woche zwei von den chinesischen 7I98 und eine 7I92 bestellt und werde die testen und hier berichten, wenn sie da sind.

Ps: Die HAL-Datei von byte2bot funktioniert nicht mit dem RPi5. Man muss erst den SPI-Port abschalten (Anleitzung dazu steht ganz oben in der HAL-Datei) und die vierte Achse in der HAL abschalten oder so, genau habe ich das aber gerade nicht im Kopf. 
Auch die Signallänge sollte angepasst werden, da die standardmäßig zu kurz eingestellt wurde. Ich werde die Sache aber nicht weiter verfolgen, da ich lieber auf die Mesakarten warte. GPIO mit seinen paar KHz ist sowieso viel zu langsam zum Fräsen, auch für meine kleine Tischfräse.

This is very cool, I have a customer who created cooling passages and plumbed a chiller into his spindle motor mount. Then ran it into spindle motor to keep it from growing.

Can you post your ini file as well? What does it do when it homes? Have you tried setting a slower velocity as the carousel? Carousel doesn't have double tap homing like an axis/joint. Something I had a hard time with was I wanted feedback in revolutions but carousel only takes whole numbers not floats for counts. So I made the scale of the carousel Joint 1:1 with the encoder/stepper. Then used encoder/steps do drive the position.

I'm having a remap issue, but you can look at my config here. forum.linuxcnc.org/10-advanced-configura...ord-toolchange-false

You should be able to use the inductive sensor for the index pulse. (but you seemed to be saying that that was seen multiple times per magazine rev?)

In counts mode with the carousel .comp, with the right scaling, you should be able to use the encoder counts.

Follow the links and very carefully follow the instructions.

Or you can search the forums for the multitude of threads that discuss this issue.

I will add the files when I get home.5i25t 7i77 7i74 7i73 7i84. I have yet to implement the 7i73 but I plan on using it for all of my user interface controls. I did some research and I found all of the updated nomenclature for the version I am running. I got all the old lines updated to what I believe they should be. I finally got the control panel to open without an error. Just need to figure out how to add my external estop to check some of the functions on my bench before I try putting the electronics in my machine.

This sounds like a problem with event handling, then. Probe-screen might be passing-through key-press events but not key-release events.

Do you see the same issue with probe-screen-ng? (nothing that probe-screen-v2 seems to be abandoned)

You could even try this one: github.com/andypugh/probe-screen-ng

But these might have the same problem, I know that I have not tried to specifically address the problem described.