DSC problem

Like in a subject, I have a problem instaling and using DSC module for LV.
This problem is the same on versions from 8.0 to 8.5, because I tried them all.
1. When I try to install DSC over regular LV, everything goes well with the installation until reboot.
2. After rebooting at the end of installation (on a first windows start after installation), I am getting error message on MSDE Setup (picture in attachment), related with administrator account on my computer. Yes, I am doing all of this with admin account.
3. When I try to manually execute msdesetup.exe, like it's suggested in previous message, I am getting another error message that says "Error while lounching MSDE setup!".
4. Then, DSC have such behavior that it crashes when I try to deploy shared variables.
Any suggestions, please?
Thnx in advance!
B.

Hi B.
I would suggest going though all the steps under the Resolution heading in the previous KB. These steps should fix the issue with the registry and solve the errors you are seeing.
SQL Server Express is available on the DSC Setup CD/DVD that you have. It will be under Products » SQLServerEx.wrap.msi. If you can't find it, you can also get it from here.
Let me know if this helps.

Similar Messages

Problem with dsc shared shared variables and error 1950679023

I'm having trouble using shared variables on my laptop PC (with Windows XP) using Labview 8.2 and DSC. I've set up a simple project with one VI and one shared variable library. In the VI, I have a while loop that writes a number from a front panel control to the shared variable. Another loop running in parallel reads the shared variable and displays to an indicator on the front panel. The VI resides on my PC (no remote targets). This program executes just fine on my desk top PC; however I get the following error codes out of the shared variable nodes when I run the project and VI on my laptop for the write and read, respectively: ni_tagger_lv_Write 180121604 ni_tagger_lv_Read -1950679023 I've tried to manually deploy the shared variable library without success. The NI knowledge base and other entries on this forum suggested that the Windows firewall should be disabled for a quick fix, however, the firewall was already disabled on my lap top. I didn't see any entries regarding the 180121604 error code.
Any suggestions would be appreciated.

The problem has mysteriously gone away. For about the 10th time, I manually deployed the share variable library, and it started to work properly.

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

Render Service Problem - Root Cause ALC-DSC-127-000

I have decided to write a Form Guide renderer instead of using one from the Samples. The renderer process was created by carefully observing the one in the samples. After creating the renderer, I activated it and used it in my process. In the livecycle workspace, when I try to access the initialization task, A popup error shows up. Looking at the logs revealed the following error/exception:
exception: flex.messaging.MessageException: ALC-WKS-005-028: A problem occurred in the Render Service. Please review the render orchestration for this process.
2007-12-26 13:34:23,190 INFO [STDOUT] [Flex] Exception when invoking service: remoting-service
with message: Flex Message (flex.messaging.messages.RemotingMessage)
operation = render
clientId = 60F1A10E-C009-251A-6C47-179779FEB2B7
destination = task-actions
messageId = F65756D8-8D22-85D3-598E-17BBDA529B7E
timestamp = 1198694062784
timeToLive = 1198694062784
body = null
hdr(DSEndpoint) = workspace-polling-amf
hdr(DSId) = 60F1373F-590F-5AC8-B6A5-1296C747EA45
exception: flex.messaging.MessageException: ALC-WKS-005-028: A problem occurred in the Render Service. Please review the render orchestration for this process.
2007-12-26 13:34:23,377 INFO [STDOUT] [Flex] [ERROR] Root cause: ALC-DSC-127-000: com.adobe.idp.dsc.LongLivedInvocationException: The Long Lived Service i3Renderer can not be invoked synchronously.
at com.adobe.idp.dsc.routing.Router.routeRequest(Router.java:76)
at com.adobe.idp.dsc.provider.impl.base.AbstractMessageReceiver.routeMessage(AbstractMessage Receiver.java:88)
at com.adobe.idp.dsc.provider.impl.vm.VMMessageDispatcher.doSend(VMMessageDispatcher.java:21 0)
at com.adobe.idp.dsc.provider.impl.base.AbstractMessageDispatcher.send(AbstractMessageDispat cher.java:57)
at com.adobe.idp.dsc.clientsdk.ServiceClient.invoke(ServiceClient.java:208)
at com.adobe.idp.taskmanager.dsc.service.TaskManagerServiceImpl.renderForm(TaskManagerServic eImpl.java:3404)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.adobe.idp.dsc.component.impl.DefaultPOJOInvokerImpl.invoke(DefaultPOJOInvokerImpl.jav a:181)
at com.adobe.idp.dsc.interceptor.impl.InvocationInterceptor.intercept(InvocationInterceptor. java:134)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:44)
at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor$1.doInTransaction(Transa ctionInterceptor.java:74)
at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.execute(EjbTr ansactionCMTAdapterBean.java:336)
at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.doRequiresNew (EjbTransactionCMTAdapterBean.java:282)
at sun.reflect.GeneratedMethodAccessor258.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.invocation.Invocation.performCall(Invocation.java:345)
at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionConta iner.java:214)
at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionI nterceptor.java:149)
at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstance Interceptor.java:154)
at org.jboss.webservice.server.ServiceEndpointInterceptor.invoke(ServiceEndpointInterceptor. java:54)
at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:48)
at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:106)
at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:

