Hi Benny,

#1 "Stop" will issue an immediate hardware feedhold to KFlop so the motion will begin to stop immediately without a need to flush the motion buffer. "Reset" will also cause Mach3 to disable the amplifier enables so the motion will also begin to stop immediately. However because MS Windows is not real-time responsive, pushing any button on a Windows Screen is not 100% reliable in stopping motion. On most Windows systems the response to a button press is usually nearly instant 99% of the time. To get 100% reliability instant feedhold you must wire an external switch directly to KFlop that can initiate hardware feed hold.

#2 Yes issuing a hardware feedhold to KFlop either through an externally wired button or a custom Mach3 Screen button will cause KFlop to stop immediately along the current path. Releasing the feedhold will resume motion smoothly along the same path. However with hardware feedhold Mach3 is not really aware that the machine has stopped, so it is not possible to issue other Mach3 commands such as Jogs or changing offsets. You must first depress "Stop" in Mach3.

#3 This is a common misunderstanding. When defined as inputs the pins ARE floating. KFlop uses MOSFET inputs which have extremely high input resistance (> 10 Meg Ohms). That is why they change more or less randomly and possibly track the signals closest to them due to parasitic resistance and capacitance. This is normal. Inputs that are not connected to anything are not defined and may have any value high or low. If nothing is connected to the input then nothing should care what the state is. We used to apply weak pull down resistors to avoid this confusion but this caused problems using pins in "open collector" mode as the pin would never go fully "open".

I hope this helps

Regards

Group: DynoMotion	Message: 942	From: likleong	Date: 3/6/2011
Subject: Re: Buffer issue in mach3

Hi TK,

Thanks for your reply, for question 3, it is okay, I understanding, if we use the pin, we should not put it in floating state. However, for Q1 and Q2, I am a little but confuse, could you please elaborate more on following area?

1. there are 3 sec of motion buffer in Mach3, is it store in mach3 or downloaded to kflop hardware buffer?

2. If I press the "feedhold" button in Mach3, mach3 will stop to feed the instruction to kflop and the buffered motions will continue running until the buffer empty, right after I press the "start" button again in mach3, the motion will continue and there should no missed step or instruction, right?

3. If I press the "stop" button in mach3, the mach3 and kflop will stop immediatly, then how about the content in the buffer? Are they being erase?

4. You said there is a hardware feedhold in kflop, how can we make use of it? If we use this hardware feedhold, how can we keep mach3 and kflop syncronized (make mach3 and flop stop at the same time)

5. What is the difference if I press "stop" and "reset" in mach3?

6. From kflop point of view, is there any concept of "reset", "emergency, "stop" and "feed"? Or just received instruction from Mach3 ?

Best regards,
Benny

--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Benny,
>
> #1 "Stop" will issue an immediateÂ hardware feedhold to KFlop so the motion will
> begin to stop immediately without a need to flush the motion buffer.Â "Reset"
> will also cause Mach3 to disable the amplifier enables so the motion will also
> begin to stop immediately.Â However because MS Windows is not real-time
> responsive, pushing any button on a Windows Screen is not 100% reliable in
> stopping motion.Â On most Windows systems the response to a button press is
> usually nearly instant 99% of the time.Â To get 100% reliability instant
> feedhold you must wire an external switch directly to KFlop that can initiate
> hardware feed hold.
>
> #2 Yes issuing a hardware feedhold to KFlop either through an externally wired
> button or a custom Mach3 Screen button will cause KFlop to stop immediately
> along the current path.Â Releasing the feedhold will resume motion smoothly
> along the same path.Â However with hardware feedhold Mach3 is not really aware
> that the machine has stopped, so it is not possible to issue other Mach3
> commands such as Jogs or changing offsets.Â You must first depress "Stop"
> inÂ Mach3.
>
> #3 This is a common misunderstanding.Â When defined as inputs the pins ARE
> floating.Â KFlop uses MOSFET inputs which have extremely high input resistance
> (> 10 Meg Ohms).Â That is why they change more or less randomly andÂ possibly
> track the signals closest to them due to parasitic resistance and capacitance.Â
> This is normal.Â Â Inputs that are not connected to anything are not defined and
> may have any value high or low.Â If nothing is connected to the input then
> nothing should care what the state is.Â We used to applyÂ weak pull down
> resistors to avoid this confusion but this caused problems using pins in "open
> collector" mode as the pin would never go fully "open".
>
> I hope this helps
> Regards
> TKÂ
>
>
>
>
> ________________________________
> From: likleong <likleong@...>
> To: DynoMotion@yahoogroups.com
> Sent: Sun, March 6, 2011 5:59:27 AM
> Subject: [DynoMotion] Buffer issue in mach3
>
> Â
> Hi TK,
>
> I have the following questions regarding to mach3 and kflop:
>
> 1. There are 3 sec buffer in mach3 plugin, is it meaning that, there will be 3
> sec of motion command will be download to kflop's motion buffer? that means even
> mach3 stopped with "stop" or "reset" button, the kflop will keep running for 3
> sec until buffer empty, right?
>
>
> 2. In case of some emergency situation, in spit of hardware EMG stop, is there
> any way to stop the mach3 and kflop immediately but keep the contents in motion
> buffer so that it can resume within mache?
>
> 3. I found that, some IO pins (eg, IO42, IO43), if I define them as Input and
> keep them floating, normally, they will read as low, however, if I put One of
> them high, both of them will read high, until I ground the another one, is it
> normal? Is it not possible to put the input pin floating?
>
> Bes reagrds,
> Benny
>

Group: DynoMotion	Message: 943	From: Tom Kerekes	Date: 3/7/2011
Subject: Re: Buffer issue in mach3

Hi Benny,

Regarding:

#1 - some of both actually.

#2 - Yes the normal Mach3 feedhold works like that. However Mach3 doesn't really stop feeding instructions, rather it changed the instructions to a decelerated motion along the path and then a fixed location.

#3 - Yes, Stop flushes all the buffers.

#4 - Below is a simple program (ExternalFeedhold.c example) to watch an I/O bit and perform hardware feedhold when the input goes high. Mach3 naturally stays in sync because it doesn't even know it happened. From its perspective the motion is just taking a long time to execute and the buffer pipeline remains full.

#include

"KMotionDef.h"

main()

