Hello Guest it is April 15, 2021, 10:07:36 AM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Konrad K

Pages: « 1 2 3 4 5 »
11
General Mach Discussion / Re: Mach did again!
« on: October 10, 2010, 06:22:31 PM »
Quote
"z = GetToolChangeStart(2)" delivers the WORK coordinates before start of the toolchange. Unfortunately, this value does NOT include the tool lenght offset.
One could argue about whether that means the 'Z coord' is wrong or just misunderstood, but clearly one has to be very careful about what ASSUMPTIONS about definitions one makes in writing the code.
Once again, very valuable information.
[...]
All very helpful: thank you.

Cheers


Thanks for your feedback :-)
I better should have said: "wrong for what I wanted to do with it"  ;-)

My reference was the default script which comes together with Mach3. I just took apart and reassembled it. So, my conclusion was that I just could return to the coordinates delivered by "GetToolChangeStart" function...  At least my conclusion was wrong...  ;-)

Konrad


12
General Mach Discussion / Re: Mach did again!
« on: October 10, 2010, 06:03:44 PM »
Good afternoon,   ;D

as promised, I spent the weekend in the lab.

1.
As I stated, I am quite sure that the M6End Script is sometimes not started, or is interrupted by another "Ghost" sending commands to the trajectory planner. Maybe, Mach3 does not see wether the M6End Script is terminated before continueing with other (paused) operations.
To be sure that my tool-change script is able to finish properly, I attached the content of M6End Script to M6Start Script, generated a Message window to have a pause for the manual tool change. As a result, the M6End is no longer needed.
--> After this change, I could do tests for hours, without encountering any surprising events.

2.
Secondly, I noticed a clearly reproduceable position error after completing the tool change: Z-Axis was wrong.
So to say: Machine DRO and Work DRO are showing correct coordinates, but, the "Z target position" was incorrect.
"z = GetToolChangeStart(2)" delivers the WORK coordinates before start of the toolchange. Unfortunately, this value does NOT include the tool lenght offset. So, when commanding the return movement with a "straight feed" or "straight traverse" command, the Z position is wrong, because those commands need the "controlled point" as target coordinate, which includes the tool lenght offset.
Of course, it has to be taken into account that you need the tool lenght offset BEFORE performing the tool change and new tool measurement... So, you have to do it all in one script, or you have to use a global variable to store the "old" tool offset.


So, I am fine now, waiting for new adventures... I will inform you about the next crashed drill bit.  >:D


Regards, Konrad

13
General Mach Discussion / Re: Mach did again!
« on: September 30, 2010, 05:30:54 PM »
If it only happens after a tool change, it may be interesting to look at the M6 macros in some detail?

Cheers


It also happens when the M6End is an empty file.  *lol*

14
General Mach Discussion / Re: Mach did again!
« on: September 30, 2010, 05:13:55 PM »
Ok look forward to your results but it seems to be Mach does indeed know where the axis is if the machine coords are correct, doing a verify would confirm this I think.

Hood

Yes, it seems to know where the axis is, but wants to go to the absolutely wrong position for some reason I am not yet able to see :-(
(I only spend so much time in Mach3 because I honestly don't expect he competitors to work better - they will also have their own quirks. In fact, Mach3 with all it's possibilities is brilliant. Hopefully, we will catch the glitch before christmas  *gg*)

15
General Mach Discussion / Re: Mach did again!
« on: September 30, 2010, 04:47:02 PM »
Konrad
so your DROs and Toolpath show where the tool is supposed to be but its not?
Hood

The MACHINE coordinates are correct. (same as physical axis position)
-- This is easy to recognize, because the physical machine moves quite continously.

The CURRENT coordinates (with work, fixture, tool and temporary offsets) are heavy to recognise, because the offsets seem to be switched during execution of toolchange and selecting another tool-table entry.
(So to say, I was not able to determine wether they are correct or not.)
-- This will be my work on the next weekends, because I am not working in the mechanical lab during the week.
-- I think it makes sense to capture everything (display and machine) by camera, to be able to review the crash. (I fear any screen capture software could influence the CPU load and thus timing of the PC)


16
General Mach Discussion / Re: Mach did again!
« on: September 30, 2010, 04:28:46 PM »
Ok do you ever home the machine by pressing the Ref All button?

For my machine, I can confirm that homing is regularly done by "ref all" and home switches. So, my machine coordinates always refer to the same mechanical position reliably...

I also confirmed (by watching DROs) that MACHINE coordinates remain correct when the big accident (TM) occurs. i.e. the machine does NOT get out of reference by itself (of course, after hitting the stock and trashing the bit, everything stalls and is de-referenced)

Next step will be to run programmes from the diagnostic screen and check offsets and so on...

17
General Mach Discussion / Re: Mach did again!
« on: September 30, 2010, 04:08:49 PM »
No home switches, no limit switches

So, it can be stated that electric noise does NOT cause the trouble we have  ;-)

(In deed, I also made test runs with de-activated switches to isolate "noise" from the possible causes...)

18
General Mach Discussion / Re: Mach did again!
« on: September 30, 2010, 03:53:50 PM »
This thread is like a deja vu for me.  :o

It seems I am suffering from a very similar trouble also on my machine: After performing a toolchange, sometimes something goes wrong.
The crazy thing is: I was (and I still am) not able to recognize any pattern in the accidential loss of position, except that it happens after tool change, when pressing "Cycle start" to perform Auto-tool-zero.

-The machine is equipped with home switches on all axis' and tool height sensor.

And here is, what should happen:

G-Code runs
Tool change commanded in G-Code
Z, and then X and Y are moved to a convenient tool change position (by M6Start-script)
---
   Manual tool change
---
Home Z axis
go 20mm above tool height sensor
then do the whole referencing stuff...
(In fact, this doesn't matter, because it seems, that the "M6End-Script is not even executed, or something bad happens before mach3 can execute the script..)

... and this happens after Manual tool change

maybe an unexpected movement to somewhere in the center of the stock,  :-\
maybe there appears the "preparation move" dialog before the unexpected movement will take place...  :'(
What I can state:
- The Z Axis is homed by my M6End script before the tool leght is measured, so, if this homing is not performed, I KNOW, that the movement is NOT caused by my script
- This "terrible accident" happens SOMETIMES not ALWAYS, whenever:
  - G-Code remains absolutely unchanged (same part)
  - XML remains absolutely unchanged
  - NO ONE button is pressed during program execution

---> This is the whole story...

This, I feel, is a real quirk, and I know for sure, it will be very hard to find and repair what is causing this trouble.
(maybe some race-condition in mach 3 code, or some other timing problem which also might not be reproducable on any hardware...)

After spending lots of working hours in researching this damned mis-behaviour, I decided to keep my hand just over the emergency-off after tool change and wait for the release of Mach3 V4... (by the way: when...?????)

regards,
Konrad

19
General Mach Discussion / Re: Softlimit update by macro
« on: August 08, 2010, 07:14:51 PM »
Anybody any further ideas?     ::)

20
General Mach Discussion / Re: Softlimit update by macro
« on: August 02, 2010, 01:31:47 AM »
have you tried to turn the softlimits off then on again via the macro? It may reset the new value.

yes, didn't change anything  :-(

Pages: « 1 2 3 4 5 »