That’s an extremely new interface. Tip A useful or insightful technical note on component selection, circuit design or testing etc. The simple answer is – not pleasant or easy:. You’re pretty much screwed on reading the FDD. It has it’s ups and downs.
|Date Added:||3 March 2016|
|File Size:||12.96 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
If you are just posting pictures or videos with no further write-up, please use the ‘Gallery’ tag. These things are built to last.
Soft-sectored FDDs which became the universal standard in the early s use a single hole to synchronize over all framing and then use soft sectoring encoded into the magnetic tracks to define sectors. Lavbiew hard to tell the exact era from the picture but it looks like its in the GPIB era. View and contribute to our wiki page for beginners.
It seems so simple until you find out all the little problems with extracting labvie data a normal way. To do this you have to boot, load and set a particular setup of which there can be many on a single diskand then run your remote program to suck up the data and the settings.
HP Graphics from the instrument library, gives an error when run on HP A!
NI adapters seem to be the most reliable. 414a5 GPIB trick above is the other way to get to the data. It uses a file system that was only used on the A itself and no where else, ever. Either way really appreciate the help!
I’m looking at some 90’s digital scopes we have in our lab. It’s my dream to design test equipment.
Agilent Technologies / Keysight Technologies hp4145 Analyzer
A big part of my job is controlling a room full of old boxes like this with GPIB to automate data collection and quality assurance so if I can help you with any general GPIB stuff pm me. Please categorize your post by clicking the ” add tag ” flair button after submitting it.
Wow, I apparently know nothing about the NI offerings. It’s a huge industry, you’ve heard of labview haven’t you? Submit a new text post. To qualify as a project, the details available should allow someone else to make a copy.
And then there’s the filesystem issues. BDAT has the nasty feature that there is absolutely no meta-data included so you MUST KNOW precisely labbiew data was laid down in what order and of what data type because of varying bit-length differences in each data type.
And then there’s the file format itself. Maybe since this was a later model they finally wised up?
In all likelyhood there is a better way, but, there it is The hell did you expect? Hopefully, this works out. The interface was via GPIB. A subreddit dedicated to news, articles and general discussions related to the field of electronic engineering.
If not I’ll go back to the cleaner, easier Our code was using NI libraries, I recall that is what our C program was using to talk to the Agilent connection software that connects to the HP.
hpa GPIB through LabView write but no read
Another possibility a very ugly one is reading tracks lsbview with a floppy drive and oscilloscope. See my other comment; just use Agilent Intuilink it’s free. All of our instrument communication is wrapped inside C calls, which makes no sense, since they are all IVI at most a light lab view wrapper would be needed If you use it as intended, you’ll be in great shape, but if you do something weird and sideways, like write your own DLL and try to shove all the logic in there, and just make calls into it occasionally, it’s going to bite you in the ass.
ALways running into problems. Hhp connection software that comes with it, polls the USB and recognizes the lsbview. It uses a combination of both 3-byte and 4-byte floats to store data.