ASCII Object Dropped Connections on Unsolicited Data

[erblock]

This is a long standing issue (on this forum more than once, years ago) where Lookout ASCII objects gathering unsolicited data, lose connections when there is any issue with the source hardware and the connections do not automatically come back.  For example, if I reboot an Ethernet serial server, the com port driver object reattaches as soon as the device is back up, but Lookout doesn't start collecting the data again unless I go into edit mode and "touch" each ASCII object's properties dialog box by opening and clicking OK.

Is there a way to "touch" ASCII object "properties" pragmatically within Lookout?  Restarting the process fixes it of course, so is that a possible workaround (automated)?  Others?

PLEASE, work on a solution for this!  This is an issue of data reliability and it has screwed me many times and is embarrassing because it always happens when your not looking and when the data is more important than normal...like today when it happened again!

Thanks,

Ed

[Ryan.S]

If you reboot the Ethernet-Serial server, all the serial ports are disabled and enabled again. I guess the problem is that lookout doesn't try to reopen the serial port after it is "dead".

One possible solution is to add a datamember for ASCII called "reconnect".

[erblock]

I would like to test such a solution please.  I envision trying a reconnect after 5 minutes without a successful ASCII.update.

Thanks,

Ed

[Ryan.S]

send you an ascii.cbx for testing.

6.5 version.