VadimB

UPD: I found out, that the point is I have no (!) permission as admin to modify this file. Restart into install mode allowed me access to modify "config3.mxs" and "config3.mxs.jnl". But I still have no access to RT file. Permissions for it are rw-rw-rw. They are not able to be modified, file can't be replaced with application executed on target device or by ftp. What's wrong with it?

Hi everyone. I'm writing an Utility to retrieve image from Remote RT PXI system under PharLap 15 and RealTime 15. I use Create System Image.vi for that. During the execution this vi returns an error with code -2147220331 and description that some files on remote system might be corrupted. I desided to find out what is wrong with files and what are this files. So I have "config3.mxs", "config3.mxs.jnl" and "RT" (with no extension). What kind of problem is this?

Thank you for this!

finally, I suppose, the best solution is to use DVR in junction with single element queue or notifier. And there is a classic OOP pattern to solve this problem - Singleton Pattern. Found it's description and example here.

what if I would like to use dynamic events instead queues as a pattern Event-driven message handler instead QMH? Is there any underwater rocks I should keep in minds? Should I mention I buid RT application?

Mmmm... I have a hardware (power source) to continiously collect data from in one operation and perform user controlled events in another one. Class is defined for hardwear. The only data they share is COM-port. To avoid conflicts in COM-port usage I'm going to create a property that will point to "port is busy right now". Is there a better solution? Maybe the core concepts is weak?

Hello. What is the best practice to share one class instance (object) between two, or more, loops? New to lvoop, I suspect a correct answer is reference.

Had the same problem guys. Spent about a week to find a solution. Implemented ways to restart TCP connection, as described before. Finally called to support NI. Support engineer recomended to check the network properties. The broblem was as follows: my microcontroller (MC) and operator machine (PC) were in defferent subnets. As subnet was tuned to simmiliar fo both MC and PC, the error 66 has varnished, as the problem did. Good luck. Take care of yourself.