Advanced Search

Dafür gibt es die 'toggle2nist' Komponente:
linuxcnc.org/docs/html/man/man9/toggle2nist.9.html
'loadrt' and 'addf' nicht vergessen

>> is the scaling set correctly
I suppose, you mean the "scale" factor inside linuxcnc ini file.
The problem arises as soon as i upload the uf2 file.

>> try another pin
I've been trying to associate zpulse to another pin, but it didn't work:
the old pin steel presented the square wave, the new zpin was mute.
Insted, i had a functional zdir pin, in both cases.

G.

The only ones disliking it are persons who do not bother to read the manual and move jumpers around with no idea of what and how that effects the card.
Probelem is, those persons make the most noise.
Again, i have in use over 70 or 80 (probably more) of Mesa boards, be it PCI or PCI-E or Ethernet, never had a single issue, ever, for over 10 years (probably more), all those machines are in use daily in production, not hobby use.
And i have no affiliations with Mesa, i have to pay at least twice the listed price to get them, and it is bloody worth it as i set them once and can sleep at ease knowing they will not fail, ever.
By now it has gotten to the point where if and when any fail, i will have a party.

Hello phillc54,
thank you for info.
 As I mentioned earlier - my version is QtPlasmaC v2.10-008.054
my linuxcnc version:

Hallo,

Wie schon geschrieben, ich will die MMS mit einem Taster ein und wieder ausschalten. Mit zwei Taster kein Problem.
Ich habe es mit (toggle) versucht. Hier nein Code.

net mist_on          toggle.0.in      hm2_7i76e.0.gpio.040.in_not
net mist_on          halui.mist.on    toggle.0.in
net mist_off         halui.mist.off   toggle.0.out

Das funktioniert auch soweit, nur, dass wenn ich den Taster das erste mal drücke schaltet der Ausgang einmal ein und dann wieder aus. Danach funktioniert es wie es soll.

Jetzt habe ich noch folgendes versuch was auch funktioniert. Nur dass ich dann beim Starten eine Fehlermeldung bekomme, dass  der Nebel nicht geschaltet werden kann solange der Notaus aktiv ist.
 
setp toggle.0.out 1
setp toggle.0.in 0

net mist_on          toggle.0.in      hm2_7i76e.0.gpio.040.in_not
net mist_on          halui.mist.on    toggle.0.in
net mist_off         halui.mist.off   toggle.0.out

Also beides funktioniert aber eben nicht sauber. Ich kann den Ausgang auch direkt schalten aber dann ist die Anzeige auf dem Bildschirm nicht Korrekt.

Schone Grüß.
 

There seems to be a general dislike for PCI-E cards?
In theory i should be less issues in communication between PC and card and almost no jitter/latency between both.

Problem seems to be really solved today.
The error message reappeared yesterday. Not only LinuxCNC shows the "Could not connect to display 0.0", but other applications also show the same message as well. I think the problem may be due to some corrupted files in Debian in my old SanDisk 120GB SSD.
Today I replace it will another SSD with the latest LinuxCNC 2.9.3, everything seems ok now.
Sorry VisionTek Radeon display card, it is not your fault.

Thanks Tom

JT

Flex now has a user timer that can be used in the user python module.



JT

Weird that spidev doesn't show up, I think that the overlay is not complete, since it worked (or at least visible) before you could try to add the overlay files of the other boards to see if it helps.

The (gpu?) lag is probably because all the small cores are isolated now, you can try to see if the latency is still low enough with less cores isolated, isolcpus=3-5, isolcpus=4,5 or isolcpus=5. The first 2 cores are faster, so ideally you would isolate the second core, but then I think it should be changed in the source of LinuxCNC to run on that core instead of the last core, but 31.8us is certainly not bad
So you can try the following config:

Where did you read about Ethernet compromising performance?
Mesa has no such issues, they can do easily MHz range pulses, KHz servo rates (i have tested at 4 KHz 5i25, 6i25 and 7i92).
I have several industrial machines using Mesa, in use daily for many years. Retrofit and build logs are on this forum and youtube, but my videos are cr@p compared to RotarySMP's.

Ah, i´ve been watching your stuff for a while to get a sense for what i am getting into, nice content!
You are using a pretty elaborate control interface on your Schaublin. I am not sure if i want to go down that route though. All i need is some jogging control to set offsets, tool measurements, start stop and feed override. My idea is using a USB pendant, a footswitch for my chuck and everything else on a touchscreen.
For years i have done nothing but adjust tool offsets on the control itself, everything else is straight from cam. And for jogging a pendant doesn´t need to be real time control via the FPGA in my mind.
Or am i totally wrong about LinuxCNCs control interface?

Regarding max step rate: that potential bottleneck is eliminated with Ethercat, there are no pulse/direction signals. Instead a new target position is give over EtherCAT to the driver.
I think the two technologies complement each other. If you have/want to use traditional drives with pulse/direction or analog voltage control you go with Mesa. If you want to invest in a field bus system with drives and other units, you go with EtherCAT.

Hi
In Qt Designer, how can I edit an entered g code using the qt widgets??

Good morning guys, I bought my nvem v5 board to test with linuxcnc, I'm still waiting, I saw in the files that there is an encoder component to compile in linuxcnc to use in remora, this component was created to only accept the mpg encoder or is there a possibility of using the mpg input to connect an encoder to a spindle or the spindle shaft of a lathe, I don't know if it is possible to use just the mpg encoder input or there is a way to use other inputs if configured, could you give me more details of this part of the encoder on the nvem board? thank you in advance thank you very much