Breaking News
Comments
Newest First | Oldest First | Threaded View
MeasurementBlues
User Rank
Author
Re: Call it IEEE-488 or HPIB
MeasurementBlues   5/19/2014 12:39:56 PM
NO RATINGS
@_hm

Agilent stopped calling it HPIB after it was split off from HP. The HPIB term died in 1999.

ChristophZ
User Rank
Author
Re: Call it IEEE-488 or HPIB
ChristophZ   5/19/2014 3:03:15 AM
NO RATINGS
IEEE-488 is not exactely right.

You can call it IEEE-488.1 to be precise. The IEEE-488.1 standard covers the physical and electrical interface (Where the time has come to retire it).

IEEE-488.2 standard covers the command structure, number representation, line ending etc. and is far away from being obsolete. It is the basis for commands used when you have a LXI or USB TMC measurement device (toghether with SCPI).

 

When you buy USB based measurement equipment, try to use USB TMC devices. As with GPIB it makes your live easier in the future (simply because it is a multivendor standard).

Sanjib.A
User Rank
Author
Remotely display measurement data
Sanjib.A   5/18/2014 11:22:29 PM
NO RATINGS
"...The next logical step is embedding the measurement results into a web site and accessing them with a standard web browser."

Not understanding exactly how the question of survival of GPIB (IEEE-488) is dependent on this, as I have not used it in last 5-7 years but I completely agree...that remote monitoring is going to be the trend for measurement going forward and as mentioned. Also, the instruments would get more dependent on an external display rather than having an internal display.

_hm
User Rank
Author
Call it IEEE-488 or HPIB
_hm   5/17/2014 4:36:34 PM
NO RATINGS
Why not call it IEEE-488 and if not call it original name HPIB.

 



Datasheets.com Parts Search

185 million searchable parts
(please enter a part number or hit search to begin)
Radio
NEXT UPCOMING BROADCAST

What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.
Like Us on Facebook
Special Video Section
LED lighting is an important feature in today’s and future ...
05:27
The LT8602 has two high voltage buck regulators with an ...
05:18
Silego Technology’s highly versatile Mixed-signal GreenPAK ...
The quality and reliability of Mill-Max's two-piece ...
01:34
Why the multicopter? It has every thing in it. 58 of ...
Security is important in all parts of the IoT chain, ...
Infineon explains their philosophy and why the multicopter ...
The LTC4282 Hot SwapTM controller allows a board to be ...
This video highlights the Zynq® UltraScale+™ MPSoC, and sho...
Homeowners may soon be able to store the energy generated ...
The LTC®6363 is a low power, low noise, fully differential ...
See the Virtex® UltraScale+™ FPGA with 32.75G backplane ...
Vincent Ching, applications engineer at Avago Technologies, ...
The LT®6375 is a unity-gain difference amplifier which ...
The LTC®4015 is a complete synchronous buck controller/ ...
10:35
The LTC®2983 measures a wide variety of temperature sensors ...
The LTC®3886 is a dual PolyPhase DC/DC synchronous ...
The LTC®2348-18 is an 18-bit, low noise 8-channel ...
The LT®3042 is a high performance low dropout linear ...