Agilent 34970A External Reference Configuration via Labview 8.2

Hello
I am trying to scan up to 12 channels with the Agilent 34970A. My goal is to measure the temperature using channel 101 as the external reference using 4-wire RTD whereas all the other channels are supposed to use Thermocouple (k-Type). I know that the Agilent is able to do so, because you can configure it on the manual display. My problem is that every time I have configured Channel 101 ( CONF: TEMP FRTD,85, (@101)) and then the other Channels 102:1XX ( CONF: TEMP TC,K, (@102:1XX)) it seems that the configurations for Channel 101 are lost. I tried everything I could come up with to seperate the inputs, but nothing usable comes up. Any Advice?
Thanks Neja

There are two different drivers sets for the 34970, but they're not from Agilent. They're available from the NI Instrument Driver Network. Since you said you had it working under 7.1 you're probably using the older "hp34970" drivers. The error codes you indicated are -138, which is "Suffix not allowed", and -113, which is "Undefined header". Both of these basically mean a syntax error, which is likely incorrect code with the drivers. There are numerous configuration VIs. Which one are you using, and how are you calling it? Can you use the updated project-style drivers available from the link I posted?
I'm not quite sure I understand what you're saying with the COM ports. You said you get nothing when using COM1 or COM2. How many devices do you have connected to your COM ports? What communication parameters (baud rate) are you setting?
It would probably be worthwhile to see what happens if you try to talk to instrument via MAX to see if this is a communication problem or a LabVIEW problem. With the LabVIEW drivers you can see what command is being sent out to the instrument by simply putting a probe on the string that's being fed to the VISA Write. Then, you can enter the same command in MAX (as well as confirming the command from the user manual) to see what happens.

Similar Messages

Errors 410 and 420 with Agilent 34970A

Hello, all. I'm helping a colleague with an application measuring ten channels each of temperature, frequency, and current using an Agilent 34970A DAQ switch (GPIB) and LabVIEW 7. We keep getting errors 410 and 420 from the switch. When the error occurs, then the switch doesn't report all 30 pieces of data. I'm looking for ways to a) clear the error; and b) prevent the errors.
Thanks in advance,
-Dan A

According to the manual, 410 is Query Interupted and 420 is Query Unterminated. The first can happen when you send a query but there is still data in the output buffer. If you've requested a certain number of bytes during a read, you probably need to increase that number in order to sure that all data is retrieved. A Device clear command will clear the error. Query Unterminated happens when the instrument is addressed to talk but there is no command pending that will place data in the buffer. The example in the manual cites sending a CONFIG command which doesn't generate data and then doing a read.
Are you using the drivr from NI or have you written your own?

How do you setup a fixed reference in LabView when gathering temperature data with Agilent 34970A

Hi I am using Agilent 34970A to gather a lot of thermocouple data. Until now I was using it soley with the internal reference. I was hoping to switch and set this to a fixed reference. In Lab View, how do I select which thermocouple is the fixed reference thermocouple?

19rachael91 wrote:
Hi I am using Agilent 34970A to gather a lot of thermocouple data. Until now I was using it soley with the internal reference. I was hoping to switch and set this to a fixed reference. In Lab View, how do I select which thermocouple is the fixed reference thermocouple?
Could you show us some code? Your question is a bit open-ended and we could considerably narrow down the choices based on what we see.
Bill
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

LabView - Agilent 34970A initializer error

i am using LabView 6i connect with GPIB-PCII (ISA) to Agilent 34970A
i downloaded VISA software and use it to control my device. However,
the initializer for the 34970A sent an error message "old visa occur
with my device". LabView can still run, but didn't trigger the device
to start taking measurement.
the error message number is 107380743
i would be appricated if anyone can help on this issue

Here's a copy of my modifed VI.
Attachments:
HP34970A_Initialize.vi ‏113 KB

Communicating with agilent 34970A using labview.

Hi,
I'm using labview to control agilent 34970A DAQ. I was using VEE and
now I'm planning to use Labview. I downloaded the necassary drivers. I
want to know how i can get started. i.e. generating sub vi's like
initialize.vi etc.
-Satya

