Our full technical support staff does not monitor this forum. If you need assistance from a member of our staff, please submit your question from the Ask a Question page.


Log in or register to post/reply in the forum.

Unexpected Socket Errors


wx2day Mar 30, 2012 12:41 AM

BACKGROUND:
Version: LoggernetAdmin 3.4.1
Instance: Single
IP Ports:9
Addresses: All Unique
Pak Bus Devices: Many
Addresses: All Unique

In a multiple IP port network with many pak-bus port devices, what would cause unexpected socket errors resulting in the loggernet server to intermittently drop connections?

v/r
wx2night

* Last updated by: wx2day on 3/29/2012 @ 6:43 PM *


ChipsNSalsa Mar 30, 2012 06:44 PM

My first thought is that there's a lot of latency associated with the socket. You can increase the extra response time on the IPPort in the Setup screen to work around a latency issue.

My second thought is that there's more than one LoggerNet trying to contact the station at the same time and each LoggerNet has the same PakBus address on that PakBus port thus creating a PakBus address conflict. If there are more than one LoggerNet trying to contact the station they should each have a unique PakBus address on their respective PakBus port. Adjust the PakBus addresses in the Setup screen | Options pull-down menu | LoggerNet PakBus Settings menu item | LoggerNet PakBus Settings dialog box.


wx2day Mar 31, 2012 03:25 PM

Thanks-I will check those items. I will post back to let you know what remedy is.

wx2day

Log in or register to post/reply in the forum.