`TO: Dave Brown, 72103,2235
`DATE: 11/10/94 10:29 PM
`
`Re:. WOSA/XMC, Draft 2, ITimer
`
`Hello Dave,
`
`NDA - WlN6400.DLL I received the signed NDA for the WIN6400.DLL source as well as your addendum to the
`NDA. Bob has a copy of the NDA and will work out any additional matters with you.
`
`Meanwhile, I’would like to plow through sections 8 and 9 of the WOSA/XMC specification. This correspondence will concentrate
`on the ITimer interface.
`
`ITimer Interface ..... Every 6000 product has 1 timer. On stepper products the timer resolution is fixed at 2ms. On servo
`products the timer resolution is dependent on the system update period (see SSFR command). In either case a Set- Resolution()
`method would not be appropriate.
`
`To time events,.the 6000 timer can be started (TIMST1), stopped (TIMSTP) and reset (TIMST0). The current timer value can be
`obtained from all 6000 products via a timer variable ([TIM]). On bus-based products the current timer value can also be
`obtained more efficiently via the "fast status" registers. I think there should be a StartTimer0, Stop’[imer0, ResetTimer0 and
`GetElapsedTime0 methods added to the ITimer interface.
`
`To implement time delays, every 6000 product has the time delay command (r). I wasn’t sure if the GetTimer0 and SetTimer0
`methods applied to this. If so, maybe they should be renamed SetTimeDelay0 and GetTimeDelay0.
`
`Bus-based 6000 products have the ability to interrupt the PC when a timer setpoint has been reached (see INTHW and TIMINT
`commands). There should be a method called SetTimerlnterrupt0. It’s still not clear to me what Attachlnterrupt0 and
`Detachlnterrupt0 do?
`
`Also, I don’t understand what GetErrorStatus0 and Enable() do?
`
`Conclusion .... Dave, I would like to proceed with evaluating the remaining interfaces in this manner. I realize that you are
`now working with the 6000 hardware/software and will discover most of this for yourself. Let me know if you find this kind of
`information helpful.
`
`RGB00051664
`
`Deponen~ ¯
Accessing this document will incur an additional charge of $.
After purchase, you can access this document again without charge.
Accept $ Charge
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.
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.
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
