01-24-2011 10:22 AM - edited 01-24-2011 10:22 AM
I have an application I've written for a cFP-2200 target which requires TCP communication. I chose STM since it seemed easy to work with and it worked fine up until now when I've moved from testing on windows machines to using the actual target.
Now, my server app (running on a windows machine) returns an "Error 1" after "STM Write Meta Data" when serving a request from the cFP-2200. I think this has to do with # or a square looking character which is placed in the string sent over TCP when the input meta data array is converted using "flatten" inside the STM write meta data VI.
I've seen other posts dealing with this issue for other targets but none for the cFP-2200. Does anyone know of any progress made or workarounds? Maybe an upgrade of the target OS?
I've attached the related VIs. testdbmessagereceipt is the server, request... is the client running on cFP-2200.
Solved! Go to Solution.
01-24-2011 10:57 AM
Doing more testing, it looks like it's not working on the windows machine either whereas it was previously.
01-24-2011 11:33 AM
Ok, Nevermind. I had the Listener ID wired to the STM Write instead of the connection ID.
I wish the error just told me what input the problem came from. This would've saved me a lot of time.