{

for (;;) // loop forever

{

WaitNextTimeSlice();

if (ReadBit(46)) // Watch an external input switch

{

StopCoordinatedMotion();

//feedhold

}

#5 - Basically Stop - stops the motion, Reset - disables al the axes and requires a re-initialization.

#6 - KFlop basically receives instructions from Mach3

Regards

Group: DynoMotion	Message: 944	From: likleong	Date: 3/7/2011
Subject: Re: Buffer issue in mach3

Hi TK,

Is it meaning that,

1. Only "feedhold" button in mach3 can stop the running code without lost step and motion instruction and then continue after the pause.

2. The hardware feedhold in kflop is actually monitor the input pin by c program and then call a routine to stop/disable all the axis,and all the contents in motion buffer will also be erase.

3. Both hardware feedhold and "stop" button in mach3 will immediately motion the motion, however the buffered instruction will be lost. If we use hardware feedhold, there is no way to notify mach3 when hardware feedhold enabled in kflop.

Best regards,
Benny

--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Benny,
>
> Regarding:
>
> #1 -Â some of both actually.
>
> #2 - Yes the normal Mach3 feedhold works like that.Â However Mach3 doesn't
> really stop feeding instructions, rather it changed the instructions to a
> decelerated motion along the path and then a fixed location.
>
> #3 - Yes, Stop flushes all the buffers.
>
> #4 - Below is a simple programÂ (ExternalFeedhold.c example)Â to watch an I/O bit
> and perform hardware feedhold when the input goes high.Â Mach3 naturally stays
> in sync because it doesn't even know it happened.Â From its perspective the
> motion is just taking a long time to execute and the buffer pipeline remains
> full.Â Â
> #include
> main()
> {"KMotionDef.h"Â Â Â for(;;) // loop foreverÂ Â Â {
> Â Â Â Â Â Â WaitNextTimeSlice();Â Â Â Â Â Â if(ReadBit(46)) // Watch an external input
> switchÂ Â Â Â Â Â {
> Â Â Â Â Â Â Â Â Â StopCoordinatedMotion(); //feedholdÂ Â Â Â Â Â }
> Â Â Â }
> }
>
>
> #5 - Basically Stop - stops the motion, Reset - disables al the axes and
> requires a re-initialization.
>
> #6 - KFlop basicallyÂ receives instructions from Mach3
>
> Regards
> TK
>
>
>
>
> ________________________________
> From: likleong <likleong@...>
> To: DynoMotion@yahoogroups.com
> Sent: Sun, March 6, 2011 11:41:08 PM
> Subject: [DynoMotion] Re: Buffer issue in mach3
>
> Â
> Hi TK,
>
> Thanks for your reply, for question 3, it is okay, I understanding, if we use
> the pin, we should not put it in floating state. However, for Q1 and Q2, I am a
> little but confuse, could you please elaborate more on following area?
>
> 1. there are 3 sec of motion buffer in Mach3, is it store in mach3 or downloaded
> to kflop hardware buffer?
>
> 2. If I press the "feedhold" button in Mach3, mach3 will stop to feed the
> instruction to kflop and the buffered motions will continue running until the
> buffer empty, right after I press the "start" button again in mach3, the motion
> will continue and there should no missed step or instruction, right?
>
> 3. If I press the "stop" button in mach3, the mach3 and kflop will stop
> immediatly, then how about the content in the buffer? Are they being erase?
>
>
> 4. You said there is a hardware feedhold in kflop, how can we make use of it? If
> we use this hardware feedhold, how can we keep mach3 and kflop syncronized (make
> mach3 and flop stop at the same time)
>
> 5. What is the difference if I press "stop" and "reset" in mach3?
>
> 6. From kflop point of view, is there any concept of "reset", "emergency, "stop"
> and "feed"? Or just received instruction from Mach3 ?
>
> Best regards,
> Benny
>
> --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> >
> > Hi Benny,
> >
> > #1 "Stop" will issue an immediateÃÂ hardware feedhold to KFlop so the motion
> >will
> >
> > begin to stop immediately without a need to flush the motion buffer.ÃÂ "Reset"
>
> > will also cause Mach3 to disable the amplifier enables so the motion will also
>
> > begin to stop immediately.ÃÂ However because MS Windows is not real-time
> > responsive, pushing any button on a Windows Screen is not 100% reliable in
> > stopping motion.ÃÂ On most Windows systems the response to a button press is
> > usually nearly instant 99% of the time.ÃÂ To get 100% reliability instant
> > feedhold you must wire an external switch directly to KFlop that can initiate
> > hardware feed hold.
> >
> > #2 Yes issuing a hardware feedhold to KFlop either through an externally wired
>
> > button or a custom Mach3 Screen button will cause KFlop to stop immediately
> > along the current path.ÃÂ Releasing the feedhold will resume motion smoothly
> > along the same path.ÃÂ However with hardware feedhold Mach3 is not really aware
> >
> > that the machine has stopped, so it is not possible to issue other Mach3
> > commands such as Jogs or changing offsets.ÃÂ You must first depress "Stop"
> > inÃÂ Mach3.
> >
> > #3 This is a common misunderstanding.ÃÂ When defined as inputs the pins ARE
> > floating.ÃÂ KFlop uses MOSFET inputs which have extremely high input resistance
> >
> > (> 10 Meg Ohms).ÃÂ That is why they change more or less randomly andÃÂ possibly
>
> > track the signals closest to them due to parasitic resistance and
> >capacitance.ÃÂ
> >
> > This is normal.ÃÂ ÃÂ Inputs that are not connected to anything are not defined
> >and
> >
> > may have any value high or low.ÃÂ If nothing is connected to the input then
> > nothing should care what the state is.ÃÂ We used to applyÃÂ weak pull down
> > resistors to avoid this confusion but this caused problems using pins in "open
>
> > collector" mode as the pin would never go fully "open".
> >
> > I hope this helps
> > Regards
> > TKÃÂ
> >
> >
> >
> >
> > ________________________________
> > From: likleong <likleong@>
> > To: DynoMotion@yahoogroups.com
> > Sent: Sun, March 6, 2011 5:59:27 AM
> > Subject: [DynoMotion] Buffer issue in mach3
> >
> > ÃÂ
> > Hi TK,
> >
> > I have the following questions regarding to mach3 and kflop:
> >
> > 1. There are 3 sec buffer in mach3 plugin, is it meaning that, there will be 3
>
> > sec of motion command will be download to kflop's motion buffer? that means
> >even
> >
> > mach3 stopped with "stop" or "reset" button, the kflop will keep running for 3
>
> > sec until buffer empty, right?
> >
> >
> > 2. In case of some emergency situation, in spit of hardware EMG stop, is there
>
> > any way to stop the mach3 and kflop immediately but keep the contents in motion
> >
> > buffer so that it can resume within mache?
> >
> > 3. I found that, some IO pins (eg, IO42, IO43), if I define them as Input and
> > keep them floating, normally, they will read as low, however, if I put One of
> > them high, both of them will read high, until I ground the another one, is it
> > normal? Is it not possible to put the input pin floating?
> >
> > Bes reagrds,
> > Benny
> >
>

Group: DynoMotion	Message: 945	From: Tom Kerekes	Date: 3/8/2011
Subject: Re: Buffer issue in mach3

Hi Benny,

#1 - No. It is also possible to resume instant hardware feedhold without lost steps.

#2 - No. The hardware does not disable the axes or erase the buffer. Basically KFlop slows down to a stop and stops taking motion from the buffer. The buffer remains full. To resume Kflop again starts taking motion from the buffer.

#3 - No. Buffered instructions will not be lost. Mach3 is always waiting for there to be space in the buffer. Whenever there becomes space available it fills the buffer. After KFlop stops consuming motion the buffer will remain full and Mach3 will wait.

The only problem with hardware feedhold is with issuing other commands while in feedhold. For example the tool breaks. You hit hardware feedhold and the machine instantly stops. But now you want to Jog the machine, change the tool, adjust a work offset, etc.., then resume. Before doing this you must push Stop in Mach3.

Regards

Group: DynoMotion	Message: 947	From: likleong	Date: 3/8/2011
Subject: Re: Buffer issue in mach3

Hi TK,

Okay, for kflop HW feedhold, there is no step lost. for mach2 feedhold, there is also no step lost, but need to waiting for couple of sec until buffer empty, and may be risk of slow respond from windows, right?

Then, how about the "stop" in mach3? you said the buffer contents will be erase in last reply. Is it related to kflop HW feedhold or just use another way to stop immedately?

Finally, if I ignore the respond issue from windows and just use the feedhold in mach3, is there any way to make the mach 3 issue a feedhold command to kflop immedately(StopCoordinatedMotion) without waiting the buffer to empty?

Best regards,
Benny.

--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Benny,
>
> #1 - No.Â It is also possible to resume instant hardware feedhold without lost
> steps.
>
> #2 - No.Â The hardware does not disable the axes or erase the buffer.Â Basically
> KFlop slows down to a stop and stops taking motion from the buffer.Â The buffer
> remains full.Â To resume Kflop again starts taking motion from the buffer.
>
> #3 -Â No.Â Buffered instructions will not be lost.Â Â Mach3 is always waiting for
> there to be space in the buffer.Â Whenever there becomes space available it
> fills the buffer.Â AfterÂ KFlop stopsÂ consuming motion the buffer will remain
> full and Mach3 will wait.
>
>
> The only problem with hardware feedhold is with issuing other commands whileÂ in
> feedhold.Â For example the tool breaks.Â You hit hardware feedhold and the
> machine instantly stops.Â But now you want to Jog the machine, change the
> tool,Â adjust a work offset, etc.., then resume.Â Before doing this you must push
> Stop in Mach3.Â
>
> Regards
> TK
>
>
>
> ________________________________
> From: likleong <likleong@...>
> To: DynoMotion@yahoogroups.com
> Sent: Mon, March 7, 2011 11:38:26 PM
> Subject: [DynoMotion] Re: Buffer issue in mach3
>
> Â
> Hi TK,
>
> Is it meaning that,
>
> 1. Only "feedhold" button in mach3 can stop the running code without lost step
> and motion instruction and then continue after the pause.
>
> 2. The hardware feedhold in kflop is actually monitor the input pin by c program
> and then call a routine to stop/disable all the axis,and all the contents in
> motion buffer will also be erase.
>
> 3. Both hardware feedhold and "stop" button in mach3 will immediately motion the
> motion, however the buffered instruction will be lost. If we use hardware
> feedhold, there is no way to notify mach3 when hardware feedhold enabled in
> kflop.
>
> Best regards,
> Benny
>
> --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> >
> > Hi Benny,
> >
> > Regarding:
> >
> > #1 -ÃÂ some of both actually.
> >
> > #2 - Yes the normal Mach3 feedhold works like that.ÃÂ However Mach3 doesn't
> > really stop feeding instructions, rather it changed the instructions to a
> > decelerated motion along the path and then a fixed location.
> >
> > #3 - Yes, Stop flushes all the buffers.
> >
> > #4 - Below is a simple programÃÂ (ExternalFeedhold.c example)ÃÂ to watch an I/O
> >bit
> >
> > and perform hardware feedhold when the input goes high.ÃÂ Mach3 naturally stays
> >
> > in sync because it doesn't even know it happened.ÃÂ From its perspective the
> > motion is just taking a long time to execute and the buffer pipeline remains
> > full.ÃÂ ÃÂ
> > #include
> > main()
> > {"KMotionDef.h"ÃÂ ÃÂ ÃÂ for(;;) // loop foreverÃÂ ÃÂ ÃÂ {
> > ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ WaitNextTimeSlice();ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ if(ReadBit(46)) // Watch an
> >external input
> >
> > switchÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ {
> > ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ StopCoordinatedMotion(); //feedholdÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ }
> > ÃÂ ÃÂ ÃÂ }
> > }
> >
> >
> > #5 - Basically Stop - stops the motion, Reset - disables al the axes and
> > requires a re-initialization.
> >
> > #6 - KFlop basicallyÃÂ receives instructions from Mach3
> >
> > Regards
> > TK
> >
> >
> >
> >
> > ________________________________
> > From: likleong <likleong@>
> > To: DynoMotion@yahoogroups.com
> > Sent: Sun, March 6, 2011 11:41:08 PM
> > Subject: [DynoMotion] Re: Buffer issue in mach3
> >
> > ÃÂ
> > Hi TK,
> >
> > Thanks for your reply, for question 3, it is okay, I understanding, if we use
> > the pin, we should not put it in floating state. However, for Q1 and Q2, I am a
> >
> > little but confuse, could you please elaborate more on following area?
> >
> > 1. there are 3 sec of motion buffer in Mach3, is it store in mach3 or
> >downloaded
> >
> > to kflop hardware buffer?
> >
> > 2. If I press the "feedhold" button in Mach3, mach3 will stop to feed the
> > instruction to kflop and the buffered motions will continue running until the
> > buffer empty, right after I press the "start" button again in mach3, the motion
> >
> > will continue and there should no missed step or instruction, right?
> >
> > 3. If I press the "stop" button in mach3, the mach3 and kflop will stop
> > immediatly, then how about the content in the buffer? Are they being erase?
> >
> >
> > 4. You said there is a hardware feedhold in kflop, how can we make use of it?
> >If
> >
> > we use this hardware feedhold, how can we keep mach3 and kflop syncronized
> >(make
> >
> > mach3 and flop stop at the same time)
> >
> > 5. What is the difference if I press "stop" and "reset" in mach3?
> >
> > 6. From kflop point of view, is there any concept of "reset", "emergency,
> >"stop"
> >
> > and "feed"? Or just received instruction from Mach3 ?
> >
> > Best regards,
> > Benny
> >
> > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > >
> > > Hi Benny,
> > >
> > > #1 "Stop" will issue an immediateÃâÃÂ hardware feedhold to KFlop so the motion
> >
> > >will
> > >
> > > begin to stop immediately without a need to flush the motion buffer.ÃâÃÂ
> >"Reset"
> >
> >
> > > will also cause Mach3 to disable the amplifier enables so the motion will
> >also
> >
> >
> > > begin to stop immediately.ÃâÃÂ However because MS Windows is not real-time
> > > responsive, pushing any button on a Windows Screen is not 100% reliable in
> > > stopping motion.ÃâÃÂ On most Windows systems the response to a button press
> >is
> >
> > > usually nearly instant 99% of the time.ÃâÃÂ To get 100% reliability instant
> > > feedhold you must wire an external switch directly to KFlop that can initiate
> >
> > > hardware feed hold.
> > >
> > > #2 Yes issuing a hardware feedhold to KFlop either through an externally
> >wired
> >
> >
> > > button or a custom Mach3 Screen button will cause KFlop to stop immediately
> > > along the current path.ÃâÃÂ Releasing the feedhold will resume motion
> >smoothly
> >
> > > along the same path.ÃâÃÂ However with hardware feedhold Mach3 is not really
> >aware
> >
> > >
> > > that the machine has stopped, so it is not possible to issue other Mach3
> > > commands such as Jogs or changing offsets.ÃâÃÂ You must first depress "Stop"
>
> > > inÃâÃÂ Mach3.
> > >
> > > #3 This is a common misunderstanding.ÃâÃÂ When defined as inputs the pins ARE
> >
> > > floating.ÃâÃÂ KFlop uses MOSFET inputs which have extremely high input
> >resistance
> >
> > >
> > > (> 10 Meg Ohms).ÃâÃÂ That is why they change more or less randomly
> >andÃâÃÂ possibly
> >
> >
> > > track the signals closest to them due to parasitic resistance and
> > >capacitance.ÃâÃÂ
> > >
> > > This is normal.ÃâÃÂ ÃâÃÂ Inputs that are not connected to anything are not
> >defined
> >
> > >and
> > >
> > > may have any value high or low.ÃâÃÂ If nothing is connected to the input then
> >
> > > nothing should care what the state is.ÃâÃÂ We used to applyÃâÃÂ weak pull down
> >
> > > resistors to avoid this confusion but this caused problems using pins in
> >"open
> >
> >
> > > collector" mode as the pin would never go fully "open".
> > >
> > > I hope this helps
> > > Regards
> > > TKÃâÃÂ
> > >
> > >
> > >
> > >
> > > ________________________________
> > > From: likleong <likleong@>
> > > To: DynoMotion@yahoogroups.com
> > > Sent: Sun, March 6, 2011 5:59:27 AM
> > > Subject: [DynoMotion] Buffer issue in mach3
> > >
> > > ÃâÃÂ
> > > Hi TK,
> > >
> > > I have the following questions regarding to mach3 and kflop:
> > >
> > > 1. There are 3 sec buffer in mach3 plugin, is it meaning that, there will be
> >3
> >
> >
> > > sec of motion command will be download to kflop's motion buffer? that means
> > >even
> > >
> > > mach3 stopped with "stop" or "reset" button, the kflop will keep running for
> >3
> >
> >
> > > sec until buffer empty, right?
> > >
> > >
> > > 2. In case of some emergency situation, in spit of hardware EMG stop, is
> >there
> >
> >
> > > any way to stop the mach3 and kflop immediately but keep the contents in
> >motion
> >
> > >
> > > buffer so that it can resume within mache?
> > >
> > > 3. I found that, some IO pins (eg, IO42, IO43), if I define them as Input and
> >
> > > keep them floating, normally, they will read as low, however, if I put One of
> >
> > > them high, both of them will read high, until I ground the another one, is it
> >
> > > normal? Is it not possible to put the input pin floating?
> > >
> > > Bes reagrds,
> > > Benny
> > >
> >
>

Group: DynoMotion	Message: 948	From: Tom Kerekes	Date: 3/9/2011
Subject: Re: Buffer issue in mach3

Hi Benny,

Regarding question #1 - Exactly Correct.

Regarding question #2 - I'm not sure exactly what you are asking - but I think the Mach3 manual states that "Stop" is likely to loose steps as it abruptly stops generating motion and flushes its buffers. In our plugin we attempt to issue a hardware feedhold, then after coming to a stop, flush our buffers, then re-sync the position with Mach3. So it should be instant and with no loss of steps, but not necessarily resume-able.

Regarding question #3 - Yes. To issue a hardware feedhold from a Mach3 screen you will need to modify a Mach3 screen to add or change the functionality of a button to issue a NotifyPlugins(XX) message. This will cause your Notify C program to execute in KFlop and pass it the message XX. (Message numbers 10000 - 10999 will be passed to KFLOP). You can then code your Notify C program to issue the StopCoordinatedMotion().

Regards

Group: DynoMotion	Message: 949	From: likleong	Date: 3/9/2011
Subject: Re: Buffer issue in mach3

Hi TK,

Do you have any idea how to modify the existing "feedhold" button in mach3, on top of the existing function, also make it issue a NotifyPlugins(XX) message to klop. On the other hand, how to handle the resume after the above feedhold? Thanks.

Best regards,
Benny

--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Benny,
>
> Regarding question #1 - Exactly Correct.
>
> Regarding question #2 -Â I'm not sure exactly what you are asking - but I think
> the Mach3 manual states that "Stop" is likely to loose steps as it abruptly
> stops generating motion and flushes its buffers.Â In our plugin we attempt to
> issue a hardware feedhold, then after coming to a stop, flush our buffers, then
> re-sync the position with Mach3.Â So it should be instant and with no loss of
> steps, but not necessarily resume-able.
>
> Regarding question #3 - Yes.Â To issue a hardware feedhold from a Mach3 screen
> you will need to modifyÂ a Mach3 screen to add or change the functionality of a
> button to issue a NotifyPlugins(XX) message.Â This will causeÂ your Notify C
> program to execute in KFlop and pass it the message XX.Â Â (Message numbers 10000
> - 10999 will be passed to KFLOP).Â You can then code your Notify C program to
> issue the StopCoordinatedMotion().
>
> Regards
> TKÂ
>
>
>
>
> ________________________________
> From: likleong <likleong@...>
> To: DynoMotion@yahoogroups.com
> Sent: Tue, March 8, 2011 11:02:52 PM
> Subject: [DynoMotion] Re: Buffer issue in mach3
>
> Â
> Hi TK,
>
> Okay, for kflop HW feedhold, there is no step lost. for mach2 feedhold, there is
> also no step lost, but need to waiting for couple of sec until buffer empty, and
> may be risk of slow respond from windows, right?
>
> Then, how about the "stop" in mach3? you said the buffer contents will be erase
> in last reply. Is it related to kflop HW feedhold or just use another way to
> stop immedately?
>
> Finally, if I ignore the respond issue from windows and just use the feedhold in
> mach3, is there any way to make the mach 3 issue a feedhold command to kflop
> immedately(StopCoordinatedMotion) without waiting the buffer to empty?
>
> Best regards,
> Benny.
>
> --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> >
> > Hi Benny,
> >
> > #1 - No.ÃÂ It is also possible to resume instant hardware feedhold without lost
> >
> > steps.
> >
> > #2 - No.ÃÂ The hardware does not disable the axes or erase the buffer.ÃÂ
> >Basically
> >
> > KFlop slows down to a stop and stops taking motion from the buffer.ÃÂ The
> >buffer
> >
> > remains full.ÃÂ To resume Kflop again starts taking motion from the buffer.
> >
> > #3 -ÃÂ No.ÃÂ Buffered instructions will not be lost.ÃÂ ÃÂ Mach3 is always waiting
> >for
> >
> > there to be space in the buffer.ÃÂ Whenever there becomes space available it
> > fills the buffer.ÃÂ AfterÃÂ KFlop stopsÃÂ consuming motion the buffer will remain
> >
> > full and Mach3 will wait.
> >
> >
> > The only problem with hardware feedhold is with issuing other commands
> >whileÃÂ in
> >
> > feedhold.ÃÂ For example the tool breaks.ÃÂ You hit hardware feedhold and the
> > machine instantly stops.ÃÂ But now you want to Jog the machine, change the
> > tool,ÃÂ adjust a work offset, etc.., then resume.ÃÂ Before doing this you must
> >push
> >
> > Stop in Mach3.ÃÂ
> >
> > Regards
> > TK
> >
> >
> >
> > ________________________________
> > From: likleong <likleong@>
> > To: DynoMotion@yahoogroups.com
> > Sent: Mon, March 7, 2011 11:38:26 PM
> > Subject: [DynoMotion] Re: Buffer issue in mach3
> >
> > ÃÂ
> > Hi TK,
> >
> > Is it meaning that,
> >
> > 1. Only "feedhold" button in mach3 can stop the running code without lost step
>
> > and motion instruction and then continue after the pause.
> >
> > 2. The hardware feedhold in kflop is actually monitor the input pin by c
> >program
> >
> > and then call a routine to stop/disable all the axis,and all the contents in
> > motion buffer will also be erase.
> >
> > 3. Both hardware feedhold and "stop" button in mach3 will immediately motion
> >the
> >
> > motion, however the buffered instruction will be lost. If we use hardware
> > feedhold, there is no way to notify mach3 when hardware feedhold enabled in
> > kflop.
> >
> > Best regards,
> > Benny
> >
> > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > >
> > > Hi Benny,
> > >
> > > Regarding:
> > >
> > > #1 -ÃâÃÂ some of both actually.
> > >
> > > #2 - Yes the normal Mach3 feedhold works like that.ÃâÃÂ However Mach3 doesn't
> >
> > > really stop feeding instructions, rather it changed the instructions to a
> > > decelerated motion along the path and then a fixed location.
> > >
> > > #3 - Yes, Stop flushes all the buffers.
> > >
> > > #4 - Below is a simple programÃâÃÂ (ExternalFeedhold.c example)ÃâÃÂ to watch an
> >I/O
> >
> > >bit
> > >
> > > and perform hardware feedhold when the input goes high.ÃâÃÂ Mach3 naturally
> >stays
> >
> > >
> > > in sync because it doesn't even know it happened.ÃâÃÂ From its perspective
> >the
> >
> > > motion is just taking a long time to execute and the buffer pipeline remains
>
> > > full.ÃâÃÂ ÃâÃÂ
> > > #include
> > > main()
> > > {"KMotionDef.h"ÃâÃÂ ÃâÃÂ ÃâÃÂ for(;;) // loop foreverÃâÃÂ ÃâÃÂ ÃâÃÂ {
> > > ÃâÃÂ ÃâÃÂ ÃâÃÂ ÃâÃÂ ÃâÃÂ ÃâÃÂ WaitNextTimeSlice();ÃâÃÂ ÃâÃÂ ÃâÃÂ ÃâÃÂ ÃâÃÂ ÃâÃÂ
> >if(ReadBit(46)) // Watch an
> >
> > >external input
> > >
> > > switchÃâÃÂ ÃâÃÂ ÃâÃÂ ÃâÃÂ ÃâÃÂ ÃâÃÂ {
> > > ÃâÃÂ ÃâÃÂ ÃâÃÂ ÃâÃÂ ÃâÃÂ ÃâÃÂ ÃâÃÂ ÃâÃÂ ÃâÃÂ StopCoordinatedMotion();
> >//feedholdÃâÃÂ ÃâÃÂ ÃâÃÂ ÃâÃÂ ÃâÃÂ ÃâÃÂ }
> > > ÃâÃÂ ÃâÃÂ ÃâÃÂ }
> > > }
> > >
> > >
> > > #5 - Basically Stop - stops the motion, Reset - disables al the axes and
> > > requires a re-initialization.
> > >
> > > #6 - KFlop basicallyÃâÃÂ receives instructions from Mach3
> > >
> > > Regards
> > > TK
> > >
> > >
> > >
> > >
> > > ________________________________
> > > From: likleong <likleong@>
> > > To: DynoMotion@yahoogroups.com
> > > Sent: Sun, March 6, 2011 11:41:08 PM
> > > Subject: [DynoMotion] Re: Buffer issue in mach3
> > >
> > > ÃâÃÂ
> > > Hi TK,
> > >
> > > Thanks for your reply, for question 3, it is okay, I understanding, if we use
> >
> > > the pin, we should not put it in floating state. However, for Q1 and Q2, I am
> >a
> >
> > >
> > > little but confuse, could you please elaborate more on following area?
> > >
> > > 1. there are 3 sec of motion buffer in Mach3, is it store in mach3 or
> > >downloaded
> > >
> > > to kflop hardware buffer?
> > >
> > > 2. If I press the "feedhold" button in Mach3, mach3 will stop to feed the
> > > instruction to kflop and the buffered motions will continue running until the
> >
> > > buffer empty, right after I press the "start" button again in mach3, the
> >motion
> >
> > >
> > > will continue and there should no missed step or instruction, right?
> > >
> > > 3. If I press the "stop" button in mach3, the mach3 and kflop will stop
> > > immediatly, then how about the content in the buffer? Are they being erase?
> > >
> > >
> > > 4. You said there is a hardware feedhold in kflop, how can we make use of it?
> >
> > >If
> > >
> > > we use this hardware feedhold, how can we keep mach3 and kflop syncronized
> > >(make
> > >
> > > mach3 and flop stop at the same time)
> > >
> > > 5. What is the difference if I press "stop" and "reset" in mach3?
> > >
> > > 6. From kflop point of view, is there any concept of "reset", "emergency,
> > >"stop"
> > >
> > > and "feed"? Or just received instruction from Mach3 ?
> > >
> > > Best regards,
> > > Benny
> > >
> > > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > >
> > > > Hi Benny,
> > > >
> > > > #1 "Stop" will issue an immediateÃÆ'Ã¢â¬Å¡ÃâÃÂ hardware feedhold to KFlop so the
> >motion
> >
> > >
> > > >will
> > > >
> > > > begin to stop immediately without a need to flush the motion
> >buffer.ÃÆ'Ã¢â¬Å¡ÃâÃÂ
> >
> > >"Reset"
> > >
> > >
> > > > will also cause Mach3 to disable the amplifier enables so the motion will
> > >also
> > >
> > >
> > > > begin to stop immediately.ÃÆ'Ã¢â¬Å¡ÃâÃÂ However because MS Windows is not
> >real-time
> >
> > > > responsive, pushing any button on a Windows Screen is not 100% reliable in
>
> > > > stopping motion.ÃÆ'Ã¢â¬Å¡ÃâÃÂ On most Windows systems the response to a button
> >press
> >
> > >is
> > >
> > > > usually nearly instant 99% of the time.ÃÆ'Ã¢â¬Å¡ÃâÃÂ To get 100% reliability
> >instant
> >
> > > > feedhold you must wire an external switch directly to KFlop that can
> >initiate
> >
> > >
> > > > hardware feed hold.
> > > >
> > > > #2 Yes issuing a hardware feedhold to KFlop either through an externally
> > >wired
> > >
> > >
> > > > button or a custom Mach3 Screen button will cause KFlop to stop immediately
> >
> > > > along the current path.ÃÆ'Ã¢â¬Å¡ÃâÃÂ Releasing the feedhold will resume motion
>
> > >smoothly
> > >
> > > > along the same path.ÃÆ'Ã¢â¬Å¡ÃâÃÂ However with hardware feedhold Mach3 is not
> >really
> >
> > >aware
> > >
> > > >
> > > > that the machine has stopped, so it is not possible to issue other Mach3
> > > > commands such as Jogs or changing offsets.ÃÆ'Ã¢â¬Å¡ÃâÃÂ You must first depress
> >"Stop"
> >
> >
> > > > inÃÆ'Ã¢â¬Å¡ÃâÃÂ Mach3.
> > > >
> > > > #3 This is a common misunderstanding.ÃÆ'Ã¢â¬Å¡ÃâÃÂ When defined as inputs the
> >pins ARE
> >
> > >
> > > > floating.ÃÆ'Ã¢â¬Å¡ÃâÃÂ KFlop uses MOSFET inputs which have extremely high input
> >
> > >resistance
> > >
> > > >
> > > > (> 10 Meg Ohms).ÃÆ'Ã¢â¬Å¡ÃâÃÂ That is why they change more or less randomly
> > >andÃÆ'Ã¢â¬Å¡ÃâÃÂ possibly
> > >
> > >
> > > > track the signals closest to them due to parasitic resistance and
> > > >capacitance.ÃÆ'Ã¢â¬Å¡ÃâÃÂ
> > > >
> > > > This is normal.ÃÆ'Ã¢â¬Å¡ÃâÃÂ ÃÆ'Ã¢â¬Å¡ÃâÃÂ Inputs that are not connected to anything
> >are not
> >
> > >defined
> > >
> > > >and
> > > >
> > > > may have any value high or low.ÃÆ'Ã¢â¬Å¡ÃâÃÂ If nothing is connected to the
> >input then
> >
> > >
> > > > nothing should care what the state is.ÃÆ'Ã¢â¬Å¡ÃâÃÂ We used to
> >applyÃÆ'Ã¢â¬Å¡ÃâÃÂ weak pull down
> >
> > >
> > > > resistors to avoid this confusion but this caused problems using pins in
> > >"open
> > >
> > >
> > > > collector" mode as the pin would never go fully "open".
> > > >
> > > > I hope this helps
> > > > Regards
> > > > TKÃÆ'Ã¢â¬Å¡ÃâÃÂ
> > > >
> > > >
> > > >
> > > >
> > > > ________________________________
> > > > From: likleong <likleong@>
> > > > To: DynoMotion@yahoogroups.com
> > > > Sent: Sun, March 6, 2011 5:59:27 AM
> > > > Subject: [DynoMotion] Buffer issue in mach3
> > > >
> > > > ÃÆ'Ã¢â¬Å¡ÃâÃÂ
> > > > Hi TK,
> > > >
> > > > I have the following questions regarding to mach3 and kflop:
> > > >
> > > > 1. There are 3 sec buffer in mach3 plugin, is it meaning that, there will
> >be
> >
> > >3
> > >
> > >
> > > > sec of motion command will be download to kflop's motion buffer? that means
> >
> > > >even
> > > >
> > > > mach3 stopped with "stop" or "reset" button, the kflop will keep running
> >for
> >
> > >3
> > >
> > >
> > > > sec until buffer empty, right?
> > > >
> > > >
> > > > 2. In case of some emergency situation, in spit of hardware EMG stop, is
> > >there
> > >
> > >
> > > > any way to stop the mach3 and kflop immediately but keep the contents in
> > >motion
> > >
> > > >
> > > > buffer so that it can resume within mache?
> > > >
> > > > 3. I found that, some IO pins (eg, IO42, IO43), if I define them as Input
> >and
> >
> > >
> > > > keep them floating, normally, they will read as low, however, if I put One
> >of
> >
> > >
> > > > them high, both of them will read high, until I ground the another one, is
> >it
> >
> > >
> > > > normal? Is it not possible to put the input pin floating?
> > > >
> > > > Bes reagrds,
> > > > Benny
> > > >
> > >
> >
>

Group: DynoMotion	Message: 950	From: Tom Kerekes	Date: 3/9/2011
Subject: Re: Buffer issue in mach3

Hi Benny,

Read this and see if you still have questions. Look for information on the Mach3 site on how to change the screens. We recommend the one written by Klaus Dietz.

http://www.dynomotion.com/Help/Mach3Plugin/Mach3Encoders.htm

If you change the Cycle Start button to do:

NotifyPlugins(11000)

The Cycle Start button should resume if KFlop is in the Hardware Feedhold state, otherwise it will do a normal Cycle Start.

Let me know if it isn't clear.

Regards

Group: DynoMotion	Message: 951	From: likleong	Date: 3/10/2011
Subject: Re: Buffer issue in mach3

Hi TK,

Thanks, I will try it out. I have another question regarding to the IO pins in kflop, can I define a general IO pin as output and in open collector at the same time? If I want to use the IO pin to drive a relay, any suggestion? Thanks.

Best regards,
Benny

--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Benny,
>
> Read this and see if you still have questions.Â Look for information on the
> Mach3 site on how to change the screens. Â We recommend the one written by Klaus
> Dietz.Â
>
>
> http://www.dynomotion.com/Help/Mach3Plugin/Mach3Encoders.htm
>
> If you change the Cycle Start button to do:
>
> NotifyPlugins(11000)Â
>
> The Cycle Start button should resume if KFlop is in the Hardware Feedhold state,
> otherwise it will do a normal Cycle Start.
>
> Let me know if it isn't clear.
>
> Regards
> TK
>
>
>
>
>
> ________________________________
> From: likleong <likleong@...>
> To: DynoMotion@yahoogroups.com
> Sent: Wed, March 9, 2011 5:31:06 PM
> Subject: [DynoMotion] Re: Buffer issue in mach3
>
> Â
> Hi TK,
>
> Do you have any idea how to modify the existing "feedhold" button in mach3, on
> top of the existing function, also make it issue a NotifyPlugins(XX) message to
> klop. On the other hand, how to handle the resume after the above feedhold?
> Thanks.
>
> Best regards,
> Benny
>
> --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> >
> > Hi Benny,
> >
> > Regarding question #1 - Exactly Correct.
> >
> > Regarding question #2 -ÃÂ I'm not sure exactly what you are asking - but I think
> >
> > the Mach3 manual states that "Stop" is likely to loose steps as it abruptly
> > stops generating motion and flushes its buffers.ÃÂ In our plugin we attempt to
>
> > issue a hardware feedhold, then after coming to a stop, flush our buffers, then
> >
> > re-sync the position with Mach3.ÃÂ So it should be instant and with no loss of
>
> > steps, but not necessarily resume-able.
> >
> > Regarding question #3 - Yes.ÃÂ To issue a hardware feedhold from a Mach3 screen
> >
> > you will need to modifyÃÂ a Mach3 screen to add or change the functionality of a
> >
> > button to issue a NotifyPlugins(XX) message.ÃÂ This will causeÃÂ your Notify C
> > program to execute in KFlop and pass it the message XX.ÃÂ ÃÂ (Message numbers
> >10000
> >
> > - 10999 will be passed to KFLOP).ÃÂ You can then code your Notify C program to
>
> > issue the StopCoordinatedMotion().
> >
> > Regards
> > TKÃÂ
> >
> >
> >
> >
> > ________________________________
> > From: likleong <likleong@>
> > To: DynoMotion@yahoogroups.com
> > Sent: Tue, March 8, 2011 11:02:52 PM
> > Subject: [DynoMotion] Re: Buffer issue in mach3
> >
> > ÃÂ
> > Hi TK,
> >
> > Okay, for kflop HW feedhold, there is no step lost. for mach2 feedhold, there
> >is
> >
> > also no step lost, but need to waiting for couple of sec until buffer empty,
> >and
> >
> > may be risk of slow respond from windows, right?
> >
> > Then, how about the "stop" in mach3? you said the buffer contents will be erase
> >
> > in last reply. Is it related to kflop HW feedhold or just use another way to
> > stop immedately?
> >
> > Finally, if I ignore the respond issue from windows and just use the feedhold
> >in
> >
> > mach3, is there any way to make the mach 3 issue a feedhold command to kflop
> > immedately(StopCoordinatedMotion) without waiting the buffer to empty?
> >
> > Best regards,
> > Benny.
> >
> > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > >
> > > Hi Benny,
> > >
> > > #1 - No.ÃâÃÂ It is also possible to resume instant hardware feedhold without
> >lost
> >
> > >
> > > steps.
> > >
> > > #2 - No.ÃâÃÂ The hardware does not disable the axes or erase the buffer.ÃâÃÂ
>
> > >Basically
> > >
> > > KFlop slows down to a stop and stops taking motion from the buffer.ÃâÃÂ The
> > >buffer
> > >
> > > remains full.ÃâÃÂ To resume Kflop again starts taking motion from the
> buffer.
> > >
> > > #3 -ÃâÃÂ No.ÃâÃÂ Buffered instructions will not be lost.ÃâÃÂ ÃâÃÂ Mach3 is always
> >waiting
> >
> > >for
> > >
> > > there to be space in the buffer.ÃâÃÂ Whenever there becomes space available
> >it
> >
> > > fills the buffer.ÃâÃÂ AfterÃâÃÂ KFlop stopsÃâÃÂ consuming motion the buffer
> >will remain
> >
> > >
> > > full and Mach3 will wait.
> > >
> > >
> > > The only problem with hardware feedhold is with issuing other commands
> > >whileÃâÃÂ in
> > >
> > > feedhold.ÃâÃÂ For example the tool breaks.ÃâÃÂ You hit hardware feedhold and
> >the
> >
> > > machine instantly stops.ÃâÃÂ But now you want to Jog the machine, change the
>
> > > tool,ÃâÃÂ adjust a work offset, etc.., then resume.ÃâÃÂ Before doing this you
> >must
> >
> > >push
> > >
> > > Stop in Mach3.ÃâÃÂ
> > >
> > > Regards
> > > TK
> > >
> > >
> > >
> > > ________________________________
> > > From: likleong <likleong@>
> > > To: DynoMotion@yahoogroups.com
> > > Sent: Mon, March 7, 2011 11:38:26 PM
> > > Subject: [DynoMotion] Re: Buffer issue in mach3
> > >
> > > ÃâÃÂ
> > > Hi TK,
> > >
> > > Is it meaning that,
> > >
> > > 1. Only "feedhold" button in mach3 can stop the running code without lost
> >step
> >
> >
> > > and motion instruction and then continue after the pause.
> > >
> > > 2. The hardware feedhold in kflop is actually monitor the input pin by c
> > >program
> > >
> > > and then call a routine to stop/disable all the axis,and all the contents in
>
> > > motion buffer will also be erase.
> > >
> > > 3. Both hardware feedhold and "stop" button in mach3 will immediately motion
>
> > >the
> > >
> > > motion, however the buffered instruction will be lost. If we use hardware
> > > feedhold, there is no way to notify mach3 when hardware feedhold enabled in
> > > kflop.
> > >
> > > Best regards,
> > > Benny
> > >
> > > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > >
> > > > Hi Benny,
> > > >
> > > > Regarding:
> > > >
> > > > #1 -ÃÆ'Ã¢â¬Å¡ÃâÃÂ some of both actually.
> > > >
> > > > #2 - Yes the normal Mach3 feedhold works like that.ÃÆ'Ã¢â¬Å¡ÃâÃÂ However Mach3
> >doesn't
> >
> > >
> > > > really stop feeding instructions, rather it changed the instructions to a
> > > > decelerated motion along the path and then a fixed location.
> > > >
> > > > #3 - Yes, Stop flushes all the buffers.
> > > >
> > > > #4 - Below is a simple programÃÆ'Ã¢â¬Å¡ÃâÃÂ (ExternalFeedhold.c
> >example)ÃÆ'Ã¢â¬Å¡ÃâÃÂ to watch an
> >
> > >I/O
> > >
> > > >bit
> > > >
> > > > and perform hardware feedhold when the input goes high.ÃÆ'Ã¢â¬Å¡ÃâÃÂ Mach3
> >naturally
> >
> > >stays
> > >
> > > >
> > > > in sync because it doesn't even know it happened.ÃÆ'Ã¢â¬Å¡ÃâÃÂ From its
> >perspective
> >
> > >the
> > >
> > > > motion is just taking a long time to execute and the buffer pipeline
> >remains
> >
> >
> > > > full.ÃÆ'Ã¢â¬Å¡ÃâÃÂ ÃÆ'Ã¢â¬Å¡ÃâÃÂ
> > > > #include
> > > > main()
> > > > {"KMotionDef.h"ÃÆ'Ã¢â¬Å¡ÃâÃÂ ÃÆ'Ã¢â¬Å¡ÃâÃÂ ÃÆ'Ã¢â¬Å¡ÃâÃÂ for(;;) // loop
> >foreverÃÆ'Ã¢â¬Å¡ÃâÃÂ ÃÆ'Ã¢â¬Å¡ÃâÃÂ ÃÆ'Ã¢â¬Å¡ÃâÃÂ {
> > > > ÃÆ'Ã¢â¬Å¡ÃâÃÂ ÃÆ'Ã¢â¬Å¡ÃâÃÂ ÃÆ'Ã¢â¬Å¡ÃâÃÂ ÃÆ'Ã¢â¬Å¡ÃâÃÂ ÃÆ'Ã¢â¬Å¡ÃâÃÂ ÃÆ'Ã¢â¬Å¡ÃâÃÂ
> >WaitNextTimeSlice();ÃÆ'Ã¢â¬Å¡ÃâÃÂ ÃÆ'Ã¢â¬Å¡ÃâÃÂ ÃÆ'Ã¢â¬Å¡ÃâÃÂ ÃÆ'Ã¢â¬Å¡ÃâÃÂ ÃÆ'Ã¢â¬Å¡ÃâÃÂ ÃÆ'Ã¢â¬Å¡ÃâÃÂ
> >
> > >if(ReadBit(46)) // Watch an
> > >
> > > >external input
> > > >
> > > > switchÃÆ'Ã¢â¬Å¡ÃâÃÂ ÃÆ'Ã¢â¬Å¡ÃâÃÂ ÃÆ'Ã¢â¬Å¡ÃâÃÂ ÃÆ'Ã¢â¬Å¡ÃâÃÂ ÃÆ'Ã¢â¬Å¡ÃâÃÂ ÃÆ'Ã¢â¬Å¡ÃâÃÂ {
> > > > ÃÆ'Ã¢â¬Å¡ÃâÃÂ ÃÆ'Ã¢â¬Å¡ÃâÃÂ ÃÆ'Ã¢â¬Å¡ÃâÃÂ ÃÆ'Ã¢â¬Å¡ÃâÃÂ ÃÆ'Ã¢â¬Å¡ÃâÃÂ ÃÆ'Ã¢â¬Å¡ÃâÃÂ
> >ÃÆ'Ã¢â¬Å¡ÃâÃÂ ÃÆ'Ã¢â¬Å¡ÃâÃÂ ÃÆ'Ã¢â¬Å¡ÃâÃÂ StopCoordinatedMotion();
> >
> > >//feedholdÃÆ'Ã¢â¬Å¡ÃâÃÂ ÃÆ'Ã¢â¬Å¡ÃâÃÂ ÃÆ'Ã¢â¬Å¡ÃâÃÂ ÃÆ'Ã¢â¬Å¡ÃâÃÂ ÃÆ'Ã¢â¬Å¡ÃâÃÂ ÃÆ'Ã¢â¬Å¡ÃâÃÂ }
> > > > ÃÆ'Ã¢â¬Å¡ÃâÃÂ ÃÆ'Ã¢â¬Å¡ÃâÃÂ ÃÆ'Ã¢â¬Å¡ÃâÃÂ }
> > > > }
> > > >
> > > >
> > > > #5 - Basically Stop - stops the motion, Reset - disables al the axes and
> > > > requires a re-initialization.
> > > >
> > > > #6 - KFlop basicallyÃÆ'Ã¢â¬Å¡ÃâÃÂ receives instructions from Mach3
> > > >
> > > > Regards
> > > > TK
> > > >
> > > >
> > > >
> > > >
> > > > ________________________________
> > > > From: likleong <likleong@>
> > > > To: DynoMotion@yahoogroups.com
> > > > Sent: Sun, March 6, 2011 11:41:08 PM
> > > > Subject: [DynoMotion] Re: Buffer issue in mach3
> > > >
> > > > ÃÆ'Ã¢â¬Å¡ÃâÃÂ
> > > > Hi TK,
> > > >
> > > > Thanks for your reply, for question 3, it is okay, I understanding, if we
> >use
> >
> > >
> > > > the pin, we should not put it in floating state. However, for Q1 and Q2, I
> >am
> >
> > >a
> > >
> > > >
> > > > little but confuse, could you please elaborate more on following area?
> > > >
> > > > 1. there are 3 sec of motion buffer in Mach3, is it store in mach3 or
> > > >downloaded
> > > >
> > > > to kflop hardware buffer?
> > > >
> > > > 2. If I press the "feedhold" button in Mach3, mach3 will stop to feed the
> > > > instruction to kflop and the buffered motions will continue running until
> >the
> >
> > >
> > > > buffer empty, right after I press the "start" button again in mach3, the
> > >motion
> > >
> > > >
> > > > will continue and there should no missed step or instruction, right?
> > > >
> > > > 3. If I press the "stop" button in mach3, the mach3 and kflop will stop
> > > > immediatly, then how about the content in the buffer? Are they being erase?
> >
> > > >
> > > >
> > > > 4. You said there is a hardware feedhold in kflop, how can we make use of
> >it?
> >
> > >
> > > >If
> > > >
> > > > we use this hardware feedhold, how can we keep mach3 and kflop syncronized
>
> > > >(make
> > > >
> > > > mach3 and flop stop at the same time)
> > > >
> > > > 5. What is the difference if I press "stop" and "reset" in mach3?
> > > >
> > > > 6. From kflop point of view, is there any concept of "reset", "emergency,
> > > >"stop"
> > > >
> > > > and "feed"? Or just received instruction from Mach3 ?
> > > >
> > > > Best regards,
> > > > Benny
> > > >
> > > > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > > >
> > > > > Hi Benny,
> > > > >
> > > > > #1 "Stop" will issue an immediateÃÆ'Ã'ÃÂ¢Ã¢âÂ¬ÃÂ¡ÃÆ'Ã¢â¬Å¡ÃâÃÂ hardware feedhold to
> >KFlop so the
> >
> > >motion
> > >
> > > >
> > > > >will
> > > > >
> > > > > begin to stop immediately without a need to flush the motion
> > >buffer.ÃÆ'Ã'ÃÂ¢Ã¢âÂ¬ÃÂ¡ÃÆ'Ã¢â¬Å¡ÃâÃÂ
> > >
> > > >"Reset"
> > > >
> > > >
> > > > > will also cause Mach3 to disable the amplifier enables so the motion will
> >
> > > >also
> > > >
> > > >
> > > > > begin to stop immediately.ÃÆ'Ã'ÃÂ¢Ã¢âÂ¬ÃÂ¡ÃÆ'Ã¢â¬Å¡ÃâÃÂ However because MS Windows
> >is not
> >
> > >real-time
> > >
> > > > > responsive, pushing any button on a Windows Screen is not 100% reliable
> >in
> >
> >
> > > > > stopping motion.ÃÆ'Ã'ÃÂ¢Ã¢âÂ¬ÃÂ¡ÃÆ'Ã¢â¬Å¡ÃâÃÂ On most Windows systems the response
> >to a button
> >
> > >press
> > >
> > > >is
> > > >
> > > > > usually nearly instant 99% of the time.ÃÆ'Ã'ÃÂ¢Ã¢âÂ¬ÃÂ¡ÃÆ'Ã¢â¬Å¡ÃâÃÂ To get 100%
> >reliability
> >
> > >instant
> > >
> > > > > feedhold you must wire an external switch directly to KFlop that can
> > >initiate
> > >
> > > >
> > > > > hardware feed hold.
> > > > >
> > > > > #2 Yes issuing a hardware feedhold to KFlop either through an externally
>
> > > >wired
> > > >
> > > >
> > > > > button or a custom Mach3 Screen button will cause KFlop to stop
> >immediately
> >
> > >
> > > > > along the current path.ÃÆ'Ã'ÃÂ¢Ã¢âÂ¬ÃÂ¡ÃÆ'Ã¢â¬Å¡ÃâÃÂ Releasing the feedhold will
> >resume motion
> >
> >
> > > >smoothly
> > > >
> > > > > along the same path.ÃÆ'Ã'ÃÂ¢Ã¢âÂ¬ÃÂ¡ÃÆ'Ã¢â¬Å¡ÃâÃÂ However with hardware feedhold
> >Mach3 is not
> >
> > >really
> > >
> > > >aware
> > > >
> > > > >
> > > > > that the machine has stopped, so it is not possible to issue other Mach3
>
> > > > > commands such as Jogs or changing offsets.ÃÆ'Ã'ÃÂ¢Ã¢âÂ¬ÃÂ¡ÃÆ'Ã¢â¬Å¡ÃâÃÂ You must
> >first depress
> >
> > >"Stop"
> > >
> > >
> > > > > inÃÆ'Ã'ÃÂ¢Ã¢âÂ¬ÃÂ¡ÃÆ'Ã¢â¬Å¡ÃâÃÂ Mach3.
> > > > >
> > > > > #3 This is a common misunderstanding.ÃÆ'Ã'ÃÂ¢Ã¢âÂ¬ÃÂ¡ÃÆ'Ã¢â¬Å¡ÃâÃÂ When defined as
> >inputs the
> >
> > >pins ARE
> > >
> > > >
> > > > > floating.ÃÆ'Ã'ÃÂ¢Ã¢âÂ¬ÃÂ¡ÃÆ'Ã¢â¬Å¡ÃâÃÂ KFlop uses MOSFET inputs which have
> >extremely high input
> >
> > >
> > > >resistance
> > > >
> > > > >
> > > > > (> 10 Meg Ohms).ÃÆ'Ã'ÃÂ¢Ã¢âÂ¬ÃÂ¡ÃÆ'Ã¢â¬Å¡ÃâÃÂ That is why they change more or less
> >randomly
> >
> > > >andÃÆ'Ã'ÃÂ¢Ã¢âÂ¬ÃÂ¡ÃÆ'Ã¢â¬Å¡ÃâÃÂ possibly
> > > >
> > > >
> > > > > track the signals closest to them due to parasitic resistance and
> > > > >capacitance.ÃÆ'Ã'ÃÂ¢Ã¢âÂ¬ÃÂ¡ÃÆ'Ã¢â¬Å¡ÃâÃÂ
> > > > >
> > > > > This is normal.ÃÆ'Ã'ÃÂ¢Ã¢âÂ¬ÃÂ¡ÃÆ'Ã¢â¬Å¡ÃâÃÂ ÃÆ'Ã'ÃÂ¢Ã¢âÂ¬ÃÂ¡ÃÆ'Ã¢â¬Å¡ÃâÃÂ Inputs that are
> >not connected to anything
> >
> > >are not
> > >
> > > >defined
> > > >
> > > > >and
> > > > >
> > > > > may have any value high or low.ÃÆ'Ã'ÃÂ¢Ã¢âÂ¬ÃÂ¡ÃÆ'Ã¢â¬Å¡ÃâÃÂ If nothing is
> >connected to the
> >
> > >input then
> > >
> > > >
> > > > > nothing should care what the state is.ÃÆ'Ã'ÃÂ¢Ã¢âÂ¬ÃÂ¡ÃÆ'Ã¢â¬Å¡ÃâÃÂ We used to
> > >applyÃÆ'Ã'ÃÂ¢Ã¢âÂ¬ÃÂ¡ÃÆ'Ã¢â¬Å¡ÃâÃÂ weak pull down
> > >
> > > >
> > > > > resistors to avoid this confusion but this caused problems using pins in
>
> > > >"open
> > > >
> > > >
> > > > > collector" mode as the pin would never go fully "open".
> > > > >
> > > > > I hope this helps
> > > > > Regards
> > > > > TKÃÆ'Ã'ÃÂ¢Ã¢âÂ¬ÃÂ¡ÃÆ'Ã¢â¬Å¡ÃâÃÂ
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > ________________________________
> > > > > From: likleong <likleong@>
> > > > > To: DynoMotion@yahoogroups.com
> > > > > Sent: Sun, March 6, 2011 5:59:27 AM
> > > > > Subject: [DynoMotion] Buffer issue in mach3
> > > > >
> > > > > ÃÆ'Ã'ÃÂ¢Ã¢âÂ¬ÃÂ¡ÃÆ'Ã¢â¬Å¡ÃâÃÂ
> > > > > Hi TK,
> > > > >
> > > > > I have the following questions regarding to mach3 and kflop:
> > > > >
> > > > > 1. There are 3 sec buffer in mach3 plugin, is it meaning that, there will
> >
> > >be
> > >
> > > >3
> > > >
> > > >
> > > > > sec of motion command will be download to kflop's motion buffer? that
> >means
> >
> > >
> > > > >even
> > > > >
> > > > > mach3 stopped with "stop" or "reset" button, the kflop will keep running
>
> > >for
> > >
> > > >3
> > > >
> > > >
> > > > > sec until buffer empty, right?
> > > > >
> > > > >
> > > > > 2. In case of some emergency situation, in spit of hardware EMG stop, is
>
> > > >there
> > > >
> > > >
> > > > > any way to stop the mach3 and kflop immediately but keep the contents in
>
> > > >motion
> > > >
> > > > >
> > > > > buffer so that it can resume within mache?
> > > > >
> > > > > 3. I found that, some IO pins (eg, IO42, IO43), if I define them as Input
> >
> > >and
> > >
> > > >
> > > > > keep them floating, normally, they will read as low, however, if I put
> >One
> >
> > >of
> > >
> > > >
> > > > > them high, both of them will read high, until I ground the another one,
> >is
> >
> > >it
> > >
> > > >
> > > > > normal? Is it not possible to put the input pin floating?
> > > > >
> > > > > Bes reagrds,
> > > > > Benny
> > > > >
> > > >
> > >
> >
>

Group: DynoMotion	Message: 952	From: Tom Kerekes	Date: 3/11/2011
Subject: Re: Buffer issue in mach3

Hi Benny,

I assume you are trying to drive something like the +5V input of a SSR (Solid State Relay) in open collector mode and NOT something like a 12V relay.

From a User Program to drive an I/O pin low set the Bit low and set it as an Output with:

ClearBit(XX);

SetBitDirection(XX,1);

To set an I/O pin "open" set the pin as an input.

SetBitDirection(XX,0);

As an input the Pin will be able to "float" up to ~3.9V because it is diode clamped to the 3.3V supply.

Regards

Group: DynoMotion	Message: 953	From: likleong	Date: 3/11/2011
Subject: Re: Buffer issue in mach3

Hi TK,

May be my question is not clear enough, I want to use the kflop IO pin as an output to drive a 3v relay directly, but I am afraid the current is not enough, because the relay need 50 mA to operate. Is there any way to solve this problem? How about set the IO pin in open collector mode?

Best regards,
Benny

--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Benny,
>
> I assume you are trying to drive something like the +5V input of a SSR (Solid
> State Relay) in open collector mode and NOT something like a 12V relay.
>
> From a User Program to drive an I/O pin low set the Bit low and set it as an
> Output with:
>
> ClearBit(XX);
> SetBitDirection(XX,1);
>
> To set an I/O pin "open" set the pin as an input.
>
> SetBitDirection(XX,0);
>
> As an input the Pin will be able to "float" up to ~3.9V because it is diode
> clamped to the 3.3V supply.
>
> Regards
> TK
>
>
>
>
>
> ________________________________
> From: likleong <likleong@...>
> To: DynoMotion@yahoogroups.com
> Sent: Thu, March 10, 2011 11:28:57 PM
> Subject: [DynoMotion] Re: Buffer issue in mach3
>
> �
> Hi TK,
>
> Thanks, I will try it out. I have another question regarding to the IO pins in
> kflop, can I define a general IO pin as output and in open collector at the same
> time? If I want to use the IO pin to drive a relay, any suggestion? Thanks.
>
> Best regards,
> Benny
>
> --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> >
> > Hi Benny,
> >
> > Read this and see if you still have questions.�� Look for information on the
> > Mach3 site on how to change the screens. ��We recommend the one written by
> >Klaus
> >
> > Dietz.��
> >
> >
> > http://www.dynomotion.com/Help/Mach3Plugin/Mach3Encoders.htm
> >
> > If you change the Cycle Start button to do:
> >
> > NotifyPlugins(11000)��
> >
> > The Cycle Start button should resume if KFlop is in the Hardware Feedhold
> >state,
> >
> > otherwise it will do a normal Cycle Start.
> >
> > Let me know if it isn't clear.
> >
> > Regards
> > TK
> >
> >
> >
> >
> >
> > ________________________________
> > From: likleong <likleong@>
> > To: DynoMotion@yahoogroups.com
> > Sent: Wed, March 9, 2011 5:31:06 PM
> > Subject: [DynoMotion] Re: Buffer issue in mach3
> >
> > ��
> > Hi TK,
> >
> > Do you have any idea how to modify the existing "feedhold" button in mach3, on
>
> > top of the existing function, also make it issue a NotifyPlugins(XX) message to
> >
> > klop. On the other hand, how to handle the resume after the above feedhold?
> > Thanks.
> >
> > Best regards,
> > Benny
> >
> > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > >
> > > Hi Benny,
> > >
> > > Regarding question #1 - Exactly Correct.
> > >
> > > Regarding question #2 -��斾寉啱'm not sure exactly what you are asking - but I
> >think
> >
> > >
> > > the Mach3 manual states that "Stop" is likely to loose steps as it abruptly
> > > stops generating motion and flushes its buffers.��斾寉 In our plugin we attempt
> >to
> >
> >
> > > issue a hardware feedhold, then after coming to a stop, flush our buffers,
> >then
> >
> > >
> > > re-sync the position with Mach3.��斾寉 So it should be instant and with no loss
> >of
> >
> >
> > > steps, but not necessarily resume-able.
> > >
> > > Regarding question #3 - Yes.��斾寉 To issue a hardware feedhold from a Mach3
> >screen
> >
> > >
> > > you will need to modify��斾寉乸 Mach3 screen to add or change the functionality
> >of a
> >
> > >
> > > button to issue a NotifyPlugins(XX) message.��斾寉 This will cause��斾寉∂our
> >Notify C
> >
> > > program to execute in KFlop and pass it the message XX.��斾寉ó钊�斾寉 (Message
> >numbers
> >
> > >10000
> > >
> > > - 10999 will be passed to KFLOP).��斾寉 You can then code your Notify C program
> >to
> >
> >
> > > issue the StopCoordinatedMotion().
> > >
> > > Regards
> > > TK��斾寉
> > >
> > >
> > >
> > >
> > > ________________________________
> > > From: likleong <likleong@>
> > > To: DynoMotion@yahoogroups.com
> > > Sent: Tue, March 8, 2011 11:02:52 PM
> > > Subject: [DynoMotion] Re: Buffer issue in mach3
> > >
> > > ��斾寉
> > > Hi TK,
> > >
> > > Okay, for kflop HW feedhold, there is no step lost. for mach2 feedhold, there
> >
> > >is
> > >
> > > also no step lost, but need to waiting for couple of sec until buffer empty,
>
> > >and
> > >
> > > may be risk of slow respond from windows, right?
> > >
> > > Then, how about the "stop" in mach3? you said the buffer contents will be
> >erase
> >
> > >
> > > in last reply. Is it related to kflop HW feedhold or just use another way to
>
> > > stop immedately?
> > >
> > > Finally, if I ignore the respond issue from windows and just use the feedhold
> >
> > >in
> > >
> > > mach3, is there any way to make the mach 3 issue a feedhold command to kflop
>
> > > immedately(StopCoordinatedMotion) without waiting the buffer to empty?
> > >
> > > Best regards,
> > > Benny.
> > >
> > > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > >
> > > > Hi Benny,
> > > >
> > > > #1 - No.��Ã¢�¬Å¡Ã钊�斾寉 It is also possible to resume instant hardware feedhold
> >without
> >
> > >lost
> > >
> > > >
> > > > steps.
> > > >
> > > > #2 - No.��Ã¢�¬Å¡Ã钊�斾寉 The hardware does not disable the axes or erase the
> >buffer.��Ã¢�¬Å¡Ã钊�斾寉
> >
> >
> > > >Basically
> > > >
> > > > KFlop slows down to a stop and stops taking motion from the
> >buffer.��Ã¢�¬Å¡Ã钊�斾寉 The
> >
> > > >buffer
> > > >
> > > > remains full.��Ã¢�¬Å¡Ã钊�斾寉 To resume Kflop again starts taking motion from the
>
> > buffer.
> > > >
> > > > #3 -��Ã¢�¬Å¡Ã钊�斾寉嘅o.��Ã¢�¬Å¡Ã钊�斾寉脷uffered instructions will not be
> >lost.��Ã¢�¬Å¡Ã钊�斾寉ó纱黒¢ââ\Å¡��斾寉嗰ach3 is always
> >
> > >waiting
> > >
> > > >for
> > > >
> > > > there to be space in the buffer.��Ã¢�¬Å¡Ã钊�斾寉 Whenever there becomes space
> >available
> >
> > >it
> > >
> > > > fills the buffer.��Ã¢�¬Å¡Ã钊�斾寉 After��Ã¢�¬Å¡Ã钊�斾寉嗱Flop stops��Ã¢�¬Å¡Ã钊�斾寉氲onsuming
> >motion the buffer
> >
> > >will remain
> > >
> > > >
> > > > full and Mach3 will wait.
> > > >
> > > >
> > > > The only problem with hardware feedhold is with issuing other commands
> > > >while��Ã¢�¬Å¡Ã钊�斾寉湶n
> > > >
> > > > feedhold.��Ã¢�¬Å¡Ã钊�斾寉 For example the tool breaks.��Ã¢�¬Å¡Ã钊�斾寉 You hit hardware
> >feedhold and
> >
> > >the
> > >
> > > > machine instantly stops.��Ã¢�¬Å¡Ã钊�斾寉 But now you want to Jog the machine,
> >change the
> >
> >
> > > > tool,��Ã¢�¬Å¡Ã钊�斾寉乸djust a work offset, etc.., then resume.��Ã¢�¬Å¡Ã钊�斾寉 Before
> >doing this you
> >
> > >must
> > >
> > > >push
> > > >
> > > > Stop in Mach3.��Ã¢�¬Å¡Ã钊�斾寉
> > > >
> > > > Regards
> > > > TK
> > > >
> > > >
> > > >
> > > > ________________________________
> > > > From: likleong <likleong@>
> > > > To: DynoMotion@yahoogroups.com
> > > > Sent: Mon, March 7, 2011 11:38:26 PM
> > > > Subject: [DynoMotion] Re: Buffer issue in mach3
> > > >
> > > > ��Ã¢�¬Å¡Ã钊�斾寉
> > > > Hi TK,
> > > >
> > > > Is it meaning that,
> > > >
> > > > 1. Only "feedhold" button in mach3 can stop the running code without lost
> > >step
> > >
> > >
> > > > and motion instruction and then continue after the pause.
> > > >
> > > > 2. The hardware feedhold in kflop is actually monitor the input pin by c
> > > >program
> > > >
> > > > and then call a routine to stop/disable all the axis,and all the contents
> >in
> >
> >
> > > > motion buffer will also be erase.
> > > >
> > > > 3. Both hardware feedhold and "stop" button in mach3 will immediately
> >motion
> >
> >
> > > >the
> > > >
> > > > motion, however the buffered instruction will be lost. If we use hardware
> > > > feedhold, there is no way to notify mach3 when hardware feedhold enabled in
> >
> > > > kflop.
> > > >
> > > > Best regards,
> > > > Benny
> > > >
> > > > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > > >
> > > > > Hi Benny,
> > > > >
> > > > > Regarding:
> > > > >
> > > > > #1 -��'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉澵ome of both actually.
> > > > >
> > > > > #2 - Yes the normal Mach3 feedhold works like that.��'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉
> >However Mach3
> >
> > >doesn't
> > >
> > > >
> > > > > really stop feeding instructions, rather it changed the instructions to a
> >
> > > > > decelerated motion along the path and then a fixed location.
> > > > >
> > > > > #3 - Yes, Stop flushes all the buffers.
> > > > >
> > > > > #4 - Below is a simple program��'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉 (ExternalFeedhold.c
> > >example)��'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉濳o watch an
> > >
> > > >I/O
> > > >
> > > > >bit
> > > > >
> > > > > and perform hardware feedhold when the input goes
> >high.��'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉 Mach3
> >
> > >naturally
> > >
> > > >stays
> > > >
> > > > >
> > > > > in sync because it doesn't even know it happened.��'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉
> >From its
> >
> > >perspective
> > >
> > > >the
> > > >
> > > > > motion is just taking a long time to execute and the buffer pipeline
> > >remains
> > >
> > >
> > > > > full.��'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉 ��'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉
> > > > > #include
> > > > > main()
> > > > >
> >{"KMotionDef.h"��'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉
> >for(;;) // loop
> >
> > >forever��'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉 {
> > > > > ��'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉
> >��'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉
> >
> >>WaitNextTimeSlice();��'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉
> >� ��'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉
> >
> > >
> > > >if(ReadBit(46)) // Watch an
> > > >
> > > > >external input
> > > > >
> > > > > switch��'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉
> >��'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉 {
> > > > > ��'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉
> >��'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉
> >
> > >��'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉
> >StopCoordinatedMotion();
> >
> > >
> > > >//feedhold��'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉
> >��'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉 }
> > > > > ��'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉 }
> > > > > }
> > > > >
> > > > >
> > > > > #5 - Basically Stop - stops the motion, Reset - disables al the axes and
>
> > > > > requires a re-initialization.
> > > > >
> > > > > #6 - KFlop basically��'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉澑eceives instructions from Mach3
> > > > >
> > > > > Regards
> > > > > TK
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > ________________________________
> > > > > From: likleong <likleong@>
> > > > > To: DynoMotion@yahoogroups.com
> > > > > Sent: Sun, March 6, 2011 11:41:08 PM
> > > > > Subject: [DynoMotion] Re: Buffer issue in mach3
> > > > >
> > > > > ��'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉
> > > > > Hi TK,
> > > > >
> > > > > Thanks for your reply, for question 3, it is okay, I understanding, if we
> >
> > >use
> > >
> > > >
> > > > > the pin, we should not put it in floating state. However, for Q1 and Q2,
> >I
> >
> > >am
> > >
> > > >a
> > > >
> > > > >
> > > > > little but confuse, could you please elaborate more on following area?
> > > > >
> > > > > 1. there are 3 sec of motion buffer in Mach3, is it store in mach3 or
> > > > >downloaded
> > > > >
> > > > > to kflop hardware buffer?
> > > > >
> > > > > 2. If I press the "feedhold" button in Mach3, mach3 will stop to feed the
> >
> > > > > instruction to kflop and the buffered motions will continue running until
> >
> > >the
> > >
> > > >
> > > > > buffer empty, right after I press the "start" button again in mach3, the
>
> > > >motion
> > > >
> > > > >
> > > > > will continue and there should no missed step or instruction, right?
> > > > >
> > > > > 3. If I press the "stop" button in mach3, the mach3 and kflop will stop
> > > > > immediatly, then how about the content in the buffer? Are they being
> >erase?
> >
> > >
> > > > >
> > > > >
> > > > > 4. You said there is a hardware feedhold in kflop, how can we make use of
> >
> > >it?
> > >
> > > >
> > > > >If
> > > > >
> > > > > we use this hardware feedhold, how can we keep mach3 and kflop
> >syncronized
> >
> >
> > > > >(make
> > > > >
> > > > > mach3 and flop stop at the same time)
> > > > >
> > > > > 5. What is the difference if I press "stop" and "reset" in mach3?
> > > > >
> > > > > 6. From kflop point of view, is there any concept of "reset", "emergency,
> >
> > > > >"stop"
> > > > >
> > > > > and "feed"? Or just received instruction from Mach3 ?
> > > > >
> > > > > Best regards,
> > > > > Benny
> > > > >
> > > > > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > > > >
> > > > > > Hi Benny,
> > > > > >
> > > > > > #1 "Stop" will issue an
> >immediate��'�� '��Â¢�Â¢Ã¢�¬Å¡Ã寉¬Ã钊�¦Ã寉¡Ã纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉温ardware feedhold to
> >
> > >KFlop so the
> > >
> > > >motion
> > > >
> > > > >
> > > > > >will
> > > > > >
> > > > > > begin to stop immediately without a need to flush the motion
> > > >buffer.��'�� '��Â¢�Â¢Ã¢�¬Å¡Ã寉¬Ã钊�¦Ã寉¡Ã纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉
> > > >
> > > > >"Reset"
> > > > >
> > > > >
> > > > > > will also cause Mach3 to disable the amplifier enables so the motion
> >will
> >
> > >
> > > > >also
> > > > >
> > > > >
> > > > > > begin to stop immediately.��'�� '��Â¢�Â¢Ã¢�¬Å¡Ã寉¬Ã钊�¦Ã寉¡Ã纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉
> >However because MS Windows
> >
> > >is not
> > >
> > > >real-time
> > > >
> > > > > > responsive, pushing any button on a Windows Screen is not 100% reliable
> >
> > >in
> > >
> > >
> > > > > > stopping motion.��'�� '��Â¢�Â¢Ã¢�¬Å¡Ã寉¬Ã钊�¦Ã寉¡Ã纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉 On most
> >Windows systems the response
> >
> > >to a button
> > >
> > > >press
> > > >
> > > > >is
> > > > >
> > > > > > usually nearly instant 99% of the
> >time.��'�� '��Â¢�Â¢Ã¢�¬Å¡Ã寉¬Ã钊�¦Ã寉¡Ã纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉 To get 100%
> >
> > >reliability
> > >
> > > >instant
> > > >
> > > > > > feedhold you must wire an external switch directly to KFlop that can
> > > >initiate
> > > >
> > > > >
> > > > > > hardware feed hold.
> > > > > >
> > > > > > #2 Yes issuing a hardware feedhold to KFlop either through an
> >externally
> >
> >
> > > > >wired
> > > > >
> > > > >
> > > > > > button or a custom Mach3 Screen button will cause KFlop to stop
> > >immediately
> > >
> > > >
> > > > > > along the current path.��'�� '��Â¢�Â¢Ã¢�¬Å¡Ã寉¬Ã钊�¦Ã寉¡Ã纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉
> >Releasing the feedhold will
> >
> > >resume motion
> > >
> > >
> > > > >smoothly
> > > > >
> > > > > > along the same path.��'�� '��Â¢�Â¢Ã¢�¬Å¡Ã寉¬Ã钊�¦Ã寉¡Ã纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉 However
> >with hardware feedhold
> >
> > >Mach3 is not
> > >
> > > >really
> > > >
> > > > >aware
> > > > >
> > > > > >
> > > > > > that the machine has stopped, so it is not possible to issue other
> >Mach3
> >
> >
> > > > > > commands such as Jogs or changing
> >offsets.��'�� '��Â¢�Â¢Ã¢�¬Å¡Ã寉¬Ã钊�¦Ã寉¡Ã纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉 You must
> >
> > >first depress
> > >
> > > >"Stop"
> > > >
> > > >
> > > > > > in��'�� '��Â¢�Â¢Ã¢�¬Å¡Ã寉¬Ã钊�¦Ã寉¡Ã纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉嗰ach3.
> > > > > >
> > > > > > #3 This is a common
> >misunderstanding.��'�� '��Â¢�Â¢Ã¢�¬Å¡Ã寉¬Ã钊�¦Ã寉¡Ã纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉 When defined as
> >
> > >inputs the
> > >
> > > >pins ARE
> > > >
> > > > >
> > > > > > floating.��'�� '��Â¢�Â¢Ã¢�¬Å¡Ã寉¬Ã钊�¦Ã寉¡Ã纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉 KFlop uses MOSFET
> >inputs which have
> >
> > >extremely high input
> > >
> > > >
> > > > >resistance
> > > > >
> > > > > >
> > > > > > (> 10 Meg Ohms).��'�� '��Â¢�Â¢Ã¢�¬Å¡Ã寉¬Ã钊�¦Ã寉¡Ã纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉 That is why
> >they change more or less
> >
> > >randomly
> > >
> > > > >and��'�� '��Â¢�Â¢Ã¢�¬Å¡Ã寉¬Ã钊�¦Ã寉¡Ã纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉漤ossibly
> > > > >
> > > > >
> > > > > > track the signals closest to them due to parasitic resistance and
> > > > > >capacitance.��'�� '��Â¢�Â¢Ã¢�¬Å¡Ã寉¬Ã钊�¦Ã寉¡Ã纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉
> > > > > >
> > > > > > This is
> >normal.��'�� '��Â¢�Â¢Ã¢�¬Å¡Ã寉¬Ã钊�¦Ã寉¡Ã纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�� '��Â¢�Â¢Ã¢�¬Å¡Ã寉¬Ã钊�¦Ã寉¡Ã纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉
> > Inputs that are
> >
> > >not connected to anything
> > >
> > > >are not
> > > >
> > > > >defined
> > > > >
> > > > > >and
> > > > > >
> > > > > > may have any value high or
> >low.��'�� '��Â¢�Â¢Ã¢�¬Å¡Ã寉¬Ã钊�¦Ã寉¡Ã纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉 If nothing is
> >
> > >connected to the
> > >
> > > >input then
> > > >
> > > > >
> > > > > > nothing should care what the state
> >is.��'�� '��Â¢�Â¢Ã¢�¬Å¡Ã寉¬Ã钊�¦Ã寉¡Ã纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉 We used to
> >
> > > >apply��'�� '��Â¢�Â¢Ã¢�¬Å¡Ã寉¬Ã钊�¦Ã寉¡Ã纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉烀eak pull down
> > > >
> > > > >
> > > > > > resistors to avoid this confusion but this caused problems using pins
> >in
> >
> >
> > > > >"open
> > > > >
> > > > >
> > > > > > collector" mode as the pin would never go fully "open".
> > > > > >
> > > > > > I hope this helps
> > > > > > Regards
> > > > > > TK��'�� '��Â¢�Â¢Ã¢�¬Å¡Ã寉¬Ã钊�¦Ã寉¡Ã纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > ________________________________
> > > > > > From: likleong <likleong@>
> > > > > > To: DynoMotion@yahoogroups.com
> > > > > > Sent: Sun, March 6, 2011 5:59:27 AM
> > > > > > Subject: [DynoMotion] Buffer issue in mach3
> > > > > >
> > > > > > ��'�� '��Â¢�Â¢Ã¢�¬Å¡Ã寉¬Ã钊�¦Ã寉¡Ã纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉
> > > > > > Hi TK,
> > > > > >
> > > > > > I have the following questions regarding to mach3 and kflop:
> > > > > >
> > > > > > 1. There are 3 sec buffer in mach3 plugin, is it meaning that, there
> >will
> >
> > >
> > > >be
> > > >
> > > > >3
> > > > >
> > > > >
> > > > > > sec of motion command will be download to kflop's motion buffer? that
> > >means
> > >
> > > >
> > > > > >even
> > > > > >
> > > > > > mach3 stopped with "stop" or "reset" button, the kflop will keep
> >running
> >
> >
> > > >for
> > > >
> > > > >3
> > > > >
> > > > >
> > > > > > sec until buffer empty, right?
> > > > > >
> > > > > >
> > > > > > 2. In case of some emergency situation, in spit of hardware EMG stop,
> >is
> >
> >
> > > > >there
> > > > >
> > > > >
> > > > > > any way to stop the mach3 and kflop immediately but keep the contents
> >in
> >
> >
> > > > >motion
> > > > >
> > > > > >
> > > > > > buffer so that it can resume within mache?
> > > > > >
> > > > > > 3. I found that, some IO pins (eg, IO42, IO43), if I define them as
> >Input
> >
> > >
> > > >and
> > > >
> > > > >
> > > > > > keep them floating, normally, they will read as low, however, if I put
>
> > >One
> > >
> > > >of
> > > >
> > > > >
> > > > > > them high, both of them will read high, until I ground the another one,
> >
> > >is
> > >
> > > >it
> > > >
> > > > >
> > > > > > normal? Is it not possible to put the input pin floating?
> > > > > >
> > > > > > Bes reagrds,
> > > > > > Benny
> > > > > >
> > > > >
> > > >
> > >
> >
>

Group: DynoMotion	Message: 954	From: Tom Kerekes	Date: 3/11/2011
Subject: Re: Buffer issue in mach3

Hi Benny,

The 3.3V outputs can only source/sink 16ma. You would need some form of a driver. Or use a 3V Solid state relay.

Regards

Group: DynoMotion	Message: 955	From: Lee Studley	Date: 3/11/2011
Subject: Re: Buffer issue in mach3

Hi Benny,
I admire tom his patience: His support of his product cannot include teaching of electronics or full design of your application.
You need to investigate this on you own. Otherwise he will go insane and none of us will get supported :-)

