AnsweredAssumed Answered

Python COM automated

Question asked by dochang on Mar 18, 2014
Latest reply on Apr 1, 2014 by dochang

Like • Show 0 Likes0
Comment • 11

Dear professor,

I have successfully connected to my Logic Analyzer, 16901A via Python COM remote control. I am able to load the configure file to my LA and let it run or stop. But I meet some issues when I cast to some specific modules or call constants, such as AgtDataLong.

when I call “win32com.client.constants.AgtDataLong”, there will be AttributeError, which means ‘AgtDataLong’ is not defined. Because ‘AgtDataLong’ is their own data constant type, I doubt there should be something installed at first, as well as I get error track information when running the command “LAAnalyzerModule = win32com.client.CastTo(LAModule, "IAnalyzerModule")”, the error information is attached.

######################## My Code #####################################
import win32com.client

LAHostNameOrIP = '135.24.17.88‘
LAConnect = win32com.client.Dispatch("AgtLA.Connect")
LAInst = LAConnect.GetInstrument(LAHostNameOrIP)
LAModule = LAInst.GetModuleByName("My 16950B-1")
print LAModule.Type

LAInst.Open("OOO.ala")

#if LAModule.Type == "Analyzer":
#   LAAnalyzerModule = win32com.client.CastTo(LAModule, "IAnalyzerModule")
#   LAAnalyzerModule.SimpleTrigger("My Bus 1=hff")

LAInst.Run()

LABusSignals = LAModule.BusSignals
LABusSignalsCount = LABusSignals.Count
LABusSignalNameArray = []
LABusSignalTypeArray = []

for index in range(LABusSignalsCount):
    LABusSignalName = LABusSignals.Item(index).Name
    LABusSignalType = LABusSignals.Item(index).BusSignalType
    LABusSignalNameArray.append(LABusSignalName)
    LABusSignalTypeArray.append(LABusSignalType)

    print LABusSignalName,LABusSignalType

###Get the module's bus/signal data and store into 'LADataArrays'.
LADataArrays = []
LADataArrays.append(LABusSignalNameArray)
LADataArrays.append(LABusSignalTypeArray)
LAStartRange = -10
LAEndRange = 10

for index in range(LABusSignalsCount):
    LAData = LABusSignals.Item(index).BusSignalData
    LABusSignalType = LABusSignalTypeArray[index]
    LADataType = win32com.client.constants.AgtDataLong
    .....
    .....
#######################################################

Edited by: dochang on Mar 18, 2014 10:55 PM

Edited by: dochang on Mar 18, 2014 10:56 PM

Attachments

ss.png21.2 KB

No one else has this question

Outcomes

algoss

Mar 19, 2014 5:11 AM

First, please don't copy and paste your code into the thread. It just messes up the window format.

It appears that you copy and pasted some of the example code from the LA help file. Did you follow the instructions from the top of the help page on early binding?

Are you using the same version of Python as recommended ( Python version 2.2.3 and the Python for Windows extensions build 200) ?

What happens if you use the entire example from the help file, without changes?

Al

Disclaimer: For more reliable response, you should consider calling your local Agilent Technical Call Center. The Agilent Forums are monitored on an "as available" basis, and aren't necessarily the fastest way to get technical questions answered.

Actions

dochang @ algoss on Mar 19, 2014 10:10 PM

All are not on purpose.
At first, I called Agilent support at the end of last year, all your supporters and AEs told me that they had no idea on anything about Python. Then nothing. Nobody comes out for help.
Then I posted my case to Agilent e-mail support, and there have been even four months by now. Anything I received is supporter's mail in which she had not received any reply from the factory for four month, and she suggested me trying my luck on the forum.
Last but not least, I am an Engineer. I won't post a question without any trials by myself. I lose my temper and patience now.
I am very angry about all your supporters' reply. It is surely an easy question, but still up in the air for 4 months.

Actions

dochang @ algoss on Mar 19, 2014 10:15 PM

I use Python 2.7 on Windows 7 operation system. I have read online help, most of it are related to VB. And there isn't a section for Windows modules or constants initialization. It is really a hard-to-follow help file.
I called your supporters that I could not run out your demo scripts, and asked for the reason. It has been for 4 months. It drivers me crazy.

Actions

algoss

@ dochang on Mar 20, 2014 8:23 AM

I am sorry for the problems you are having with Python, and your problems getting technical support. It appears that you are not in the US. I know the people that do the support here, and there are some who know and understand Python.