When you do what Dennis has suggested you'll also find that there will be one or more high level examples included with the Instrument Driver that use the lower level functions. The document on how to write LabVIEW Instrument drivers is pretty useful in getting an overview:
http://zone.ni.com/devzone/devzoneweb.nsf/Opendoc?openagent&D318B79F473D3C838625680A005AC409
Regards,
Kamran

External Reference field not populating via CRM_ORDER_MAINTAIN

Hi ,
I am using the FM CRM_ORDER_MAINTAIN and wanted to add EXTERNAL REFERENCE Field in existing Complain Order(Transaction :CRMD_ORDER). I am passing the following parameter to add the Reference. But it is not updating the
with the follwoing Reference number. Could you please help on this.
ls_ext_ref-REFERENCE_TYPE           = 'Z002'.
ls_ext_ref-REFERENCE_NUMBER      = '12345678'.
ls_ext_ref-REFERENCE_TYPE_T        = 'SOCS Number'.
ls_ext_ref-REFERENCE_MODE           = 'A'.
ls_Ext_ref-handle                                = '0000000001'.
ls_ext_ref-ref_guid          = gs_orderadm_h-guid.
ls_ext_ref-ref_kind          = gc_object_ref_kind-orderadm_h.
INSERT ls_ext_ref INTO TABLE gt_ext_ref.
ls_input_field-ref_guid    = gs_orderadm_h-guid.
ls_input_field-ref_kind    = gc_object_ref_kind-orderadm_h.
ls_input_field-objectname = gc_object_name-ext_ref.
ls_input_field-LOGICAL_KEY = '0000000001'.
ls_input_field_names-fieldname = 'REFERENCE_TYPE_T'.
INSERT ls_input_field_names INTO TABLE ls_input_field-field_names.
ls_input_field_names-fieldname = 'REFERENCE_TYPE'.
INSERT ls_input_field_names INTO TABLE ls_input_field-field_names.
ls_input_field_names-fieldname = 'REFERENCE_NUMBER'.
INSERT ls_input_field_names INTO TABLE ls_input_field-field_names.
INSERT ls_input_field INTO TABLE gt_input_fields.
CALL FUNCTION 'CRM_ORDER_MAINTAIN'
    EXPORTING
    ct_orderadm_h   = gt_orderadm_h
     it_ext_ref           = gt_ext_ref
   CHANGING
      ct_input_fields = gt_input_fields.
Get guids
LOOP AT gt_orderadm_h INTO gs_orderadm_h.
    INSERT gs_orderadm_h-guid INTO TABLE gt_obj_guids.
ENDLOOP.
CALL FUNCTION 'CRM_ORDER_SAVE'
    EXPORTING
      IT_OBJECTS_TO_SAVE = gt_obj_guids
    EXCEPTIONS
      DOCUMENT_NOT_SAVED = 1
      OTHERS             = 2.

Hi,
For external reference field
Use Crm_order_read funtion module to read the details.
get the details of sales lt_sales and create same structure of sales and pass the value.
IF lt_sales IS NOT INITIAL.
    CLEAR ls_sales.
    READ TABLE lt_sales INTO ls_sales INDEX 1.
    IF sy-subrc = 0.
      ls_sales-po_number_sold = ls_orderadm_h-object_id. """" Ticket no
      MODIFY lt_sales FROM ls_sales INDEX 1.
    ENDIF.
    CLEAR ls_sales.
    CLEAR ls_sales1.
    READ TABLE lt_sales INTO ls_sales INDEX 1.
    IF sy-subrc = 0.
      MOVE-CORRESPONDING ls_sales TO ls_sales1.
      ls_sales1-ref_handle    = 1.
      ls_sales1-ref_guid      = lv_hguid .                          ls_sales1-ref_kind      = 'A' .
      h2_ls_sales1-po_number_sold = ls_sales-po_number_sold. "" this is external reference no field._h2
      INSERT ls_sales1 INTO TABLE lt_sales1.
    ENDIF.
    " Input Fields
    ls_input_field-ref_handle = 1.
    ls_input_field-ref_kind   = 'A' .                  "A
    ls_input_field-ref_guid   = lv_hguid.                   "External System GUID Assignment."
    ls_input_field-objectname = sales.                   "SALES
    ls_input_field_names-fieldname = PO_NUMBER_SOLD.
    INSERT ls_input_field_names INTO TABLE ls_input_field-field_names.
    ls_input_field_names-fieldname = PO_DATE_SOLD.
    INSERT ls_input_field_names INTO TABLE ls_input_field-field_names.
    INSERT ls_input_field INTO TABLE it_input_fields.
ENDIF.
Pass lt_sales1 to crm_order_maintain and crm_order_save.

Using an external reference clock for counter measurements

Hi all,
I have several PXI chassis
configured for testing, each of which uses an NI-DAQ-6221 for
conducting period and frequency measurements among other things.
However each of my setups give me a slightly different reading when conducting identical measurements due to
the tolerance of the DAQ on board reference
clocks.
The chassis' have a 10MHz GPS calibrated reference fed into them via the reference input and this is connected to the backplane. I have tried and failed to try to route and use this as my reference
base for my counter measurements so that each of my cards will give me
the same reading every time. I have tried the routing method using the
DAQ connect terminals vi but could not get this to work. I have looked through the labview examples and cant find anything thta shows me what i need to do to take frequency and period measurments using my external reference as my base clock. There are some examples showing the use of the DAQmx timing vi set to sample clock mode which allows a clock source to be selected. However these examples are only for counting digital events and when i apply the same vi to a frequency or period measurement an error is thrown saying 'invalid timing type for this channel', 'you can select: implicit, on demand'.
I do not
understand the working of the DAQ hardware very well so was hoping
someone could help explain to me how to do this if it is even possible
or give me any guidance as to how else to overcome my problem. Any vis
showing how to use my external 10MHz reference
as the base clock for these kind of measurements would be greatly appreciated.
Regards,
Dan

Hi Dan,
Thanks for the reply. When trying to use the connect terminals i just tried connecting the PXI10 to the onboard clock in the hope that this would configure it to use the PXI10 signal to synchronise the onboard clocks via the PLL. Doing this didn't throw any errors as i recall, it just gave me a reading of infinity as it couldn't measure the signal.
I have actually just managed to successfully do what i wanted thanks to help from Rob at NI tech support UK. There is a DAQmx timing property node which allows you to choose a reference clock source. By using the PXI_Clk10 signal this makes the DAQ synchronise its reference clocks to this signal. I have included an image of the code i used to achieve this to take period measurements.
Here is a very useful link which Rob sent me which may be of help to anyone else with similar problems
http://zone.ni.com/devzone/cda/tut/p/id/3615
Best regards,
Dan.
Attachments:
ExtRef Source Image.jpg ‏105 KB

2012: Execute Package Task (external reference) Very Slow in SSDT

Hi All,
I have 4 packages which I've deployed using the package deployment model to the MSDB package store.
Configuration setup is System Env Var pointing at SSIS Configurations table that populates the connection string of my SSISConfig data source. Source/Dest configurations are in the SSIS Configuration table.
I have a 'master' package that executes the 4 packages in parallel using the Execute Package control flow task (external reference, SSIS Package Store)
When I execute this master package in SSDT it takes 1minute 56 seconds to finish. All the execute package tasks seem to hang until the last few sec then finish one after the other. It's the same if execute one of the Execute Package Task items individually.
It just hangs there for nearly 2 min then rushes through its work (i've verified by looking at the destination tables; nothing happens until the end).
But the packages executed directly in ssdt take 2-3 sec to execute.
I've deployed the master package to the server and executed it via SSMS. It takes <3 sec.
I've RDPed into the ssis box and it's the same. Executing the packages individually or the master package in dtexecui takes less than 3 sec.
Something's going wrong inside SSDT (some kind of timeout? but there are no error msgs or warning) that's making it take nearly 2 minutes.
Have others experienced this? Have I misconfigured something? The env var has been working on my local machine since last week and i've restarted many times since then, so I'm positive SSDT is using the 'current' version of the env var.
Jakub @ Adelaide, Australia

Very strange. The sysssislogs are the same for any method of execution, but there's a 5 sec delay for each step when executing via SSDT
endtime,message
2014-02-06 09:37:15.000,Execute phase is beginning.
2014-02-06 09:37:20.000,PrimeOutput will be called on a component. : 104 : Merge Join : Merge Join
2014-02-06 09:37:20.000,PrimeOutput will be called on a component. : 213 : Unchanged : Unchanged
2014-02-06 09:37:25.000,A component has returned from its PrimeOutput call. : 213 : Unchanged : Unchanged
2014-02-06 09:37:25.000,A component has returned from its PrimeOutput call. : 104 : Merge Join : Merge Join
2014-02-06 09:37:30.000,PrimeOutput will be called on a component. : 143 : ODS - Src - State : ODS - Src - State
2014-02-06 09:37:30.000,PrimeOutput will be called on a component. : 17 : Src - dbo - State : Src - dbo - State
2014-02-06 09:37:35.000,A component has returned from its PrimeOutput call. : 143 : ODS - Src - State : ODS - Src - State
2014-02-06 09:37:35.000,A component has returned from its PrimeOutput call. : 17 : Src - dbo - State : Src - dbo - State
2014-02-06 09:37:35.000,Rows were provided to a data flow component as input. : : 264 : OLE DB Source Output : 182 : Source Checksum : 185 : ChecksumInput : 7 : Source Checksum : Paths[Src - dbo - State.OLE DB Source Output] : Source Checksum.Inputs[ChecksumInput]
2014-02-06 09:37:35.000,Rows were provided to a data flow component as input. : : 263 : OLE DB Source Output : 53 : Destination Checksum : 56 : ChecksumInput : 7 : Destination Checksum : Paths[ODS - Src - State.OLE DB Source Output] : Destination Checksum.Inputs[ChecksumInput]
2014-02-06 09:37:40.000,A component will be given the end of rowset signal. : 53 : Destination Checksum : 56 : ChecksumInput : Destination Checksum : Destination Checksum.Inputs[ChecksumInput]
2014-02-06 09:37:40.000,Rows were provided to a data flow component as input. : : 258 : ChecksumOutput : 104 : Merge Join : 109 : Merge Join Left Input : 7 : Merge Join : Paths[Source Checksum.ChecksumOutput] : Merge Join.Inputs[Merge Join Left Input]
2014-02-06 09:37:40.000,A component will be given the end of rowset signal. : 182 : Source Checksum : 185 : ChecksumInput : Source Checksum : Source Checksum.Inputs[ChecksumInput]
2014-02-06 09:37:45.000,Rows were provided to a data flow component as input. : : 259 : ChecksumOutput : 104 : Merge Join : 118 : Merge Join Right Input : 7 : Merge Join : Paths[Destination Checksum.ChecksumOutput] : Merge Join.Inputs[Merge Join Right Input]
2014-02-06 09:37:45.000,Rows were provided to a data flow component as input. : : 264 : OLE DB Source Output : 182 : Source Checksum : 185 : ChecksumInput : 0 : Source Checksum : Paths[Src - dbo - State.OLE DB Source Output] : Source Checksum.Inputs[ChecksumInput]
2014-02-06 09:37:45.000,Rows were provided to a data flow component as input. : : 263 : OLE DB Source Output : 53 : Destination Checksum : 56 : ChecksumInput : 0 : Destination Checksum : Paths[ODS - Src - State.OLE DB Source Output] : Destination Checksum.Inputs[ChecksumInput]
2014-02-06 09:37:50.000,A component has finished processing all of its rows. : 53 : Destination Checksum : 56 : ChecksumInput : Destination Checksum : Destination Checksum.Inputs[ChecksumInput]
2014-02-06 09:37:50.000,A component has finished processing all of its rows. : 182 : Source Checksum : 185 : ChecksumInput : Source Checksum : Source Checksum.Inputs[ChecksumInput]
2014-02-06 09:37:55.000,A component will be given the end of rowset signal. : 104 : Merge Join : 118 : Merge Join Right Input : Merge Join : Merge Join.Inputs[Merge Join Right Input]
2014-02-06 09:38:00.000,Rows were provided to a data flow component as input. : : 259 : ChecksumOutput : 104 : Merge Join : 118 : Merge Join Right Input : 0 : Merge Join : Paths[Destination Checksum.ChecksumOutput] : Merge Join.Inputs[Merge Join Right Input]
2014-02-06 09:38:05.000,A component has finished processing all of its rows. : 104 : Merge Join : 118 : Merge Join Right Input : Merge Join : Merge Join.Inputs[Merge Join Right Input]
2014-02-06 09:38:10.000,A component will be given the end of rowset signal. : 104 : Merge Join : 109 : Merge Join Left Input : Merge Join : Merge Join.Inputs[Merge Join Left Input]
2014-02-06 09:38:15.000,Rows were provided to a data flow component as input. : : 258 : ChecksumOutput : 104 : Merge Join : 109 : Merge Join Left Input : 0 : Merge Join : Paths[Source Checksum.ChecksumOutput] : Merge Join.Inputs[Merge Join Left Input]
2014-02-06 09:38:20.000,A component has finished processing all of its rows. : 104 : Merge Join : 109 : Merge Join Left Input : Merge Join : Merge Join.Inputs[Merge Join Left Input]
2014-02-06 09:38:20.000,Rows were provided to a data flow component as input. : : 261 : Merge Join Output : 2 : Add audit columns : 3 : Derived Column Input : 7 : Add audit columns : Paths[Merge Join.Merge Join Output] : Add audit columns.Inputs[Derived Column Input]
2014-02-06 09:38:25.000,A component will be given the end of rowset signal. : 2 : Add audit columns : 3 : Derived Column Input : Add audit columns : Add audit columns.Inputs[Derived Column Input]
2014-02-06 09:38:25.000,Rows were provided to a data flow component as input. : : 260 : Derived Column Output : 195 : Type 1 SCD : 196 : Conditional Split Input : 7 : Type 1 SCD : Paths[Add audit columns.Derived Column Output] : Type 1 SCD.Inputs[Conditional Split Input]
2014-02-06 09:38:30.000,Rows were provided to a data flow component as input. : : 265 : Unchanged : 213 : Unchanged : 214 : Union All Input 1 : 7 : Unchanged : Paths[Type 1 SCD.Unchanged] : Unchanged.Inputs[Union All Input 1]
2014-02-06 09:38:30.000,Rows were provided to a data flow component as input. : : 261 : Merge Join Output : 2 : Add audit columns : 3 : Derived Column Input : 0 : Add audit columns : Paths[Merge Join.Merge Join Output] : Add audit columns.Inputs[Derived Column Input]
2014-02-06 09:38:35.000,A component has finished processing all of its rows. : 2 : Add audit columns : 3 : Derived Column Input : Add audit columns : Add audit columns.Inputs[Derived Column Input]
2014-02-06 09:38:40.000,A component will be given the end of rowset signal. : 195 : Type 1 SCD : 196 : Conditional Split Input : Type 1 SCD : Type 1 SCD.Inputs[Conditional Split Input]
2014-02-06 09:38:45.000,Rows were provided to a data flow component as input. : : 260 : Derived Column Output : 195 : Type 1 SCD : 196 : Conditional Split Input : 0 : Type 1 SCD : Paths[Add audit columns.Derived Column Output] : Type 1 SCD.Inputs[Conditional Split Input]
2014-02-06 09:38:50.000,A component has finished processing all of its rows. : 195 : Type 1 SCD : 196 : Conditional Split Input : Type 1 SCD : Type 1 SCD.Inputs[Conditional Split Input]
2014-02-06 09:38:55.000,A component will be given the end of rowset signal. : 66 : Insert ODS - Src - State : 79 : OLE DB Destination Input : Insert ODS - Src - State : Insert ODS - Src - State.Inputs[OLE DB Destination Input]
2014-02-06 09:38:55.000,A component will be given the end of rowset signal. : 220 : Update ODS - Src - State : 225 : OLE DB Command Input : Update ODS - Src - State : Update ODS - Src - State.Inputs[OLE DB Command Input]
2014-02-06 09:38:55.000,A component will be given the end of rowset signal. : 213 : Unchanged : 214 : Union All Input 1 : Unchanged : Unchanged.Inputs[Union All Input 1]
2014-02-06 09:39:00.000,Rows were provided to a data flow component as input. : : 262 : New : 66 : Insert ODS - Src - State : 79 : OLE DB Destination Input : 0 : Insert ODS - Src - State : Paths[Type 1 SCD.New] : Insert ODS - Src - State.Inputs[OLE DB Destination Input]
2014-02-06 09:39:00.000,Rows were provided to a data flow component as input. : : 257 : Changed : 220 : Update ODS - Src - State : 225 : OLE DB Command Input : 0 : Update ODS - Src - State : Paths[Type 1 SCD.Changed] : Update ODS - Src - State.Inputs[OLE DB Command Input]
2014-02-06 09:39:00.000,"The final commit for the data insertion in ""Insert ODS - Src - State"" has started."
2014-02-06 09:39:00.000,Rows were provided to a data flow component as input. : : 265 : Unchanged : 213 : Unchanged : 214 : Union All Input 1 : 0 : Unchanged : Paths[Type 1 SCD.Unchanged] : Unchanged.Inputs[Union All Input 1]
2014-02-06 09:39:00.000,"The final commit for the data insertion in ""Insert ODS - Src - State"" has ended."
2014-02-06 09:39:05.000,A component has finished processing all of its rows. : 213 : Unchanged : 214 : Union All Input 1 : Unchanged : Unchanged.Inputs[Union All Input 1]
2014-02-06 09:39:05.000,A component has finished processing all of its rows. : 220 : Update ODS - Src - State : 225 : OLE DB Command Input : Update ODS - Src - State : Update ODS - Src - State.Inputs[OLE DB Command Input]
2014-02-06 09:39:05.000,A component has finished processing all of its rows. : 66 : Insert ODS - Src - State : 79 : OLE DB Destination Input : Insert ODS - Src - State : Insert ODS - Src - State.Inputs[OLE DB Destination Input]
2014-02-06 09:39:05.000,Post Execute phase is beginning.
2014-02-06 09:39:05.000,Insert ODS - Src - State wrote 0 rows.
2014-02-06 09:39:05.000,Cleanup phase is beginning.
2014-02-06 09:39:05.000,End of package execution.
2014-02-06 09:39:05.000,
2014-02-06 09:39:05.000,"<?xml version=""1.0""?><DTS:ProcessMemoryUsage xmlns:DTS=""www.microsoft.com/SqlServer/Dts""><DTS:PeakWorkingSetSize>66457600</DTS:PeakWorkingSetSize></DTS:ProcessMemoryUsage>"
2014-02-06 09:39:05.000,End of package execution.
Look at the times. It's going up in exact 5sec increments! The package takes about 3 sec to run when the master package is executed via dtexecUI outside SSDT. The log looks "normal" in those instances as well; the end times are more randomised
This is with SP1 CU8 installed.
Jakub @ Adelaide, Australia

Trying to update channels in real time while controlling Agilent 34970a

Hello all,
I've gotten such valuable help on these forums and I am hoping that someone will be able to point me in the right direction with this issue. I'm still pretty new to LabVIEW so please bear with me.
I am working with the LabVIEW driver for the Agilent 34970A connected over a GPIB-ENET 100/1000. The device was detected and works just fine. The reason I am writing today is that I am trying to update the channel list in real time. Currently I need to stop the whole process in order to edit the channel list but due to the nature of the tests we will be performing it is important that I can add more channels as I go without interrupting the testing going on.
I've searched the forums and tried modifying the channel string control to "Update value while typing," and "Limit to single line." The motivation behind the latter change was so that I could modify the channel list and use the ENTER key to execute. I've also tried creating a while loop with shift registers but the construction ws so clumsy that it did not work either.
I am pretty sure that the modification should occur right at the string control but cannot be certain since the pint is for it to reinitialize what channels to scan and that occurs further down in the VI. I've attached the VI I am working with; it is an only slightly modified version of the driver's Advanced Scan Example.
Thank you all in advance,
Yusif
Solved!
Go to Solution.
Attachments:
HP34970A Advanced Scan Example_YN_5-16a-12.vi ‏77 KB

You may have added a shift register, but you're not actually comparing anything. You need to compare the value of the control to the value of the data coming from the shift register to see if it changed. If so, change the scan list.
If you need to have a delay after changing the scan list, then you should add the delay inside the case structure that calls the VI to reconfigure the scan list. You can use the Time Delay VI to cause the delay to occur after configuring the scan by using the error wires to force execution order.
P.S. Your naming scheme for VIs implies that you are probably not using a source code control system. If so, you would be well served in taking the time to learn about source code controls systems and installing one. It's very easy, and there have been numerous threads in the LabVIEW forum on recommendations of source code control systems.
Attachments:
changed.png ‏15 KB

External Reference Clock on pci-5640R

Hi. I want to clock my IF-RIO 5640R board, with an external reference clock at 2MHz frequency and i would to generate a 200 MHz clock inside the board (as the vcxo).
If I set properly the parameters inside the "configuration timebase" vi, using the pll on the cdc7005, can i achieve this feature?
How can i do?
Thanks....

If you use the fixed-personality driver, and you are feeling a little bit brave, you should be able to use ni5640R Configure Timebase.vi. It can be found (at least on my computer) at:
C:\Program Files\National Instruments\LabVIEW 8.2\instr.lib\ni5640R\Driver\NI-5640R VIs
Leave the defaults as they are, except change as follows:
Ref Divider (M) = 2 (for 2 MHz)
SMB Ext Ref Enable = True
VCXO Control = PLL
CP Enable = True
That should be everything, to the best of my memory. You may have to enable the Invert CP bit.
Hope this helps,
Ed

Compatability with Agilent 34970a Model

I need to check if the Agilent 34970a Data Acquisition/Switch Unit is compatible with DASYLab. I know it functions with Labview, but the company I am performing a project for prefers DASYLab. The unit uses the VISA language. Thank you for your help.
Josh

How are you connecting it?
It's not quite as easy as the LabVIEW VISA drivers, but DASYLab has both GPIB and RS232 inputs which can be configured with the appropriate SCPI commands.
- cj
Measurement Computing (MCC) has free technical support. Visit www.mccdaq.com and click on the "Support" tab for all support options, including DASYLab.

Thinkpad Edge S430 - Windows does not detect external display connected via HDMI

On a Thinkpad S430 with HD4000 integrated graphics, an external display connected via a HDMI cable is not detected at all when using Windows. The system is fully updated as of the time of posting this message, both via the Lenovo Update tool as well as Windows update.
The Intel driver version is 8.15.10.2696. It appears that this is the latest version, since it does not offer an update when I try to auto-update it via Device Manager.
NB: I am running Ubuntu 12.04 with kernel 3.4.0 on the same machine, and the external display works perfectly fine with this software configuration.
Hence I think that it's very likely that this is a Windows-specific driver issue.
Would Lenovo happen to have a driver update in the works? Alternatively, I will be thankful for any suggestions about possible resolution of this problem.

skn2011 wrote:
My Macbook Pro notbook 13.3" does not detect external display throught it's mini display port to HDMI connector when connected to Sony Bravia 32" LCD TV.Can anyone help me get the answer as i tried reading everywhere on internet and none does not seems to work.Please help me out guys.
Are you using the Apple adaptor or a 3rd party

Problème carte 34901A sur Agilent 34970A

Bonjour,
J'ai un problème sur l'acquisition en impédance de mes cartes 34901A des centrales d'acquisition Agilent 34970A. Lorsque j'utilise mon programme labview, la centrale me retourne une valeur d'impédance fausse. (pour une résistance connue 351Ohm, la centrale me renvoie 351 +/- 40Ohm).
Ce problème est récurrent et cela arrive sur plusieurs de mes systèmes utilisant les cartes 34901A.
Quelqu'un a t'il déjà recontré ce problème la?
Merci,

Bonjour Tomaks,
Il semble en effet d'après votre retour que le problème soit matériel et non pas logiciel si celui-ci n'apparaît qu'avec certains systèmes.
Peut-être serait-il plus bénéfique de vous tourner Agilent pour vérifier ces points et vous assurer qu'il n'y aurait pas de problèmes au niveau de vos systèmes.
Par ailleurs, si en effet un autre utilisateur venait à avoir rencontré ce problème, son expérience pourrait être qu'appréciable.
De mon côté, je ne peux malheureusement apporter plus d'aide car il ne s'agit pas de nos systèmes.
Cordialement,
Antonin G. Associated LabVIEW Developper
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
Communauté francophone des développeurs LabVIEW et des enseignants en STI2D
Si vous souhaitez partage...

Creating Complaints/Returns from external reference for Billing Documents.

Hi Experts,
I have question regarding Creating Complaints/Returns from external reference.
My requirement is to fetch data for Billing Type, Billing Documents and other related from ECC system and to create Complaints/Returns using the same in Web UI.
Is there any SPRO configuration as such so that we can pinpoint to the ECC system where it should fetch the data or is there be a custom development involved for the Drop down lists in Web UI?
I know about the BADI CRM_COPY_BADI_EXTERN which is triggered when creating using reference, but I am not able to see where the method SEARCH_HELP_FOR_EXTERN_DOC or GET_SEARCH_HELP are triggered.
I have gone through many forums within SDN but not able to find any solution. Please help!
Regards,
Mahesh

Hi Ly,
I wouldn't be able to share the code with you, but I would ask you to check with the functional counterpart regarding the important fields that are to be copied.
What I did in my case is, based on the Billing document number passed from CRM in the RFC I hit the tables VBRK and VBRP for header and item data respectively.
For pricing I passed the relevant fields from KONV table (KSCHL, KWERT, KAWRT etc..)
For document flow VBFA.
For partner VBPA.
I faced issues only with pricing as there were many settings and pricing routine logic differences between CRM and ERP.
Regards,
Mahesh

ABAP Shared Objects - External Reference

Hi,
I am using ABAP SHared Objects (SHMA and SHMM) as data persistence between 2 BSP Applications
I want to create a generic Root class with one attribute that is TYPE REF TO OBJECT. The idea is to store any class instance in this attribute of the Root class so as to AVOID creating a seperate Shared AREA for each Class...
WHen I try to put this generic Root Class in the shared area via detach_commit(), it gives a exception that there are External references in the Shared area which should be closed first
Does this mean u cannot have a instance variable as an attribute in your ROOT Class.
Thanks
SAP User

Hi,
Go through the below code, it's working fine....
*& Report Z13708_ABAPOBJECTS_INHER
REPORT Z13708_ABAPOBJECTS_INHER.
      CLASS C1 DEFINITION
CLASS C1 DEFINITION.
PUBLIC SECTION.
    data: var1 type ref to object.
    METHODS: METH1.
ENDCLASS.                    "C1 DEFINITION
      CLASS C1 IMPLEMENTATION
CLASS C1 IMPLEMENTATION.
METHOD METH1.
    WRITE: / 'This is a method one'.
ENDMETHOD.                                                "METH1
ENDCLASS.                    "C1 IMPLEMENTATION
      CLASS C2 DEFINITION
CLASS C2 DEFINITION.
PUBLIC SECTION.
    METHODS: METH2.
ENDCLASS.                    "C2 DEFINITION
      CLASS C2 IMPLEMENTATION
CLASS C2 IMPLEMENTATION.
METHOD METH2.
    WRITE: / 'This is a method two'.
ENDMETHOD.                                                "METH2
ENDCLASS.                    "C2 IMPLEMENTATION
START-OF-SELECTION.
DATA REF1 TYPE REF TO C1.
DATA REF2 TYPE REF TO C2.
CREATE OBJECT REF2.
ref1->var1 ?= ref2.
Regards,
Azaz Ali.

Agilent 34970A External Reference Configuration via Labview 8.2

Similar Messages

Maybe you are looking for