Advanced Search

The axis desynchronization issue was caused by an error in my INI configuration—the parameters I had set required a frequency higher than 50 kHz. I changed the servo period, and the error disappeared.

“Probe tripped during non-probe move” is resolved by setting delays. In my case, using an electrical capacitor. Over 2 million activations.

This leads to the conclusion that it would be appropriate to implement a Probe delay parameter in the machine settings. “Feedback” delay. That is, when the probe triggers, the machine must immediately recognize this and begin braking, and then even execute the next command (typically, recording and rebound). And the specified parameter in seconds or milliseconds should not react to a change in the probe’s state.

@christer
github.com/LinuxCNC/linuxcnc/pull/3971
could you test this?

@AkkiSan
github.com/LinuxCNC/linuxcnc/pull/3971
could you test this?

@ fery15sty
github.com/LinuxCNC/linuxcnc/pull/3971
could you test this?

Hello,

have found out the Problem - have flashed another bin gain - now 4 different Versions in the same project.

Have edit the above Post for others looking a way to bring this thing to work.

Hello
So bad I missed this topic, I was looking for this board for years !!

One question regarding the doc

Feedback 0 will typically be the encoder or resolver mounted on the motor, and feedback 1 can be used to connect either Hall sensors for initial commutation or (potentially) scales mounted directly to the axes. See the  Pinouts section of this document for pin assignments and typical wiring color codes.

  So we can connect linear scale ? but does it include a PID closed feedback?
I sent you a message on matrix to get the price of a board please.

Thank you for your awesome work 

Moin, also nach ewigen rumgesuche - habe ich jetzt nochmal NVEM erased und neu geflasht. Und zwar jetzt mit dieser bin:

Jetzt kann ich die Achsen verfahren ohne Probleme auch hochladen der configs führt zu keinem Problem.

Also scheint es irgendwo in dem NVEM Ordner zuviele Remora-NVEM.bin Firmwares zu geben die nicht funktionieren.

andrax wrote:

Do you have a sample program that uses the G43 call?

Not handy at the moment, but the issue persists across multiple programs.  First noticed on a fairly simple turning pgm with 3 tool changes, but the same thing happens when I just hand code or trim down a pgm for testing.

I can double-check for something abnormal later, but is there something I (or the post processor) could put in a program which would cause LCNC to ignore G43?  It's not like there's a GOTO statement skipping over the G43 words.

Hello,
Hope you are well,
I have bought a 7i76EU and would like to know if you have any specific firmware I should use.
My setup is Linuxcnc 2.9.7, VFD is Omron MX2 and I will connect this using the RS-485 mode. Other config details, I am using 5 Gecko Stepper Drives driving X1,X2 Y, Z and A rotary axis. I don't have any encoders.
All Jumpers are default and I have a unregulated power supply that I can connect to the board.
Can you also confirm if a CAT5 cable or higher speed cable is required.

Thank you.
Kind Regards,
Orrin

Witam mam linuxcnc 2.9.8 płyta Mesa7i92 z SSK-MB2 jest to frezarka trzy osie X Y Z programy ngc działają prawidłowo.
Uruchomiłem WHBO4B-4 na przewodzie i nie do końca działa prawidłowo czyli gdy kręcę kółkiem i gdy przestanę oś idzie dalej .
Proszę co mam nie tak ustawione.
Załączam moją konfigurację.
  
 
 
 

Do you have a sample program that uses the G43 call?

nice Idea

Would love to have a logo for linuxcnc-ethercat to match

Moin,

kannst du mir ev. sagen welche HAL und INI du nutzt? Mir kommt es so vor als ob der NVEM gar nicht reagiert. Habe zwar Ping zur 10.10.10.10 aber das wars wohl auch - weder ändern sich Input-Pins in Halshow oder Scope noch anderes...

there is also a Discord server discord.gg/guQXfw2R