Advanced Search

I totally get the desire to stick with the existing tool changer. 1 thing you could make would be a gang holder, that would certainly give you more options.

 

Thayloreing wrote:

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

Hi, for the MPG the encoder counting is done in LinuxCNC using the normal inputs as the speed is low. The PRUencoder module is used for the hardware based encoder modules. The NVEM is limited on Inputs, but please check the EC500 configuration below with the NVEM configuration to identify which inputs are available for the QDC encoder module.

Remora-RT1052-cpp/LinuxCNC/ec500-rt1052-DMA-ENC.txt at main · scottalford75/Remora-RT1052-cpp
Remora-RT1052-cpp/LinuxCNC/nvem-rt1052.txt at main · scottalford75/Remora-RT1052-cpp
 

Sounds like maybe laser intensity setting?
Can you use motion-current-vel?

Try searching for "adaptive feed", although a bit fuzzy on it, and not sure if you are looking for exactly that.
Is this for a lathe or mill?
I assume it is a mill since you mention XY but no Z.

Failing to build the kernel due to issues with the RealTek DKMS drivers:
Consult /var/lib/dkms/rtl8814au/4.3.21/
I would try removing the DKMS driver, install QtPyVCP then install the driver again.

Here is an interesting discussion regarding IC AX58100 designed by Håkan BåstedtMetalMusings
github.com/MetalMusings/MyOwnEtherCATDev...uecomment-2474082363. With the kindly given instructions I have my board working and ready to run on LINUXCNC

Hello all

I now have installed pyocd, but no luck with connecting. I guess it should show a target id here ?

xx@xxxxxx:~# pyocd list
# Probe/Board Unique ID Target

---

0 X893 ARM CMSIS-DAP 0001A0000000 n/a



Flashing fails then too:

xx@xxxxxx:~# pyocd flash /home/bf/Downloads/remora-rt1052-3.1.3.bin –-target mimxrt1050_quadspi
0000497 W Generic 'cortex_m' target type is selected by default; is this intentional? You will be able to debug most devices, but not program flash. To set the target type use the '--target' argument or 'target_override' option. Use 'pyocd list --targets' to see available targets types. [board]
0000674 I Loading /home/bf/Downloads/remora-rt1052-3.1.3.bin [load_cmd]
0000690 C No boot memory is defined for this device [__main__]

 

Anything wrong with the wiring ? I got 24v supplied to the remora board

-
schnellmued
 

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