throbber
FROM: M~VlcClung, 76336,3110
`TO: Dave Brown, 72103,2235
`DA’rE: 11111194 7:47 PM
`
`Re: WOSA/XMC, Draft 2, ICounter
`
`Hello Dave,
`
`I would like to go over the ICounter interface in this correspondence.
`
`ICounter Interface .................. Only the AT6400-AUX1 (bus-based indexer) allows the user to have access to hardware
`counters. Each of the four encoder inputs can be configured as an individual up/down counter (see CN-IE command). A
`ResetCounter0 method needs to be added to the ICounter interface (see CNTR command).
`
`The current counter value for each counter can be obtained via the TCNT command. The counter value cannot be obtained via
`the "fast status" registers.
`
`The AT6400-AUX1 product also has the ability to interrupt the PC when a count value has exceeded a maximum count, or when
`a count value falls below a minimum count (see INTHW and CNTINT commands). Perhaps you would include an
`Enablelnterrupt0 method.
`
`Conclusion ........... After reviewing the ITimer and ICounter interfaces, it just occurred to me that you might want to provide
`timer and counter services within the Motion Component itself. For example, a user might want access to the high-resolution
`timer in WIN32. Or the user might want to count "motion complete on axis n" interrupts (see INTHW command). Is this what you
`had in mind with Attachlnterrupt0?
`
`Correction In the discussion of the ITimer interface the current timer value should be obtained from the T’rIM
`command rather than the [TIM] variable.
`
`RGB00051666
`
`EXHIBIT
`
`W~VW.DEPOBOOK.COM

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket