You are correct. UsbTmc exposes no multi device capability. Also when I made first versions many years ago I had no "garden hose" GPIB cables and saw they were more expensive as the whole adapter.
V3 which will come early next year supports GPIB daisy chaining/multi device support via Ethernet VXI11 & HiSlip.
The V2 adapter shown here supports trigger, SRQ, serial poll, trigger, clear, local lockout, goto lockal, pulse indicator, all features though.
If you absolutely need common synchronous trigger to a chain of GPIB instruments which is quite seldomly absolutely required, you'll have it in next version V3.
Interesting. I built an AR488 a while back (https://github.com/Twilight-Logic/AR488) and it worked alright for my needs. I'd be interested to see a comparison of the two projects.
Am I wrong in understanding that each physical device supports only a single GPIB device at a time? The enumeration and discovery scheme is certainly novel, but one device per hardware would seem to prevent using some of GPIB’s advanced features like parallel polling and low latency triggers.
Maybe someonw can explain me, but I never understood the appeal of GPIB for modern instruments (legacy instruments are of course "excused"). Electrically is a terrible interface that introduces ground loops with the control computer. Speed are laughable and it requires exensive and exotic adapters with complex sw stack (I wish this projects good success, it's needed!). Ethernet in comparison tick all my boxes. It's electrically decoupled by default (just use UTP cables), crazy cheap, very fast and with sane sw stack thanks to vxi-11. You can even bypass visa if you wish and open a plain TCP socket, no need for any library. What am I missing?
I strongly suspect that this does not meet the strict timing requirements that GPIB has. Putting this on your bus is likely to violate both the T1 hard timing requirements and the impedance requirements.
Use of the "standard" set of 74-series buffers that everybody uses would meet impedance requirements and would also allow the usage of a much faster MCU which likely could be made to adhere to the strict T1 timing requirements (with the caveat that most microcontroller USB stacks are piles of garbage that demand that they get interrupt priority even when you tell them otherwise).
You are correct. UsbTmc exposes no multi device capability. Also when I made first versions many years ago I had no "garden hose" GPIB cables and saw they were more expensive as the whole adapter. V3 which will come early next year supports GPIB daisy chaining/multi device support via Ethernet VXI11 & HiSlip. The V2 adapter shown here supports trigger, SRQ, serial poll, trigger, clear, local lockout, goto lockal, pulse indicator, all features though. If you absolutely need common synchronous trigger to a chain of GPIB instruments which is quite seldomly absolutely required, you'll have it in next version V3.
Interesting. I built an AR488 a while back (https://github.com/Twilight-Logic/AR488) and it worked alright for my needs. I'd be interested to see a comparison of the two projects.
Here a comparison from a user: https://github.com/xyphro/UsbGpib/discussions/47
Am I wrong in understanding that each physical device supports only a single GPIB device at a time? The enumeration and discovery scheme is certainly novel, but one device per hardware would seem to prevent using some of GPIB’s advanced features like parallel polling and low latency triggers.
Isn't this a better link? https://github.com/xyphro/UsbGpib/blob/9a8c18a7be1b17127496e...
At least it renders the Markdown.
Maybe someonw can explain me, but I never understood the appeal of GPIB for modern instruments (legacy instruments are of course "excused"). Electrically is a terrible interface that introduces ground loops with the control computer. Speed are laughable and it requires exensive and exotic adapters with complex sw stack (I wish this projects good success, it's needed!). Ethernet in comparison tick all my boxes. It's electrically decoupled by default (just use UTP cables), crazy cheap, very fast and with sane sw stack thanks to vxi-11. You can even bypass visa if you wish and open a plain TCP socket, no need for any library. What am I missing?
Glad to see there's a REV 3 in progress that would support ethernet. That's the one thing that would make me go out of my way to build one of these.
I strongly suspect that this does not meet the strict timing requirements that GPIB has. Putting this on your bus is likely to violate both the T1 hard timing requirements and the impedance requirements.
Use of the "standard" set of 74-series buffers that everybody uses would meet impedance requirements and would also allow the usage of a much faster MCU which likely could be made to adhere to the strict T1 timing requirements (with the caveat that most microcontroller USB stacks are piles of garbage that demand that they get interrupt priority even when you tell them otherwise).
very impressive. better than anything on the market either NI or Keysight.