nice Idea

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.

The dev mail list is almost useless.

Just curious, is there a current developer forum, mailing list or discord server for asking technical LinuxCNC code questions? Is GitHub the best option?

Hey everyone... I really appreciate the fast replies! I've contacted Wayne and sent him this link... so I am certain he will get it running.

Thanks again!
Jerry

Hi,
Does anybody know what connector is used for the MPG of the NVUM4-SP Board.
Tried:
1)IDC 2x8
 2) 2,54mm Modu
3) JST
None of them fit.
 
 


They are 8x2 pins.

Thanks

Hallo,
Du brauchst für den ersten Test keine confg in den NVEM zu spielen, die Basiskonfiguration für den Test ist dort bereits in der Firmware per default vorhanden. Zumindest bei mir war das so, sofern der NVEM antwortet (was er ja bei Dir auch tut) sollte das reichen. Die Fehlermeldung hatte ich auch, anfangs hatte ich da wahrscheinlich auch die falsche Firmware.
Ich habe dann testweise mal mit dem Oszilloskop die Achsausgänge kontrolliert, die liefern auch brav die Impulse.
Viel weiter bin ich allerdings auch noch nicht gekommen, es stehen und standen andere Dinge mit höherer Priorität an, daher sorry....

Gruß
Mario

@andrax
I appreciate your help and efforts on the topic. Actually, this was my working configuration, I just added the additional rows in .ini and .hal files as per you absolute encoder guide topic.

The "sdoConfig" line for 0x6098 is there to set the homing method of the drive. I added it before looking at your guide. It simply sets homing mode 34 - index pulse.

What do you mean by the wrong naming convention? You stated the halpin "opmode". Did I write it wrong or is the data type of signed 32 wrong? As per servo manual, it is an 8 bit variable but LinuxCNC expects it as signed 32.

I did not use the "name" attribute for the EtherCAT slave in the .xml, instead I use the slave ID number in the .hal file.

Would elaborate more on what is wrong the .xml file? I can get the .ini and .hal files from you absolute encoder tutorial but there is no .xml file there. That is why I ask about my errors in the .xml file.

Disable secure boot  in your BIOS.
I had this issue recently. I thought I had done this to this machine ages ago but, I found it was hard to make the change stick. Eventually got it. I found the numeric keypad is not enabled in the BIOS and used the top row.