Machsupport Forum
Mach Discussion => General Mach Discussion => Topic started by: woffler on December 28, 2011, 01:25:16 PM
-
I am just starting to use mach turn ,have used mill for years, problem when using outside post proc. i get this Tool radius index too big line 40 . How ever there is no line 40, it seems to buck line N19 ,i am posting the g code please look it over and let me know what i am doing wrong ,so i can fix it .
Thank You Dusty
-
It is your G76 on line 19, reason it says line 40 I presume will be the macro does it longhand internally so there will be lots of lines as far as Mach is concerned.
The reason for your error is you are using words that Mach does not support in a G76. See screenshot for valid ones.
Hood
-
Thank's for replying Hood ,i figured it would be you ,anyway i see a D word in there that is wrong . I have got a call into support for a change in the post . i am not sure what the (D) word is for . I will have to search out a known good post for( Boob) cad cam from someone in the mean time.
Thank's Dusty
-
Also a U there, not sure what that is meant to be. Your amount of spring passes are quite high as well ;)
Not sure what BobCAD post processors are available but I did send them some code a few years back so they could see what the typical lathe code from Mach was like. I dont use BobCAD so not sure if it was ever used.
Hood
-
What version of BobCAD are you using? I see there are post processors for MachTurn, are you using one of them?
Hood
-
I just got off the phone with them they changed the (D) to a (H) and i am on my way to the shop to do a test run and see what we get . I am using the std Mach turn post there are only two Std. and Metric. Version 24 lathe . I will let you know what happens and if it works ,is there somewhere to post it for other's so they can find it for there use?
-
There is a post processor section of the forum for that :)
Hood
-
http://www.machsupport.com/forum/index.php/board,8.0.html
-
Well that did not fix it, still did the same thing , ???
-
can you post the new code? Last one had a F for the feed, should P for pitch, also had a U which I am not sure what its meant to be. As said the Q was 60 which seems a heck of a lot of spring passes, normally 1 or 2 would be sufficient.
I looked at the post processor page for BOBCAD and under CAM Ver2 there were a load of posts.
Hood
-
Here is the file with the (D) changed to (H).
-
I looked in the software there is only one finish pass on the thread's.
-
The G76 is nothing like what is needed for Mach, not sure whats what in it but shouldnt be an F and shouldnt be a U. As said the spring pass (Q) is 60 so not sure what they are putting in there if its only meant to be one. Did you tell the CAM it was an infeed of 60 degrees? maybe thats what it is, BTW 29.5 would be a normal infeed value to use.
Hood
-
I believe that Q. is the in feed angle of 60 ,i have foud some more posts but i am not sure idf they will work with V. 24 iall i can do is try them in mach and see what a happens. Kind of a bad way to do thing's .I am still looking for a user with a good post ,he or she is out there just have to stumble across them.
-
Hood if i post the xml. file for lathe could you take a look at the settings and see if i ahve thing's set correctly ,i had Burr man look at the posts, he tried three of them and mach came back with several errors in tool tip radius and tool length offset. I am new to this lathe deal ,so i have a few questions .
(1) do i need to set the tool table i in mach to mach the table in the cad software?
(2) is there some kind of gouge tech. in mach that needs setting or turning off?
-
Yes post you xml and also the Tool3.dat which you will find in the macro folder for the profile you are using.
You dont need to set p the tooltable in Mach to get running but once you have things set up then you would normally have the offsets for different tools set, assuming that is you have a turret or some means of repeating when swapping tools.
Hood
-
Hey hood i am trying to send you those files but for some reason it will not let me post them ,they are zipped and under the size limit ,any ideas.
-
What message are you getting? may just be you need to rename the zip to something unique.
Hood
-
We try and try , lets see if it will post!
-
Ah HA ! we have won with our little grey cell's!
-
Seems to be fine, loaded some code of my own and all is well. Just need to get your BobCAD post sorted and you will be on the way :)
The G76 BobCAD is putting out is all wrong, heres and example of the code in my G76
G76 X10.25 Z-10.5 I29.0 P1.75 H0.2 Q02 T0 C1.2
Mine is metric so numbers may look funny :D
If you use the simple threading wizard you should get code that will run well enough for you.
Hood
-
Thank's Hood ,i am working on it over at the zone with a couple guy's hopefully they can figure it out . I purchased the software so i could put multiple cuts together in one set of code .
I had know idea this was going to turn into this mess just part of it i guess ,there policy says that,they have to output a usable g code so we will see what happen's.
Thanks for the help
-
Noticed your licence was Dolphin CADCAM, do you have Dolphin? If yes do you not like it that you bought BobCAD?
Hood
-
Hi Hood ,i have an old version of Dolphin mill from when they first started in the US and i bought my Mach license from them ,it was a kind of real basic program .
And from what i can see it still is.
I got a call from the post folk's at bobcam they want a good g code program for them to look at with rough and thread program , they are going to modify the original post.
Can you send me a sample please ? and they also want a list of all the canned cycle stuff that Mach use's ,i have tried to go to Mach and get it but i keep getting an error that the sight is not available started last night .
I was only able to get in through the e mail notification from the forum sight trouble i guess .
Thanks
-
Do you have a DXF of the part you want and I will code it via Dolphin so BobCAD can see how its done ;D
Hood
-
I made one up for you ,with a rough and a finish and a 3/8 thread i think this will work for you . If there is a problem please let me know ,you better include a copy file of your post so the dummy's can see how it is supposed to be .
I started with these guy's a few versions ago V21, i think they have made some great improvement's and then something like this come's along and i start cruising for different cad cam programs.
I think we will have to give some serious thought in the coming month's to changing but the cost is so high for a decent program.
Thank's Hood
-
Forum has been crashing every time I have tried to reply, lets hope it stays up long enough this time ;D
I couldnt open your dxf properly so I have just attached one of my own with the code, its metric but really that shouldnt matter?
Hopefully it will help BobCAD get you a post.
I have also attached a couple of screenshots, one of the toolpath in Mach with your xml and also a pic of the toolpath in Dolphin.
Hood
-
Oh BTW the reason it shows the toolpath above centre in Dolphin is my lathe has front and rear turrets and I was using the rear as that is where my standard turning tools are :)
Hood
-
Thank's Hood ,i have also been experiencing the same problem, i hope that this will resolve the issue with the post .
Thanks for the screen shot's and the dxf files and code this was very kind of you and will not be forgotten by me.
Thank's Dusty
-
Heres hoping it ets things sorted for you :)
In Dolphin the standard Mach post was ok for a standard lathe but mine is a bit different and I made a lot of changes to the post processor. It looked quite daunting at first but once you got into it it was relatively easy to do. Not sure if the BOBCAD post processor editing would be as easy but may be worth having a look? Dolphin does have quite a good manual explaining the parameters and syntax used in its post processors so that helped, dont know if BobCAD has similar though.
Hood
-
Hi Hood ,sorry it took me so long to get back the sight was down. Any way i am still having some problems ,i tried to run your g code it got to the G76 line and then it just stops gives no error message , i checked the diagnostics page everything seems to be working correctly spindle feed back and everything it just stops spindle stays running. Can you send me a screen shot of your general config page so i can look at ,could the initialization string cause this problem i am not sure what to put in there.
-
Just looked at your profile and you have the turn diagnostics plugin enabled. That was for previous versions when Art was trying to get threading better for the parallel port, it doesnt work now with the current driver and may be your problem so switch it off and restart Mach.
Cant remember, are you using the parallel port or some other controller?
Hood
-
I will give that a try ,i am using a parallel port 1and 2 on AC servos , there is so much information you do not know what to use, and what not . It will be morning before i can get back to it ,i will make the changes and see what happen's and let you know .
Thank's Dusty
-
Ok that is likely your problem.
If its still not working look on diagnostics page and see what the state of wait for trigger and threading leds are.
Hood
-
everything seems to be working correctly spindle feed back and everything it just stops spindle stays running
Mach may be waiting for a number of spindle rev's to confirm the timing.
Debounce and index debounce can affect the indexing so maybe try different settings.
You can check the index by rotating the spindle manualy and when in G94 mode you will see the indicating light in diagnostics turn on and off.
Just generate a threading code via the wizard (we know that code works) and run without actual cutting. If the threading cycle starts then the
those settings are not the problem.
RICH
-
Just looked at your xml after Rich mentioned the Index Debounce and you have 100, that is also likely a problem, when I used the parallel port if I had any value in there at all then it would affect things, you would notice it easily by spindle speed readings being slow to respond or being totally off. You have averaging so maybe you dont notice it so much, I never used averaging.
BTW Rich the code I posted works ;)
Hood
-
Hi Hood , i have made the changes suggested disabled thread diag. and set index debounce to zero ,i ran the threading wizard got the same result stop's at G76 .
I am looking at the diag. screen , tool path led lit,spindle feedback lit,threading led lit , index light flashing. I get an output light flashing even though none are enabled.
It says G95 mode led lit,spindle on led lit,true rpm pulsing 588 to 587 rpm. I tried to send screen shots but i not get any kind of file to load to the forum.
-
Strange, can you attach your latest xml?
Also you do have the licence loaded on that machine? If it says Demo then threading wont work.
Hood
-
I have just run your xml with that code simulating the index and it ran fine so it would seem your index pulse is not being seen, assuming you are not in demo mode that is.
Hood
-
This was my thought also, i just changed out the proximity switch that i had to anouther , maybe i need a different kind of sensor, what would you suggest ?
I checked the under help it shows that it is licensed under dolphin cad cam.
-
Ok then it must be the index. Is your spindle RPM showing correctly? Can you uncheck the spindle speed averaging and see if it still is ok.
I now use the spindles encoders index pulse for the index as I use the SS on all machines but previously when using the PP I used Optek OPB916B optos to good effect.
Also is the active state of the prox correct?
Hood
-
Yes the spindle rpm shows correctly and i have had the averaging unchecked and that made know difference .I tried different states of the pin never made a difference i hooked a meter to the +- of the switch it changes voltage but it seems to be very slow or just not enough change 4.5 volts and down to 2.2 volts but it is not consistent .
I am also wondering about using the second port on the index ,could this be a problem i can see the led on the switch fire perfectly every time but it does not match the led on the diag. screen at higher speeds . I do not know what to make of it since it get's the rpm correct?
-
Ok as a test, can you make sure all is clear so you are cutting air. Go to Config, Ports and Pins then Inputs and enable the emulated for the index and then set a keyboard key for it, maybe the F1. Run the code and if it stops at the threading then start pressing the F1 key as fast as you can and see if it starts threading.
Regarding the LED on the prox and LED in Mach, no thats just the screen cant refresh fast enough to see it.
Oh one more thing, maybe your axis cant move fast enough for the spindle speed in the code and the pitch, maybe try editing the spindle speed to 300 instead of the 1000.
Hood
-
Just looked at your Z axis and its topping out at 1775mm/min where the code is asking it to do 2000mm/min so that could well be the issue. Dropping the spindle to 500 in code may make it work.
Hood
-
I used the wizard and wrote a small program ,with a spindle speed around 150 rpm and emulated the signal and it started to thread,so the problem is the signal i can see the led pulse on the screen but for some reason it is not recognizing it .
-
It is maybe not clean enough for some reason to be used as the index to start the thread.
Take it it did not run at all without you emulating?
Hood
-
No Hood it would not,i ordered a new hall effect gear tooth sensor ,i had used on my mill hopefully it will read it .
-
Spindle speed averaging won't cause the problem as it only looks at 8 or so different rpms and then averages them
for the threading planner.
If you are trying to cut a thread and your axis velocity is not fast enough for the feed rate then the threading wizard will
warn you and not post the code. That is the reason i suggested you generate the code from the wizard.
I didn't remember if the G95 wouldn't be activated though and that may be the case.
Didn't look at the code Hood posted.......you should have around 3 to 5 x the pitch in Z travel so the axis has time to accelerate.
Would seem that with a correct rpm showing that you should get an index to start the treading.
What version of Mach are you using? ....hopefully somethng greater than V3.042.32
RICH
-
My Hall effect works like a charm and was easy to install ( crazy glued the rare earth magnet to the gear ).
How it was attached:
http://www.machsupport.com/forum/index.php/topic,12484.msg82818.html#msg82818
RICH
-
Hello , thanks' for helping ,the version of mach is V 3.043.037 ,i gave what you suggested a try and i increased my velocity to the z axis gave the z plenty of room to start from ,no change.
I have ordered a new gear tooth sensor and am waiting it's arrival ,mean time i will hook the scope to the switch and take a look at it .
-
Lets us know how you make out with the new sensor.
RICH
-
If you scope then make sure you scope both ends, ie direct at the sensor will let you know so much but if it goes through a BOB then it could well be that that is causing issues.
Hood
-
I hooked up a C3 board from Aurturo that i had and forgotten about and a opto ,same result ,the first switch checked out fine on the scope gave a nice 2 to 5 mill sec pulse.
Just what Mach requires to see the pulse so i guess the board is the next logical step to check ,man what a pain for a few thread's ,i wrote Aurturo to see if he had a suggestion for a board.
I have a Probotix board on that second port ,i had from another mill project when i went to servo's i do not believe it is buffered and this could be the problem i am facing . I am going to try and read some on that board and see what is up with it.
-
Sorry for the mistake on the buffering it should of said , that the board was not buffered. ???
-
Just thought i would update everyone ,i ran the sensor through my port one BOB with the same result speed sensed but mach still refusing to pick up a thread . Could some one post me a G code for a thread that they created in the wizard and has been successfully run.
I am still thinking i do not have something set right somewhere and i am over looking it .
-
It certainly does seem strange that RPM is reading OK and your index etc LEDs are fine.
The threading code I posted the last day I ran but afraid if its wizard code that is tested it will be tomorrow before I can do that as its 11pm here and the workshop is 10 miles away :D
Hood
-
Code from the wizard for a 1/4-20 thread. Tested and works.
RICH
-
Thank's Rich ,i will give it a try and see what i get .
-
Thank's Hood Rich ,sent one and i will test it and see what we get , just can not figure this out ,i am sure it is a simple thing i am missing somewhere .
As i have tested two completley different sensors and BOB's with the same result it must be an error on my part or a software issue.
-
Hi Rich, why the -.3 in the Z start box? i have been using zero there.
-
I have been following this thread and will continue till we get her fixed.
It is really weird because if the sensor was not working correctly you would not get a correct rpm read out
or it would be erratic and varing in rpm in the readout. So i like you and Hood are probably trying to pinpoint is it software, electronics,
or computer related at the port. If we just start throwing out suggestions you'll end up loosing the hair on the upper lip.... ;)
RICH
-
The thread starts at Z=0 so I'm giving the Z axis some travel time to reach proper feedrate ( 6x.050 lead= .3 could be less as the general rule is 3 to 5x lead ). Actualy the X should be positioned at the stock OD so you don't get that combination move from x=0.
RICH
-
Testing the index pulse:
A few things I would try...
1. Do the triggering test page 9 of Threading on The Lathe writeup which can be found in Members Docs. You will see the index turn on and off
and that would say that Mach is sensing the index.
2. You can play with the distance the hall sensor is away from the magnet. maybe a little closer may help....again if it's reading rpm you would
think it wouldn't matter.
3. Set the spindle rpm for something slow like 50 rpm ( if you have a VFD can you set it manualy?) , then with the psindle running and the
diagnostics screen open you should see the index LED blinking on and off. If it works for that then increase the rpm and see if it still blinks.
4.If the above works than use the wizard to generate code but use a very slow rpm ( rather than the 400 spindle rpm use maybe 50 ) as that
would provide a longer time for sensor and Mach to respond. All you need is to have the spindle turning and the drives can be disengaged
if you can / want to do that. Monitor the diagnostics screen and watch the LED's change from threading , waite for thrigger, and the index.
If the above works then would seem that the software is behaving correctly relative to the sensor and at different spindle rpm.
RICH
-
Woffler, can you post your xml file?
RICH
-
Rich you have -0.3 for the Z Start, I think thats what Woffler was asking about as z0.3 would be expected more, maybe its a typo?
The situation of no threading just sounds like there is no licence file loaded yet there is. Wonder if such a thing could happen with a corrupt licence?
Hood
-
Could be Hood and didn't think of the license file. Maybe try Mach with it removed from the directory and then put it back in .
Another thing to try would be to create a new xml file as i have had one of them get corrupted once ( couldn't get the axis to move).
Copy the xml from the original download, rename it, then change the settings and save. Easily done and worth a try.
RICH
-
I will try that later today ,i have to go out of town till this afternoon and will give that a try as soon as i return ,with out a license does it exclusively just cut out threading or would it cut out the turning wizard , because the turning wizard code will run. I will do it and try to eliminate the possability of a bad file ,i also have the new sensor that is a gear tooth need's no magnet can sense a metal gear tooth , used one on my mill works great from 0 to 10,000 rpm they are used for gear sensing on industrial equipment. I had one other thought while i was sleeping (yes i am dreaming about the stupid thing!!) maybe more than one trigger say four and see what happens?
-
Timing no longer works in Mach so you can not use that, Index is the only one you can use.
Yes most functions work without the licence, limitations are
No Threading
100 (or maybe 150) lines of code limit in Turn
No Run From Here.
May be a few others but think thats about it.
Hood
-
Just been talking to Brian, he said to delete all your plugins and see if that helps, you could rename the plugin folder rather than delete if you wished. You will need to restart Mach after you have done that if it was open at the time.
Hood
-
Thanks Hood ,i just got back took longer than expected,my new sensor and break out board where here when i got home .
Ya, i do not want to delete all my plugins i have Mach Std Mill with tool setups tool changer locations and everything for the mill. So i will rename the folder and move it and delete everything .I to have wondered about mach std. mill causing a problem but since it had nothing to do with Lathe i could not see him messing around in there.
-
New development it works! i un-installed Mach and reinstalled added the Lisense and copied my xml. lathe profile into the folder , works first time.
Things that where not loaded back in, yet : Mach standard mill ,and shuttle pro ,i intend to reload these and see what happens to see one of them will recreate the problem .
I will report back soon with my finding's and hopefully the offending program or not ,who the heck know's.
-
The problem is Mach Standard Mill ,i re- in stalled it and the problem re-apeared some how it is not allowing the pulse signal from index to be read by the threading program.
-
So who does one report the problem to Mach or Mach dtd. mill and who fix's it?
-
Sorry for the spelling error,should have been Mach Standard Mill .
-
I will mention it to Brian but I suspect it would be Dave that will have to work out what the issue is.
Good news in a way I suppose and might help others in the future if they find they have the same problem.
Hood
-
Yes you are right about good and bad , i will have to dump mach std mill until it gets resolved . I appreciate all the help you and Rich put in on this and hopefully it will be resolved soon .
I don't think Dave has a lathe to even do any testing on ,but i would volunteer to be a Ginny pig to resolve it.
Thank's Dusty
-
Good for you Dusty on getting to the bottom of the problem.
Don't use Mach Standard Mill or follow that sites forum so thanks for posting on the problem.
RICH
-
Hi Guys,
Dusty contacted me about this topic on the CVI support forum forum - I thought I'd offer an update.
I suspect the root problem was with Mach 3.43.22 and PP driver 570 (which is what Dusty tells me he had running when he experienced this issue).
For MSM use, we recommend mach 3.43.37 (which also installs PP driver 601). I've settled on mach 3.43.37 as the MSM recommendation as it has patches for some serious safety issues that exist with the lockdown (3.43.22) rev.
(BTW, if you want mach 3.43.37, it is avail (via permission) from the CVI web site download area at www.CalyopsoVentures.com since it is not on the FTP page of Machsupport.com)
It looks as if the index pulse problem exists with the PP 570 level driver but is fixed in the 601 level driver.
I have some hints as to what the internal issue is in the 570 PP driver from correspondence with Art, and it involves changes in how plug-ins and the PP driver interact wrt to updating the RPM DRO (39) - I suspect the change Art made for that also fixed whatever this issue is in the 570 PP driver re threading sync (as there is only one input pin for the index pulse, the driver does both the RPM DRO update and Threading sync handling).
In any case, whatever the mach bug is, it seems not to exist with mach 3.43.37 and PP driver 601. I did not go back and verify the bug on 3.43.22 and driver 570 (as that would have required time that I didn't want to spend just to verify a mach bug).
FYI - to test this I set up a test system, connected to a PMDX125 breakout board on my test bench. It is fully configured for 3 axes and I'm using a signal generator to supply index pulses to the BoB - so I know it's getting nice square 50% duty cycle index pulses and I can vary the pulse speed to anything needed. Essentially this is a complete PP control system that just is not hooked to motor drivers (though the motor tunings etc are all configured).
I then set up 3 mach profiles, the only difference between the three are the profile names and the screen set the profile loads.
The first profile loads the mach 1024.set screen and gives stock mach mill mode.
The second profile loads the mach 1024.lset screen and gives stock mach lathe mode.
The third profile loads MSM.
I've used the test set up to run mach with 1024 mill, mach with 1024 lathe and mach with MSM, shifting from one to the other in all possible combinations. I can do that and I can run the threading test gcode (that Dusty said failed for him) every time without problem. I've also not had any trouble running any other gocde with any of the profiles - so the "proof by example that it's possible" is not dependent on the single gcode test case. I think that verifies that it is indeed possible to run MSM and mach lathe on the same PC without needing to uninstall MSM and reinstall Mach to make a lathe work.
So to set the record straight for those that may find this thread in the future, while using MSM may have illuminated the situation, the root issue is not an MSM bug, it is a mach bug. :D
Finally, from a post he made on the MSM forum, I have the impression that Dusty has this solved too - I've pinged him to verify that and am currently awaiting an ack that the mach update resolved this for him too.
Dave
-
Thanks for the update Dave, always good to have a thread end in a resolution as it will hopefully help others if they suffer from the same issue.
Hood
-
Will put some words in the Threading On The Lathe - Mach3 Turn write up as follows:
- Threading was first fixed in Version 3.042.032
- Threading was then updated in Version 3.042.033 to account for CPU's with a fast bus speed >2.1 GHz to eliminate a (-)
spindle speed in the DRO
- Version 3.043.37 recomended if using MSM and it is available (via permission) from the CVI web site download area
at www.CalyopsoVentures.com
Should the user have a threading problem using versions after 3.042.033 and greater please post on the Artsoft Forum.
RICH
-
Rich,
That is probably good enough, but if we wanted to be specific I think it's really a matter of the PP driver revision rather than the mach rev #: PP driver 601 works, 570 had the problem.
I'm unsure as to the mapping between PP driver versions and mach release versions (would be nice if we could look that up easily in the mach release notes :D)
In any case, mach revs are what users can download, so referring to the mach rev is prob ok.
For MSM, I happen to recommend 3.43.37 or later for reasons unrelated to this thread - I don't know that 3.43.37 was the first with PP driver 601.
Dave
Will put some words in the Threading On The Lathe - Mach3 Turn write up as follows:
- Threading was first fixed in Version 3.042.032
- Threading was then updated in Version 3.042.033 to account for CPU's with a fast bus speed >2.1 GHz to eliminate a (-)
spindle speed in the DRO
- Version 3.043.37 recomended if using MSM and it is available (via permission) from the CVI web site download area
at www.CalyopsoVentures.com
Should the user have a threading problem using versions after 3.042.033 and greater please post on the Artsoft Forum.
RICH
-
Dave,
When you say PP driver are you referring to the Mach3 Driver version one would find under the Windows Device Manager?
If that's the case,I have two different drivers for the same version of Mach installed on two different computers and can only say that
for Version 3.042.033 ....5.50.0.0 works.
RICH
-
Alas, I've found the driver info shown by the windows device manager useless for mach - I don't think that mach fills in the info fields that the device manager looks at...
The only way I know to learn the actual version number of the loaded PP driver is to run the Drivertest program - that shows parallel port driver version.
Attached is a pic of the ver # in drivertest.
I got in the habit of checking the PP driver version via drivertest when I realized that mach installs & uninstalls don't always update/revert the driver correctly. I've had cases where installing mach would leave me with the driver from a previous mach install - and the mismatch has caused problems.
Dave
Dave,
When you say PP driver are you referring to the Mach3 Driver version one would find under the Windows Device Manager?
If that's the case,I have two different drivers for the same version of Mach installed on two different computers and can only say that
for Version 3.042.033 ....5.50.0.0 works.
RICH
(http://)
-
Note that starting with Ver 3.042.034 the driver test was modified to show the revision of driver being used.
I'll add that to the the comments also in the write up.
RICH
-
Hi,
Before we go changing the Wiki, we might want to consider this additional data...
I took my test system, and installed mach 3.32.22 - I did not first uninstall Mach 3.43.37, I just ran the 3.43.22 installer and overwrote the 3.43.37 installation. I then ran drivertest and verified that the PP driver version had changed from 601 to 570.
The I repeated the MSM/1024 lathe tests - all combinations are still good.
I could run mach 1024 lathe and MSM mill in any order and there were no problems.
That tends to say that it is not driver level / mach release dependent as I last suspected.
I heard from Dusty, and he said that after changing from mach 3.43.22 up to 3.32.37 his system now works also (thogh he is experiencing some other issue that show up as a art code).
This makes me wonder is there is some other issue in Dusty's setup - not to pick on Dusty, just noting that the common thing at this point is that system's setup. It's exhibiting unwanted behavior while the same software is running fine on other systems.
I'm not sure what the root issue is/was, but my test show that it is not an MSM issue, and probably not a mach 3.43.22/3.43.37 issue as I've successfully run both of those combinations.... so maybe an wiki update is premature at this time?
Dave
-
OK, I think we can finally put this one to rest....
From an email from Dusty:
"I deleted the original install of XP home edition and replaced it, i had bought a couple XP. operating systems a few years ago so i used one of them , and this solved everything !
I can now run Mach version mach 3 v3.43.37 with MSM and Thread on the Lathe"
In all this interaction it seems no one had realized that the win version was Win XP HOME EDITION -
Of course, WIn XP home is not on the list of supported OS versions at machsupport...
Now wouldn't it have been nice if Mach checked the OS version when it starts so that it would not attempt to run on an unsupported OS version.... ?!? ::)
Dave
-
I have never heard Home edition doesnt work, is there more info on that?
Hood
-
I'm really just making an extrapolation... Given that the XP pro solved the issues, it could be either XP home vs XP pro, or it could be the clean up done by starting from an OS install.
If someone wants to do the experiments, I'd be semi-interested in hearing the results (but that'll never get to the top of my spare time list!).
Dave
I have never heard Home edition doesnt work, is there more info on that?
Hood
;D
-
I would imagine there are lots of people using Home edition so think it would have reared its ugly head before now if there was an issue. Maybe it is that no one has a lathe on Home and that the only issue is with threading, still find that unlikely. More likely as you say the clean up did the trick. If I had Home edition I would give it a go but afraid I dont.
Hood
-
I know that one of my friends uses XP Home and has no problems with threading.
Believe he is using V3.042.033 and I will confirm.
Not sure what Dusty's problem was. Files other than the driver needed to be changed when we were testing, so, it may be best
to find out from Brian specifics on what files in Mach ie; sys, driver, etc should be used with what version of Mach.
I had to always go into Windows and do a search for the sys and exe and delete those files and then copy in the new files for testing and run the driver test to install it.
The PC here would use the first file it found on the hard drive and ignore the replacement files. Same would happen on a reinstall.
Don't want to confuse the issue, but, it could be something other than MSM or only one file of a MACH version. Just don't know.
RICH
MODIFIED: BTW, no thread testing done here for any after Ver 3.042.034.
-
know that one of my friends uses XP Home and has no problems with threading.
Check with my friend and he is using XP pro.
RICH