Hi Gary,
I am getting following error message, can you pls help me with this
Mar 26, 2008 5:25:53 PM com.adobe.workspace.processes.ProcessActions getProcessInstance
WARNING: ALC-WKS-005-059: An error occurred while retrieving the list of process instances for process "Process Packages".
[Flex] Exception when invoking service: remoting-service
with message: Flex Message (flex.messaging.messages.RemotingMessage)
operation = getProcessInstance
clientId = DA923519-C11F-EDFE-A537-D10A27A3FA00
destination = process-actions
messageId = A9726928-7AEA-8308-B7C4-ECFB90EFA472
timestamp = 1206566753361
timeToLive = 1206566753361
body = null
hdr(DSEndpoint) = workspace-polling-amf
hdr(DSId) = DA8DF62D-CD1E-2718-618C-0902E3DF178A
exception: flex.messaging.MessageException: ALC-WKS-005-059: An error occurred while retrieving the list of process instances for process "Process Packages".
[Flex] [ERROR] Exception when invoking service: remoting-service
with message: Flex Message (flex.messaging.messages.RemotingMessage)
operation = getProcessInstance
clientId = DA923519-C11F-EDFE-A537-D10A27A3FA00
destination = process-actions
messageId = A9726928-7AEA-8308-B7C4-ECFB90EFA472
timestamp = 1206566753361
timeToLive = 1206566753361
body = null
hdr(DSEndpoint) = workspace-polling-amf
hdr(DSId) = DA8DF62D-CD1E-2718-618C-0902E3DF178A
exception: flex.messaging.MessageException: ALC-WKS-005-059: An error occurred while retrieving the list of process instances for process "Process Packages".
[Flex] Root cause: com.adobe.idp.taskmanager.dsc.client.query.TaskQueryServiceException: com.adobe.pof.schema.AttributeNotFoundException: Attribute: creator_id does not exist on object-type: workflow.pt_process packages.
at com.adobe.idp.taskmanager.dsc.queryservice.TaskManagerQueryServiceImpl.processSearch(Task ManagerQueryServiceImpl.java:730)
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.adobe.idp.dsc.component.impl.DefaultPOJOInvokerImpl.invoke(DefaultPOJOInvokerImpl.jav a:181)
at com.adobe.idp.dsc.interceptor.impl.InvocationInterceptor.intercept(InvocationInterceptor. java:134)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:44)
at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor$1.doInTransaction(Transa ctionInterceptor.java:74)
at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.execute(EjbTr ansactionCMTAdapterBean.java:336)
at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.doSupports(Ej bTransactionCMTAdapterBean.java:212)
at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapter_z73hg_ELOImpl.doS upports(EjbTransactionCMTAdapter_z73hg_ELOImpl.java:67)
at com.adobe.idp.dsc.transaction.impl.ejb.EjbTransactionProvider.execute(EjbTransactionProvi der.java:104)
at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor.intercept(TransactionInt erceptor.java:72)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:44)
at com.adobe.idp.dsc.interceptor.impl.InvalidStateInterceptor.intercept(InvalidStateIntercep tor.java:37)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:44)
at com.adobe.idp.dsc.interceptor.impl.AuthorizationInterceptor.intercept(AuthorizationInterc eptor.java:80)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:44)
at com.adobe.idp.dsc.engine.impl.ServiceEngineImpl.invoke(ServiceEngineImpl.java:113)
at com.adobe.idp.dsc.routing.Router.routeRequest(Router.java:102)
at com.adobe.idp.dsc.provider.impl.base.AbstractMessageReceiver.routeMessage(AbstractMessage Receiver.java:88)
at com.adobe.idp.dsc.provider.impl.vm.VMMessageDispatcher.doSend(VMMessageDispatcher.java:18 3)
at com.adobe.idp.dsc.provider.impl.base.AbstractMessageDispatcher.send(AbstractMessageDispat cher.java:57)
at com.adobe.idp.dsc.clientsdk.ServiceClient.invoke(ServiceClient.java:208)
at com.adobe.idp.taskmanager.dsc.client.TypedTaskManagerQueryService.processSearch(TypedTask ManagerQueryService.java:245)
at com.adobe.workspace.processes.ProcessActions.getProcessInstance(ProcessActions.java:174)
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Unknown Source)
Caused by: com.adobe.pof.schema.AttributeNotFoundException: Attribute: creator_id does not exist on object-type: workflow.pt_process packages.
at com.adobe.pof.schema.POFAbstractObjectType.getAttribute(POFAbstractObjectType.java:177)
at com.adobe.pof.omapi.POFDefaultQuery.projectAttribute(POFDefaultQuery.java:634)
at com.adobe.idp.taskmanager.dsc.queryservice.TaskManagerQueryServiceImpl.processSearch(Task ManagerQueryServiceImpl.java:627)
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.adobe.idp.dsc.component.impl.DefaultPOJOInvokerImpl.invoke(DefaultPOJOInvokerImpl.jav a:181)
at com.adobe.idp.dsc.interceptor.impl.InvocationInterceptor.intercept(InvocationInterceptor. java:134)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:44)
at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor$1.doInTransaction(Transa ctionInterceptor.java:74)
at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.execute(EjbTr ansactionCMTAdapterBean.java:336)
at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.doSupports(Ej bTransactionCMTAdapterBean.java:212)
at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapter_z73hg_ELOImpl.doS upports(EjbTransactionCMTAdapter_z73hg_ELOImpl.java:67)
at com.adobe.idp.dsc.transaction.impl.ejb.EjbTransactionProvider.execute(EjbTransactionProvi der.java:104)
at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor.intercept(TransactionInt erceptor.java:72)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:44)
at com.adobe.idp.dsc.interceptor.impl.InvalidStateInterceptor.intercept(InvalidStateIntercep tor.java:37)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:44)
at com.adobe.idp.dsc.interceptor.impl.AuthorizationInterceptor.intercept(AuthorizationInterc eptor.java:80)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:44)
at com.adobe.idp.dsc.engine.impl.ServiceEngineImpl.invoke(ServiceEngineImpl.java:113)
at com.adobe.idp.dsc.routing.Router.routeRequest(Router.java:102)
at com.adobe.idp.dsc.provider.impl.base.AbstractMessageReceiver.routeMessage(AbstractMessage Receiver.java:88)
at com.adobe.idp.dsc.provider.impl.vm.VMMessageDispatcher.doSend(VMMessageDispatcher.java:18 3)
at com.adobe.idp.dsc.provider.impl.base.AbstractMessageDispatcher.send(AbstractMessageDispat cher.java:57)
at com.adobe.idp.dsc.clientsdk.ServiceClient.invoke(ServiceClient.java:208)
at com.adobe.idp.taskmanager.dsc.client.TypedTaskManagerQueryService.processSearch(TypedTask ManagerQueryService.java:245)
at com.adobe.workspace.processes.ProcessActions.getProcessInstance(ProcessActions.java:174)
[Flex] [ERROR] Root cause: com.adobe.idp.taskmanager.dsc.client.query.TaskQueryServiceException: com.adobe.pof.schema.AttributeNotFoundException: Attribute: creator_id does not exist on object-type: workflow.pt_process packages.
at com.adobe.idp.taskmanager.dsc.queryservice.TaskManagerQueryServiceImpl.processSearch(Task ManagerQueryServiceImpl.java:730)
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.ad

