Can NSPK also act like the Serial Port Redirector product and redirect a virtual serial port to another system that has just mapped a physical port to a TCP port, or does it only communicate with other NSPK installations?
The system where I am now testing NSPK also needs to talk to other serial devices that have been mapped to TCP ports on Linux systems. Is NSPK enough, or does the Redirector product also need to be installed on the same system? It would seem that the more expensive NSPK product should have an option to connect to non-NSPK TCP ports as well.
Unfortutanely NSPK cannot connect to non-NSPK TCP ports.
So why is SPR not enough? You can install it on the Windows machine, configure it as Server and connect to the Linux ports.
However, you won't be able to control the signals at the port, i.e. only data transfer will work. In case you are able to add the signals to the Telnet protocol, then it'll work also.
Because NSPK would have to be installed on the server in question for another application. Looks like both NSPK and SPR would have to be purchased and installed to use a shared serial device on a Windows PC via NSPK and serial mapped devices on Linux terminals via SPR.
Home
Search
Members
Login
Register
Reply
Notify of replies
Print
Author
Quote
Modify
IP Logged