One question I didn't ask last time was what Version of LA SW you are running. The current version is 5.70. Please make sure you have the latest version. It is available, free, from the Agilent website. There are Python examples, both in a directory, and in the help file. I just opened the help file and searched using "python", and it brought me right to the example.

There are questions I did ask, but I don't see an answer to:

- What happens if you use the entire example from the help file, without changes? Does it run correctly? I don't have Python loaded right now, but I have used it in the past, including running the example from the help file. I may get a chance today or tomorrow to load Python, but I may not get to it.

- Did you follow the instructions from the top of the help page on early binding?

Al

Actions

dochang @ algoss on Mar 27, 2014 12:33 AM

Dear professor,

I think I hit the mark this time.
1) I did not install LA SW on my lab computer, as well as Remote Programming Interface.
2) The LA SW version on my LA is 03.67, and the operation system is Window XP SP2. However, my lab computer operation system is Window 7, on which only support LA SW version 05.70. Moreover, SW version has to match to each other.
3) Remote Programming Interface supports Windows XP SP2 but could not install without LA SW.
In other words, only if I re-install the operation system of my LA to Window XP SP3, I may not use Remote control.

Thanks a lot for your help. Do you have any suggestions? It seems that my LA operation system is out-of-date.

Best regards,
Doris

Actions

algoss

@ dochang on Mar 27, 2014 4:26 AM

I'm sorry, it didn't occur to me that you wouldn't have the most recent versions of all of the SW.

1) Yes, you should load the same version of SW on both computers. There is a way around that, but the SW is free, so there's no reason not to.

2) Yes, you need a new version of LA SW, but all versions of LA SW will run on Windows XP, as long as you have all of the latest patches, including .NET.

3) You don't need the Remote Programming Interface to do COM programming. RPI is only for talking to older 16700 series analyzers.

You should connect your LA to the internet, and run Microsoft Update repeatedly until you have loaded every available patch, including all versions and patches to .NET. Do it soon, since Microsoft will stop supporting Win XP within a month or so. Once you have done that, you can load the latest version of LA SW on the LA. Recently, I collected 6 LA's for a seminar, and they each needed between 150 and 200 patches. It took a long time, and lots of mouse clicks to get them up to date.

Once you have everything up to date, you should be able to connect and run with no problems.

Al

Actions

dochang @ algoss on Mar 28, 2014 1:42 AM

Hi Al,

Thanks a lot for your direction. I met the easiest problem that I had turn on the automatic updates but it had never updated with Internet connection.I think it is due to our network settings. I installed Window XP SP3 package and .Net Frame 4 manually. Then I installed LA SW 05.70.0002 successfully. But I met another problem that It could not configure SW successfully because it could not find some temp files. Do you have a .msi version for installation? Thanks a lot.

Best regards,
Doris

Actions

algoss

@ dochang on Mar 28, 2014 1:12 PM

There is no msi version of the installer. I suspect that you are still missing patches. You need ALL of the .NET packages and ALL of the patched for both Windows and .NET. You need to connect the analyzer to the internet and get all of the patches.

Before you continue with the installation of the newest LA SW, you should completely remove it, then delete everything in the c:\Program Files\Agilent Technologies\Logic Analyzer directory, except the Licenses directory that should be there. Then you should run a good registry cleaner. I use CCleaner from Piriform. Then you should reboot. There will be warning messages about missing drivers, since the LA HW is a device, and removing the SW removes the drivers. Reinstall the LA SW, and reboot.

Al

Actions

dochang @ algoss on Mar 31, 2014 12:14 AM

Hi Al,

Very appreciate your help! It works finally!!!
BTW, if I want to export data to a .csv as we do File/Export, do you have any Python command example? I found some useful info in the help file and in the Python script 'C:\Python27\Lib\site-packages\win32com\gen_py\91F3E657-040B-4499-9047-3461107FFD3Fx0x1x0\IInstrument.py', but seems not enough for me.

LAInst = LAConnect.GetInstrument(LAHostNameOrIP)
LAModule = LAInst.GetModuleByName("My 16950B-1")
LABusSignals = LAModule.BusSignals

LAInst.ExportEx(ExportFileName='dochang_test', SourceName=*LABusSignals*, ExportRange=False, StartRange=85.16, EndRange=314.8, FileType=u'Standard CSV text file',\ FileOptions=u'SeparationCharacters=","')

I think I use the wrong SourceName. Please do me a favor that teach me how to find the proper module name or source. Thanks a lot!