Preview Problem for DSC 2.0 files in CS4

I'm having problems getting a preview for a file created in Adbobe PSCS4. The file is a Multi-channel using spot colors. The file was created new by going from a blank RGB straight to Multi-channels and spot colors assigned to each channel with an additional 4th channel. File was saved including 8 bit preview and a single file with color composite. When placed into Illustrator CS4 I get a solid black area. When imported to Windows Illustrator CS3 the preview is soon as expected.
Also there are problems printing DSC 2.0 placed files for color separations. In windows cs3 I have to copy the DSC 2.0 to a new document in order to do color separations using PowerRIP ImageSet as the print driver. I don't do color seps on Mac with CS4 since I only have a windows license at this time for the RIP.

After further testing I've found out what the reason is for the black rending in CS4 Illustrator.
When rending DSC 2.0 within Illustrator CS4 for a preview, it doesn't calculate the opacity of each channel. I use the first channel to render my substrate color, my original file had a pure black for my substrate. Then I calculate the opacity of Inks being used on the other channels. This is a major bug for me. I have no idea what Illustrator will do if my first channel in the DCS 2.0 is something other than Black, I haven't tried yet.

Our picture transfer from iphone, ipads and or Sony DSC-W150 camera ended when we changed int providers from xfinity to frontier. All attempts to troubleshoot have not corrected problem, HELP!!

Our picture transfer from iphone, ipads and or Sony DSC-W150 camera ended when we changed int providers from xfinity to frontier. All attempts to troubleshoot have not corrected problem. The only changes to the system that was functioning properly are Fios int service and router. All apple components are using the fios router. Can anyone Help get us up and running again? Thanks

How have you been making the physical connection from:
iPhone
iPads
Sony DSC-W150 camera
...to your Mac?
If WiFi, have you changed the WiFi encryption method or WiFi password? If so, each device need the new information netered into it manually to get onto your "new" WiFi Network.

Problem installing DSC 8.2.1 module

