Bill, I recall there was some question on the Prologix "unlisten", but I suspect you're seeing a 5334A issue. While testing my driver at max 5334A throughput, I found found you cannot trust a ++read until the status byte returns data ready, else you may get the previous reading. That would happen even at reduced throughput, depending on gate time. So I send a trigger, then loop on status byte (with timeout of gate time+), then read. Because that is necessary, I didn't see any advantage to the WA1 mode. Gerry
>wje <[EMAIL PROTECTED]> >With the 5334A, I can get samples for as long as I want, no problem. >However, if I set the 5334A to 'WA1' mode, which is supposed to wait >until the counter is addressed before taking each sample, what happens >is that I can read one value. Every successive read returns the same >value; the 5334A never triggers for a new sample. Either I don't >understand the behavior of WA1, although HP's sample program indicates >that what I've described is proper, or there is some incompatibility >between the Prologix and the 5334A. _______________________________________________ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.