LabVIEW DSC: Migration from 6.1 to 8.6 problems

Colleagues,
I need help from someone who experienced with LabVIEW DSC. I would like to recompile pretty old application written in LabVIEW 6.1/DSC 6.1 to LabVIEW 8.6, and got lot of troubles with this.
At the first I have tried to migrate my old scf file as described here: "Migrating from LabVIEW DSC 7.1 to 8.0".
Well, it seems to be OK, and LabVIEW.lvlib library with variables was created, but when I tried to double click on the some items, then exception occurred in LabVIEW (see dsc_exception.png in attachment).
Can you please open test project (attached to this post) and double-click on the Slave005_A0 Item? Is crash happened only by me or by someone else?
The second problem with understanding.
In LabVIEW DSC 6.1 I have used "Read Tag.vi" / "Write Tag.vi" vis for accessing the items. When my VI opened in LabVIEW/DSC 8.6, then these calls replaced with "legacy_Write_Tag_(analog)7x.vi" (see screenshot). I'm unable to found according VIs in DSC 8.6. How can I write/read my tags in the latest version? As far as I can understand, I can use Shared Variables directly. Is this correct? But then how can I read multiple tags? Through DataSocket VIs?
The same with "legacy_Get_Tag_List7x.vi". How can I get items list in DSC 8.6 programmatically?
Or should I leave all legacy* vis in my application?
thanks in advance and best regards,
Andrey.
Attachments:
dsc_exception.png ‏26 KB
dsc_legacy_Write_Tag.png ‏3 KB
TestProject.zip ‏4 KB

