Work with probe

Thank you. I hadn't clicked onto that issue as a solution.
Best thing to do then is remove the old .axisrc file, remove the existing macro, python and probe-icons folders from PSV2 and then re-install and just make sure the hal and ini files have the correct changes.

I'll report back when that's done.

That should do the job as it does for me ... and you make me think I forgot to update .axisrc.

The .axisrc is dramatically different between versions so you probably do need to update it.
Some observations on the Pi4 with 2.8.2 AXIS remembering I don't actually have a machine connected and just a wire for the probe. (Should really wire in a button). Anyway.

1. The jog buttons now work and the DROs on the PSNG screen now change.

2. Click on one of the probe action buttons and the DROs do not change. At first I wasn't sure if they were even working since nothing is connected. However, quickly flip to the main screen and the DROs are changing and you can see the tool following the path as outlined in the original first posting in this thread for whatever operation is chosen.

3. Run a G-Code program with tool T1 in the tool table and T1 M6 G43 and the tool lifts up, moves to the tool change position. Goes down, Goes up, Goes down and then the dialog with the date of the T1 entry into the tool table shows up. Click on tool has changed button, dialog box vanishes and program stops. After that it won't run again.

Likely this is an interaction between the need for an automatic tool changer and manual tool changing which was commented out as part of the installation procedure for PSNG.

Point #2 isn't critical but really _should_ show all axis motion no matter how it's happening.

Point #3 needs a change to the installation instructions which alludes back to my previous comment that I have no idea what that M6 checkbox etc are for and how to use it. And since I am still changing tools using the tool #'s in the tool table and not then checking tool height with a sensor pad, there's probably no need for this part of the screen.

So perhaps someone who knows, can explain:
a) What is required if the automatic tool changer (and possibly a probe operation to determine tool height) is not needed or wanted.

b) What is required if there is a manual tool change at the tool change position but there is also a probe to a sensor pad to determine tool height. Useful if a different size drill bit is put into a jacobs chuck.

c) What is required if there is an automatic tool changer with tool number and slot number and valid entries in the tool table.

Thanks
John

Gave it a try to put it on the actual machine.  Step one after installing as per instructions for the AXIS interface is to comment out all lines in the psng.hal file and do not comment out the manual too change stuff. 
That restores manual tool change with only one annoying feature that as yet I have not solved.  We move to the tool change position.  Then it moves move up and then down again before putting up the original dialog rather than the one from the PSNG code.

The second issue and way more annoying is there doesn't seem to be a way to load the smaller icons etc.  renaming the icons folder to icons_1280 and the icons_1024x768 to icons doesn't seem to make a difference in icon sizes.  And I can't find anything that directly references the size of the screen.

What is needed is one of two things:  either a smaller PSNG screen or the ability to slide the panel on the right out of the way whenever the PSNG screen has focus.  I can't be the only one who has stuff sitting beside the main screen.

Other than that, as expected it reaches the -Z distance before the contact occurs (because nothing is connected) so that part appears to work.

John



 

Hi John, have a look to ini file and replace

EMBED_TAB_COMMAND=gladevcp -c probe -x {XID} -u psng/python -H psng/psng.hal psng/psng.glade

by

EMBED_TAB_COMMAND=gladevcp -c probe -x {XID} -u psng/python -H psng/psng.hal psng/psng_1024x768.glade

I updated axisrc file but it didn't fix my previous problems except settings that seems to be saved and restored properly now.

I think I'll find some time to read all 50 pages of this topic and dive into this project code to fully understand all functionalities. I'll write a full documentation if I can.

In the meantime, I tried "auto zero" option, I guess it set up offsets of current coordinate system.

Thanks.
I'll try that. I've been digging into the Python code to see how some of it relates to the tool change. I've got some of it figured out but as usual, the only real documentation of any substance is this:

Whereas for my Python code for the CAN support at least I'm doing this sort of thing:

I'm going to start documenting some of the code because two hours later I've forgotten what the heck it was doing.  I think for external documentation some state change and dictionary drawings would also be helpful.  Something like the attached.  I did this a long time ago.
 

BTW, instead of changing the INI file with the psng/psng_1024x768.glade I renamed psng.glade to psng_1280.glade and rename the 1024x768 file to psng.glade.

No difference. My monitor screen is 1280x1024 and the image I posted is actually that size. On the Pi4 the 1080P screen does show both my panel and the touch psng screen.

Here it is on the Pi4 which is connected to a MESA 7i92H. Not sure if the real time delay warning is because I'm also connected via WiFi or if the CAN bus code is taking too much time.

On my side I just renamed psng.glade to psng_1280x1024.glade and made a symbolic link to the file that fit my screen and I have a different panel according to which file I choose.