I am trying to install the DSC module for 8.2.1 on my home PC. I had no problems installing it on my development PC at work overtop of 8.2. But on my home PC I get the following dialog (in the .png file) after the machine spends a long time (~5 minutes) in its "wait for the installer to initialize" phase. If I click on the details button, I get additional information as shown in the .txt file.
I went back and uninstalled DSC module for 8.2 and tried again, but get the same results.
Any ideas?
Thanks,
Bill
Attachments:
DSC8.2.1 install error.PNG ‏32 KB
Details.txt ‏2 KB

Hi Centerbolt,
I discovered the problem.
First, disabling the firewall and antvirus did not help.
Second, I looked for DSC module on NI's website but could only find 8.2 and not 8.2.1 to download.
Third, I looked to copy over the CD to my harddrive. I opened the directory and saw the Products folder, I decided to look in there. It seemed very slow to browse. Finally, I saw the Portable_Configuration folder in there, it took a very long time to try to open, then came up with an error that it was not accessible or else something about "incorrect function". Some other directories would open, but were slow to do so. So now I know why the initialization took so long and ultimately failed, Windows had a hard time accessing the folders. Also, through all of this, the CD drive did not sound like it was spinning up properly.
I moved the CD over to my other drive to try it there in case the problem was with my drive. I had no problems installing the software from there. Browsing the folders was reasonably quick. After installing, I moved it back to the first drive and made sure all smudges were wiped off. I still had problems.
For whatever reason, that CD had a problem that my primary CD drive was sensitive to. I've never had problems with other CD's in that drive, or that particular CD in other drives. What is interesting, looking at the back of the CD, there is a difference in color between the inside and outside that looks kind of like a burned CD-R or CD-RW disc would except in silver rather than blue, and except that be circular, this pattern has kind of a oblong lobe and is oddly shaped.
Anyway, my problem is solved. I think I have a marginal CD that did not work very well in that one drive, but wasn't a problem in a couple other drives.
Thanks for your help. It put me down a path that got me the answer.

I purchased Lightroom 5, loaded it on my Mac, and updated to version 5.6. I then tried importing photos from my Sony DSC-RX100iii. Unfortunately it only imports JPEG files but no RAW files. What is the problem and how do I fix it?

I purchased Lightroom 5, loaded it on my Mac, and updated to version 5.6. I then tried importing photos from my Sony DSC-RX100iii. Unfortunately it only imports JPEG files but no RAW files. What is the problem and how do I fix it?

Than LR should have brought in the RAW files as well. ACR is the RAW
processing engine used by LR under the covers so anything not supported by
ACR would not be supported by Lightroom.
Are you shooting RAW plus JPEG? By default, Lightroom will stack then
unless you tell it not to. Check to see if there is a small badge on the
preview that looks like two sheets of paper with a number. That is how
Lightroom indicates a stack. You can unstack them by clicking on the badge.
There is also a menu item to stack/unstack photos. Otherwise, I would have
to research but not sure why Lightroom would ignore the RAW photos but
still import the JPEGS.

DSC runtime engine problems

Hi,
I recently started a project which involves DSC runtime engine. This being my first contact with runtime engines, i obviously ran into some problems. Hope someone can shed some light. Here goes: I developed a project on my work laptop on which I have LV / DSC 8.6 installed. The project is then built into an EXE application and then run on a desktop computer with DSC runtime engine.The desktop computer receives data from a PLC through an OPC server (which is not NI OPC server). At first, I imported a csv file containing the list of variables in my project with the correct path of the OPC server from the desktop. When I ran the EXE application on the desktop, I got an error (PSP Led was red) saying that the variables could not be read / written. This was because the variables were not declared in the Distributed System Manager. And so my first question is this: is there a way to import my list of variables from a csv file or something similar, and if so, how can i achieve this? Because so far, all I was able to do was to manually enter only one variable at a time in the Distributed System Manager, and after about 50 of them I decided I would really hate to enter almost 800...
My next question regards the Citadel Database. As I told you before, I entered a few variables in the system manager and played with them for a brief amount of time. I set them T / F, I got the correct readings from OPC server, my PLC leds light up, the works. Now I wanted to see my actions in the Citadel DB, but when i ran MAX, there was no Citadel DB, only Default DB, and I could not find any of those variables which I entered and chaged states. Is there a problem with the Citadel DB not showing up? Am I not declaring correctly the variables in the System Manager? (i followed the help directions to the letter). Anyone has an idea as to why I cannot see the varaibles in my DB?
And now for a final problem.. In the LV front panel, i have some boolean buttons which are set to switch when pressed Mechanical Action. When I have the PLC connected sometimes when I press a button, it remains stuck on the TRUE state, thus screwing up my logic scheme (e.g. for a feed mill conveyor motor I have two buttons - start, stop. If i sometimes press the start button and it gets stuck, i can no longer SHUT DOWN that conveyor, which is really a big problem. I found a so-called 'fix' - right click on the stuck button and select Reinitialize to default value, but I was looking for an answer to understand this problem, not a silly little fix).
Hope I have been clear enough and you have not got tired of reading so much,
Cheers,
Sabin

