09-21-2006 09:05 AM
09-28-2006
06:28 AM
- last edited on
08-06-2026
10:48 AM
by
Content Cleaner
Hi Patrick,
I hope you're doing well. My first inclination was the say that not all functions that run in LabVIEW for Windows will run in the Real-Time Operating system because the Real-Time VIs are usually limited subset of the entire pallete, but the SMTP VIs use TCP, which I wouldn't think would be a problem. If you drill down into the VI using the debug tools, is it apparant which "input parameter is invalid?" It's possible that a network issue could block communication since SMTP uses a specific port, but I would think the error message would be different in that case. The following KnowledgeBase talks about other issues that could cause the SMTP VIs to fail in general, but not specific to a Real-Time target. If you try to do TCP communication on port 25, does this work correctly outside of the SMTP VIs? I'm not sure that a PC would have more network access versus a Real-Time controller though, so if it works on a PC on the same network, this may not be the issue. Let us know what you find!
Thaison V
Applications Engineer
National Instruments
09-28-2006 07:05 AM
09-28-2006 10:48 AM
09-29-2006 06:21 AM
Are you using the local PC and the RT controller on the same subnet. A router, gateway in between might be the issue.
@pabr wrote:
thanks for your reply. The thing that makes me suspect that it could be a network access problem is that I'm working in a company where the network is very secured. Not everyone has an internet access and we use Lotus Notes for emails! Also all compters are scanned for not allowed software! But back in the subject, our RT is in the lab subnet and I doubt that something on the network doesn't allow the RT to open such a socket. From a previous project, I experienced the Error 1 with TCP Read and Write - that would be the result of an invalid TCP Connection ID.
09-29-2006 07:04 AM