Advanced Search

I am having problems with the loading of examples from the GladeVCP manual:  Run the sample GladeVCP panel integrated into AXIS like PyVCP as follows:

when the workpiece is touched off in fact the tool table is shifted

I don't think that's how it works[*].  The only time my tool table changes is when I measure a tool with my toolsetter, it never changes because I've touched off the workpiece.  Touching off the workpiece should change the WCS's offsets, accounting for tool length, not the tool lengths themselves.
I think you've figured out the right way to do it, though.
I've not used "tool touchoff" yet but from what I've read, it works relative to the WCS.  Thus, you have to start with a tool that the WCS is zero'd to (regular touchoff), and you can set the rest relative to that (with tool touchoff).  With TT you first put the end of the tool at a known location relative to the WCS, then tell the system "this tool is at XYZ regardless of what you think, to adjust your idea of the tool's location[2]" but it only works if you know what the XYZ is.
So what you're doing with your depth gauge is measuring it's Z with a "known good" tool, then setting all the rest of the tools to "that Z" because "the tool is at that Z, adjust for it".  You have to re-measure it each time you change the WCS, with another "known good" tool, because when you change the WCS you change the location of the depth gauge *relative to the WCS*.
What my system does is use a separate WCS just for the toolsetter (depth gauge in your case) which is always the same offset from the machine origin (G59.3, set from the INI file by my M6 code).  That way I never have to measure the toolsetter, because it's always at the same XYZ relative to the machine.  It does mean, though, that the tool "lengths" are relative to some arbitrary datum.

[*] although maybe we're not understanding each other, because the odds of English being the problem are just as good
[2] I just realized I set up my camera and laser offsets the hard way...
 

I understand what is happening here now. When I set all the tools together, using a depth gauge on the machine table the tool table is filled out with a set of z heights. When I then touch of one tool to the work piece, I get the desired effect of a set of tools all set to the work piece and if nothing needs changing, all is well. The piece can be machined
However when the workpiece is touched off in fact the tool table is shifted by what ever the difference in height is between the work piece datum and the depth gauge, and if just one tool needs adjusting, you need to know what this difference is. I didn’t. 
So to set the tools and also know what this offset is in case of breakage etc, I think this can be achieved by taking one tool, touching off the z axis to the workpiece datum, then moving this same tool to the tool depth gauge and recording the z offset to trigger it. Then when triggered touch the tool off and enter the recorded offset, which is the z offset of the workpiece datum. Then change to the next tool using MDI TX M6 and again move the tool on to the depth gauge and when triggered, touch that tool off, entering this same z offset just recorded before and again with all the tools.
Should you then need to make a tool adjustment or change this can be done by touching off on the same gauge on the machine table, entering our established z offset from the gauge to the work piece datum.
must work as just made this on my Hurco KMB-I

It has been very stable other then an occasional following error when I home.
I'm still using standard homing, guess I haven't taken the time to pursue the absolute encoder instant homing.

Only time that I had a racking issue was when one of my Y homing sensors went bad and the other side of the gantry kept going...

This video of mine explains how to set up the network.


if you type man hm2_eth it explains how to edit the network file to set a fixed Ip address for the 10.10.10.1 IP address on the PC (after you review the output from the IP a command tommy mentions

When touch off tool to workpiece in axis, the z-value is related to the current active coordinatesystem. If you touch off tool again, after modify z-offset, make shure g49 tollength is canceled, touch off as usual and dial in the displayed z-value from dro. Thats what i would try carefully

 

Some BIOS's disable memory access in PCI peripheral cards
LinuxCNCs hm2_pci driver re-enables them. This is the likely
cause of this issue.

You _may_ be able to access the card with mesaflash after running LinuxCNC
but this is not necessary unless you need to change your daughtercard setup.

you helped me out, thanks a lot!
I wasn't aware about the dpll module with/without...

The machine is working now but mesaflash doesn't see the 5i25 anyway,
but doesn't matter for me, just wondering...
 

If mesaflash does not find the card, that seems more like a hardware/BIOS issue

Also:

setp hm2_5i25.0.dpll.01.timer-us -50
setp hm2_5i25.0.stepgen.timer-number 1

Will fail on a 5I25 that does not have a DPLL module,
so you might try commenting those lines out.


 

Can you post whet the exact error is?

Can you post whatin a terminal returns?

Hi Guys,

tried to update a system with Mesa 5i25/7i76 kit, running well on wheezy 2.7 to 2.9.8.

The hostmot driver seems to have problems to see the cards. Maybe they are too old? (10-12 Years)
lspci shows a device called "DPIO 2718:5125", mesaflash does not find the 5i25
pncconf seems to see the cards and uses the correct config and mesa tabs.
But Linuxcnc doesn't start because of unknown pins(?) in the hal file
I have attached hal and ini... (See comments in hal where the wrong entries are)

Do you experienced guys see whats wrong here?

Thanks in Advance and best Regards
Stefan

This would be the handler.py for the popup, the ui is currently a blank QDialog Window from QTDesigner nothing on it, i would add that after i got the window working like i want it to work. The problem is that it is something self created and nothing really proofed. I ocouldnt find a post here in the forum and the LinuxWiki side about Qtvcp and QtDragon isnt helping much ,too. Ive really no idea if im even on the right way.

Hello everyone, I’m asking for your help to understand how I can automatically square my gantry, which is equipped with two motors for the Y and Z axes. The motors have multi-turn absolute encoders, so I don’t have sensors for homing. For me, it would be enough if both motors had the same value. Currently, I perform this operation manually in jog mode when starting LinuxCNC. I’m attaching both the .ini and .hal files. Thanks for your help.

can you post the ui file that defines your popup dialog?