Best regards,
Doris

Actions

algoss

@ dochang on Mar 31, 2014 4:58 AM

I don't have an example, but the help file says "When the "Module CSV text file" or "Module binary file" FileType is specified, the SourceName must be a logic analyzer or import module."

This means that instead of using "LABusSignals", you should probably use "LAModule".

Al

Actions

dochang @ dochang on Apr 1, 2014 12:36 AM

Hi Al,

Thank you very much for all your help! It works!

LAInst.ExportEx(ExportFileName='dochang_test_chop.csv', SourceName=LAModule, ExportRange=True, StartRange=-340e-9, EndRange=7.8e-6, FileType=u'Standard CSV text file')

Best regards,
Doris

Actions

11 Replies

algoss Mar 19, 2014 5:11 AM
Mark Correct
Correct Answer
First, please don't copy and paste your code into the thread. It just messes up the window format.

It appears that you copy and pasted some of the example code from the LA help file. Did you follow the instructions from the top of the help page on early binding?

Are you using the same version of Python as recommended ( Python version 2.2.3 and the Python for Windows extensions build 200) ?

What happens if you use the entire example from the help file, without changes?

Al

Disclaimer: For more reliable response, you should consider calling your local Agilent Technical Call Center. The Agilent Forums are monitored on an "as available" basis, and aren't necessarily the fastest way to get technical questions answered.
Like • Show 0 Likes0
Actions
- dochang @ algoss on Mar 19, 2014 10:10 PM
  Mark Correct
  Correct Answer
  All are not on purpose.
  At first, I called Agilent support at the end of last year, all your supporters and AEs told me that they had no idea on anything about Python. Then nothing. Nobody comes out for help.
  Then I posted my case to Agilent e-mail support, and there have been even four months by now. Anything I received is supporter's mail in which she had not received any reply from the factory for four month, and she suggested me trying my luck on the forum.
  Last but not least, I am an Engineer. I won't post a question without any trials by myself. I lose my temper and patience now.
  I am very angry about all your supporters' reply. It is surely an easy question, but still up in the air for 4 months.
  Like • Show 0 Likes0
  Actions
