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.

loggernet stability


benjammin Jan 25, 2011 11:58 PM

Hello,

Running the latest version of loggernet which uses TAPI/IPPort to collect data from a variety of CSI loggers. One problem we've been having is that Loggernet likes to intermittently crash. For awhile the latest patch (4.1) seemed to have taken care of what I assumed were TAPI issues but the crashes seem to be recurring more often now. Have you run into this issue? Is there any way to make loggernet more stable? Does it have a preferable OS? Just wanting to explore some options.

Thanks


Sam Jan 26, 2011 12:45 AM

The success of using TAPI is dependent on the driver the modem manufacturer is supplying, not LoggerNet. Even though TAPI provides an abstraction for access to the modem, it is heavily impacted by the specific behavior of the underlying hardware and driver set.

If TAPI works great with your modem ... perfect ... use it. But when a customer has an issue like you describe, I recommend ditching the TAPI root and using the ComPort root with a PhoneBase device. If your modem is not listed in the "Modem Database" you'll need to add it. This can be daunting if your unfamiliar with the AT commands used for control of your modem. However, once it is set up, I bet your crashing days will be over.


benjammin Jan 31, 2011 06:23 PM

Since this last post and loggernet computer freakout everything seems to be OK. I think the 4.1 patch corrected some issues. Unfortunately I think the last time the drivers for our TAPI modem were updated was sometime last century... or maybe 5+ years ago. We're going to wait and see. Uptime is far better with 4.1 than 4.0.

This is pretty far out there but any chance network policy changes could affect how loggernet runs?

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