Advanced Search

Thank you very much

The point is that you cannot inject MDI commands when in auto mode.
My approach would be to use a custom mcode.
Have a look at this
forum.linuxcnc.org/38-general-linuxcnc-q...iable?start=10#57149

It's a bit dated but should still work. You could also use python instead of tcl.

Ok, I made some tests
I managed to replace the button, but
I can do nothing from the dialog itself
it looks like during the dialog im in "auto" mode
and non of my attempts

cmdList.append(('command',"G1 G53 X300"))
#ACTION.PAUSE_MACHINE()
ACTION.CALL_MDI_LIST(cmdList)
#ACTION.CALL_MDI_WAIT('o<pnc_tc_manual> call',time=10, mode_return=True)
#ACTION.CALL_OWORD('o<pnc_tc_manual> call')
#ACTION.RESUME()
#ACTION.cmd.mdi_and_return(None,cmdList)

works

[QTvcp.QTVCP.QT_ACTION][DEBUG] MDI_WAIT_Command= G0 G53 X300, maxt = 10 (qt_action.py:204)
[QTvcp.QTVCP.QT_ACTION][DEBUG] CALL_MDI_WAIT Command: G0 G53 X300 (qt_action.py:207)
[QTvcp.QTVCP.QT_ACTION][ERROR] CALL_MDI_WAIT timeout surpassed 10 seconds (qt_action.py:211)
mdi_execute_abort: dropping 1 queued MDI commands



I probably miss the point you try to explain earlier

The only option I have not tried yet is
change the dialog, so tool_change button press return some value
work with that value in the loop in qt_toolchangeauto macro, since it's in normal auto mode - it may execute gcode / commands

it would reload dialog every button press (on pi4 its a pain), but at least it might work

Again I apologize....but I do not see that option anywhere in pcconfig...what am I missing?

Thanks

You can use pncconfs discovery option for this.

Most of the hobby machine-builder (*myselfincluded) hardly put effort in selecting the correct wiring for the job!! /lazy. And a lot of us can't differentiate between power-vs-signal wire, mΩ/m a.k.a. voltage drop, let alone using the correct gauge-vs-freq if they do. Shielding and wiring arrangement requirements comes last, imho.

Great vid regardless. Watched it all, relaxing! I like the guy and will bookmark his website/store.

Sorry..I meant the Mesa configuration tool...pncconfig works...the problem is that I nee new firmware for more axis through 7i96s and thought I needed Mesa Configuration tool to do this...is that wrong?...

Thanks

Thanks - I have it working using pyvcp, I connected the pin to both the LED and joystick in the postgui file.

Not clear what you mean when you say the configuration
tool does not work.  What happens if you launch pncconf
from a terminal window by typing:

pncconf

 (return)
 

DPFlex wrote:

Hello Todd,
I understand that you make example of "incremental encoder" with quadrature.
My encoder is 17 bit absolute multi-turn type, so the counts for one turn is huge value 131072.
I calculate: 131072*80/360 = 29127.111111. Is it still correct to apply ?.

I put ENCODER_SCALE = 29127.111111 to INI file, but nothing happen.
I understand need to revise HAL file to use ENCODER_SCALE, but it seem encoder component is only suitable to incremental encoder type.
linuxcnc.org/docs/devel/html/man/man9/encoder.9.html

Please advise Thank you.
 

This is a little bit of late reply, the encoder component documentation you referenced is a software encoder counting component applicable for reading an encoder via gpio such as through a parallel port. This would not be applicable to your situation with Ether CAT. But it sounds like you are on the right track now.
(I have no experience with Ether CAT.)

For positioning, I normally use a grid widget to give the rough position to an item within the main window. Then within its box, you can tell it to center, or be to the top,bottom, left or right.

When you try to connect glade halpin to a signal, you must do it in a hal file that is loaded after the gui is started (aka the post-gui-hal file.) If you try to use the pin name in one of your regular hal files that are loaded before the gui is functioning, you will get a hal pin not found error and Linuxcnc will close without opening.

Hi...seem to be stuck here...I can not get configuration tool to work..installed from usb debian 12 bookwork...could not get mirror so continued without..from there downloaded configuration tool..could not get to install...not sure why this is not easy but whatever......I am very new to linux...how can I update the firmware and use discover option..by other means..or do I need to resolve installation issues first?

Thanks,

Rick

Kernel 5.4 is not that new, there have been some issues with Ryzen CPUs. So if Tommylight's solution doesn't work you could try this rt kernel 6.10

drive.google.com/drive/folders/1L28lG0zD...2XQJx?usp=drive_link

No, you should just leave the Kins setting as Trivkins. As Rod was trying to say, the Trivkins machine model was modified to handle slaved joint gantries in version 2.8, as well as handle arbitrary joint to axis assignments. There is no need to to try to use another kins model.

Now a history lesson. (Stop reading if you don't care.) Previous to v2.8 the Trivkins machine model was truly simple. Just assigning each joint 0-8 to each axis x,y,z,a,b,c,u,v,w respectively. Such that if you needed a config that used axis X,Y,Z, and W. you had to set up and configure dummy joints and axis for the unused A,B,C,U,V axis. You could hide the unused axis in the user interface configuration so they were not seen, but they were still there under the skin. There was also no means for attaching multiple joints to an axis or to square a gantry. That necessitated the gantry kins config, it was a bit of a kludge and caused some minor confusion of joints and axis within Linuxcnc most noticeable with some user interfaces. With the merger of the Joints/Axis development branch into 2.8 (while 2.8 was in development as Master) the last version Gangrykins eventually became/was developed into the current version of Trivkins. Previous to Joints/Axis, the defining/separation of a joint and an axis, was not always clear or separated in the Linuxcnc code. This wasn't a big deal for trivial machines or even much of a problem for a gantry, but it could complicate setting up and running non trivial machines where the movement of a joint did not identically match the movement of an axis. Hence the push to clearly separate in the Linuxcnc codebase the difference between a joint and an axis.

Thank you, thats what I was looking
will start from here and update if succeded/failed )