@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

Revisiting an issue I noticed here:

forum.linuxcnc.org/10-advanced-configura...l-orientation#345715

At the time I wasn't sure if this was a GUI issue, or something in my config.  I've since switched GUIs (Axis, FlexGUI, and Qtpyvcp) and the issue is the same across all three GUIs.

Problem I have is that G43 isn't being applied consistently during a program.  G43 works via MDI, and all three GUI tool-change buttons.

I've tried every permutation:
Tn M6 G43
Tn M6 G43 Hn
M6 Tn G43
M6 Tn G43 Hn

And the same as above, but with G43 on another line.  Also tried an M1 after the tool change line(s) - even a few lines down - but LCNC just isn't applying the tool offset.

When I run a program, LCNC excutes the tool change - new tool number is displayed in all three GUIs - but doesn't apply the offset.

Tool number doesn't matter - whatever tool offset was previously applied remains active after the Tn M6 line.

Under Axis I was using the "T" remap from the sim lathe-fanucy
Under qtpyvcp, I commented out the "T" and "M6" remap and was just using the 'stock' M6

I'm sure this is something on my end and unlikely to be an LCNC problem.  Maybe the remap.py and stdglue.py used by my other remapped M-codes is interfering with 'normal' M6/G43?

Anyone have an idea what would interfere with G43 being applied during a program, but not via MDI or a GUI-based command?

I pushed some changes to master to fix this and much other stuff.

The fix for running macros with a button was two characters in the handler file.
If you just want to edit your's directly let me know and I'll give instructions.

I also added to the online docs to help.

Thanks for the report and please let me know if this is fixed for you.