Nov 21st, 2024, 5:14pm
Welcome, Guest. Please Login or Register.
Pages: 1  Reply Reply  Notify of replies Notify of replies  Print Print
   Author  Topic: NSPK vs Remote Desktop  (Read 5606 times)
NSPK vs Remote Desktop
on: Dec 7th, 2007, 9:05am
Quote Quote  Modify Modify

Is there a benefit of using the Network Serial Port Kit (NSPK) instead of using the serial port sharing of Remote Desktop?  We have a program running on a remote PC that needs to access data from a handheld device on our local PC.  Through Remote Desktop we are able to access the data, though it pulls quite a bit slower than if the device was hooked up locally.  Does NSPK increase this speed?
IP Logged
Re: NSPK vs Remote Desktop
Reply #1 on: Dec 13th, 2007, 1:01am
Quote Quote  Modify Modify

Hi!
Thanks for interesting question!
 
For example there are two computers:
PC and Notebook. PC has COM port th which some device is plugged. And you would like to access that device from Notebook.
 
RDP:
You should go to PC, and then logon to your Notebook via RDP from PC Smiley As result you can access COM port of PC, being logged in to notebook via RDP.
But why not to use PC's COM port locally in such case.
 
NSPK:
Using NSPK you can access remote PC's COM port directly from your Notebook.
 
As to speed: it depends on many parameters. If you use it in local network, it should work exactly as if you work with local COM port. In any case, if any doubts, there are a lot of settings we can use to optimize the data transfer speed  over network.
 
We offer 15 days trial from our web site, so try our solution and then decide if that's OK for you.
 
Once again, thanks for interesting question.
IP Logged

Andrew Scott

FabulaTech
===================
http://www.fabulatech.com
Re: NSPK vs Remote Desktop
Reply #2 on: Dec 13th, 2007, 6:51am
Quote Quote  Modify Modify

Thanks for the response on this!
 
Our situation is that we have a device with 1500-2000 80 byte records we need to transfer from a local workstation to a remote PC over the internet.  During my testing using Remote Desktop and having the serial port shared, the transfer process took around 45 minutes to complete, when transferring locally it took between 1 and 2 minutes.  The software that reads the data must transfer each record one at a time and it seems that over the Internet there's lag.  We think this lag is caused by the device waiting to get a signal back from the other computer that a record was received.
 
Would NSPK speed up the process?  Our other option is to just write some software to dump the data from the device locally, then have another process that will read in the data to the remote system.
IP Logged
Re: NSPK vs Remote Desktop
Reply #3 on: Dec 14th, 2007, 12:41am
Quote Quote  Modify Modify

Hi!
NSPK allows to cache data read from COM port. It means that it will read the data from COM port and then send it over network by whole block. It uses smart algorithm to decide send the data of continue buffering. You can enable this feature in advanced options for shared physical COM port.
It would be interesting to know how it works for you.
 
Thanks!
IP Logged

Andrew Scott

FabulaTech
===================
http://www.fabulatech.com
Pages: 1  Reply Reply  Notify of replies Notify of replies  Print Print

Previous topic | Next topic
Online Talk to our
support team or
sales department.