LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Exe not communicating in other PC

Some OS's consider C:\ protected.  C:\<MyCompany>\ usually works 


"Should be" isn't "Is" -Jay
Message 11 of 15
(1,022 Views)

Hi Ptakkar,

                         Do you have DSC run time license for your deployment machine? Looking at your code; I see that you are using DSC module for making LaBVIEW as OPC client.

 

Regards,

Kamlesh

AE NI India

0 Kudos
Message 12 of 15
(985 Views)

Dear Kamlesh

 

Seems like DSC run time was the problem,but now I have another problem,I am able to communicate through data socket where as something is wrong with shared varicble settings.

It reads from the developer pc and when  I turn it off  the devoper PC only data socket variables communicate and shared variable doesnt .kindly let me know if i need to provide any other information.

 

Thanks & Regads

Ptakkar

0 Kudos
Message 13 of 15
(971 Views)

Hi Platkkar,

                         What do you mean by turnning off the developer PC? were these shared variables created on your developer pc?

0 Kudos
Message 14 of 15
(935 Views)

Dear Kalmlesh

 

seems like the problem is solved,the only i needed to make was to change the computer name with local host,and everything is every fine after it. however i have another doubt.i am using data logging and the data is coming through opc.sometimes it misses few changes ,is there any drawback using opc for data logging .i want to log data in miliseconds(approx 10ms).is that possible with ni OPC.

 

Regards

Ptakkar

0 Kudos
Message 15 of 15
(914 Views)