AnsweredAssumed Answered

vrf ?? Probable Spam vrf digest: June 25, 2008

Question asked by VRFuser on Jun 26, 2008
Latest reply on Jun 26, 2008 by VRFuser
You may have to enable Utility --> LAN --> LAN Services Setup --> VXI-11 on SCPI.
 
Regards,
Uday
 

  _____  

From: Olivier DORME [mailto:olivier.dorme@mstarsemi.com]
Sent: Thursday, June 26, 2008 1:56 PM
To: VRF
Subject: Re:[vrf] [?? Probable Spam] vrf digest: June 25, 2008



Hi Dennis,

I have the same problem than yours.
I am using VEE 8.5 and the only way to upload data to my ESG is to configure the GPIB as a legacy equipment (i.e ESG@719).
If I want to use the "new" I/O libraries (i.e. equipment define as ESG@GPIB0::19::INSTR) I have the same problem than you with
more erros... And the same when using the LAN as you do...
If my program works with a legacy definition of the equipment, I don't understand why it doesn't with the LAN. The SICL commands
are the same, no?

Regards,
Olivier D.




  _____  


Sujet:
Using the mem:data command to upload a user file to and ESG signal generator
Expéditeur:
"Byk Dennis-EDB023" HYPERLINK "mailto:EDB023@motorola.com"<EDB023@motorola.com>
Date:
Wed, 25 Jun 2008 16:10:55 -0400

Hello,
 
I have a program that has been used since at least 2002 to upload a binary patterns to ESG series signal generators.  I tried to use it recently for the first time since upgrading to VEE 8.0.  I now get errors (on the signal generator) when I try to send the file to the instrument. It seems to receive the command OK, but then as soon as the first byte of data is transmitted, the signal generator give an "-113 invalid header" error.  Anyone familiar with loading patterns into signal generators?
 
Thanks,
Dennis Byk

  _____  


Sujet:
RE: Using the mem:data command to upload a user file to and ESG signal generator
Expéditeur:
"Les Hammer" HYPERLINK "mailto:les_hammer@att.net"<les_hammer@att.net>
Date:
Wed, 25 Jun 2008 16:21:41 -0600

 
 > I have a program that has been used since at least 2002 to upload a binary patterns to ESG series signal generators.  
>  I tried to use it recently for the first time since upgrading to VEE 8.0.  I now get errors (on the signal generator) when 
>  I try to send the file to the instrument. It seems to receive the command OK, but then as soon as the first byte of data 
>  is transmitted, the signal generator give an "-113 invalid header" error.  Anyone familiar with loading patterns into signal generators?
 
