[time-nuts] OT: Prologix GPIB and HP3478A...
Jeff Mock
jeff at mock.com
Wed Nov 28 04:04:18 EST 2007
++eot_char is usually okay. The particular problem I was hacking at the
time was a screen dump from a Tek scope (TDS 754A). The screen dump is
an 8-bit binary file in a weird image format and you don't know exactly
how many bytes are going to be dumped (~50k bytes), but it does set EOI
with the last byte sent.
++eot_char doesn't work 100% since the chosen EOT character might be
binary data or it might be the EOT character. The reason I asked is
that the solution would be cleaner if you could do a "++read eoi" and
then issue some other ++ query command to ask if EOI was set on the
previous read.
jeff
Prologix wrote:
> Hello Jeff,
>
> Thanks for the compliments. Much appreciated.
>
> You may configure the Prologix adapter (using ++eot_enable and ++eot_char)
> to send (append, really) a user-specified character to USB ouput when it
> detects EOI. By checking for the character you can determine if EOI was
> asserted.
>
> Regards,
> Abdul
>
> -----Original Message-----
> From: time-nuts-bounces at febo.com [mailto:time-nuts-bounces at febo.com] On
> Behalf Of Jeff Mock
>
>
> I have a slightly off-topic question about reads. When issuing a
> "++read eoi", is it possible to tell whether an EOI was actually
> returned by the instrument or whether the read was terminated by timeout
> or block size limitation?
>
> jeff
>
>
>
> _______________________________________________
> time-nuts mailing list -- time-nuts at febo.com
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>
More information about the time-nuts
mailing list