MAX/FP Explorer giving strange values

[Matthew_Williams]

cFP-2010 running a compiled application.  Connecting with MAX shows values as shown in max.jpg.
Temperatures intermittently show 0, 1, INF but mostly a correct value.  Timestamps show 19:00:xx but
sometimes :xxx (no 19:00).  Correct time is not 19:00 😉  FieldPoint Explorer has similar errors.

Remote viewing a panel of (qualified) readings shows good values, memory available, proper time, etc.
viewer.jpg below.  Any thoughts on what is happening?  Only occurs after the unit has been running for some
time ( > 24 hours but not known precisely).  After a reboot MAX and FP Exp. behave properly.  Any
thoughts on what is happening or suggestions to fix would be appreciated.  Thanks.

Matt

[Matthew_Williams]

2nd image.

[Hal_L]

Hi Matthew,

Intermittent problems are usually tougher to fix due to their inconsistent nature.  The first thing I suggest is to make sure that you have the most current FieldPoint driver. 

Please answer the following questions as I am trying to gain a more thorough understanding of what is happening to your FieldPoint system.
1. Are you losing the valid timestamp and the temperature readings at the same time?
2. When you lose a temperature reading, are you just missing a single reading or are all of your thermocouples reading bad temperatures?
3. If you are just losing a single temperature reading: are you always missing the same thermocouple reading?
4. How long do you record the bad data?
5. Does it only start recording valid data after resetting the module?

Regards,

Hal L.

[Matthew_Williams]

Hi Hal.  Thanks for your interest.

---

@HAL L wrote:

1. Are you losing the valid timestamp and the temperature readings at the same time?

2. When you lose a temperature reading, are you just missing a single reading or are all of your thermocouples reading bad temperatures?

3. If you are just losing a single temperature reading: are you always missing the same thermocouple reading?

When I start losing readings, all channels are affected.  The readings and timestamps go bad on different channels seemingly randomly, changing channel and bad reading approximately once a second.  For example, ch 1 temp and ch 7 time are bad, the next second they are correct (still 19:00:00:xxx for time) but ch 3 time is :637.  Then ch 3 time is 19:00:00:xxx and ch 5 temp is +1.#INF0 and ch 6 temp is #0.  There isn't any pattern that I can see, aside from the timestamps being only 19:00:00:xxx or :xxx.  Status for all channels remains 'Successful!'.  We see the same problems across multiple I/O modules on the same controller (when one module has the problem, they all exhibit the problem).  Obseved on RTD and TC modules (no AI modules in use).  Not observed on DI only controllers running for a comparable time.

4. How long do you record the bad data?
5. Does it only start recording valid data after resetting the module?

Our application qualifies data before recording it, so we ignore erroneous readings.  Actually, I don't know whether the FP Read vis are returning bad data to our application.  I'll have to explore that.  We don't use the timeserver function and instead download time from a PC.  We have not had any bad readings get into our data.  My concern is that FP Exp. and MAX are primarily troubleshooting tools for us and strange random readings decrease their utility in that role.

We are using FP Exp. 3.0.2(build 177) and MAX 3.1.0.3021; same results.  I'll try with a newer MAX as well.

Bad readings seem to be specific to a combination of controller and run-time.  The same instance of FP Exp. or MAX will show good controllers and bad.  Any controllers that are bad show bad readings on all modules.  Restarting MAX or FP Exp. has no effect, nor does the specific combination of controllers viewed.  A rebooted controller will always show good readings for at least approximately 24 hours.

Thanks.

Matt

[Hal_L]

Hi Matt,

Thank you for the thorough reply.  I think that upgrading to the current versions of MAX and the FieldPoint drivers is worth investigating. Also, have you considered using a crossover cable instead of connecting over the network? Doing this will eliminate the possibility of network problems causing the erroneous timestamps and data.  I'm also interested to know how long this has been happening. Has this been a recurring problem since you have had the system setup or did this just happen recently?  Please keep me posted with your progress on this issue.

Regards,

Hal L.