Hi Tom
I think I have the axis defined correctly. In my Init program I have DefineCoordSystem(5,-1,4,6)

If I do a defineCS I get 5 -1 4 6

I tried adding the NotifyPlugins(10000) but I am not sure what I should have in my NotifyMach.C program, I just have the default one, but this did'nt help at all either. Should I change my NotifyMach.c to something else???


Regards
Andrew

--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Andrew,
>
> I looked through our Plugin code and I can't find a bug with regard to the A axis.
>
> You do have the A axis defined in the KFLOP Coordinate Systems don't you?  If you type DefineCS on the console what is displayed?
>
> What if we try adding a dummy NotifyPlugins(10000) before the Sleep(1000) in your VB Script?  If you don't already have a Notify KFLOP program create one that just prints the notification code or something (and use a code that you are not already using).  After the KFlop Notification program finishes it should tell Mach3 to re-sync to the hardware state.  See if it fixes the problem.
>
> Thanks
> TK
>
>
>
> ________________________________
> From: babinda01 <a_k@...>
> To: DynoMotion@yahoogroups.com
> Sent: Tue, March 2, 2010 4:47:31 PM
> Subject: [DynoMotion] Re: Mach3
>
>  
> Hi Tom
> I have done a bit of testing in regard to my homing problems, and I think your first point below is correct.
> On my very first home command after mach3 has been started, the machine homes correctly and moves to the A120 position ok.. But any other homes after that it just ignores the A120 movement command and just changes the DRO to read 120.000.
>
> And your point 2 is correct also, if I jog the machine to A180 and then run my homing script the machine actually goes to A60.
>
> If I change my homing script from A120 to X12. this works every time, so it is something to do with the rotary axis.
>
> I hope this helps, if you need me to try other tests please let me know.
>
> Regards
> Andrew
>
> --- In DynoMotion@yahoogro ups.com, Tom Kerekes <tk@> wrote:
> >
> > Hey Andrew,
> >
> > That is too strange...
> >
> > Where is A at before you start the Homing process?  I'm guessing that Mach somehow still thinks A is at 120 even though we homed.  So then if we say go to 120 it doesn't move.  Any jogging causes Mach3 to re-sync it's internal position.
> >
> > So to test that theory move to 180 before hand.  Then after homing if Mach still thinks we are at 180, then a move to 120 would cause a motion of -60.
> >
> > What happens if you do something similar with the X axis instead of A??
> >
> > When the DRO changes to 120 does it change gradually like there was a motion?
> >
> > What is the DRO before the G00 A120 ??
> >
> > What does the KMotion Axis Screen say the raw steps are before and after?
> >
> >
> > Sorry for all the questions and no answers :}
> >
> > TK
> >
> >
> >
> >
> > ____________ _________ _________ __
> > From: babinda01 <a_k@>
> > To: DynoMotion@yahoogro ups.com
> > Sent: Sat, February 27, 2010 8:30:13 PM
> > Subject: [DynoMotion] Re: Mach3
> >
> >  
> >
> >
> > Hi Tom
> > I am getting closer.
> > I now have my homing complete signal working ok - using Bit 48 instead of 160 worked.
> > Now for my next problem - it may be a bug in the plug-in (or else I am just stupid)
> > If I have my Homing script in Mach3 like this:
> >
> > Message ""
> > Code "G90 G54"
> > DoButton(24)
> > DoButton(22)
> > DoButton(25)
> > Message "Homing All Axis"
> > While IsActive(input2) ### Input2 is activated by bit 48 to
> > say homing is completed
> > Sleep(1000)
> > Wend
> >
> > Everything works perfectly...
> >
> > Then I changed it to:
> > Message ""
> > Code "G90 G54"
> > DoButton(24)
> > DoButton(22)
> > DoButton(25)
> > Message "Homing All Axis"
> > While IsActive(input2)
> > Sleep(1000)
> > Wend
> > Code "M899"
> >
> > With My M899 as:
> >
> > Code "G00 A120"
> > Message "Homing Completed"
> >
> > This homes as it did before and then just the DRO's in Mach change to A120 (the axis don't actually move).
> > I then tried deleting the code "M899" from my homing script, and then ran the script and then manually in MDI mode entered the M899, again it stayed in position and just the dro's move to A120. So then I ran the home script, manually jogged the A axis (just a bit) and then ran the M899 and everything worked as it should have.
> >
> > Any thoughts
> >
> > Andrew
> >
> > --- In DynoMotion@yahoogro ups.com, "babinda01" <a_k@> wrote:
> > >
> > > Hi Tom
> > > Yes, I am using the patched version. My estop, and a couple of other inputs are working fine and they are connected to the opto inputs of the kanalog.
> > > For testing all I have been doing is looking to see if the input2 led will come on, on the diagnosics page of Mach3 - but no go. As I said, I can see the bits change in the kmaotion software , but I cant see it working on the mach3 leds.
> > > I will try a couple of these other bits you mentioned. I was thinking that the plugin only recognised certain bits as inputs and certain ones as outputs.
> > >
> > > Andrew
> > >
> > > --- In DynoMotion@yahoogro ups.com, Tom Kerekes <tk@> wrote:
> > > >
> > > > Andrew,
> > > >
> > > > You need to use the patched plugin to access IO's > 128.  Are you using this?
> > > >
> > > > Otherwise you might use IO46 or 47 which are the KFLOP LEDs.
> > > >
> > > > Or 48 - 63 are hidden Virtual Bits originally designed to be used as flags.
> > > >
> > > > How do you know it isn't working?  What is the symptom?  I was thinking there might be a race condition where your routine starts checking for the bit to go low before it actually gets set high?
> > > >
> > > > TK
> > > >
> > > >
> > > >  
> > > >
> > > >
> > > >
> > > > ____________ _________ _________ __
> > > > From: babinda01 <a_k@>
> > > > To: DynoMotion@yahoogro ups.com
> > > > Sent: Sat, February 27, 2010 5:47:28 PM
> > > > Subject: [DynoMotion] Re: Mach3
> > > >
> > > >  
> > > >
> > > > Hi Tom
> > > > I am having a little trouble still with getting a "homing completed" signal coming back to mach3.
> > > > In my homing C program I have added a SetStateBit( 160,1) at the start of my homing routine and then a SetStateBit( 160,0) at the end. This works ok, I can see the bits change on the IO screen of KMotion, but for the life of mee I cant get these signals back to Mach3 Input #2 which I have set as port 2 pin 32.
> > > > I was trying 160 because all my opto inputs are used for other things bits 128-135 appear to be used so 160-167 are all I have free.
> > > > Any thought on what I could try - is there another bit I should be trying?
> > > >
> > > > Regards
> > > > Andrew
> > > >
> > >
> >
>

