VISA Write differs between TS Development System and LV Run-Time Engine

Hi all
I made an application on LabVIEW to test BERs (Bit Error Rates), and I used VISA Write between two COM ports to exchange data.
Everything works fine using just LabVIEW.
Afterwards, I used TestStand to call my application (VI). The LabVIEW adapters from TestStand were set to Development System by default, and everything works OK!!
Finally, I needed to disable the development system, and set the LabVIEW adapters from TestStand to LabVIEW Run-Time Engine and I notice that the speed of the data exchange between the two COM ports decreased dramatically.
The only difference was the speed...because all the data (changed slowly in this case) arrived correctly on the other COM port too.
The symptom was the same as decreasing the baud rate...but the baud rate and all the other configurations remained the same. The only difference was the change between Develpment System to Run-Time Engine to notice this decreased speed between the exchanged data using VISA Write.
Any solutions for this?
Thanks in advance
Joao
Solved!
Go to Solution.

Joao,
you state that using the LV Developement System as execution platform for your LV code modules result in faster datatransfer between the COM ports than using the LV Run-Time Engine.
So i am pondering: Does this refer to TS at all?
Please check the following:
Run you communication using a sole LV application in LV Developement System. This should be fast. Now build an executable of this application and run that one. Do you see the same behavior?
If there is no difference in a sole LV approach, there have to be some settings in the TS approach making this slow. So please let us know:
Are there different modules involved in that data transfer (which in fact points to the reply Christophe made)?
What about loading/unloading options of the modules?
How big is the hierarchy of the modules, e.g. is it necessary for the RTE to load stuff the Dev Env has already in memory due to loading a lvproj.......?
Could you provide a simple example sequence+modules showing this behavior?
What versions of LV and TS are you using?
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Similar Messages

References: Appearance different in Development System and in Run Time System

I noticed a difference the references appearance in Development System and in Run Time System. It seems to have no effect in the executable version but, per curiosity, someone have an explanation?
Development System
Run Time System
Jean-Marc
Jean-Marc
LV2009 and LV2013
Free PDF Report with iTextSharp
Solved!
Go to Solution.

tst wrote:
When LabVIEW builds an executable, it removes the parts which are not needed from the VIs (like BDs, or FPs of VIs which will not be opened). I'm assuming this is an extension of that where the icon is not copied over. Another option is that the RTE is simply missing the code necessary to display this specific this.
In any case, I would say it's a bug, albeit a minor one.
I don't think this is a bug, the references refere to a given CTL file, which is not present in the RTE, I think LabVIEW disconnects the reference form the typedef and only saves the properties needed.
Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas
LabVIEW, programming like it should be!

Error -17600 when switching from LabVIEW Development System to LabVIEW Run-Time Engine in Adapter Configuration

I receive an error message (code -17600) while loading my test sequence after switching from LabVIEW Development System (2009 f3) to LabVIEW Run-TIme Engine using the Adapter Configuration.
ErrorCode: -17600,
Failed to load a required step's associated module.
LabVIEW Run-Time Engine version 9.0.1f3.
When I switch back to the LV development system, everything is OK, and the sequence loads and runs perfectly.
My TestStand Engine Version is 2012 f1 (5.0.0.262).
I'd appreciate any help on this issue.
Roman