Hi Andrew and thanks for the reply!
I don't think I deployed the library file, because I didn't know exactly how to do it. In the Source Files Property Page on Build Specifications I only selected VIs. I never selected lvlib files, so this may be the case. On the Source File Settings I saw that .lvlib files had the property Include if referenced and I thought that was the property which deployed the library. I will change the build specifications at once and keep you updated, but it could take 1 or 2 more days, because the computer with DSC runtime is in another city, and I have to get there first maybe tomorrow.
I have several buttons set on Mechanical Action Switch Until Released. They are all Shared Variables which are connected through OPC server to memory locations in the PLC CPU. In my LV Block Diagram, they are NOT connected to anything. They are just located in a While Loop, to get their state. The preffered action is that when I press a button on my Front Panel, I get to change a memory location in my PLC and then something happens in Ladder Logic. So, the boolean values are just there, in my Block Diagram, alone and not connected to anything. Do you have an idea as to why I get that kind of behaviour (I mean the buttons get stuck on True state)?
And finally, someone told me that the Citadel 5 might be missing because of incorrect option checking at install. However, I remeber that on the desktop, I installed the DSC runtime engine FULL INSTALL, I mean I checked each and every tick box, everything, examples and the like. One thing I was told was to insert the install CD once again and perform a re-install. I will of course try this, but let's not consider this for a second. Do you have another idea as to why the Citadel DB wouldn't show up?
And no, in the EXE Build Specifications, I did not check the option Enable Enhanced DSC Run-Time support. What does it do? Could you please elaborate?
Looking forward to your answer,
Sabin

Video import problems from a Sony DSC-HX9V

Hey There
I have a Sony DSC-HX9V which I've owned for several months now, a Intel based MBP and iMovie 11.
Something strange is cooking and I wonder if anyone could let me have some suggestions of how to solve the issue?
In the past both iPhoto and iMovie has had no problems at all recognizing the camera and downloading photos and video files. I've created projects, burnt DVDs all the normal stuff.
This afternoon though a problem has arisen. Although iPhoto is letting me download photos from the camera, iMovie I guess is not "seeing" the camera. I've done exactly what I think I usually do, but this time its not working. When you click on "Import from camera" the window opens up but only the iSight camera is being used. I've clicked the "camera" drop down but again only the iSight camera is an option.
I've made sure all of my software is updated, no problems there, turned the camera off, turned the MBP off and on numerous times, but still it won't see the camera.
I've spent the last few hours trolling through various posts, even tried shooting video in all of the different quality grades available on the camera, just to make sure, but still nothing.
This Sony camera is definitely compatible with iMovie 11, again I've check and as I mentioned before, I've used it several times in the past.
Any suggestions would be warmly received.
David

I found this link helpful, I'm going to change the camera settings to 60i from 60p as on post mentions and will report the results http://forums.dpreview.com/forums/readflat.asp?forum=1009&message=39416949&chang emode=1

Probleme LabVIEW - module DSC / OPC

Bonjour,
j'utilise LabVIEW 2010 avec son module DSC.
Et je souhaite accéder à des variables OPC en Lecture et Ecriture depuis une application labVIEW.
Le serveur OPC que j'utilise fonctionne correctement (j'ai également fait le test avec le serveur de NI, mais le resultat est identique). Je peux lire et ecrire des variables avec 'OPC Quick Client'
J'ai configuré la connexion DCOM avec une "identité" : 'Utilisateur interactif'
Cependant depuis le projet LabVIEW, la creation des variables partagees ne fonctionne pas (Create Bound Variables) (cf. piece jointe)
J'ai suivi la note : Connect to Any PLC using OPC (lien : http://zone.ni.com/devzone/cda/tut/p/id/7450)
? Est-ce que quelqu'un a deja rencontré ce probleme et surtout trouvé une solution ?!?!?!???
Dans l'attente et en vous remerciant d'avance pour votre aide
<Nicolas>
Attachments:
CreateBoundVariables.JPG ‏40 KB

