Is anyone experienced with Newport Electronics iServer-Microserver ethernet device?

[BuddyHaun]

I have been testing the iServer devices with alot of the same issues everyone else has been having. An additional item I noticed when stress testing the system is that if I used TCP queries in a reasonable fast loop the iServer would lock up and require a reset in 1-2 days. I seem to be having better luck using UDP and having the iServer broadcast. I haven't been able to get the TCP broadcast to work correctly yet and don't really need absolute timing anyway. Just thought I would toss that out in case anyone runs into reliability problems they can't explain.

Buddy Haun

CLA

[Stephmon]

I sort of "intuited" that the device wouldn't be agreeable to being constantly queried... So, I set it to "Continuous" and let it deliver at its own pace. I test the incoming string for its first two characters (TA, TB, HA, HB, ...) and pass the resulting string to the appropriate chart, or numeric indicator, through a number conversion and an If/Then that repeats the previous non-zero value, until a new value comes along. My case logic is a tiny bit flawed, in that it will never pass along 0.00F, but I never anticipate my lab, or the insides of my devices, reaching that temp. Even so, it would pass 0.01F and -0.01F...

Cheers,
Stephen 

[BuddyHaun]

Be careful just checking for a non zero number. The devices that I am using will randomly return -41.8F on the open temperature channels and -41.8% for the humidity. Most of the time the open "B" channels will sent back "Open" but not always.

[Stephmon]

When you say open channels, do you mean channels without a detector attached at the time?

Thanks for the heads-up!

Stephen

[BuddyHaun]

The IServers that I am using have a hydra attachment where you can attach two temperature/humidity sensors. If you don't attach the second sensor those channels may read "open" or a negative reading.