Hi Roman,
There are a couple of things you can try:
1) Determine if the LabVIEW RunTime Engine is corrupted in some way. Create a new simple VI with no sub-VIs, using the same LabVIEW Development system you used for mass-compiling the VIs. Create a TestStand step that calls this VI and ensure it runs correctly. Now switch your LabVIEW adapter to use the RuntimeEngine and choose the "Auto detect using VI version" option.
Check if the simple VI is loadable and runs without errors in TestStand.
If the step generates the same error, you should try a re-install of the LabVIEW development system.
If not, its most likely that there is some VI you are using that is not loadable in the LabVIEW Runtime Engine because:
1) Some sub-VI is still not saved in the right version or bitness. Open the VI heirarchy of the top-level VI that you are calling from TestStand and examine the paths of all the sub-VIs to check if they were in the folder you masscompiled and re-save any that are outside this directory.
Also, when you try to close the top level VI, do you get a prompt to save any unsaved files? If so, they could be the sub-VIs that are not saved in the right version. Save all of them.
Check if you are loading any VIs programatically and if these are compiled and saved in the right version as well.
2) There is some feature you are using in your LabVIEW code that is not supported in the LabVIEW RunTime Engine. To check this, add your top-level VI to a LabVIEW project and create a new build specification and create a new executable from this VI.
    Right-click "Build Specifications" and choose "New->Application(EXE)".
    In the Application Properties window, select Source Files and choose the top level VI as the start-up VI.
    Save the properties.
    Right-click on the newly created build specification and choose Build.
Run this executable (it will be run using the LabVIEW RunTime) and check if the VI has a broken arrow indicating that it cannot be loaded and run in the LabVIEW Runtime Engine.
You might need to examine your code and find the feature which is not supported in the LabVIEW RunTime and find an alternative.
Another thing i forgot to mention the last time around is if you are using 64-bit LabVIEW with 32-bit TestStand, then executing code using LabVIEW RTE from TestStand will not work since the 64-bit LabVIEW RTE dll cannot be loaded by the 32-bit TestStand process.
If none of the above steps resolve the issue, consider sharing your LabVIEW code so i can take a look.
Regards,
TRJ

Labview 7.0 is compatable with Labview Imaq6.1 , vision builder 6.0 and Imaq run time engine 6.0.

Sir,
My system is PXI 8174 and i an using NI 1411 card for my application. I want to know the compatability of the softwares. Whether Labview 7 is compatable with Labview Imaq 6.1 , vision builder 6.0 and Imaq run time engine 6.0.

Hi,
Assuming you meant IMAQ Vision 6.1 instead of IMAC 6.1, this software was intended to run on LabVIEW 5.1, 6.0, and 6.1. I have heard of it being used with LabVIEW 7 on occasion, so it may be possible to make it work, but this has not been tested and is not officially supported. Vision Builder 6.0 should run; however, it was developed long before LabVIEW 7.x and will not generated code for LabVIEW 7.0 and later. The Vision RTE version should correspond to the version of Vision you are using. For instance, if the program was developed with Vision 6.1, the computer should have the Vision 6.1 RTE installed. With this being said, if you plan to use LabVIEW 7, I recommend updating your other software.
Regards,
Ryan M.
Applications Engineer

Has NI plans to develop CVI for WinCE run time engine?

Has NI plans to develop CVI for WinCE run time engine?

At this point, LabWindows/CVI does not have plans to support Windows CE. There are many reasons we do not have plans for support, but two main reasons are:
Windows CE uses a different kernel from other Windows operatings systems.
Windows CE does not support the full WinAPI.
National Instruments
Product Support Engineer

NI 5660 Driver DLL Errors when using Teststand 2010 and LabVIEW Run-Time Engine 2010

This problem seems similar to the post "Resource not found error in executable on development machine." but I didn't want to repost under that thread because I only happened upon it by chance and none of my searches brought me there... so I made a more descriptive Subject.
I am working on a system that uses a PXI Chassis with a NI 5600 Downconverter and a NI 5620 high speed digitizer, among other PXI Cards.
I inherited working code written in LabVIEW 2010, running with the LabVIEW Run-Time Engine 2010. The code was using a custom executive and my task was to rewrite the test using TestStand 2010. I reused the majority of the old code. The old code used NI-5660 to control the 5600 and 5620. When I run my sequence using the LV Development System and TestStand, it runs without any issues. When I change the adapter over to LabVIEW Run-Time Engine 2010, all of my NI5660 VIs become broken due to DLL issues. It warns that the nipxi5600u.dll was not initialized correctly. Many of the errors are associated with the NI Tuner and NI Scope. After this LabVIEW will crash randomly, and the seqeunce will not work in TestStand even when back with the LV Development Adapter. The only way to recover after this is to restart the computer - TestStand automatically reverts back to the development system, the VIs are no longer broken and the sequence works again.
I have all of my VIs associated with a project. After reading a little bit about DLLs and TestStand, I found all of the DLLs in the dependencies section of my project and added them to my TestStand workspace. I also used Dependency Walker to track down the problems with the nipxi5600u.dll, the 2 DLL files that it said were not found already existed in the same folder as the original DLL (C:\Windows\System32). I have also performed a Mass Compile to make sure everything was running in LV 2010. If I skip the steps involving the 5660, my entire sequence runs fine.
The previous code was running with the LabVIEW Run-Time Engine without any issues. Is there just a step I am missing? Has anyone seen anything like this before? I can send screenshots of errors to provide more detail if necessary.

