[Bacnet-developers] Issue with mstpcap.exe when using named pipes
Brought to you by:
skarg
|
From: Jeff M. <jef...@gm...> - 2014-06-04 20:08:33
|
For some reason, I've lost my named pipe capture capability recently in Win32 (running on Win7 64 bit). First of all, standard captures without the named pipe argument still work great for me. When I add the third argument, things break. I execute as below: C:\mstpcap>mstpcap com7 19200 \\.\pipe\wireshark Adjusted interface name to \\.\COM7 RS485 Interface: \\.\COM7 mstpcap: Using \\.\COM7 for capture at 19200 bps. mstpcap: Creating Named Pipe "\\.\pipe\wireshark" I can see the RX light on my USB--RS485 adapter flicker as usual when this opens the connection to the serial port, but after 5-10 seconds, the light turns off (like when I end a capture). In the past, when the named pipe has worked, I've noticed that mstpcap has created a .cap file in addition to streaming packets to the named pipe. With my issue, no .cap file is being created. In case it matters, I have tried at multiple baud rates, and the serial port seems to close faster at higher baud rates (possibly because we reach 100 packets faster?). I just tried rebuilding mstpcap in 0.8.2 using MinGW, and it's exhibiting the same symptoms. Has anyone else experienced this issue? If so, how did you fix it? Thanks in advance for any help you can provide. Best Regards, Jeff |