Error: Creating SignalExpress Plug-Ins with LabView

[Measure1]

Hello LV Gurus,

I can communicate successfully with my Rohde & Schwarz RTM Oscilloscope in MAX 5.3 and LabVIEW 2011. For testing purposes, I created a simple VI (see LV snippet below) to acquire a waveform from the oscilloscope in LabVIEW. It works, I can view the data/waveform. My goal is to see whether I can run this instrument in SignalExpress 2012.

Below is the error I see in SignalExpress2012:

Problem: I have been unable to correctly create a "run LabVIEW VI" step for my VI in SignalExpress. My LV code may not be perfect, and I would appreciate your help in writing it correctly to see data in SignalExpress. I have read the document "Creating SignalExpress Plug-Ins with LabView" over and over and tried but with no avail. Please help me create this step or show me an example of a completed "correct" step (with inputs/outputs of my VI with no errors in SE). 

Details: Running Windows 7, SignalExpress 2012 (Professional), LabVIEW 2011 (Professional), Click here for the Rohde & Schwarz RTM/LabVIEW driver.

[juergenstraub]

Did you have a look into this one: http://www.rohde-schwarz.com/en/applications/introduction-to-attribute-based-instrument-drivers-appl...

Please check chapter 3.4.2. I think this solves your problem... 😉

br jürgen

[Measure1]

Hello Jurgen,

Thank u for your response. I added the Callback Folder, but still; same error in SignalExpress :(. In the SE Error above, notice that the input section is grayed out. I set up the connector pane of the VI in LabVIEW, so im not sure why. The input section was also grayed out after adding the callback folder

[Measure1]

 Creating the "run LabVIEW VI" step in SignalExpress of the snippet above does not requre the RTM Instrument. Just LabVIEW magic... Any help will be appreciated..

[D-Cubed]

Hi Measure1,

I am unable to see the error message you are receiving in SignalExpress.  Can you attach the image and type the text of the error?  It would be helpful for me to see what the exact error message is.

Thanks,

[Measure1]

Hello D-Cubed, here is the SE 2012 Error. It says "Failure opening VI."

Your help is appreiciated.

[Measure1]

When I click on the Error List, i get this window below. Any ideas/thoughts are welcome

[juergenstraub]

Hi, please note that the driver uses a kind of callbacks which are linked dynamically, thus the hole rsrtm/_utility folder should be inculded in you exported llb. Furthermore it is important that the driver session itself is initialized, "rsrtm Initialize.vi", here also the driver and the so called "attribute database" inside is configured. For more information refert to the application note: http://www.rohde-schwarz.com/en/search/applications_63466.html?term=1ma170 br j.

[Measure1]

Hello Juergen,

I tried the following:  

1.  I copied the whole callback folder and placed it outside the rtm2libtest folder (image shown in post 02-12-2013 04:50 AM). The rtm2libtest is the llb of my main VI that I created  (from VI snippet above); as instructed in the Creating SignalExpress Plug-Ins with LabView document. Building the Source Distribution passed, but I get the SignalExpress error posted above.

2.  I copied the whole callback folder and placed it inside the rtm2libtest folder. Building the Source Distribution passed, but I get the SignalExpress error posted above.

3. I saved the callback VI's as re-entrant, and did steps 1-2 above, same SignalExpress error.

4. I copied the whole _utility folder as is and placed it inside/outside the rtm2libtest folder. This gave me conflict errors in the project. When I expanded the folder tree, it showed all the conflicts, including the driver core conflict. Building the source distribution failed.

5. I saved all the _utility folder VI's as re-entrant (including the callback VIs), this gave me the same issue as 4 above.

------------------------------------------------------------------------------------

What am I doing wrong? Can someone please try creating a "run LabVIEW VI" step in SignalExpress for this VI snippet?

[juergenstraub]

I'm sorry, I'm running out of ideas. I do not have an Signal Express experience! 😞