Hi Andrey,
Yes, my LabVIEW crashes as well. As you may have noticed, a lot has changed in LabVIEW 8.0 with regards to DSC, the most important being that tags are replaced with Shared Variables. I would recommend that you go through each variable and create them by yourself to ensure the most reliable performance.
If you are interested in reading 'tags', then you just need to drag the Shared Variable and place it on the block diagram (that's the direct way). If you are interested in doing this programatically, then have a look at the DSC Module -> Engine Control -> Variables & I/O Servers -> Get Shared Variable List palette on the block diagram. You can then use DataSocket to access the Shared Variables.
Don't leave the legacy VIs on your block diagram. Upgrade your whole project; shared variables are here to stay. Have a look at the following article to get a thorough understanding of them:
Using the LabVIEW Shared Variable
Let us know if you have more questions.
Adnan Zafar
Certified LabVIEW Architect
Coleman Technologies

Similar Messages

Migration from WLI2.0 to WLI2.1 - problems and solutions

We have experienced a number of issues when migrating from WLI2.0 (no service packs)
to WLI2.1 - We are only using the WLPI (BPM) part of WLI. We decided to publish
these issues in case they can be of help to others.
Problems:
1. The documentation (http://edocs.bea.com/wlintegration/v2_1/migrate/4zubemig.htm#998197)
says the migration process works from WLPI 1.2.1 and from WLI 2.0 (SP2, 3, 4).
What about WLI2.0 with no service packs - I don't see why BEA should have left
out migration from that platform. We decided to follow the process and see what
happened.
2. There is no indication in the documentation of how to run the GUI based migration
tools on Unix, only for Windows so we had to follow the manual route.
3. The Manual process refers (http://edocs.bea.com/wlintegration/v2_1/migrate/4zubemig.htm#999969)
to the DB variable setting scripts. It then says to run "migratedb.sh". None of
these files have extensions ".sh" - the files that were installed have no extension.
Obviously that did not stop us running them but the documentation needs correcting.
4. The migratedb scripts calls "WLI_HOME/setenv.sh" - it is confusing that there
is a second copy of this file in the bin folder called "setenv". Why are there
2 copies. Also I note that the one in bin is executable and the other is not.
All very confusing!!
5. The migratedb script fails to run because we have not previously run setDomain.
This is not documented.
6. Running setDomain on a domain moved from a WLI2.0 installaion fails since it
does not contain the expected folders. That basically means you cannot migrate
such a domain. We carried on with the process using the bpmdomain so that we could
at least migrate our database automatically.
7. Having run setDomain, we tried migratedb again but it failed because we had
not run switchdb. Again, this is not documented. We ran switchdb successfully.
8. Now running migratedb creates a file called "migrate.sh". Unfortunately the
script migratedb then attempts to run a file called "migrate". This is evidence
that no-one has ever tested this script at BEA and we are very disconcerted by
this fact!! We renamed the script and ran migratedb again - this time it ran the
migrate script.
9. This still fails with the following errors (when calling migrateCommonRep)
     -v (No such file or directory)
     null
     java.lang.NullPointerException
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:120)
     at com.bea.eci.migration.Migrate.getConnection(Migrate.java:207)
     at com.bea.eci.migration.Migrate.main(Migrate.java:73)
     java.lang.NullPointerException
     at com.bea.eci.migration.Migrate.main(Migrate.java:192)
10. It also fails because it cannot find "sqlplus" - a fatal problem - we do not
have sqlplus installed on the same machine as WLI and yet again this requirement
is not documented. At this point we gave up trying to run the migrate script as
there seemed to be no route forward.
The process we took to move from WLI2.0 (WLPI only) was as follows:
a. Since we had done no changes to filerealm.properties we simply copied the one
fron bpmdomain into our own domain.
b. We have been unable to run the step to migrate the common repository (see note
9). If this is referring to the XML repository then that should not be a problem
to us as we have not used it.
c. We moved the "migrate/BPM_20SP3-21.sql" script to an NT machine and ran that
script on our database. This seems to have successfully updated the database.
Lastly, having completed the migration process we tried to run the server but
it fails. This is because the startWeblogic script fails to call checkdomain properly.
We modified the line to become:
     ". $WLI_HOME/bin/checkdomain"     # the '.' was missing
Does anyone else have any experiences with this that would help us all?
Pete

Pete,
Please post this to the weblogic.integration.interest and weblogic.integration.developer newsgroups?
Pete Edwards wrote:
We have experienced a number of issues when migrating from WLI2.0 (no service packs)
to WLI2.1 - We are only using the WLPI (BPM) part of WLI. We decided to publish
these issues in case they can be of help to others.
Problems:
1. The documentation (http://edocs.bea.com/wlintegration/v2_1/migrate/4zubemig.htm#998197)
says the migration process works from WLPI 1.2.1 and from WLI 2.0 (SP2, 3, 4).
What about WLI2.0 with no service packs - I don't see why BEA should have left
out migration from that platform. We decided to follow the process and see what
happened.
2. There is no indication in the documentation of how to run the GUI based migration
tools on Unix, only for Windows so we had to follow the manual route.
3. The Manual process refers (http://edocs.bea.com/wlintegration/v2_1/migrate/4zubemig.htm#999969)
to the DB variable setting scripts. It then says to run "migratedb.sh". None of
these files have extensions ".sh" - the files that were installed have no extension.
Obviously that did not stop us running them but the documentation needs correcting.
4. The migratedb scripts calls "WLI_HOME/setenv.sh" - it is confusing that there
is a second copy of this file in the bin folder called "setenv". Why are there
2 copies. Also I note that the one in bin is executable and the other is not.
All very confusing!!
5. The migratedb script fails to run because we have not previously run setDomain.
This is not documented.
6. Running setDomain on a domain moved from a WLI2.0 installaion fails since it
does not contain the expected folders. That basically means you cannot migrate
such a domain. We carried on with the process using the bpmdomain so that we could
at least migrate our database automatically.
7. Having run setDomain, we tried migratedb again but it failed because we had
not run switchdb. Again, this is not documented. We ran switchdb successfully.
8. Now running migratedb creates a file called "migrate.sh". Unfortunately the
script migratedb then attempts to run a file called "migrate". This is evidence
that no-one has ever tested this script at BEA and we are very disconcerted by
this fact!! We renamed the script and ran migratedb again - this time it ran the
migrate script.
9. This still fails with the following errors (when calling migrateCommonRep)
-v (No such file or directory)
null
java.lang.NullPointerException
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:120)
at com.bea.eci.migration.Migrate.getConnection(Migrate.java:207)
at com.bea.eci.migration.Migrate.main(Migrate.java:73)
java.lang.NullPointerException
at com.bea.eci.migration.Migrate.main(Migrate.java:192)
10. It also fails because it cannot find "sqlplus" - a fatal problem - we do not
have sqlplus installed on the same machine as WLI and yet again this requirement
is not documented. At this point we gave up trying to run the migrate script as
there seemed to be no route forward.
The process we took to move from WLI2.0 (WLPI only) was as follows:
a. Since we had done no changes to filerealm.properties we simply copied the one
fron bpmdomain into our own domain.
b. We have been unable to run the step to migrate the common repository (see note
9). If this is referring to the XML repository then that should not be a problem
to us as we have not used it.
c. We moved the "migrate/BPM_20SP3-21.sql" script to an NT machine and ran that
script on our database. This seems to have successfully updated the database.
Lastly, having completed the migration process we tried to run the server but
it fails. This is because the startWeblogic script fails to call checkdomain properly.
We modified the line to become:
". $WLI_HOME/bin/checkdomain" # the '.' was missing
Does anyone else have any experiences with this that would help us all?
Pete--
Developer Relations Engineer
BEA Support

Migrate from Lightroom 3 to Aperture 3 - Problems with DNG

Hello : )
I will migrate from Lightroom 3 to Aperture 3. I've tested Aperture for a while and I like it, but I have one problem. If I import DNG files, I lost all the settings I've made in Lightroom, except Metadata. Is there any way to import DNG files and get all the settings? If not I think a migration to Aperture will not be possible to me, because I've over 50.000 DNG files and I don't want to convert them to tiff or other formats and lost all the benefits of the RAW files.
Thanks
derRabe

Look at the video below- I think it will solve your problem.
http://www.youtube.com/watch?v=7R4HgOZ3oBc

Migrating from NIS to JDS 6.3 - problems with addNISObject

I'm trying (again) to transfer our NIS maps to the LDAP server using the inityp2l command.
This seems to work. It sets up the NISLDAPmapping and the /etc/default/ypserv files, but when I run ypserv -Ir, I get the following errors:
Mar 30 15:45:14 sun34 ypserv[6260]: [ID 473756 user.error] addNISObject: ldapAdd error 32 (No such object) for (dn: dc=starfleet,dc=example,dc=com)
Mar 30 15:45:15 sun34 ypserv[6260]: [ID 473756 user.error] addNISObject: ldapAdd error 32 (No such object) for (dn: dc=com)
Mar 30 15:45:15 sun34 ypserv[6260]: [ID 556977 user.error] addParent: Unable to create parent (dn: dc=com) of (dn: dc=example,dc=com) in the DIT
Mar 30 15:45:15 sun34 ypserv[6260]: [ID 556977 user.error] addParent: Unable to create parent (dn: dc=example,dc=com) of (dn: dc=starfleet,dc=example,dc=com) in the DIT
Mar 30 15:45:15 sun34 ypserv[6260]: [ID 572537 user.error] Could not make nisDomain object for starfleet.example.com
Now, I've looked for the nis attributes in the LDAP server, and I can't find any. Do I have to manually add all of the nisObject classes? I used the ldapsearch command giveni n the following site here.
I still get nothing when I use the following command:
ldapsearch -b cn=schema objectclass=* | grep nisDomainObject Anyway, it looks like the LDAP server instance in JDS 6.3 doesn't include any nis object classes at all. Following the instructions in the documentation results in the errors above.
Interestingly, the errors log has the following entry (which leads me to assume that JDS 6.3 does not include nis object classes):
[30/Mar/2009:13:28:49 +0100] - ERROR<5894> - Schema - conn=10 op=1 msgId=2 - User error: Entry "dc=example,dc=com" has unknown object class "nisDomainObject"
Note that I had to add that objectclass myself.
Any ideas?
Thanks
Edited by: cannonac on 30-Mar-2009 15:53

You've done it again. I have to say, I'm new to this but I thought, and the documentation doesn't really give much of a clue, that idsconfig was meant fo iPlanet Directory Server 5.x, not JDS 6.x. That's why I hadn't done anything with it.
Thank you for all the help you've given me with this install. I'd be bald with frustration now if it wasn't for your help.
Andy

Migrated from VBAI to labview 8.2.

I’m fairly new at these vision programs and need some advise. I have migrated from VBAI to LabView 8.2. However I can’t seem to get the LV program to work like VBAI program works. The LV program gets stuck in a loop processing the same photo rather than the entire folder of 25. The other problems are: It will not show the photo; it will fail all photos, and will not log results.
I am running the LV 8.2, Vision Acquisition 8.2, and VBAI 3.0

Hi Davis,
I'm not experienced in VBAI and IMAQ, but in your code I couldn't find any function to load your JPG photos...
There's only an 'IMAQ Create' in the initialize-sequence, which generates an empty image. So it seems you have to attach your own code here ;-)
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

What are the steps necessary to create an EXE using LabVIEW DSC ?

I´m developing an application in LabVIEW 7.0 using the LabVIEW DSC 7.0 Toolkit. I´d like to know the steps I should take to cretae an EXE for this application.

There is information regarding building a LVDSC .exe at
http://zone.ni.com/devzone/conceptd.nsf/webmain/2f7cf918f3b412db86256a1c006af25f?OpenDocument
It's from the time of LV6, but contains some useful info.
=====================================================
Fading out. " ... J. Arthur Rank on gong."

LabView DSC, RSLinx, SLC505 and Data transfer (Best way for large blocks of data?)

I am currently programming in Labview 6.1 with the Datalogging and
Supervisory Control module to transfer 720 floating point numbers to a
SLC505 Allen Bradley PLC (with ethernet) using RSLinx as an OPC server. I
have found that using the Datasocket Write takes about 30 - 40 seconds, and
making the tags and writing to them takes about the same amount of time. Is
it possible to transfer this data faster?
Thanks,
Michael Thomson (Surcher)

Cyril,
I was just experimenting with different ways to transfer the data from the
computer to the PLC. In the past I have built large tag databases with
specific tag names. This made the code rather cumbersome when you wanted to
write to a large group of tags with descriptive names. I was just using
datasocket write as a way to transfer the data to the plc using code to
build the url and without having the DSC engine running. I have found that
importing the tags right from the tag configuration editor with the names
being simply the PLC addresses and then accessing them with the tag write is
considerably faster (under 5 seconds). I can then build the names in an
embedded for/next loop and change them to a tag name before I write to each
one. The appli
cation is a user interface that allows the machine operator
to pick what kind of arch to put on cabinet door part. With the selections
chosen I calculate the servo moves and download the data to the PLC.
Thanks for the link!
Michael Thomson
"Cyril" wrote in message
news:[email protected]..
> Michael,
>
> I am a little bit confused about the configuration here and the
> programming here: why are you using Datasocket Write if you are using
> tags? Are the 720 floating numbers written to 720 different I/O
> Points(registers). If so this shouldn't be that slow especially with
> DSC
> I would strongly encourage you contact the support at National
> Instruments for LabVIEW DSC, either by phone or e-mail and give a
> detailed description of the issue:
> www.ni.com/ask, and communication method phone NI or e-mail NI.

Has somebody already used Applicom PCI2000ETH Card or Applicom SW1000ETH software to communicate with ETHERNET bewteen siemens s7-300 and LabVIEW DSC ?

I want to use ETHERNET and not PROFIBUS to communicate and I think you can do that with only the applicom software SW-1000ETH. You must just have an ethernet card on your PC. So, you could use a notebook with an
ethernet card. You can also use Applicom PCI2000ETH for better performance.

Hi,
You might be able to get the configuration listed above working as long as you can get from Siemens/Applicom or any other third party provider a OPC Server that communicates with the S7-300. Since LabVIEW DSC is a OPC client, you would be able to establish connection.
The National Instruments driver for the S7-300 (Containnned in the product called "IA OPC Server CD") does not support communication through ethernet directly, you would either have to have a Profibus board or use a serial port with a Siemens HMI Adapter.
I hope it helps
Best Regards
Andre Oliveira

What is the best way to put LabVIEW DSC data into an Oracle database?

I have been collecting data using LabVIEW DSC 7.0 for several years and have always accessed the data from the Citadel database via the Historical Data Viewer. I would now like to begin putting this data into an Oracle database. My company stores all their data in Oracle and it would provide me all the benefits of their existing infrastructure such as automated backups, data mining tools, etc.
My initial thought is to use "Read Trace.vi" in LabVIEW to pull historical data from the citadel database at regular intervals (e.g. 1 minute) and insert this data into Oracle via ODBC. In this way, I do not need to track the value changes in order to know when to write to Oracle. I also considered replicating the citadel database using some other method, but I recall that the tables used by citadel are somewhat complicated. I only need a simple table with columns for channel, timestamp, and data. The "Read Trace.vi" will provide me data in this format.
I do not need to update the Oracle database in real time, a few minute delay is acceptable. If anyone has a better idea or additional insight please let me know. Thanks.

In terms of connectivity, you want to use ADO, not ODBC. Beyond that, it all depends on the structure of the data and what you are going to want to do with it. This is a very big question that you need to be getting some in-depth assistance.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Migration from Serial polling to Serial queue with event handler

Hi, I am trying to migrate from classical serial polling communications to serial queue with "event handler" for the buttons pressed by the user. I have placed four while loops, one for the event handler, a second one for serial reading, a third one for serial writing (depending on what button was pressed) and the last one for processing what was read from the serial reading while loop, via a queue.
My attached device reads the signals from 8 sensor ( 4 temperature and another 4 temperature plus humidity in the same sensor ) and send them via serial to Lavbiew.
First of all, only once just after running the LV program, I must turn on my attached device with an ON command plus a carriage return after that the device will respond with the number of sensors plugged to it, disabling the corresponding buttons in the front panel. Then labview must wait until I pressed Acquire Button (event handler) and send a CF command plus what sensors to acquire plus a carriage return, then the device will respond continuously to labview with the sensor readings until I press the stop button (event handler), there is also another button to exit the program, also with event handler.
I am having problems using the event handler and the queues because I am new using these structures, I have looked at the LV examples but there is nothing concrete on using serial with event handler and queue.
Take a look at my VI and you will soon notice what kind of problems I am having, any suggestions will welcome.
Thank's in advance.
Regards.
Attachments:
serial queue.zip ‏76 KB

Hi Luisete,
Maybe the problem arise because you are En- and DeQueue in parallel. You do a lot of things in parallel, that is nice if you are sure that one loop doesn't have to wait for another loop. Make sure you don't dequeue before enqueue.
Hope this helps
I never knew that the standard error cluster output could be wired directly to the loop control of a while loop.
First time I see this

"History of Labview DSC"

Where I can find out more information on the history of Labview DSC? I would like to know when the module was developed and the reasons for its development.

It came from BridgeVIEW.
LV started growing out and greatly over-lapped BV functions. The dev of the two was stream'lined and DSC was introduce soon after LV 6.0.
Just to get started,
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Does LabVIEW DSC 8.5 support Windows Server 2008?

Hi,
I am developing a SCADA system using LabVIEW DSC 8.5. Apparently, customer wants the Server Computer to be latest Windows Server 2008 operating System.
But the Release and Upgrade note specify that DSC Module does not support Windows NT/Me/98/95/Server 2003. (System Requirement section)
Does it support Windows server 2008?
Any feedback most appreciated.
Message Edited by Vsh on 09-28-2009 08:56 AM

Hi Vsh
Sadly no version of LabVIEW (and therefor no modules like DSC either) officially supports Server 2008. That has however not stopped people from trying and I've seen both cases were it has worked fine and cases were it has not worked. This thread might be of interest to you.
Best Regards
David
NISW

Labview dsc client server

Hi,
I use LV7 and labview dsc.
I would like to read historical traces from a client PC. my database is saved on a server PC. I'm using "Read Traces.vi". It works well but i have to wait 10 or 20 seconds to have results (for only 100 points).
I have no problem for reading tags in real time but it is very too slow for reading historical data.
I would like to know if there is a solution to minimise time for echanging historical data.
Thanks.
Alexis de la fontaine
SECMAI

Hi Alexis,
Are you observing the same delay with Read Traces.vi when you read traces locally? 100 points means 100 I/O points (tags) ?
Remzi A.
Applications Engineering
National Instruments

LabView / DSC / FieldPoint with Symantec Endpoint Encryption Device Control

I am developing a LabView DSC based control program to communicate with multiple FieldPoint modules (cFP2200/cFP1808) for a client. Their IT department has implemented Symantec Endpoint Encryption Device Control ( http://www.symantec.com/endpoint-encryption-device-control ) and I was wondering if anyone has had experience with this software?
From what I have read and had explained to me, it is much more than an antivirus program. It operates at a very low level within Windows and restricts reading/writing to external devices, USB sticks, network shares, etc. It can also monitor / restrict network traffic and WiFi access.
Thanks,
Steve

Hi MillerMech,
I believe it will cause some errors to be thrown due to its restrictive nature. Symantec has a discussion forum which will most likely be more helpful:
http://www.symantec.com/business/support/index?page=home
Sunaina K.
Product Manager
Embedded Systems

LabVIEW DSC installation problems

Hello,
I'm trying to install LabVIEW DSC 6.1 but when I launch setup.exe file this message pops up:
"Unable to load ini file. Windows Error 1157"
I have Labview 6.1 installed and my OS is Windows 2000 with Service Pack 4.
Any feedback will be wellcome.
Thanks in advance.
Jose.

Hello Jose,
I haven't ran into that issue and I'm not sure about its cause and solution, but here are some ideas on what you could try/check (they are separate ideas, not a sequence of steps):
-Login as administrator to install the software
-Make sure your PC has enough memory and free space on the HD
-Copy the content of the CD to the HD, and run the installer from there
-Modern installers have setup.exe and setup.msi launchers, try to execute the .msi instead of the .exe
-Reinstall LabVIEW 6.1 and then DSC (before that, make a backup of any custom vi's/files that may be overwritten/removed, and then uninstall LabVIEW from Control Panel->Add/Remove Programs ..Agregar y quitar programas))
If none of these helps, let me know.
Regards,
JorgeM.

LabVIEW DSC: Migration from 6.1 to 8.6 problems

Similar Messages

Maybe you are looking for