HP53310A Read Data Vi Feature

[Kaspar]

Hello,

  I have found a possible "feature" with the HP53310A Read Data vi. I was not able to read all of the data from the instrument, so I discovered that the VISA read vi used to get the data from the "DATA?" command was not large enough, it was initially set to 50000. Actually the instrument outputs over 70000 bytes, so I set it to 80000, now everything works fine. Should the driver at the NI website get updated?

Regards,

Kaspar

[Ray.R]

No because you simply need to adjust it to your needs, as you did.  Everybody's needs are not the same.

As a matter of fact, the value 50000 was probably an arbitrary value.

R

[Kaspar]

Hello,

  Ok, I understand the concept of "adjust it to your needs" but...... the HP53310A Read Data vi should simply perform the task that the name implies, it should read the data and give it to the user. This would alow the user to focus on their application as opposed to obtaining a programming manual for their equipment to verify the operation of the commands contained within the driver vi. I took the time to crawl thru the 2 inch thick HP53310A programmers manual to verify that the operation/etc of the commands contained within the "Read Data" vi when I observed that the instrument was generating errors when I went to obtain the data.  I discovered that a query "DATA?" can return more than the 50000 bytes, so I had to change it to 80000 to get it to work. I am very disappointed to discover that my request to update the driver has been denied/rejected.

  I have tried to be respectful while I was venting, I now feel better.

Regards,

Kaspar

[Dennis_Knutson]

Don't know why you feel the need to vent. If you want ro request a correct, that's your right. Since the instrument and driver are so old, I have no idea if the correction will be made but we will see.

p.s. The amount of data requested has probably been sufficient for the vast majority of users since I can find no posts regarding the instrument and this issue. The amount of data returned is obviously quite variable. I did see a function in the library that I think can be used to determine exactly how many records are available. Maybe the driver should be correct to use this function first.

[Kaspar]

Hello,

   You are right, the HP53310A is old, but HP/Agilent does not offer a drop in replacement for the Time Domain Analyzer. I have also looked at other test equipment manufacturers and so far I have not been able to find one. There are probably numerous ways to fix this problem, such as using the other vi's that you suggested. So what do you suggest if the other vi's determine that the amount of data exceeds the max of 50000 bytes coded in the Read data vi?.  How does someone get out the data out of the instrumnent? I think the simplest way to fix this is to update the Read Data vi.

Regards,

Kaspar

[Kaspar]

Hello,

   Here is some info from the HP53301A  manual to help someone update the driver (assuming that it will).  On page 5-8 of the programmers guide is a "captain midnite decoder ring"  to allow someone to decide how much data is really coming back. The first char of the data is a pound sign, the 2nd char is the number of digits that determine that amount of data that is coming back. So the actual data that comes back is variable. If someone wants more detailed information, please feel free to respond to this post.

Regards,

Kaspar

[Ray.R]

What happens when someone else needs more tha 80000 bytes of data? 😉  LOL! 🙂

The right way to correct the issue is by having the manufacturer make commands that are intuitive.  That way you tell the instrument "give me all the data" and you receive it all, no matter the size..  But that's not how they implemented their firmware 😞

Programming is far from perfect and having an expertise means more than simply knowing the language. 😉  🙂  😄

I don't think changing the Read Data.vi will solve anything.

R

[Kaspar]

Hello,

  You are correct, maybe 80000 bytes may not be sufficient for someone else. So, the correct way to updated the Read Data vi would be to implement that "captain midnite decoder ring" in the programmers manaul to "automagically" get the data back, so that the user of the driver does not have to be concerned about it. In fact, I will update the driver that I have, test it out and post it on this forum so that hopefully it might be part of the next driver release.

Regards,

Kaspar

[Dennis_Knutson]

I don't know if you are seriously whining or just being sarcastic with your captain midnite comment but go ahead and do whatever you want. As I said, feel free to provide feedback about the driver. You seem more upset that the driver does not do absolutely everything you want it to do. If that's the case, then your expectations are way too high. No driver or any other piece of software is going to be 100% perfect or suit the needs of everyone (is yours?). NI provides the driver code for that reason. It's there to be modified if necessary. I've had to modify many NI drivers in the last 20 years and I'll have to say your modification would fall into one of the easier problems to find and fix.

[Ray.R]

I agree with Dennis.  LOL!  😄

I've modified drivers many times over the years.  Now I just write my own.  I build my own library. 

Never complained nor has the thought of requesting new drivers ever crossed my mind.  Without having to change drivers I'd be out of a job!!!  😮

LOL!!  😄