I have tried some more things and still can't get it to work. I have added the VIs mentioned in the Notes On Creating Modulation Executables KB both to the TestStand workspace and the LabVIEW project holding all of my VIs. This did not change the results.
When I try to run my sequence, The first error I get is shown in Error 1445.bmp. This happens when I try to use the NI 5660 initialize.vi. If I click ignore, the next error I see is shown in Error -20551.bmp. When I try to open the VI to look at it, I get the 2 DLL errors shown in Error loading nipxi5600u.bmp and Error loading nidaq32.bmp. When I close TestStand, I get the error LabVIEW Fatal Error.bmp.
Attachments:
Error1445.JPG ‏164 KB
Error -20551.JPG ‏174 KB
Error loading nipxi5600u.JPG ‏9 KB

Error involving Report Generation Toolkit and Labview Run Time Engine

Developed an application using LabVIEW 6.1 and LabVIEW Report Generation Toolkit for Microsoft Office 1.0.1. From there, tried to build a shared application for use with the LabVIEW Run Time Engine. The Run Time version functions properly until "New Report.vi" is called and then an error is generated, code 7, calling out "Open VI Reference in New Report.vi" could not be found. When building the application, I did include the "NI Reports Support" in the advanced installer options. The machine used for original development and application build is running Windows XP Pro and Office XP. Any suggestions??

I am having the exact same problem but with LV 6.1 and M/S WORD 2000. It appears that the "New Report.vi" is trying to open "C:\APP.DIR\Word_Open.vi" and "C:\APP.Dir\Word_Open_Document.vi" by reference. The "OFFICE 2000.TXT" says that "_exclsub.llb and _wordsub.llb must be added as support files when building an application or a dynamic link library with the application builder." I added them as Support Files and I copied them to the "C:\TESTER\" where the TESTER.EXE is and I still get ERROR 7 in "NEW REPORT.VI" at VI OPEN REFERENCE.
Do I need to make a "C:\TESTER\DATA\" sub-dir and put the support files there?
I am building on MY COMPUTER on F: Drive on a network and transporting files to the real Tester.
I displayed my App.Property of APP.DI
R at start up and it is C:\TESTER\ ! How would my application know that "Word_Open.vi" and "Word_Open_Document.vi" are actually inside the _wordsub.llb?
Any ideas ?
Greg Klocek

Different Between KT4V ver1.0 and KT4V v10A