Since this program used to work I would assume that something has happened to the header.
The first byte of the header tells how many bytes are remaining in the header.
(Hmm, was there another character such as '#' in front of this?  I don't remember.)
We'll call this "n".  Some instruments are picky and may require 4 or 8 more characters.
The next n bytes/characters tell how many bytes are in the rest of the message.
I would suspect that your formula depended on something that works differently now -
perhaps padding or not padding with leading 0's.
 
~~Les

  _____  


Sujet:
RE: Using the mem:data command to upload a user file to and ESG signal generator
Expéditeur:
"Uday Nandiwada" HYPERLINK "mailto:udaya.nandiwada@broadcom.com"<udaya.nandiwada@broadcom.com>
Date:
Wed, 25 Jun 2008 22:11:40 -0700

Agilent website says that "-113: Undefined header" is an error related to IO Libraries and a National Instruments GPIB card.  I spent recently a lot of time trying to see where this error comes up and found that it comes as soon as you try any simple command (IEEE 488.2).
 
I load waveforms even though this error keeps coming and they all seem to work perfectly fine (I cross checked results with another equipment).
 
Agilent suggests that there is a patch that fixes this problem but, I did not see any effect of that patch.  I use TCPIP control for ESG and not GPIB and that might be the reason the patch did not work for me.
 
Regards,
Uday
 

  _____  

From: Byk Dennis-EDB023 [mailto:EDB023@motorola.com]
Sent: Thursday, June 26, 2008 1:41 AM
To: VRF
Subject: [vrf] Using the mem:data command to upload a user file to and ESG signal generator


Hello,
 
I have a program that has been used since at least 2002 to upload a binary patterns to ESG series signal generators.  I tried to use it recently for the first time since upgrading to VEE 8.0.  I now get errors (on the signal generator) when I try to send the file to the instrument. It seems to receive the command OK, but then as soon as the first byte of data is transmitted, the signal generator give an "-113 invalid header" error.  Anyone familiar with loading patterns into signal generators?
 
Thanks,
Dennis Byk

---
You are currently subscribed to vrf as: HYPERLINK "mailto:udaya.nandiwada@broadcom.com"udaya.nandiwada@broadcom.com
To subscribe please send an email to: HYPERLINK "mailto:vrf-request@lists.it.agilent.com""vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to HYPERLINK "mailto:leave-vrf@it.lists.it.agilent.com""leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email HYPERLINK "mailto:vrf@agilent.com""vrf@agilent.com".
If you need help with the mailing list send a message to
HYPERLINK "mailto:owner-vrf@it.lists.it.agilent.com""owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at HYPERLINK "http://www.vrfarchive.com/vrf_archive""http://www.vrfarchive.com/vrf_archive".
Search the Agilent vrf archive at HYPERLINK "http://vee.engineering.agilent.com""http://vee.engineering.agilent.com".

  _____  



  _____  


Sujet:
RE: Using the mem:data command to upload a user file to and ESG signal generator
Expéditeur:
"Jay Nemeth-Johannes" HYPERLINK "mailto:jay.johannes@smartsensorsystems.com"<jay.johannes@smartsensorsystems.com>
Date:
Thu, 26 Jun 2008 00:37:08 -0500

Les is about spot on.  The format would be mem:data <parameter>
where parameter is a definite block.
The definite block is the # character, followed by ascii 1-9 indicating how many ascii digits follow.  These digits  are the length of the data block in bytes.  This is then followed by data in the specified format.
 
What could go wrong:
First, there was a way of encapsulating all of this into a definite block within an IO object that now may be working differently.  As Les mentioned, some instruments require a specific length of header, for example #400256.
 
Second, the definite block says nothing about the shape of the data.  That is generally handled in a different
 
Third, and very likely.  Since the error occurs right away and it is an invalid header error, it is very likely that vee is no longer transmitting a space between the header and the #, thus making the instrument believe that the command is WAV:DATA# instead of WAV:DATA #.  Another possibility is that VEE is sending an EOI between the header and the data, although I would think that this would generate a parameter error instead of unrecognized header.
 

Jay Nemeth-Johannes 
3420 Riverside Street
Rockford, Illinois 61103
(815) 708-0423
(970) 290-9797 (Cell)
HYPERLINK "http://www.smartsensorsystems.com/"www.SmartSensorSystems.com

 


  _____  

From: Les Hammer [mailto:les_hammer@att.net]
Sent: Wednesday, June 25, 2008 5:22 PM
To: VRF
Subject: RE: [vrf] Using the mem:data command to upload a user file to and ESG signal generator


 
 > I have a program that has been used since at least 2002 to upload a binary patterns to ESG series signal generators.  
>  I tried to use it recently for the first time since upgrading to VEE 8.0.  I now get errors (on the signal generator) when 
>  I try to send the file to the instrument. It seems to receive the command OK, but then as soon as the first byte of data 
>  is transmitted, the signal generator give an "-113 invalid header" error.  Anyone familiar with loading patterns into signal generators?
 
Since this program used to work I would assume that something has happened to the header.
The first byte of the header tells how many bytes are remaining in the header.
(Hmm, was there another character such as '#' in front of this?  I don't remember.)
We'll call this "n".  Some instruments are picky and may require 4 or 8 more characters.
The next n bytes/characters tell how many bytes are in the rest of the message.
I would suspect that your formula depended on something that works differently now -
perhaps padding or not padding with leading 0's.
 
~~Les

---
You are currently subscribed to vrf as: HYPERLINK "mailto:jay.johannes@completetest.com"jay.johannes@completetest.com
To subscribe please send an email to: HYPERLINK "mailto:vrf-request@lists.it.agilent.com""vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to HYPERLINK "mailto:leave-vrf@it.lists.it.agilent.com""leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email HYPERLINK "mailto:vrf@agilent.com""vrf@agilent.com".
If you need help with the mailing list send a message to
HYPERLINK "mailto:owner-vrf@it.lists.it.agilent.com""owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at HYPERLINK "http://www.vrfarchive.com/vrf_archive""http://www.vrfarchive.com/vrf_archive".
Search the Agilent vrf archive at HYPERLINK "http://vee.engineering.agilent.com""http://vee.engineering.agilent.com".



---
You are currently subscribed to vrf as: hua_jing@agilent.com
To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to
"owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "http://www.vrfarchive.com/vrf_archive".
Search the Agilent vrf archive at "http://vee.engineering.agilent.com".  

Outcomes