Ah, yes, serial communication is supposed to be simple, but it is often frustrating. I have done a fair amount of this, but none under LV7.
Whether or not you get errors depends on the nature of the communication. For instance, suppose you send a request for status information to your serial device. Maybe you send a "sts" to the device. If there is nothing to receive your command, you will not get an error in your code. You will in fact send "sts" to the device, even though your device isn't hearing it. If you do a serial read each time you make this request, then you should get an error. If no device is listening to your command, then you should get a serial timeout error. The error reporting might have something to do with the new automatic error reporting features in LV7. Make sure that you are not using only the automatic error handling feature, which is unavailable in the run time engine. Before you conclude that the code is fine just because it ran on your development machine, make sure that it is even possible for your code to generate serial communication errors. Generally, it should be possible, but based on the limited information that you provided in your question, I have to issue this caution. Assuming your code can indeed generate serial communication errors and you are monitoring those errors properly, then you should double check the serial port resources. Make sure that your target control machine is defined according to the code you wrote, e.g. all of the settings, including the visa resource name should be identical. If you attach your source code, or perhaps a reduced example of your code, I'm sure we could get to the bottom of it quickly.
