Machsupport Forum

Mach Discussion => General Mach Discussion => Topic started by: Hood on February 27, 2013, 10:41:10 AM

Title: Lockdown (066) and Dev (067) versions, issues
Post by: Hood on February 27, 2013, 10:41:10 AM
Just a warning that the two versions above may  cause problems and personally I would not use them.
The problems include

In Mill, possibly Turn as well

macros not being fully run,
VB Buttons being totally ignored

In Turn

X Wear Offset DRO will double the entry you enter.
DROs often wont accept an entry you make
Also had reports of
threading not working when using the parallel port
Axis ignoring home switches and crashing into end of travels.

I have gone back to 057 on lathe and 056 on mill.

Hood
Title: Re: Lockdown (066) and Dev (067) versions, issues
Post by: stirling on February 27, 2013, 12:24:01 PM
Hi Hood - got any repeatable examples? - It's just that I've done a LOT of macro and button development recently using 066 (Mill) and thus far have not had any issues.

The change log is sadly out of date so no clues there.

Cheers

Ian
Title: Re: Lockdown (066) and Dev (067) versions, issues
Post by: Hood on February 27, 2013, 02:06:23 PM
I have a repeatable macro, every single time I pressed my Ref All button it would do absolutely nothing. I also have a panel button set up to call a custom macro that contains the same code, it will de-ref the axis then nothing, if I press again then it will send the signals to my servos to home.
 Now there could be a few things at play here, first is the VB is calling Modbus outputs, second is I am using the Smoothstepper thus a motion plugin is involved, third is I am using the MachMad plugin to call the macro from the external button.
 Normally I would really delve into the issues and try and isolate exactly where the issue lies so that Brian has an easier job tracking things down. However as Brian didnt show any interest in a previous issues I have recently reported then I have decided not to waste my time looking and just return to an older version.
 I suspect it may be some interaction with the plugin interface as I have had several reports of macros screwing up and all of them have been using external controllers.

Hood
Title: Re: Lockdown (066) and Dev (067) versions, issues
Post by: BR549 on February 27, 2013, 05:09:04 PM
As Stirling would say "They be Dragons in them versions". The problems go much deeper than just that. I had hoped that Mach3 would have been cleaned up by now, BUT????

Now I can say that some corrections and additions to Mach3 have worked well in later versions.

NOW macros are worse than ever about jumping out of thread sequence.

ToolComp is about useless IF you want to climb mill.  SOmewhere along the line TC took a serious hit.

(;-) TP
Title: Re: Lockdown (066) and Dev (067) versions, issues
Post by: Dan13 on February 28, 2013, 06:45:55 AM
Normally I would really delve into the issues and try and isolate exactly where the issue lies so that Brian has an easier job tracking things down. However as Brian didnt show any interest in a previous issues I have recently reported then I have decided not to waste my time looking and just return to an older version.
Hood

This is the sad part. They seem to be not interested anymore in providing support for Mach3. I feel like being forced to move to Mach4 (assuming it will eventually show up) - and not from my free will or choice. That's a shame considering there are only a handful of bugs that if were removed could make Mach3 a perfect program.

Dan
Title: Re: Lockdown (066) and Dev (067) versions, issues
Post by: Hood on February 28, 2013, 07:26:40 AM
Personally I would have preferred Mach 3 to have stopped development fully, at least until Mach 4 was out and working well, except for serious bug fixes of course.
These latest things, especially the Turn ones are clearly new bugs as they are only present in the latest versions.
Sad thing is some get sorted, others dont, it seems if its an issue with Mill it will likely get sorted, if its a new, introduced, issue with Turn then no chance of it getting looked at it would seem.

Hood
Title: Re: Lockdown (066) and Dev (067) versions, issues
Post by: Dan13 on February 28, 2013, 08:05:27 AM
Same here. Don't want any development, just want the bugs fixed. And you are right about Turn :(

Dan
Title: Re: Lockdown (066) and Dev (067) versions, issues
Post by: woodspinner on February 28, 2013, 10:53:54 AM
I've noticed that under .066 my ref all home button doesnt fully function either, I have an x offset in my homing sequence and the while ismoving /wend then my x move to 0 doesnt execute.