In this case you need to use the IO to drive and N channel transistor( BJT or Mosfet ) that will then be able to supply the current control of your
external device.

Please read:
http://www.scienceprog.com/interfacing-microcontrollers-to-external-devices/
http://www.diodes.com/_files/products_appnote_pdfs/zetex/an10.pdf
http://www.dnatechindia.com/index.php/Tutorials/8051-Tutorial/Relay-Interfacing.html

On 3/11/2011 10:16 AM, likleong wrote:

Hi TK,

May be my question is not clear enough, I want to use the kflop IO pin as an output to drive a 3v relay directly, but I am afraid the current is not enough, because the relay need 50 mA to operate. Is there any way to solve this problem? How about set the IO pin in open collector mode?

Best regards,
Benny

--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Benny,
>
> I assume you are trying to drive something like the +5V input of a SSR (Solid
> State Relay) in open collector mode and NOT something like a 12V relay.
>
> From a User Program to drive an I/O pin low set the Bit low and set it as an
> Output with:
>
> ClearBit(XX);
> SetBitDirection(XX,1);
>
> To set an I/O pin "open" set the pin as an input.
>
> SetBitDirection(XX,0);
>
> As an input the Pin will be able to "float" up to ~3.9V because it is diode
> clamped to the 3.3V supply.
>
> Regards
> TK
>
>
>
>
>
> ________________________________
> From: likleong <likleong@...>
> To: DynoMotion@yahoogroups.com
> Sent: Thu, March 10, 2011 11:28:57 PM
> Subject: [DynoMotion] Re: Buffer issue in mach3
>
> �
> Hi TK,
>
> Thanks, I will try it out. I have another question regarding to the IO pins in
> kflop, can I define a general IO pin as output and in open collector at the same
> time? If I want to use the IO pin to drive a relay, any suggestion? Thanks.
>
> Best regards,
> Benny
>
> --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> >
> > Hi Benny,
> >
> > Read this and see if you still have questions.�� Look for information on the
> > Mach3 site on how to change the screens. ��We recommend the one written by
> >Klaus
> >
> > Dietz.��
> >
> >
> > http://www.dynomotion.com/Help/Mach3Plugin/Mach3Encoders.htm
> >
> > If you change the Cycle Start button to do:
> >
> > NotifyPlugins(11000)��
> >
> > The Cycle Start button should resume if KFlop is in the Hardware Feedhold
> >state,
> >
> > otherwise it will do a normal Cycle Start.
> >
> > Let me know if it isn't clear.
> >
> > Regards
> > TK
> >
> >
> >
> >
> >
> > ________________________________
> > From: likleong <likleong@>
> > To: DynoMotion@yahoogroups.com
> > Sent: Wed, March 9, 2011 5:31:06 PM
> > Subject: [DynoMotion] Re: Buffer issue in mach3
> >
> > ��
> > Hi TK,
> >
> > Do you have any idea how to modify the existing "feedhold" button in mach3, on
>
> > top of the existing function, also make it issue a NotifyPlugins(XX) message to
> >
> > klop. On the other hand, how to handle the resume after the above feedhold?
> > Thanks.
> >
> > Best regards,
> > Benny
> >
> > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > >
> > > Hi Benny,
> > >
> > > Regarding question #1 - Exactly Correct.
> > >
> > > Regarding question #2 -��斾寉啱'm not sure exactly what you are asking - but I
> >think
> >
> > >
> > > the Mach3 manual states that "Stop" is likely to loose steps as it abruptly
> > > stops generating motion and flushes its buffers.��斾寉  In our plugin we attempt
> >to
> >
> >
> > > issue a hardware feedhold, then after coming to a stop, flush our buffers,
> >then
> >
> > >
> > > re-sync the position with Mach3.��斾寉  So it should be instant and with no loss
> >of
> >
> >
> > > steps, but not necessarily resume-able.
> > >
> > > Regarding question #3 - Yes.��斾寉  To issue a hardware feedhold from a Mach3
> >screen
> >
> > >
> > > you will need to modify��斾寉乸 Mach3 screen to add or change the functionality
> >of a
> >
> > >
> > > button to issue a NotifyPlugins(XX) message.��斾寉  This will cause��斾寉∂our
> >Notify C
> >
> > > program to execute in KFlop and pass it the message XX.��斾寉ó钊�斾寉  (Message
> >numbers
> >
> > >10000
> > >
> > > - 10999 will be passed to KFLOP).��斾寉  You can then code your Notify C program
> >to
> >
> >
> > > issue the StopCoordinatedMotion().
> > >
> > > Regards
> > > TK��斾寉 
> > >
> > >
> > >
> > >
> > > ________________________________
> > > From: likleong <likleong@>
> > > To: DynoMotion@yahoogroups.com
> > > Sent: Tue, March 8, 2011 11:02:52 PM
> > > Subject: [DynoMotion] Re: Buffer issue in mach3
> > >
> > > ��斾寉 
> > > Hi TK,
> > >
> > > Okay, for kflop HW feedhold, there is no step lost. for mach2 feedhold, there
> >
> > >is
> > >
> > > also no step lost, but need to waiting for couple of sec until buffer empty,
>
> > >and
> > >
> > > may be risk of slow respond from windows, right?
> > >
> > > Then, how about the "stop" in mach3? you said the buffer contents will be
> >erase
> >
> > >
> > > in last reply. Is it related to kflop HW feedhold or just use another way to
>
> > > stop immedately?
> > >
> > > Finally, if I ignore the respond issue from windows and just use the feedhold
> >
> > >in
> > >
> > > mach3, is there any way to make the mach 3 issue a feedhold command to kflop
>
> > > immedately(StopCoordinatedMotion) without waiting the buffer to empty?
> > >
> > > Best regards,
> > > Benny.
> > >
> > > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > >
> > > > Hi Benny,
> > > >
> > > > #1 - No.��Ã¢�¬Å¡Ã钊�斾寉  It is also possible to resume instant hardware feedhold
> >without
> >
> > >lost
> > >
> > > >
> > > > steps.
> > > >
> > > > #2 - No.��Ã¢�¬Å¡Ã钊�斾寉  The hardware does not disable the axes or erase the
> >buffer.��Ã¢�¬Å¡Ã钊�斾寉 
> >
> >
> > > >Basically
> > > >
> > > > KFlop slows down to a stop and stops taking motion from the
> >buffer.��Ã¢�¬Å¡Ã钊�斾寉  The
> >
> > > >buffer
> > > >
> > > > remains full.��Ã¢�¬Å¡Ã钊�斾寉  To resume Kflop again starts taking motion from the
>
> > buffer.
> > > >
> > > > #3 -��Ã¢�¬Å¡Ã钊�斾寉嘅o.��Ã¢�¬Å¡Ã钊�斾寉脷uffered instructions will not be
> >lost.��Ã¢�¬Å¡Ã钊�斾寉ó纱黒¢ââ\Å¡��斾寉嗰ach3 is always
> >
> > >waiting
> > >
> > > >for
> > > >
> > > > there to be space in the buffer.��Ã¢�¬Å¡Ã钊�斾寉  Whenever there becomes space
> >available
> >
> > >it
> > >
> > > > fills the buffer.��Ã¢�¬Å¡Ã钊�斾寉  After��Ã¢�¬Å¡Ã钊�斾寉嗱Flop stops��Ã¢�¬Å¡Ã钊�斾寉氲onsuming
> >motion the buffer
> >
> > >will remain
> > >
> > > >
> > > > full and Mach3 will wait.
> > > >
> > > >
> > > > The only problem with hardware feedhold is with issuing other commands
> > > >while��Ã¢�¬Å¡Ã钊�斾寉湶n
> > > >
> > > > feedhold.��Ã¢�¬Å¡Ã钊�斾寉  For example the tool breaks.��Ã¢�¬Å¡Ã钊�斾寉  You hit hardware
> >feedhold and
> >
> > >the
> > >
> > > > machine instantly stops.��Ã¢�¬Å¡Ã钊�斾寉  But now you want to Jog the machine,
> >change the
> >
> >
> > > > tool,��Ã¢�¬Å¡Ã钊�斾寉乸djust a work offset, etc.., then resume.��Ã¢�¬Å¡Ã钊�斾寉  Before
> >doing this you
> >
> > >must
> > >
> > > >push
> > > >
> > > > Stop in Mach3.��Ã¢�¬Å¡Ã钊�斾寉 
> > > >
> > > > Regards
> > > > TK
> > > >
> > > >
> > > >
> > > > ________________________________
> > > > From: likleong <likleong@>
> > > > To: DynoMotion@yahoogroups.com
> > > > Sent: Mon, March 7, 2011 11:38:26 PM
> > > > Subject: [DynoMotion] Re: Buffer issue in mach3
> > > >
> > > > ��Ã¢�¬Å¡Ã钊�斾寉 
> > > > Hi TK,
> > > >
> > > > Is it meaning that,
> > > >
> > > > 1. Only "feedhold" button in mach3 can stop the running code without lost
> > >step
> > >
> > >
> > > > and motion instruction and then continue after the pause.
> > > >
> > > > 2. The hardware feedhold in kflop is actually monitor the input pin by c
> > > >program
> > > >
> > > > and then call a routine to stop/disable all the axis,and all the contents
> >in
> >
> >
> > > > motion buffer will also be erase.
> > > >
> > > > 3. Both hardware feedhold and "stop" button in mach3 will immediately
> >motion
> >
> >
> > > >the
> > > >
> > > > motion, however the buffered instruction will be lost. If we use hardware
> > > > feedhold, there is no way to notify mach3 when hardware feedhold enabled in
> >
> > > > kflop.
> > > >
> > > > Best regards,
> > > > Benny
> > > >
> > > > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > > >
> > > > > Hi Benny,
> > > > >
> > > > > Regarding:
> > > > >
> > > > > #1 -���'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉澵ome of both actually.
> > > > >
> > > > > #2 - Yes the normal Mach3 feedhold works like that.���'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉 
> >However Mach3
> >
> > >doesn't
> > >
> > > >
> > > > > really stop feeding instructions, rather it changed the instructions to a
> >
> > > > > decelerated motion along the path and then a fixed location.
> > > > >
> > > > > #3 - Yes, Stop flushes all the buffers.
> > > > >
> > > > > #4 - Below is a simple program���'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉 (ExternalFeedhold.c
> > >example)���'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉濳o watch an
> > >
> > > >I/O
> > > >
> > > > >bit
> > > > >
> > > > > and perform hardware feedhold when the input goes
> >high.���'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉  Mach3
> >
> > >naturally
> > >
> > > >stays
> > > >
> > > > >
> > > > > in sync because it doesn't even know it happened.���'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉 
> >From its
> >
> > >perspective
> > >
> > > >the
> > > >
> > > > > motion is just taking a long time to execute and the buffer pipeline
> > >remains
> > >
> > >
> > > > > full.���'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉  ���'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉 
> > > > > #include
> > > > > main()
> > > > >
> >{"KMotionDef.h"���'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉 
> >for(;;) // loop
> >
> > >forever���'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉  {
> > > > > ���'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉 
> >���'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉 
> >
> >>WaitNextTimeSlice();���'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉 
> >� ���'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉 
> >
> > >
> > > >if(ReadBit(46)) // Watch an
> > > >
> > > > >external input
> > > > >
> > > > > switch���'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉 
> >���'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉  {
> > > > > ���'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉 
> >���'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉 
> >
> > >���'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉 
> >StopCoordinatedMotion();
> >
> > >
> > > >//feedhold���'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉 
> >���'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉  }
> > > > > ���'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉  }
> > > > > }
> > > > >
> > > > >
> > > > > #5 - Basically Stop - stops the motion, Reset - disables al the axes and
>
> > > > > requires a re-initialization.
> > > > >
> > > > > #6 - KFlop basically���'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉澑eceives instructions from Mach3
> > > > >
> > > > > Regards
> > > > > TK
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > ________________________________
> > > > > From: likleong <likleong@>
> > > > > To: DynoMotion@yahoogroups.com
> > > > > Sent: Sun, March 6, 2011 11:41:08 PM
> > > > > Subject: [DynoMotion] Re: Buffer issue in mach3
> > > > >
> > > > > ���'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉 
> > > > > Hi TK,
> > > > >
> > > > > Thanks for your reply, for question 3, it is okay, I understanding, if we
> >
> > >use
> > >
> > > >
> > > > > the pin, we should not put it in floating state. However, for Q1 and Q2,
> >I
> >
> > >am
> > >
> > > >a
> > > >
> > > > >
> > > > > little but confuse, could you please elaborate more on following area?
> > > > >
> > > > > 1. there are 3 sec of motion buffer in Mach3, is it store in mach3 or
> > > > >downloaded
> > > > >
> > > > > to kflop hardware buffer?
> > > > >
> > > > > 2. If I press the "feedhold" button in Mach3, mach3 will stop to feed the
> >
> > > > > instruction to kflop and the buffered motions will continue running until
> >
> > >the
> > >
> > > >
> > > > > buffer empty, right after I press the "start" button again in mach3, the
>
> > > >motion
> > > >
> > > > >
> > > > > will continue and there should no missed step or instruction, right?
> > > > >
> > > > > 3. If I press the "stop" button in mach3, the mach3 and kflop will stop
> > > > > immediatly, then how about the content in the buffer? Are they being
> >erase?
> >
> > >
> > > > >
> > > > >
> > > > > 4. You said there is a hardware feedhold in kflop, how can we make use of
> >
> > >it?
> > >
> > > >
> > > > >If
> > > > >
> > > > > we use this hardware feedhold, how can we keep mach3 and kflop
> >syncronized
> >
> >
> > > > >(make
> > > > >
> > > > > mach3 and flop stop at the same time)
> > > > >
> > > > > 5. What is the difference if I press "stop" and "reset" in mach3?
> > > > >
> > > > > 6. From kflop point of view, is there any concept of "reset", "emergency,
> >
> > > > >"stop"
> > > > >
> > > > > and "feed"? Or just received instruction from Mach3 ?
> > > > >
> > > > > Best regards,
> > > > > Benny
> > > > >
> > > > > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > > > >
> > > > > > Hi Benny,
> > > > > >
> > > > > > #1 "Stop" will issue an
> >immediate���'�� '���Â¢�Â¢Ã¢�¬Å¡Ã寉¬Ã钊�¦Ã寉¡Ã纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉温ardware feedhold to
> >
> > >KFlop so the
> > >
> > > >motion
> > > >
> > > > >
> > > > > >will
> > > > > >
> > > > > > begin to stop immediately without a need to flush the motion
> > > >buffer.���'�� '���Â¢�Â¢Ã¢�¬Å¡Ã寉¬Ã钊�¦Ã寉¡Ã纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉 
> > > >
> > > > >"Reset"
> > > > >
> > > > >
> > > > > > will also cause Mach3 to disable the amplifier enables so the motion
> >will
> >
> > >
> > > > >also
> > > > >
> > > > >
> > > > > > begin to stop immediately.���'�� '���Â¢�Â¢Ã¢�¬Å¡Ã寉¬Ã钊�¦Ã寉¡Ã纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉 
> >However because MS Windows
> >
> > >is not
> > >
> > > >real-time
> > > >
> > > > > > responsive, pushing any button on a Windows Screen is not 100% reliable
> >
> > >in
> > >
> > >
> > > > > > stopping motion.���'�� '���Â¢�Â¢Ã¢�¬Å¡Ã寉¬Ã钊�¦Ã寉¡Ã纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉  On most
> >Windows systems the response
> >
> > >to a button
> > >
> > > >press
> > > >
> > > > >is
> > > > >
> > > > > > usually nearly instant 99% of the
> >time.���'�� '���Â¢�Â¢Ã¢�¬Å¡Ã寉¬Ã钊�¦Ã寉¡Ã纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉  To get 100%
> >
> > >reliability
> > >
> > > >instant
> > > >
> > > > > > feedhold you must wire an external switch directly to KFlop that can
> > > >initiate
> > > >
> > > > >
> > > > > > hardware feed hold.
> > > > > >
> > > > > > #2 Yes issuing a hardware feedhold to KFlop either through an
> >externally
> >
> >
> > > > >wired
> > > > >
> > > > >
> > > > > > button or a custom Mach3 Screen button will cause KFlop to stop
> > >immediately
> > >
> > > >
> > > > > > along the current path.���'�� '���Â¢�Â¢Ã¢�¬Å¡Ã寉¬Ã钊�¦Ã寉¡Ã纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉 
> >Releasing the feedhold will
> >
> > >resume motion
> > >
> > >
> > > > >smoothly
> > > > >
> > > > > > along the same path.���'�� '���Â¢�Â¢Ã¢�¬Å¡Ã寉¬Ã钊�¦Ã寉¡Ã纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉  However
> >with hardware feedhold
> >
> > >Mach3 is not
> > >
> > > >really
> > > >
> > > > >aware
> > > > >
> > > > > >
> > > > > > that the machine has stopped, so it is not possible to issue other
> >Mach3
> >
> >
> > > > > > commands such as Jogs or changing
> >offsets.���'�� '���Â¢�Â¢Ã¢�¬Å¡Ã寉¬Ã钊�¦Ã寉¡Ã纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉  You must
> >
> > >first depress
> > >
> > > >"Stop"
> > > >
> > > >
> > > > > > in���'�� '���Â¢�Â¢Ã¢�¬Å¡Ã寉¬Ã钊�¦Ã寉¡Ã纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉嗰ach3.
> > > > > >
> > > > > > #3 This is a common
> >misunderstanding.���'�� '���Â¢�Â¢Ã¢�¬Å¡Ã寉¬Ã钊�¦Ã寉¡Ã纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉  When defined as
> >
> > >inputs the
> > >
> > > >pins ARE
> > > >
> > > > >
> > > > > > floating.���'�� '���Â¢�Â¢Ã¢�¬Å¡Ã寉¬Ã钊�¦Ã寉¡Ã纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉  KFlop uses MOSFET
> >inputs which have
> >
> > >extremely high input
> > >
> > > >
> > > > >resistance
> > > > >
> > > > > >
> > > > > > (> 10 Meg Ohms).���'�� '���Â¢�Â¢Ã¢�¬Å¡Ã寉¬Ã钊�¦Ã寉¡Ã纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉  That is why
> >they change more or less
> >
> > >randomly
> > >
> > > > >and���'�� '���Â¢�Â¢Ã¢�¬Å¡Ã寉¬Ã钊�¦Ã寉¡Ã纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉漤ossibly
> > > > >
> > > > >
> > > > > > track the signals closest to them due to parasitic resistance and
> > > > > >capacitance.���'�� '���Â¢�Â¢Ã¢�¬Å¡Ã寉¬Ã钊�¦Ã寉¡Ã纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉 
> > > > > >
> > > > > > This is
> >normal.���'�� '���Â¢�Â¢Ã¢�¬Å¡Ã寉¬Ã钊�¦Ã寉¡Ã纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉ó纱黒�'�� '���Â¢�Â¢Ã¢�¬Å¡Ã寉¬Ã钊�¦Ã寉¡Ã纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã ;纱黒¢ââ\Å¡��斾寉 
> > Inputs that are
> >
> > >not connected to anything
> > >
> > > >are not
> > > >
> > > > >defined
> > > > >
> > > > > >and
> > > > > >
> > > > > > may have any value high or
> >low.���'�� '���Â¢�Â¢Ã¢�¬Å¡Ã寉¬Ã钊�¦Ã寉¡Ã纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉  If nothing is
> >
> > >connected to the
> > >
> > > >input then
> > > >
> > > > >
> > > > > > nothing should care what the state
> >is.���'�� '���Â¢�Â¢Ã¢�¬Å¡Ã寉¬Ã钊�¦Ã寉¡Ã纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉  We used to
> >
> > > >apply���'�� '���Â¢�Â¢Ã¢�¬Å¡Ã寉¬Ã钊�¦Ã寉¡Ã纱黒�'�Â¢Ã¢�斵¬Ã埘¡Ã纱黒¢ââ\Å¡��斾寉烀eak pull down
> > > >
> > > > >
> > > > > > resistors to avoid this confusion but this caused problems using pins
> >in
> >
> >
> > > > >"open
> > > > >
> > > > >
> > > > > > collector" mode as the pin