Hi Tom
I have thought I would just give you a look at my homing code to see if I am doing something wrong in there:

#include "KMotionDef.h"

main()
{
int flags = persist.UserData[5]; // Mach3 flags bit0=X, bit1=Y, Bit2=Z, etc...

printf("Mach3 Home Call, flags = %d\n",flags);
SetStateBit(48,1);
Delay_sec(.1);
SetStateBit(48,1);
if (flags & 1)
{
Jog(5,-50000); // start moving X axis

while (!ReadBit(136)) ; // wait for switch (input #15) to change
Jog(5,0); // StopMotion

while(!CheckDone(5)) ;

Jog(5,5000); // start moving
while (ReadBit(136)) ; // wait for switch (input #15) to change
Jog(5,0); // StopMotion

Jog(5,-1000);
while (!ReadBit(1));
Jog(5,0);

while(!CheckDone(5)) ;
Delay_sec(.25);

DisableAxis(5);
Zero(5);
EnableAxisDest(5,0.0);
}

if (flags & 4)
{


Jog(4,50000); // start moving Z axis

while (!ReadBit(137)) ; // wait for switch (input #15) to change
Jog(4,0); // StopMotion

while(!CheckDone(4)) ;

Jog(4,-5000); // start moving
while (ReadBit(137)) ; // wait for switch (input #15) to change
Jog(4,0); // StopMotion

Jog(4,1000);
while (!ReadBit(0));
Jog(4,0);

while(!CheckDone(4)) ;
Delay_sec(.25);

DisableAxis(4);
Zero(4);
EnableAxisDest(4,0.0);


}

if (flags & 8)
{


Jog(6,1000); // start moving A axis


while (!ReadBit(2)) ; // wait for switch (input #15) to change
Jog(6,0); // StopMotion


while(!CheckDone(6)) ;
Delay_sec(.25);

DisableAxis(6);
Zero(6);
EnableAxisDest(6,0.0);



}

SetStateBit(48,0);

}