I reverted back to .062 to get it to work again. is this my best alternative or is there a more stable release?

John
Title: Re: Lockdown (066) and Dev (067) versions, issues
Post by: Hood on February 28, 2013, 11:02:55 AM
I use 056 but probably 062 will be fine, it just seems to be lockdown and dev versions that have real problems.
Hood
Title: Re: Lockdown (066) and Dev (067) versions, issues
Post by: BR549 on February 28, 2013, 11:16:42 AM
AH but for those that the Dev version FIXED some things they cannot go back. I have been stuck with this catch22 MANY TIMES in the past.

Where were yall when I was arguing this in the past FIX the BUGS in mach3 "BEFORE" you make MAch4 a priority. (;-)

TOO LATE, (;-) TP
Title: Re: Lockdown (066) and Dev (067) versions, issues
Post by: Hood on February 28, 2013, 11:26:30 AM
Fixing all the bugs would likely be impossible as is that not the reason Mach4 was started? I am sure no one would undertake such a huge task if there was no need for doing so.
 When I said serious bugs I was meaning ones that could cause damage to the machine such as home switches being ignored and the VB issues as that could damage a machine.
The big problem seems to be fix something in Mach 3 and there is a good chance  it breaks something else,  however what has been broken this time should  warrant it being pulled.
Then again thats just my opinion ;)
Hood
Title: Re: Lockdown (066) and Dev (067) versions, issues
Post by: cjmerlin on March 07, 2013, 01:27:17 PM


I have gone back to 057 on lathe and 056 on mill.

Hood


Is it possible to have download access to those 2 versions?
Title: Re: Lockdown (066) and Dev (067) versions, issues
Post by: Overloaded on March 07, 2013, 01:33:44 PM
ftp://machsupport.com/Mach/
 (ftp://machsupport.com/Mach/)
You can download them here ... if that's what you are meaning.

Russ

Fixed your FTP link Russ
Brett
Title: Re: Lockdown (066) and Dev (067) versions, issues
Post by: derek on March 12, 2013, 08:32:23 AM
Well I'm not so sure about 062 at this point. I ran the machine all day yesterday with zero problems. Started up today and mach kick out a compiler error for the M03. Restarted Mach and it seemed to be ok. Looked over after a tool change and the spindle never started. Caught it before it did any damage. Had the same error message . I'm going to downgrade further to 056 and see what happens.

Derek
Title: Re: Lockdown (066) and Dev (067) versions, issues
Post by: olf20 on March 18, 2013, 01:41:46 PM
Will anything be done about this??
Just courious.
Thanks!
olf20 / Bob
 
Title: Re: Lockdown (066) and Dev (067) versions, issues
Post by: rcaffin on March 22, 2013, 06:00:08 AM
Quote
Where were yall when I was arguing this in the past FIX the BUGS in mach3 "BEFORE" you make MAch4 a priority. (;-)

My thanks to several people on this web site for some serious discussions about the bugs. It seems to me, with 30 - 40 years of experience in writing code from machine language upwards, that the bugs in Mach3 are simply not fixable - without a TOTAL rewrite. Which is called Mach4.

An anecdote to ilustrate:
Old railway line. Engine hard worked and worn out. Owners ask a Scottish engineer to recommend cheapest repairs.
First reply: Can't repair, too clapped out.
Response: No, no, we can't afford that. How can we repair it and keep it going for a while?
Second reply: Ah weel, see yon whistle on top of the boiler? Weel, jack oop whistle and replace the bits underneath it.

Cheers



Title: Re: Lockdown (066) and Dev (067) versions, issues
Post by: Overloaded on March 22, 2013, 10:26:20 AM
 :) ;D :D ;D :),
Thanks
Title: Re: Lockdown (066) and Dev (067) versions, issues
Post by: rcaffin on March 22, 2013, 06:08:15 PM
Quote
Looked over after a tool change and the spindle never started. Caught it before it did any damage.
Dunno about that one. I find I ALWAYS have to do an m3 after a tool change.

Hum ... has the machine ever gone through an m3 after a tool change without starting the spindle? Well ... it is not impossible. There have been one or two occasions when I have hit the pause rail after a tool change because the spindle was not running. Hum ... maybe.

Cheers