|
Post by black8898 on May 14, 2012 4:46:24 GMT -8
Hi Dave Have just slaved my "A" axis to the "X" axis tuned motors etc and both are running perfectly the problem arises when homing the the "X" axis gantry moves to the home position backs off slightly and then stops as it should but since slaving the "A" and "X" axis together this procedure does the homing twice and then stops at the home position , now if I go to the General config page and tick the box marked "Home Slave Axis With Master" then machine homes perfectly but now this is the problem it stops everything from working so I have to un-tick this box in order to get everything working again , this is more than likely a Mach problem but not sure and to be honest you will give me an answer quicker than if I go onto the Mach forum. I am running as follows, Windows 7(32 bit) MSM (Lockdown version) Mach .37 and have tried .62 but makes no difference to the problem. Thanks Alan
|
|
|
Post by DaveCVI on May 14, 2012 7:33:23 GMT -8
Hi, I'm traveling today & so I'll respond with more info when I'm at a real keyboard (phone is to hard to type anything with other than short msg).
Probably a mach issue, but I'll check code when I get back to the office.
Dave
|
|
|
Post by DaveCVI on May 14, 2012 16:58:37 GMT -8
Hi, I looked and I'm thinking this is a mach bug of some type. The MSM ref all button does the same code that the 1024 set uses which (for mill mode) is
' code to send all 4 axes home to reference DoOEMButton( HomeRefZOEMBtn ) DoOEMButton( HomeRefYOEMBtn ) DoOEMButton( HomeRefXOEMBtn ) DoOEMButton( HomeRefAOEMBtn )
Each individual axis ref button just does the single OEM button for it's axis.
So, I can't see any obvious way that MSM would be effectign how slaved axes are handled.
I'd verify that the same action happens with 1024 loaded (as that is the test case that Brian will ask about) and then report/ask on the yahoo mach list (as Brian reads that regularly, but does not tend to read the machsupport web page forums).
Dave
|
|