| Electronics > Repair |
| HP 3478A: How to read/write cal SRAM |
| << < (35/41) > >> |
| djrm:
--- Quote from: WaveyDipole on March 17, 2024, 10:07:18 pm ---The question that now arises how to deal with this appropriately. On the one hand filtering could be removed so that all characters sent regardless. On the other hand, because we are dealing with bytes rather than ASCII text, ought we to be treating the data as binary and therefore having the HP3478A set to using EOI only as terminator and the AR488 set with ++eoi 1 and ++eos 3 (no terminator characters)? It looks like the meter ignores the trailing CRLF anyway, so perhaps ++eoi 1 and leaving the meter as is would be sufficient? I am open to suggestion and perhaps will also need to re-consider whether the filtering really is necessary or whether it is more of a hindrance and should be removed. --- End quote --- I have limited experience of GPIB (now on my third day) but expecting a change in the reader programs eoi setting is a separate issue to fixing the bug. The old interface worked ok and the new one will with the bug corrected, the meter doesn't seem to care about the eoi setting. I'd be happy to use the new software with the bug corrected without any other changes. Kind regards, David. |
| lmester:
I have a real Prologix adapter. I did some testing with this adapter. I can properly read cal data with EOI 1 or EOI 0. The AR488 adapter only reads cal properly with EOI 1. Is it better to exactly match the behavior of the Prologix adapter or keep AR488 how it's operating now? I would say match the behavior of the Prologix adapter since AR488 is a replacement for the Prologix. |
| m k:
Back in the day with ASCII terminals CRLF (\r\n) was not a problem, both characters were needed. I'd say that keep everything that would be sent to controller from the device, so GPIB side. And remove everything extra from non GPIB side. 488.1 is not defining any special characters for devices. EOS is just one that is defined on top of that. So if device is sending CRLF then that is how it should be. Tek 492P GPIB Concepts is using words "can" and "may" when dealing with EOI. So more like an option. |
| djrm:
I have edited AR488 version 0.51.28 to revert the eoi testing to use && as suggested (line 700 in AR488_GPIBus.cpp) and the new firmware works now with HP3478ACalibration.exe and HP3478A.exe I have noticed that under wine HP3478ACalibration.exe doesn't work as well as AR488 version 0.49 does, an error reading the version string nearly always occurs. (but not in WIndows) hth David. |
| m k:
I'm like almost having a recollection where something had a selector between versions 1 and 2. Was it a hardware or software thing, can't say. But no doubt, different style of EOI would require some action. |
| Navigation |
| Message Index |
| Next page |
| Previous page |