07-27-2018 08:13 AM
Kindly help me to resolve the issue.
Thanks
07-27-2018 08:43 AM
Ben
07-27-2018 08:54 AM - edited 07-27-2018 08:56 AM
Well, the smart-alec answer is, "just scale by 1000". But what I suspect you want is to specify a timeout with smaller-than-miillisec resolution such as 200 microsec.
Sorry to say, that won't be possible. The API for VISA sets the rules here and it requires an integer # of millisec. That simply reflects the reality of any regular OS, where it would be disingenuous to make an API that implied that it could reliably *honor* sub-millisec timing intervals.
-Kevin P
P.S. Oops, second time this morning I started a reply, got interrupted for a few minutes, came back to finish and then saw that someone got there first. Only this time, it looks like I inadvertantly called Ben a smart-alec. Which I didn't mean to do, but which he also might not argue against anyway.
07-27-2018 08:58 AM
@Kevin_Price wrote:
Well, the smart-alec answer is, "just scale by 1000". But what I suspect you want is to specify a timeout with smaller-than-miillisec resolution such as 200 microsec.
Sorry to say, that won't be possible. The API for VISA sets the rules here and it requires an integer # of millisec. That simply reflects the reality of any regular OS, where it would be disingenuous to make an API that implied that it could reliably *honor* sub-millisec timing intervals.
-Kevin P
True.
The only alternative would be to cod it up explicitly check the number of bytes at the port and only reading when the right number are there. It would also have to be run on a RT target were sub-millisecond timing of loops can be used.
Ben
07-27-2018 02:40 PM
@Ben wrote:
Ben
Umm ... you don't like the regular Divide function?
07-27-2018 02:50 PM
@paul_cardinale wrote:
@Ben wrote:
Ben
Umm ... you don't like the regular Divide function?
I do but I thought I would do something different.
"If you were supposed to divide with the compound arithmetic, you wouldn't be able to invert an input."
Ben