Hello Guest it is March 28, 2024, 04:04:57 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 - Doorn

Pages: 1 2 »
1
FAQs / A-axis orientation without Homing
« on: June 28, 2021, 12:51:13 PM »
Hello Technicians,

How can i control the A-axis orientation without Homing?

In Mach3 I have a problem with the alignment of my 4th Axis spinning my work piece around X.
I do not have a home switch on this axis and it is homed in place automatically when XYZ have homed.
The problem is that the top view of the tool path display is not perpendicular to the XY plane even when I enter 0° in the A-axis DRO.
When i rotate the display so it is approximately in the YZ plane I can see an angle of about 5° between the Z moves and lines indicating the table display Z.
When i switched to machine coordinates the A-DRO showed 355° but i read you can not change a machine coordinate.
When i set the work DRO to 355° the Z Moves do line up, but my program starts in A0 position so that is incorrect.
The first A-word does not appears before line 1300 and it also happens with programs not using the A-axis at all so it is not my program.
When i disable the A-axis the Z moves do line up, but that does not work when i want to use it.
I rotated the A-axis physically to 355 and then set this to 0 (which is something you normally do not want to do if you already lined up a part or fixation)
The Z moves lined up after regenerating the tool path display. Not the way you want, but problem solved, i thought.
Work and machine DRO both show 0 and fixating offsets all show A0.
I saved the fixations, Shut down mach 3, Clicked Yes again on the question to save fixtures an then restarted Mach3.
I Homed, Loaded my program again, DRO's work and machine show 0, A-axis did not move, all as it should be, except again the Z moves do not line up with the table display. ???
Again i need to enter 355 in the A-axis DRO to make the z moves line up, and this is where i run into a dead end. :(

When the machine coordinates show 0, all offsets show 0, and the working DRO show 0 and these are saved, where does this 5° that i just eliminated come from?
How do I make A0 the top and keep this the top even when the machine is turned off?
My program will need to run more than one day so i must be able to continue where i left. It worked in the past, but since a while i have this misalignment.
I didn't bother because i did not use the 4th axis, but now i need it again.

Best regards,

David

2
General Mach Discussion / Re: 4th Axis move after feed hold
« on: November 21, 2010, 01:30:44 PM »
I hate it when this happens >:(
I wanted to test if it was the macro or plug-in and now i can not reproduce the problem anymore.
I didn't turn off anything yet and used the same test file but the 4th axis does not rotate anymore like before.
Nice if it is gone, but will it return and when ??? and i still don't know what caused it.
For now i think i will remain very cautious using the feedhold.
Many thanks to those who tried to find a cause / solution.
If the problem reappears I hopfully find what triggers it too.

Regards David 

3
General Mach Discussion / Re: 4th Axis move after feed hold
« on: November 17, 2010, 03:07:07 PM »
Hi Hood,

You are really digging into it i see, thanks a lot.
I don't have  brains running.
The macropump i programmed myself, I'm sure i did not program movements in it, but maybe something triggers it.
What i find strange is that the A-move is synchronised with the finishing of the interrupted move of the other axis.
To make this happen there should be some intelligent programming involved which certainly wasn't me  ;)
I will test what it does without macro and plug-in as soon as the axis is free again.

Regards
David


4
General Mach Discussion / Re: 4th Axis move after feed hold
« on: November 16, 2010, 04:04:55 PM »
Hi Hood,

I do have a macropump running, it controls my pedant for jogging an the fro. There is a plugin for a pokey55 also used for the pedant.
The axis control itself runs via LPT and a BOB without plugins.
As far as i can remember the DRO was changing during this move after the feedrate. i currently can't check it, i have a part mounted to the A-axis and the program has to run about 20 hours.
I can only let it run a few hour in the evening after work and because i have no reference on the A-axis and I'm afraid to lose the product home when i go experimenting before it is finished.
As described before, it always moves 180° and reduces the speed of the other axis so it finishes at the same moment at which the programmed move, that was paused by the feedhold button, finishes.

Regards,
David

5
General Mach Discussion / Re: 4th Axis move after feed hold
« on: November 15, 2010, 04:16:43 PM »
Hello Hood / Ger21 Find the documents attached,
My test code can't be any simpler it's just zigzagging with a G01 the words i used is an F at the start and an M30 at the end the rest is just G01 X Y.

Hello Derek,
For me exactly the same, always connected, always powered.

I had never noticed it moving before, but didn't use it either until i mounted it recently.
I made an bridge between the Axis clutch and a bracket with a bearring so i can bolt my workpeace to this bridge.
Directly beside this bridge i bolted a temporary bracket to mount parts upright but it stands in the way of the bridge when rotating , so i have to remove this bracket first.
My Axis is never homing (no sensor) and was constantly at the same angle to stay clear from the the bracket but suddenly i found it moved against this bracket.
and i found scratch marks on the shaft of the bridge in the clutch so it had been slipping.
First i thought i had accidentally pushed a jog button, but a while later i witnessed the axis moving after restarting a feedhold.
I did some testing and found out it did happen constantly after every restart of a feedhold.
Since then i did milling with and without the Axis in use without a problem as long as i don't use feedhold.
but being able to use feedhold would be a lot easier.

Regards

6
General Mach Discussion / Re: 4th Axis move after feed hold
« on: November 13, 2010, 03:44:48 PM »
Hi Tweakie,

Was milling a lot so I wasn't around a while.
When you need to press stop after a feedhold, why press feedhold in the first place and not stop directly (that's how i do it now, no A-axis does not turn)
Stopping in stead of feedhold has however a disadvantage. Mach3 forgets certain words in a code line.
When you start again it reruns the current line, If this is a complete line with all coord present its ok.
However, if you are doing circles with IJK left out because they didn't change or you leave out the G code it often doesn't work anymore.
It often happens that i just have X or Y and (the last G code was G1) After restarting it says it misses IJK when it needs to do a straight line, but it just forgot.
Then i need to find the previous z move at clearance level or move to a safe place before starting again.
Feedhold does not stop the program it just delays the output until start is pressed. therefor i would like to use Feedhold if this A-axis problem would not occur

David
 

7
General Mach Discussion / 4th Axis move after feed hold
« on: October 21, 2010, 05:19:40 AM »
Has anyone encountered the same problem and know how to solve it?
I have a mill with a 4th axis. Normally i do not use this A-axis so normally "A" does not appear in my programs.
However, when I'm running a program and press the feed hold button, the A axis starts rotating as soon as i press cycle start.

I did a small test in which the i made a program flattening program with only a G01 command and the X and Y coord.
As soon as i pressed feed hold the axis stop moving as they should, but after cycle start the A-axis revolves 180°.
After every feed hold it rotates 180° further. The speed of the programmed X and Y movement is at that moment reduced to match the speed of the A-axis,
so the X,Y move that was being performed when feed hold was pressed are finished at the same moment as the A-axis completes this 180° move.
After that the X,Y moves continue on normal speed again and the A-axis stops as if nothing happened, until i press feedhold again.
It does not happen after stop start jog or what so ever, only after a feed hold.

Problem is that i now want to start using this 4th axis and that i sometimes need to place a workpeace next to the 4th axis even when i don't use it.
This means i can not use the feed hold button or the part will become scrap metal or the axis will hit the workpeace.

If anyone has an idea what causes this problem....

Regards
David




 

8
General Mach Discussion / Re: error code
« on: August 21, 2010, 05:12:47 AM »
Found it myself, ;D
I started to delete sections of the program and it appeared to be in a drilling section.
In one of the sections i used a G73 but with a Q0 and Q is not allowed to be negative or zero.
Maybe its possible to generate a more detailed error like "Q not allowed to be negative or zero" in a future release?
With G2 and G3 it also reports missing IJKR (At least during the program not sure during loading).

Best Regards
David

9
General Mach Discussion / Re: error code
« on: August 21, 2010, 04:10:36 AM »
It seems no one else had this error until now.
I get it during the generating toolpath (about 80% done) when loading a certain milling file. If i however click solve, I get the next error 9991.
If i click solve again, the 9991 keeps coming back, if i select no Mach 3 terminates.

I first thought it might be the number of code lines in the program (that was about 63,000) I reduced it to >50K, but mach 3 should support up to 10M lines.
Also I milled a program with over 40K lines successfully last week and did not change any settings.
This program uses the same milling cycles so I don't think the file contains different codes which mach3 would maybe not support.

Does anyone know what the errors 3336 and 9991 mean, what causes it and how to solve/bypass it?   

There is another strange thing caused by loading a code file which i can solve but often returns.
I control Jog via the macro pump and it works fine, but sometimes after loading a code file the responce to the buttons press or release is delayed a few seconds.
To solve this i need to close the code file and reload it one or two timed and test the jog. Once Jog works again it remains OK until i load a new code file.
Not nice, but I can live with it. Maybe it's related

10
VB and the development of wizards / Re: SLOW JOG RATE OEMDRO ?
« on: August 03, 2010, 08:30:59 AM »
Found it,  ;D
I use DoOemButton(336) to abort the jog movement, this is a toggle.
I use it for normal jog too, but that's in the macropump which starts from new every time so i do not have to toggle on again.
In the toolchange i do two jog moves after eachother and toggling off in between i forgot to toggle on again, therefor the macro never finished.
 

Pages: 1 2 »