Hello Guest it is March 29, 2024, 07:58:50 AM

Author Topic: Upgrade Failed  (Read 8283 times)

0 Members and 1 Guest are viewing this topic.

Upgrade Failed
« on: November 22, 2009, 03:00:18 PM »
Can anybody assist, I upgraded from mach ver1.84 which was working perfectly on my lathe, to ver 3.042 now the spindle will not control above 600 RPM it just ramps to full speed, axis run with an intermittent motion ramping from slow to set speed and back. The driver diagnostics appear normal, the computer is a PIII 531 MHz with 256M ram running windows XP Pro the kernel speed is unchanged at 25000Hz.

Brian.
Re: Upgrade Failed
« Reply #1 on: November 22, 2009, 04:36:54 PM »
Hi
I just went through the same thing exactly
I had a hard drive crash last Tuesday.
Had a spare system and saw that there was a newer version of mach3
so I downloaded it.
Just about pulled all my hair out. First I could not get it to
run the printer port.LPT1
Then when I did get it to run the following happened:
1) My indexer would only work at 100 or less. It work fine for years before the crash.
ie I could not thread.
2) The spindle speed would not display on the screen, no matter the speed.
3) When I tried to run a program, the 'start from here' button would not
    work. Program would rewind and start from the beginning.
Worked at this for most of last week on/off thinking I had a computer problem.Even went and got another to try.
Today I went back to R2.63 and in 15 minutes all was working again
Made some parts just to be sure.
eddie
« Last Edit: November 22, 2009, 04:52:15 PM by motorworks »
Re: Upgrade Failed
« Reply #2 on: November 22, 2009, 11:43:06 PM »
This happened to me also. The problem was the debounce value for the index pulse in the general config screen. My had been setting at 2000 for a couple years up through ver 2.42 with no issue. I had no idea what the 2000 referred to, but it was a default and worked with no issue. Somewhere along the way, the definition of the 2000 changed to 2000 x 40usec pulses in the recent releases and this was way too much - totally hid the pulse. The spindle speed dro did weird things and threading was impossible. Changing the debounce value to 2 fixed it. - Terry
Re: Upgrade Failed
« Reply #3 on: November 22, 2009, 11:45:36 PM »
Hi Eddie

Many thanks for the info, could it be that the computer is marginal, IE with the lower demand that the earlier Mach versions placed on it, it worked fine. I have just seen that the minimum system requirements are a 1Ghz machine with 512Mb ram.
Is the XML file the only thing required if one removes the program to reload an earlier version?

Brian.

Offline RICH

*
  • *
  •  7,427 7,427
    • View Profile
Re: Upgrade Failed
« Reply #4 on: November 23, 2009, 07:49:47 AM »
Lawley,
The latest versiom 3.042.032 works just fine for threading. You should take a look at the Threading on the Lathe
write up as it talks about items which apply to threading. Take a look at the configuration section.
You only use a single index.
RICH
Re: Upgrade Failed
« Reply #5 on: November 23, 2009, 07:57:17 AM »
Thanks Rich

The problem is not really with threading, but the servos on the axis are ramping up and down in speed during a cut. This is also evident on the feedrate DRO, I am running digital AC servos using step and direction from the parrallel port, which all worked fine on version 1.84. 

Offline RICH

*
  • *
  •  7,427 7,427
    • View Profile
Re: Upgrade Failed
« Reply #6 on: November 23, 2009, 08:05:06 AM »
I don't use servos so someone else that does will probably chime in.
RICH

Offline zarzul

*
  •  232 232
  • Wyoming, USA
    • View Profile
Re: Upgrade Failed
« Reply #7 on: November 23, 2009, 10:28:09 AM »
do you have backlash enabled?

Offline zarzul

*
  •  232 232
  • Wyoming, USA
    • View Profile
Re: Upgrade Failed
« Reply #8 on: November 23, 2009, 10:29:21 AM »
what do you have for accelleration settings under motor tuning?
Re: Upgrade Failed
« Reply #9 on: November 23, 2009, 12:27:19 PM »
Backlash is not enabled Motor velocity is 2000mm/min steps are 625 /unit accel is 1000 these settings have worked for 18 months with ver 1.84 Interesting is the fact that there is a vast size difference between the XML file size from ver 1.84 to ver 3.04 is 42 kb versus 102 kb

 Brian