Hello,
J’ai trouvé une solution mais est-ce la bonne ?!? en tout cas, elle fonctionne.
J’ai préalablement ‘configuré’ le gestionnaire de système distribué (accessible à partir du menu : Tools \ Distributed System Manager) :
- Je crée/J'ajoute un nouveau Processus à "Mes systèmes \ local Host \" , nommé OPC (avec les paramètres par défaut)
- J’ajoute à ce processus un serveur d’E/S
- Je configure ce serveur pour qu’il accède à mon serveur OPC avec les paramètres qui vont bien.
- Et j’accède aux Items …
( Ce processus apparaît également sur les éléments du réseau )
- J’enregistre tout ça... je ferme ... et je reviens au projet
Donc ensuite, depuis le projet, je suis la procédure Connect to Any PLC using OPC
(lien : http://zone.ni.com/devzone/cda/tut/p/id/7450
Il faut alors juste préciser dans la fenêtre de configuration "Create Bound Variables" :
Browse source = Network Items
Et ensuite je peux sélectionner des variables partagées, (des items de mon serveur OPC) en naviguant dans son arborescence.
La note de Thomas B. décrite ci dessus fonctionne très bien, mais nécessite également (dans mon cas) la configuration du gestionnaire de système distribué.
<NBA>

Problema instalando el Modulo DSC

Tengo un problema instalando el modulo DSC (Datalogging and Supervisory Control Module) en LabVIEW 8.5 anexo una imagen con mi poblema.
Alguna ayuda se los agresco de antemano.
Solved!
Go to Solution.
Attachments:
Dibujo.JPG ‏50 KB

Hola,
       La pantalla que muestras es la misma que cuando instalo el DSC RTS (Run Time Systems) que es la version para correr los ejecutables, que te instala ademas del RTS convencional las base de datos SQL y Citadel, y componentes propios del DSC.
       Me parece que estas tratando de instalar el DSC RTS sobre una máquina que tiene la suite de Desarrollo de LabVIEW y por eso el problema.
       El DSC RTS lo deberias instalar sobre una máquina sin LabVIEW.
       Por otra parte si lo que deseas es instalar el DSC sobre la suite de desarrollo debes usar son los DVDs, ya que el CD adicional es del RTS como te comente. Bueno asi lo tengo yo, espero te sea de ayuda.
Saludos Cordiales,
Luis A. Mata C.
Ing. Electrónico
Anaco - Venezuela

Problem while using camera connetor and Sony DSC-M1

Dear all
My digital Camera Sony DSC-M1 is able to take pictures and take video into mpeg4 format .
this is the revirew of this camera
http://www.steves-digicams.com/2004_reviews/m1.html
However, I got a problem while using this camera with iPod +Camera connector.
When I plug this camera into camera connector , ipod will transfer all photo from the camera , but do nothing with the video.
I guess that problem is the video file is not inside the "/DCIM" folder
All video file ( *.mp4 ) are all in the folder named " /MP_ROOT/101MNV01/ "
Can anyone help me how to make this sync from camera to ipod automatically both photo and video ?
This problem also bother me while I am using iPhoto to transfer the file when I was home .
pls , help me , thanks a lot

Hi there, I'm having exactly the same problem. Have you found out how to do it?

Problems building exe that includes dsc (vi's always in memory, causing an error)

Hi,
Thank you for your time and expertise. I am trying to build an executable (Win2000, Labview 6.0.2 and DSC) but am consistantly being told that a group of vi and ctl files are already in memory. I have removed all non-essential cards, restarted my computer and attempted to build from a blank vi. Nothing should be in memory. Would there be a service running (from boot up) that is causing this? There is nothing left in my icon tray that would indicate that this is so.
Please note that one of the vi's is entitled "dsc_Engine Status.vi."
Nathan

Here is the problem:
You are attempting to build an application that uses VIs that are in memory. They are in memory for two reasons: One, you are using VIs that are used by LabVIEW, and two, they are used by LabVIEW DSC when it runs, by the service manager.
There are two solutions. One will get you there quickly. The other, will solve all of your applications building problems now and forever.
I will give you both and let you decide, however, I recommend the first, as it will solve your problems anytime you build an application.
Solution 1:
Open your top level VI(s). Open the VI Hierarcy. Select the option that allows you to view the path of the VI when you do a mouseover. Go to each and every VI, global, and control. Ensure that each is in your development or deployment directory, and NOT in /National Instruments/LabVIEW...etc directories. These are NI Core functions, and you should build with a copy only. This will take a lot of time, and may cause crashes (I had problems changing things in the hierarchy.) Try doing a "save all" about every 3 or so VI that you change. To change the location, you must first stop all services. Goto the Service Manager and select "Stop all Services". This should unload all the callers for these functions. Now, go to the hierarchy, and for everything in the LabVIEW directories, open it, and "save as" in your directory. This will cause the callers to look in your directory for the copy you are using. As I said, save all once in a while. Also, when prompted to affect the change in all VIs in memory, select YES.
When you have copied all resources, save all once again, and close everything, including LabVIEW. Now close LabVIEW. Take the directory into which you moved all of these functions, and move it off the computer temporarily (don't rename, remove to a different drive, or a zip drive). Then restart LabVIEW. If anything got moved incorrectly, you will be asked to search for it. Open a new VI, and select save all, to remake the file search paths stay with LabVIEW. Do NOT have your project open when you do this.
Now, replace your folder where it was originally, and restart LabVIEW. You can now build your application.
Solution 2:
Start LabVIEW. Goto the Service Manager and select "Quit Service Manager". When prompted, select yes to stop all services and quit.
Now build your application.
The reason the first solution is better is because you always want a copy of all NI Resource VIs, Globals, and Controls in separate location for your build. This not only prevents issues such as the one you mention above, but also solves a lot of other issues, including any changes to those core functions that may occur in newer versions of LabVIEW that may affect your program.
Good luck.

DSC Pull Problem

I have setup a DSC Pull server and a few client to connect. The problem is on the clients the config does not pull down and I get the following in the event viewer on all the clients. If I manually copy the config to a client everything works
fine until I update the config on the Pull server then the errors start again. Am I missing some permissions somewhere?
4110 - Successfully got the action GetConfiguration from pull server using Download Manager WebDownloadManager.
4194 - Failed to delete the current configuration file
4105 - Attempting to get the configuration from pull server using Download Manager WebDownloadManager.Configuration Id is e785307e-61a2-419b-8e07-2178295326d9.
4210 - Attempting to get the configuration e785307e-61a2-419b-8e07-2178295326d9 from pull server with Server Url http://SERVER:8080/PSDSCPullServer.svc using Web Download Manager.
4226 - WebDownloadManager for configuration e785307e-61a2-419b-8e07-2178295326d9 Get-DscDocument command, GET Url: PSDSCPullServer.svc/Action(ConfigurationId='e785307e-61a2-419b-8e07-2178295326d9')/ConfigurationContent
4104 - This event indicates that failure happens when LCM is trying to get the configuration from pull server using download manager WebDownloadManager. ErrorId is 0x1. ErrorDetail is A generic exception occured during the invocation of the Get-DSCDocument
cmdlet by Download Manager WebDownloadManager.
PS C :\WINDOWS\systen32> Get-DscLocalConfigurationManager
AllowModuleOverwrite : True
CertificatelD :
ConfigurationID : e785 307e-61a2-419b-8e07--2178295 326d9
ConfigurationMode : ApplyAndAutoCorrect
ConfigurationModeFrequencyMins : 30
Credential :
DownloadManagerCustonData : {MSFT_KeyValuePair (key = “ServerUrl”), MSFL.KeyValuePair (key =
“AllowUnsecureConnection”) }
DownloadManagerName : WebDownloadManager
RebootNodelfNeeded : False
RefreshFrequencyMins : 30
RefreshMode : Pull
Thanks for any assistance.

More log:
#Software: Microsoft Internet Information Services 8.5
#Version: 1.0
#Date: 2015-05-01 10:37:55
#Fields: date time s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) cs(Referer) sc-status sc-substatus sc-win32-status time-taken
2015-05-01 10:37:55 fe80::4c44:15cc:9bc6:1455%12 POST /PSDSCPullServer.svc/Action(ConfigurationId='4a90d746-d78e-45e0-9d5d-ca6cac7c0e9b')/GetAction - 8080 PSDSCUser fe80::4c44:15cc:9bc6:1455%12 - - 200 0 0 15
2015-05-01 10:39:10 X.X.X.X POST /PSDSCPullServer.svc/Action(ConfigurationId='e785307e-61a2-419b-8e07-2178295326d9')/GetAction - 8080 PSDSCUser X.X.X.X - - 200 0 0 0
2015-05-01 10:40:59 X.X.X.X POST /PSDSCPullServer.svc/Action(ConfigurationId='7b8d8905-ee40-440c-b20f-4036fcf073a5')/GetAction - 8080 PSDSCUser X.X.X.X - - 200 0 0 78
2015-05-01 10:40:59 X.X.X.X GET /PSDSCPullServer.svc/Action(ConfigurationId='7b8d8905-ee40-440c-b20f-4036fcf073a5')/ConfigurationContent - 8080 PSDSCUser X.X.X.X - - 200 0 0 93
2015-05-01 10:44:45 X.X.X.X POST /PSDSCPullServer.svc/Action(ConfigurationId='67da0c37-24fc-4c3f-bc25-ee81aba879e5')/GetAction - 8080 PSDSCUser X.X.X.X - - 200 0 0 15
2015-05-01 10:44:45 X.X.X.X GET /PSDSCPullServer.svc/Action(ConfigurationId='67da0c37-24fc-4c3f-bc25-ee81aba879e5')/ConfigurationContent - 8080 PSDSCUser X.X.X.X - - 200 0 0 0
2015-05-01 10:49:38 X.X.X.X POST /PSDSCPullServer.svc/Action(ConfigurationId='c8cd8e64-9d55-43a2-9d32-948be8a99003')/GetAction - 8080 PSDSCUser X.X.X.X - - 200 0 0 0
2015-05-01 10:49:38 X.X.X.X GET /PSDSCPullServer.svc/Action(ConfigurationId='c8cd8e64-9d55-43a2-9d32-948be8a99003')/ConfigurationContent - 8080 PSDSCUser X.X.X.X - - 200 0 0 15
2015-05-01 10:51:32 X.X.X.X POST /PSDSCPullServer.svc/Action(ConfigurationId='1d66b01b-0768-4cd0-a639-92c386bc86af')/GetAction - 8080 PSDSCUser X.X.X.X - - 200 0 0 0
2015-05-01 10:51:32 X.X.X.X GET /PSDSCPullServer.svc/Action(ConfigurationId='1d66b01b-0768-4cd0-a639-92c386bc86af')/ConfigurationContent - 8080 PSDSCUser X.X.X.X - - 200 0 0 31
#Software: Microsoft Internet Information Services 8.5
#Version: 1.0
#Date: 2015-05-01 11:10:14
#Fields: date time s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) cs(Referer) sc-status sc-substatus sc-win32-status time-taken
2015-05-01 11:10:14 X.X.X.X POST /PSDSCPullServer.svc/Action(ConfigurationId='e785307e-61a2-419b-8e07-2178295326d9')/GetAction - 8080 PSDSCUser X.X.X.X - - 200 0 0 15
2015-05-01 11:11:54 X.X.X.X POST /PSDSCPullServer.svc/Action(ConfigurationId='7b8d8905-ee40-440c-b20f-4036fcf073a5')/GetAction - 8080 PSDSCUser X.X.X.X - - 200 0 0 93
2015-05-01 11:11:54 X.X.X.X GET /PSDSCPullServer.svc/Action(ConfigurationId='7b8d8905-ee40-440c-b20f-4036fcf073a5')/ConfigurationContent - 8080 PSDSCUser X.X.X.X - - 200 0 0 31
2015-05-01 11:19:34 X.X.X.X POST /PSDSCPullServer.svc/Action(ConfigurationId='c8cd8e64-9d55-43a2-9d32-948be8a99003')/GetAction - 8080 PSDSCUser X.X.X.X - - 200 0 0 15
2015-05-01 11:19:34 X.X.X.X GET /PSDSCPullServer.svc/Action(ConfigurationId='c8cd8e64-9d55-43a2-9d32-948be8a99003')/ConfigurationContent - 8080 PSDSCUser X.X.X.X - - 200 0 0 0
2015-05-01 11:21:34 X.X.X.X POST /PSDSCPullServer.svc/Action(ConfigurationId='1d66b01b-0768-4cd0-a639-92c386bc86af')/GetAction - 8080 PSDSCUser X.X.X.X - - 200 0 0 0
2015-05-01 11:21:34 X.X.X.X GET /PSDSCPullServer.svc/Action(ConfigurationId='1d66b01b-0768-4cd0-a639-92c386bc86af')/ConfigurationContent - 8080 PSDSCUser X.X.X.X - - 200 0 0 0
#Software: Microsoft Internet Information Services 8.5
#Version: 1.0
#Date: 2015-05-01 11:41:21
#Fields: date time s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) cs(Referer) sc-status sc-substatus sc-win32-status time-taken
2015-05-01 11:41:21 X.X.X.X POST /PSDSCPullServer.svc/Action(ConfigurationId='7b8d8905-ee40-440c-b20f-4036fcf073a5')/GetAction - 8080 PSDSCUser X.X.X.X - - 200 0 0 78
2015-05-01 11:41:21 X.X.X.X GET /PSDSCPullServer.svc/Action(ConfigurationId='7b8d8905-ee40-440c-b20f-4036fcf073a5')/ConfigurationContent - 8080 PSDSCUser X.X.X.X - - 200 0 0 93
2015-05-01 11:44:18 X.X.X.X POST /PSDSCPullServer.svc/Action(ConfigurationId='67da0c37-24fc-4c3f-bc25-ee81aba879e5')/GetAction - 8080 PSDSCUser X.X.X.X - - 200 0 0 15
2015-05-01 11:44:18 X.X.X.X GET /PSDSCPullServer.svc/Action(ConfigurationId='67da0c37-24fc-4c3f-bc25-ee81aba879e5')/ConfigurationContent - 8080 PSDSCUser X.X.X.X - - 200 0 0 0
2015-05-01 11:47:48 X.X.X.X POST /PSDSCPullServer.svc/Action(ConfigurationId='c8cd8e64-9d55-43a2-9d32-948be8a99003')/GetAction - 8080 PSDSCUser X.X.X.X - - 200 0 0 15
2015-05-01 11:47:48 X.X.X.X GET /PSDSCPullServer.svc/Action(ConfigurationId='c8cd8e64-9d55-43a2-9d32-948be8a99003')/ConfigurationContent - 8080 PSDSCUser X.X.X.X - - 200 0 0 15
2015-05-01 11:50:15 X.X.X.X POST /PSDSCPullServer.svc/Action(ConfigurationId='1d66b01b-0768-4cd0-a639-92c386bc86af')/GetAction - 8080 PSDSCUser X.X.X.X - - 200 0 0 0
2015-05-01 11:50:15 X.X.X.X GET /PSDSCPullServer.svc/Action(ConfigurationId='1d66b01b-0768-4cd0-a639-92c386bc86af')/ConfigurationContent - 8080 PSDSCUser X.X.X.X - - 200 0 0 31

DSC problem

Similar Messages

Maybe you are looking for