Machsupport Forum
Mach Discussion => General Mach Discussion => Topic started by: Hood on October 06, 2006, 12:21:58 PM
-
Is anyone else having problems with Mach not asking whether you want to save "new fixture" when shutting down?
If I just open Mach, home, move to any position and zero the axis then shut Mach down it will ask but if I load any code whatsoever I will not be asked whether I want to save the new fixture even though I have changed the offset.
Hood
-
Do you have you optional offset save and persistant offsets check boxes checked in config-state screen.
-
Yes, sorry should have said that in my post :(
Hood
-
I thought you would have. 8)
I'm assuming you
1. Load your code
2. Jog to where you want zero to be
3. Zero your axis dros.
Do I understand this? ??? From this point, if you shut Mach down it should but does not ask for fixture save. Any time I have zeroed my axis, from that point on, when I shut Mach down it ask for fixture save.
-
Yes thats exactly what I am meaning, just you are a bit more eloquent ;)
This is happening on all the computers I have Mach on, the mill, the workshop computer and the home computer.
Hood
-
Interesting thing is I have just tried going back to previous versions, when I install 1.90.017 it works perfectly but my screen doesnt show properly as this version preceded the new LED style support. The next version I have is 1.90.035 and this doesnt work as far as the new fixture is concerned. Also any version after this does not work.
Hood
-
As a wise man told me, and I quote ( It's Arts fault, it allways is) ;D
-
I saw that LOL
Hood
-
Has this been resolved?, I am having the same problem ver 1.84.001 optional offsets are checked as is persistant
-
Only way I can resolve it at the moment is go back to version 1.90.017
This is strange because I have been using later versions for a long time but it is only recently that I have been getting this problem. I am wondering if an upgrade to a later version has changed something and going back the way is not overwriting that something. This then begs the question of why 1.90.017 works for me, I am confused, but thats a normal state of mind for me ;)
Hood
-
Hood I found the answer!! Make sure you dont have selected the option for config/state..copy
G54 from G253 at startup. That could overwrite your saved values.. I copied this from the yahoo group, it seems to work for me so far!! ;D
-
Afraid thats not my problem, was one of the first thing I looked at when I started having the problem :( Glad its got you sorted though.
Hood
-
Is this still a problem in 2.0? I am going to eat with Art in about 20 min and I will ask him if he has done anything to it :)
-
Still a problem for me anyway, all versions from 1.90.035 I am having the problem with, maybe even before that but I dont have any versions between 1.90.017 and 035 so cant say for sure where it starts for me but 017 works fine apart from my screen doesnt show right due to the LED changes :(
Hood
-
it seems to work ok for me, I ran ver 2 today. There is a couple of things, I have the auto zero checked and my home off is at 0.0100 the dro's do not change to this dimension after using g54. the mach 3 manual says it should. Also after homing if I go into mdi and type in g90 g54 g00 x0. y0 it does not move, it should go to where ever I have g54 setup at.
-
Art and I tested it here at the hotel and it is working great... I think there is a setting that you are not getting right. When I get back home I will help you :)
-
Thanks Brian
I just dont understand it at all, I presumed it was only me as I thought it would have been mentioned by others if it wasn't, but why its on all my computers I have tested it on I dont know. I will keep looking to see if I can find out whats causing it in the mean time.
Hood
-
I have found the problem.
I formatted a drive and installed XP, then Mach 2.g and I got exactly the same problem as before. I knew it could not be any setting I had done as I didn't change anything from standard. I thought it may have been something in my code so I wrote a very simple code with only G0, G1 and M30 in it and it still caused the problem.
I then thought about what I had done at the install and the only thing was I had put my license file in the Mach folder, I went in and removed it and tried again and everything works perfectly. I booted to my original drive, removed the license and it too works perfectly, same on another computer that previously wasn't working properly.
So it is my license file that is causing the problem for me, I dont think its corrupted as I have several backup copies of it and all cause the problem.
I am thinking it may be some of the anti-piracy steps Art has added lately that are interfering with my license.
Any ideas on how to fix this?
Hood
-
Mail me off line with the name and I will send you a new one.
Thanks
Brian
-
The license was a red herring, I was actually doing a different sequence after I removed the file which made me think it was the file causing the problems. (OK Mark McGrath no smart comments about consistency ;) )
Heres what I think now and I have repeated this quite a few times on different computers.
Test 1
Open Mach
Reference
Go to Zeros
Load G-Code
Move axis and zero
Close Mach and all is well as I get asked whether I want to save or not.
Test 2
Open Mach
Reference
Go to Zeros
Load G-Code
Move axis and zero
Regenerate toolpath
Close Mach and I DON'T get asked whether I want to save the new fixture.
Test 3
Open Mach
Reference
Go to Zeros
Load G-Code
Move axis and zero
Shift display mode
Close Mach and I DON'T get asked whether I want to save the new fixture
So looks like maybe there is a bug in the display mode and regenerate toolpath options.
I would appreciate if a few people that have the latest version (or 1.90.035 onwards) could test this out.
Hood
-
Has anyone tried tests 1, 2 and 3 above to see if they get the same results, I would really appreciate it if you could get back with reports either way.
Thanks
Hood
-
Hello Hood,
I just repeated all of your test and was asked every time to save fiture offset on exit. I'm using the tried and true version R1.84.001.
Brett
-
Brett
Thanks for trying but I think it is related to the updated graphics in the later versions, I think probably from 1.90.035 onwards but may actually be even later versions than that..
Thanks for trying though, much appreciated.
Hood
-
Hood,
Using V 2.0F and get exactly the same results as you do in steps 1,2 and 3.
Only asks for save if the screen isn't refreshed.
John S.
-
Thanks John, I was starting to think I was haunted. I am off to work a happy man knowing I am not totally crazy :)
Hood
-
Just in case this has been problem for anyone else I have found a workaround.
If I start Mach
Reference
go to zeros
load Gcode
jog my axis and zero the axis to make the new offset
regenerate the toolpath to see the updated offset.
Now previously if I shut down at any point after this I would not get asked if I wanted to save new fixture but I have found that, if after regenerating the toolpath, I press the zero buttons for each axis (even though they are already at zero) when I shutdown I am asked if I want to save the new fixture :)
If at anytime I regenerate the toolpath or change display mode I MUST press the zero axis buttons if I am wanting Mach to ask if I want to save.
Hood
-
Good job Hood. This in no way implies your not totally crazy. ;D
-
:)
-
Are you still having the prob;em in the new Rev2.x?
-
Yes Brian, if I touch the Regen Toolpath or the Screen Mode buttons it will not ask whether I want to save the new fixture on shutdown unless I do the workaround mentioned four posts up.
Hood
-
Hi Guys:
I found this one. It is definitely fixed for next version. It was a variable overwrite in the GenLists for the new toolpath as you discovered.
Thanks for all the detective work, it led me straight there..
Art
-
Great, Thanks!!!
Hood
-
Thanks Art
Just tried ver 2.0.004 and it is working exactly as it should :)
Hood
-
Hey Hood,
Have you tried the soft limits in this version? Do they work as they should?
-
I never used the mill today but the softlimits seem to work fine on the home computer. are you having trouble with them??
Hood
-
Yes, I'm running version 1.84.xx, the lockdown. When running a program it does not slow down to a stop. It is more like an E-Stop than softlimits. I knew creep-pea had been trying to get this worked out. I just didn't know if it was in the latest version.
-
Brett
do you have a slow zone set in the homing limits page?
That is what should make the softlimits slow before they hit limits. I have my slow zones set at 20mm (3/4" approx) on X and Y and 5mm on the Z and they work fine.
I think Creap-pea was having a problem with Mach telling him that softlimits would be activated when he opened some code. This was because of the tool offsets he had and Mach for some reason was seeing these offsets and saying he would be out of limits when in fact he wouldnt be. I am not sure if this is fixed as I have never seen this problem but probably because I have not used offsets.
Hood
-
Yes, I do have a slow zone set. I have inserted a screen shot for you to see. ( A friend told me about this cool program ). When running code, when it gets in the zone it just stops, no slow down. You do not have to hit reset to jog ( as with E-Stop ) but there is deffinatley no slowdown.
-
ha ha ok, think I know who that could have been ;)
Does this happen if you are moving fairly slowly?
Try increasing the slow zone to test things out.
Hood
-
Raised the zone to 3 inches, ran a small program at 20 ipm, still no joy.
-
Try jogging with the keyboard having set a slow jog rate of 20% and see what happens.
Hood
-
Oh, I'm sorry. I meant to mention that. It works as it should jogging. Keyboard or gamepad. Slows right down to a creep.
-
mmmmmmm well thats strange, mine has always done so in a program, or at least I am sure it does, will look see.
Hood
-
Thanks Hood. Keep me posted.
-
Tested it out and its hard to say but certainly looks like its not slowing down, will test out on the mill tomorrow if I remember and let you know.
Hood
-
Downloaded version 2.0.007 today. Softlimits still do not slow down while running a program. Just a sudden stop. It does give me a warning. If I run anyway, BAM, sudden stop.
Brett
-
That is why we added the test to see if it was going to hit before you run the file :)
-
It will work a treat when the tool offsets are sorted :)
-
That seem to be giving Art a hard time but I think it is getting better all the time ;)