Regards
Andrew

--- In DynoMotion@yahoogroups.com, "babinda01" <a_k@...> wrote:
>
> Hi Tom
> I think I have the axis defined correctly. In my Init program I have DefineCoordSystem(5,-1,4,6)
>
> If I do a defineCS I get 5 -1 4 6
>
> I tried adding the NotifyPlugins(10000) but I am not sure what I should have in my NotifyMach.C program, I just have the default one, but this did'nt help at all either. Should I change my NotifyMach.c to something else???
>
>
> Regards
> Andrew
>
>
> --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> >
> > Hi Andrew,
> >
> > I looked through our Plugin code and I can't find a bug with regard to the A axis.
> >
> > You do have the A axis defined in the KFLOP Coordinate Systems don't you?  If you type DefineCS on the console what is displayed?
> >
> > What if we try adding a dummy NotifyPlugins(10000) before the Sleep(1000) in your VB Script?  If you don't already have a Notify KFLOP program create one that just prints the notification code or something (and use a code that you are not already using).  After the KFlop Notification program finishes it should tell Mach3 to re-sync to the hardware state.  See if it fixes the problem.
> >
> > Thanks
> > TK
> >
> >
> >
> > ________________________________
> > From: babinda01 <a_k@>
> > To: DynoMotion@yahoogroups.com
> > Sent: Tue, March 2, 2010 4:47:31 PM
> > Subject: [DynoMotion] Re: Mach3
> >
> >  
> > Hi Tom
> > I have done a bit of testing in regard to my homing problems, and I think your first point below is correct.
> > On my very first home command after mach3 has been started, the machine homes correctly and moves to the A120 position ok.. But any other homes after that it just ignores the A120 movement command and just changes the DRO to read 120.000.
> >
> > And your point 2 is correct also, if I jog the machine to A180 and then run my homing script the machine actually goes to A60.
> >
> > If I change my homing script from A120 to X12. this works every time, so it is something to do with the rotary axis.
> >
> > I hope this helps, if you need me to try other tests please let me know.
> >
> > Regards
> > Andrew
> >
> > --- In DynoMotion@yahoogro ups.com, Tom Kerekes <tk@> wrote:
> > >
> > > Hey Andrew,
> > >
> > > That is too strange...
> > >
> > > Where is A at before you start the Homing process?  I'm guessing that Mach somehow still thinks A is at 120 even though we homed.  So then if we say go to 120 it doesn't move.  Any jogging causes Mach3 to re-sync it's internal position.
> > >
> > > So to test that theory move to 180 before hand.  Then after homing if Mach still thinks we are at 180, then a move to 120 would cause a motion of -60.
> > >
> > > What happens if you do something similar with the X axis instead of A??
> > >
> > > When the DRO changes to 120 does it change gradually like there was a motion?
> > >
> > > What is the DRO before the G00 A120 ??
> > >
> > > What does the KMotion Axis Screen say the raw steps are before and after?
> > >
> > >
> > > Sorry for all the questions and no answers :}
> > >
> > > TK
> > >
> > >
> > >
> > >
> > > ____________ _________ _________ __
> > > From: babinda01 <a_k@>
> > > To: DynoMotion@yahoogro ups.com
> > > Sent: Sat, February 27, 2010 8:30:13 PM
> > > Subject: [DynoMotion] Re: Mach3
> > >
> > >  
> > >
> > >
> > > Hi Tom
> > > I am getting closer.
> > > I now have my homing complete signal working ok - using Bit 48 instead of 160 worked.
> > > Now for my next problem - it may be a bug in the plug-in (or else I am just stupid)
> > > If I have my Homing script in Mach3 like this:
> > >
> > > Message ""
> > > Code "G90 G54"
> > > DoButton(24)
> > > DoButton(22)
> > > DoButton(25)
> > > Message "Homing All Axis"
> > > While IsActive(input2) ### Input2 is activated by bit 48 to
> > > say homing is completed
> > > Sleep(1000)
> > > Wend
> > >
> > > Everything works perfectly...
> > >
> > > Then I changed it to:
> > > Message ""
> > > Code "G90 G54"
> > > DoButton(24)
> > > DoButton(22)
> > > DoButton(25)
> > > Message "Homing All Axis"
> > > While IsActive(input2)
> > > Sleep(1000)
> > > Wend
> > > Code "M899"
> > >
> > > With My M899 as:
> > >
> > > Code "G00 A120"
> > > Message "Homing Completed"
> > >
> > > This homes as it did before and then just the DRO's in Mach change to A120 (the axis don't actually move).
> > > I then tried deleting the code "M899" from my homing script, and then ran the script and then manually in MDI mode entered the M899, again it stayed in position and just the dro's move to A120. So then I ran the home script, manually jogged the A axis (just a bit) and then ran the M899 and everything worked as it should have.
> > >
> > > Any thoughts
> > >
> > > Andrew
> > >
> > > --- In DynoMotion@yahoogro ups.com, "babinda01" <a_k@> wrote:
> > > >
> > > > Hi Tom
> > > > Yes, I am using the patched version. My estop, and a couple of other inputs are working fine and they are connected to the opto inputs of the kanalog.
> > > > For testing all I have been doing is looking to see if the input2 led will come on, on the diagnosics page of Mach3 - but no go. As I said, I can see the bits change in the kmaotion software , but I cant see it working on the mach3 leds.
> > > > I will try a couple of these other bits you mentioned. I was thinking that the plugin only recognised certain bits as inputs and certain ones as outputs.
> > > >
> > > > Andrew
> > > >
> > > > --- In DynoMotion@yahoogro ups.com, Tom Kerekes <tk@> wrote:
> > > > >
> > > > > Andrew,
> > > > >
> > > > > You need to use the patched plugin to access IO's > 128.  Are you using this?
> > > > >
> > > > > Otherwise you might use IO46 or 47 which are the KFLOP LEDs.
> > > > >
> > > > > Or 48 - 63 are hidden Virtual Bits originally designed to be used as flags.
> > > > >
> > > > > How do you know it isn't working?  What is the symptom?  I was thinking there might be a race condition where your routine starts checking for the bit to go low before it actually gets set high?
> > > > >
> > > > > TK
> > > > >
> > > > >
> > > > >  
> > > > >
> > > > >
> > > > >
> > > > > ____________ _________ _________ __
> > > > > From: babinda01 <a_k@>
> > > > > To: DynoMotion@yahoogro ups.com
> > > > > Sent: Sat, February 27, 2010 5:47:28 PM
> > > > > Subject: [DynoMotion] Re: Mach3
> > > > >
> > > > >  
> > > > >
> > > > > Hi Tom
> > > > > I am having a little trouble still with getting a "homing completed" signal coming back to mach3.
> > > > > In my homing C program I have added a SetStateBit( 160,1) at the start of my homing routine and then a SetStateBit( 160,0) at the end. This works ok, I can see the bits change on the IO screen of KMotion, but for the life of mee I cant get these signals back to Mach3 Input #2 which I have set as port 2 pin 32.
> > > > > I was trying 160 because all my opto inputs are used for other things bits 128-135 appear to be used so 160-167 are all I have free.
> > > > > Any thought on what I could try - is there another bit I should be trying?
> > > > >
> > > > > Regards
> > > > > Andrew
> > > > >
> > > >
> > >
> >
>

Hi Tom

I HAVE IT WORKING!!!!!!!!!

I don't really understand the how's and why it is working but it is.
After a refreshing ale, I realised what you were suggesting to do in regard to using the NotifyPlugin(10000) command, so in my notifyMach3.C program I added an if statement for the 10000 message, and then just did a simple printf("blah blah") statement. I then in my vb script in mach added the notifyplugin(10000) before my commanded A120 and then put a sleep(500) after the notifyplugin. This worked. I understand that after this notifyplugin kflop is sending a reset counters through to mach3 - I don't understand why my plain homing script doesn't.

Anyway for now it is working - I think it needs a little polishing though.

Regards
Andrew

Hi everybody
I recently installed a Kflop, with Mach3 and stepper motors.
I try to use in STEP_DIR_MODE, made the configuration and with KMotionCNC works fine.
Mach3 have a lot of step losses, in single step mode the steps are different in size, the acceleration once ok at the next step no ramp.
If I use LPT it's ok. With other computer the same.
What is the problem?