(Message over 64 KB, truncated)

Group: DynoMotion	Message: 956	From: Tom Kerekes	Date: 3/11/2011
Subject: Re: Buffer issue in mach3

Hi Lee,

Those are great links. Thanks.

(I have no problem trying to answer questions on the group as other users probably have the same issues)

Group: DynoMotion	Message: 957	From: Lee Studley	Date: 3/11/2011
Subject: Re: Buffer issue in mach3

Hi Tom and Benny,
That's true. I was surprised at the lengths needed to find good examples as I searched today. I have books
from way back when I learned that stuff. Steve Ciarcia's books on building you own Z80
was classic! Had good thermal managment primer inside also.
WOW just found it in downloadable form( dated but highly recommended!!!):
http://www.scribd.com/doc/13388965/Build-Your-Own-Z80-Computer

Benny,
Look especially at figure10 page6 of this appnote. It's simple and will be perfect for
most reasonable open collector drive requirements.

http://www.diodes.com/_files/products_appnote_pdfs/zetex/an10.pdf

On 3/11/2011 12:08 PM, Tom Kerekes wrote:

Hi Lee,

Those are great links. Thanks.

(I have no problem trying to answer questions on the group as other users probably have the same issues)

TK

Group: DynoMotion	Message: 939	From: likleong	Date: 3/6/2011
Subject: Buffer issue in mach3

Group: DynoMotion	Message: 941	From: Tom Kerekes	Date: 3/6/2011
Subject: Re: Buffer issue in mach3