Hi guys, when i just bought a new MSI KT4V from a shop, it was version 1.0, but 3 month later i send for warrantty claim, they return the board to me (I think they replace the board, but i dun think it was a new board, it was a used board), but it was KT4V Ver10A, i bought this board at Malaysia, do anybody know about it ?? Can let me know what is the different between Version 1.0 and 10A ???? ?(
In my mind, i think maybe is KT4V Ver 2.0 :D
I got send mail to MSI official site, but sadly it auto reply by the machine, do anybody know how to send a mail to technical support which will reply and give a solution for you problem ???

The cpu temp looks to be slightly high for an idle temp. Could be caused by too much thermal grease or poor airflow through the case, even by high ambient temps in the room where the system is located. These temps are normally measured in centigrade and should not exceed 43 degrees to 45 degrees at idle. Yours appear to be about 50 degrees.

Is any different between ECC 5.0 and ECC 6.0 for Excel export?

Dear all,
As you know, most standard SAP report allow Excel export. I just wonder is any different between ECC 5.0 and ECC 6.0 for excel report in standard SAP reports?
In ECC 5.0, Reports in profit center accounting, LIS, or PA, etc. has their own different way to export to excel and is any improvement in ECC 6.0? I Thanks.

In ECC 5.0, a lot of reports don't have Excel export function instead user has to go to system -> List -> Save -> Local file -> spreadsheet.
I just wonder is any improvement in ECC 6.0? just like LIS report, user can select export -> Transfer XXL to either pivot table or just plain excel but the function only exist in certain reports in some modules and not all.
Thanks again.

Time difference between the Identity system and Access System: OAM

I was installing OAM. Performed the below steps.
-installed identity server
-installed webpass
-setup of identity system console
-installed policy manager
-setup of access system console
The above steps were successfull. Then when i was logging into Access system console, i am getting the below error:
Error:there was a problem obtaining the userid. One possible reason for this is a time difference between the Identity system and Access systems (Policy Manager and Access system console).+
The Identity Server, WebPass and Policy Manager are installed on the same machine.
Userdata repository: OVD 10.1.4.3
Policy and Config Data Repository: OID 11.1.1.3
OAM: 10.1.4.3
Windows2008 - 64bit
Found document in metalink similar to this issue. suggested to change ldapmaxofreties. but didn't help.
Any idea on this error. Please Advise.
Thanks in advance.

Try this::
Check Time Difference Between Identity and Access Manager Systems
Check the logfile in the Access Manager install directory. The default location is <$AMinstall_dir>/access/oblix/logs/oblogfile.
If the file exists and it contains following line "skew = slack = " that means the Identity and Access Manager Web Servers are on different machines and have not synchronized time within a minute.
Either synchronize times between the two machines within a minute's accuracy or you can increase the slack by modifying these two files: <$AMinstall_dir>/access/oblix/apps/common/bin/oblixbaseparams.lst: loginslack: <$IMinstall_dir>/identity/oblix/apps/common/bin/oblixbaseparams.xml: loginslack: where numofseconds is more than skew found in the oblogfile.
For example, if you have following line in oblogfile "skew = 121 slack = 60", set numofseconds in the two parameter files to 130. After doing this, Stop the Identity Manager Web Server. Then stop the Identity Server. Start the Identity Server.
Then start the Identity Manager Web Server. Start a new browser session and see if you get the same error.

Exchange rate is different between records in OB08 and records in document.

Hi Gurus,
The exchange rate is different between records in OB08 and records in calculated amount in line item. How does it happen? Not all of the documents in the same period has this problem.
For example, a document A created by FB05 on Jun 30 2010.
In OB08, the exchange rate is 6.80000. This rate was the same in the header of document A.
In the line item of doc A, I calculated the amount for line itme 1 and 2. Line itme 1 shows the exchange rate is 7.90000. Line item 2 shows the exchange rate is 16.0000. ( The exchange rate is not that exactly an interger. I put a similar exchange rate as an example.)
Could you please throw some light on these? Why some documents are okay but for some, the exchange rate is so different?
I just found that the exchange rate of some of the document line item calculated is from another currency. It shows in the line item (in question) button "More Data". Shall I know how the exchange rate was got from another currency exchange rate?
Thank you.
Emma
Edited by: qun yang on Aug 2, 2010 10:49 AM

Issue solved by below solution:
Existing:
      append lines of vit_final to s_s_if-maxsize to e_t_data.
      delete vit_final to s_s_if-maxsize.
    else.
      append lines of vit_final to s_s_if-maxsize to e_t_data.
      delete vit_final to s_s_if-maxsize.
New:
      append lines of vit_final to e_t_data.
      delete vit_final to s_s_if-maxsize.
    else.
      append lines of vit_final to e_t_data.
      delete vit_final to s_s_if-maxsize.

What is the different between payment methods Wire and EFT

Hi All
can anybody tell me What is the different between payment methods Wire and EFT ?
Regards ;

WIRE:
Wire is transfer of amount due directly to the supplier's bank it is an electronic transfer of funds
This mode of payment is used for international suppliers.
It can be paid in foreign currency or USD.
Wire payments are same day payments.
EFT:
EFT ensures funds transfer from one bank account to another using electronic links.
Can be used to make payments into domestic banks (within US) in USD only.
It is faster than check payments.
Hope this helps.

Connectivity between SAP ECC system and SAP BI

Connectivity between SAP ECC system and SAP BI
Hi BI-experts!
I would like to load e.g. transaction data from SAP ECC system into SAP BI system.
The Loading process is hanging in processing step u201CSERVICE APIu201D.
The process in hanging in status "yellow" and then changed after a while to status u201Credu201D.
[0FI_AR_4 |http://www.file-upload.net/view-1447743/0FI_AR_4.jpg.html ]
The following steps within Load process are yellow and then red:
Extraction (messages): Missing messages
Missing message: Request received
Missing message: Number of sent records
Missing message: Selection completed
Transfer (IDocs and TRFC): Missing messages or warnings
Request IDoc : Application document posted (is green)
Data Package 1 : arrived in BW ; Processing : 2nd processing step not yet finished
Info IDoc 1 : sent, not arrived ; Data passed to port OK
Info IDoc 2 : sent, not arrived ; Data passed to port OK
Info IDoc 3 : sent, not arrived ; Data passed to port OK
Info IDoc 4 : sent, not arrived ; Data passed to port OK
Subseq. processing (messages) : Missing messages
Missing message: Subseq. processing completed
DataStore Activation (Change Log) : not yet activated
Question:
Can some one tell me whether my distribution model or other settings are wrong?
I created 2 distribution model (BD64), one from SAP BW system and other from SAP BI system with message types RSRQST, RSINFO, RSSEND
Thank you very much!

Hi Holger.
this issue is related to the RFC but not the one which is communicating from BI to R/3 rather the one which is communicating from R/3 to BI follow these steps.
1. check your BI system logical name from the myself source system.
2. go the ECC and run the transaction sm59
3. go the ABAP Connection folder and search for your RFC which name would be by default as per your BI logical system name.
4. double click it and edit it now check whether the Target hostname or ip is OK.
5. In the logon tab check the client number User and password settings.
Save it and test it with both Connection Test and Remote Logon.
if every thing work fine i hope your problem will be solved.
kind regards,
Zeeshan

I want to create an app. Can you tell me the difference between iOS developer program and the mac developer program?

I want to create an app. Can you tell me the difference between iOS developer program and the mac developer program?
Is the difference the device you're creating your app on, or for?

iOS Developer Program is only for those who wish to develop iDevice apps. Mac program is for those only developing Mac applications. If you wish to do both, then you need to enroll in both programs.

How to Reconcile Data Between SAP Source Systems and SAP NetWeaver BI

Hi,
I just read "How to Reconcile Data Between SAP Source Systems and SAP NetWeaver BI". While I'm waiting for more authorisation to r/3 to carry it out and test this functionality.
I'd like to ask a question to anyone who has implemented this type solution. On page 10 it talks about creating a view then setting up the datasource. The solution talks about runnig a query. I suspect when we run a query I would run it for only a period(using variable) to reconcile.
My question is this. Will the datasource extractor on /r3 only select the period in our variable or will it do a full selection of the data which would then be passed to BW for filtering?
Regards

DEar Mark,
There are several avenues where you can see and reconcile your data with source system, u can see data in by tcode RSA3 for a datasource, and compare the values with actual document posted into the R/3 system. Respective fuctional consultant canhelp you a lot to confirm the data.
On BW side u can see the data in PSA and then check tranformations which subsequent change/update/reject data records based on the selective conditions.
hope this helps.
Kindly assign the points if it works.
Revert back if u need futher help/information.

VISA Write differs between TS Development System and LV Run-Time Engine

Similar Messages

Maybe you are looking for