Hi, we have a problem with our electronic scales model: VP 15 t.2 (http://www.torgdom-shtrih.ru/vesy/img/p-vpt.jpg). They not work by NSPK . We also have a bar-code scanners, they work with nspk very good.
Client machine: windows server 2003 (nspk client) Server machine: windows xp sp2 (have a shared com ports)
Can your help us?
IP Logged
Andrew FabulaTech Forum Moderator
Moderator FabulaTech Forum Senior Member
Gender: Posts: 427
Re: Problem with NSPK 5.3.2 Reply #1 on: Mar 17th, 2008, 12:15am
Let's resolve the issue. So, that scales software does not work correctly when using NSPK virtual port. Usually the problem is related to timing issues. Could you please play a bit with "Network Latency Compensation" option.
If does not help, let's see it in details.
We need investigate serial traffic to know exactly why it appears and to find the proper solution.
Please use the following portmon setting: Edit -> Max Output Bytes -> 1024 Options -> Show Time [x] Options -> Show Hex [x] Options -> Clock Time [ ]
Experiment 1 ============
Remote PC (physical COM port)
1) Launch portmon 2) Configure portmon to capture data from physical COM port: Capture -> Ports -> ... 3) Launch communications program and work with your device for some time. Then close communications program. 4) Save captured data to file: File -> Save As -> remote1.log
Experiment 2 ============
Remote PC (physical COM port) 1) Launch NSPK and share physical COM port 2) Launch portmon 3) Configure portmon to capture data from physical COM port: Capture -> Ports -> ...
Local PC (virtual COM port) 1) Launch NSPK and create virtual COM port connector (redirected to physical COM port of the remote PC) 2) Launch portmon 3) Configure portmon to capture data from virtual COM port: Capture -> Ports -> ... 4) Launch communications program and work with your device for some time. Then close communications program. 5) Save captured data to file: File -> Save As -> local2.log
Remote PC (physical COM port) 4) Save captured data to file: File -> Save As -> remote2.log
Please send us there 3 log files: remote1.log, local2.log and remote2.log