- dochang @ algoss on Mar 19, 2014 10:15 PM
  Mark Correct
  Correct Answer
  I use Python 2.7 on Windows 7 operation system. I have read online help, most of it are related to VB. And there isn't a section for Windows modules or constants initialization. It is really a hard-to-follow help file.
  I called your supporters that I could not run out your demo scripts, and asked for the reason. It has been for 4 months. It drivers me crazy.
  Like • Show 0 Likes0
  Actions
  - algoss @ dochang on Mar 20, 2014 8:23 AM
    Mark Correct
    Correct Answer
    I am sorry for the problems you are having with Python, and your problems getting technical support. It appears that you are not in the US. I know the people that do the support here, and there are some who know and understand Python.
    
    One question I didn't ask last time was what Version of LA SW you are running. The current version is 5.70. Please make sure you have the latest version. It is available, free, from the Agilent website. There are Python examples, both in a directory, and in the help file. I just opened the help file and searched using "python", and it brought me right to the example.
    
    There are questions I did ask, but I don't see an answer to:
    
    - What happens if you use the entire example from the help file, without changes? Does it run correctly? I don't have Python loaded right now, but I have used it in the past, including running the example from the help file. I may get a chance today or tomorrow to load Python, but I may not get to it.
    
    - Did you follow the instructions from the top of the help page on early binding?
    
    Al
    Like • Show 0 Likes0
    Actions
    - dochang @ algoss on Mar 27, 2014 12:33 AM
      Mark Correct
      Correct Answer
      Dear professor,
      
      I think I hit the mark this time.
      1) I did not install LA SW on my lab computer, as well as Remote Programming Interface.
      2) The LA SW version on my LA is 03.67, and the operation system is Window XP SP2. However, my lab computer operation system is Window 7, on which only support LA SW version 05.70. Moreover, SW version has to match to each other.
      3) Remote Programming Interface supports Windows XP SP2 but could not install without LA SW.
      In other words, only if I re-install the operation system of my LA to Window XP SP3, I may not use Remote control.
      
      Thanks a lot for your help. Do you have any suggestions? It seems that my LA operation system is out-of-date.
      
      Best regards,
      Doris
      Like • Show 0 Likes0
      Actions
      - algoss @ dochang on Mar 27, 2014 4:26 AM
        Mark Correct
        Correct Answer
        I'm sorry, it didn't occur to me that you wouldn't have the most recent versions of all of the SW.
        
        1) Yes, you should load the same version of SW on both computers. There is a way around that, but the SW is free, so there's no reason not to.
        
        2) Yes, you need a new version of LA SW, but all versions of LA SW will run on Windows XP, as long as you have all of the latest patches, including .NET.
        
        3) You don't need the Remote Programming Interface to do COM programming. RPI is only for talking to older 16700 series analyzers.
        
        You should connect your LA to the internet, and run Microsoft Update repeatedly until you have loaded every available patch, including all versions and patches to .NET. Do it soon, since Microsoft will stop supporting Win XP within a month or so. Once you have done that, you can load the latest version of LA SW on the LA. Recently, I collected 6 LA's for a seminar, and they each needed between 150 and 200 patches. It took a long time, and lots of mouse clicks to get them up to date.
        
        Once you have everything up to date, you should be able to connect and run with no problems.
        
        Al
        Like • Show 0 Likes0
        Actions
        dochang @ algoss on Mar 28, 2014 1:42 AM
        Mark Correct
        Correct Answer
        Hi Al,
        
        Thanks a lot for your direction. I met the easiest problem that I had turn on the automatic updates but it had never updated with Internet connection.I think it is due to our network settings. I installed Window XP SP3 package and .Net Frame 4 manually. Then I installed LA SW 05.70.0002 successfully. But I met another problem that It could not configure SW successfully because it could not find some temp files. Do you have a .msi version for installation? Thanks a lot.
        
        Best regards,
        Doris
        Like • Show 0 Likes0
        Actions
        algoss @ dochang on Mar 28, 2014 1:12 PM
        Mark Correct
        Correct Answer
        There is no msi version of the installer. I suspect that you are still missing patches. You need ALL of the .NET packages and ALL of the patched for both Windows and .NET. You need to connect the analyzer to the internet and get all of the patches.
        
        Before you continue with the installation of the newest LA SW, you should completely remove it, then delete everything in the c:\Program Files\Agilent Technologies\Logic Analyzer directory, except the Licenses directory that should be there. Then you should run a good registry cleaner. I use CCleaner from Piriform. Then you should reboot. There will be warning messages about missing drivers, since the LA HW is a device, and removing the SW removes the drivers. Reinstall the LA SW, and reboot.
        
        Al
        Like • Show 0 Likes0
        Actions
        dochang @ algoss on Mar 31, 2014 12:14 AM
        Mark Correct
        Correct Answer
        Hi Al,
        
        Very appreciate your help! It works finally!!!
        BTW, if I want to export data to a .csv as we do File/Export, do you have any Python command example? I found some useful info in the help file and in the Python script 'C:\Python27\Lib\site-packages\win32com\gen_py\91F3E657-040B-4499-9047-3461107FFD3Fx0x1x0\IInstrument.py', but seems not enough for me.
        
        LAInst = LAConnect.GetInstrument(LAHostNameOrIP)
        LAModule = LAInst.GetModuleByName("My 16950B-1")
        LABusSignals = LAModule.BusSignals
        
        LAInst.ExportEx(ExportFileName='dochang_test', SourceName=*LABusSignals*, ExportRange=False, StartRange=85.16, EndRange=314.8, FileType=u'Standard CSV text file',\ FileOptions=u'SeparationCharacters=","')
        
        I think I use the wrong SourceName. Please do me a favor that teach me how to find the proper module name or source. Thanks a lot!
        
        Best regards,
        Doris
        Like • Show 0 Likes0
        Actions
        algoss @ dochang on Mar 31, 2014 4:58 AM
        Mark Correct
        Correct Answer
        I don't have an example, but the help file says "When the "Module CSV text file" or "Module binary file" FileType is specified, the SourceName must be a logic analyzer or import module."
        
        This means that instead of using "LABusSignals", you should probably use "LAModule".
        
        Al
        Like • Show 0 Likes0
        Actions
        dochang @ dochang on Apr 1, 2014 12:36 AM
        Mark Correct
        Correct Answer
        Hi Al,
        
        Thank you very much for all your help! It works!
        
        LAInst.ExportEx(ExportFileName='dochang_test_chop.csv', SourceName=LAModule, ExportRange=True, StartRange=-340e-9, EndRange=7.8e-6, FileType=u'Standard CSV text file')
        
        Best regards,
        Doris
        Like • Show 0 Likes0
        Actions

Python COM automated

Attachments

Outcomes

Related Content

Recommended Content