I'm upgrading from an ECM-1240, and have found its second-by-second realtime reporting quite useful when testing equipment, tracking the cycling behavior of appliances, etc. So, I was disappointed to see that the GEM seems to enforce a 3-second minimum:
^^^SYSIVL001 -> IVL (acknowledged)
^^^RQSITV -> 03 (same for IVL002 or IVL000)
A search turned up this old post by Teken mentioning an early software change:
https://www.brultech.com/community/view ... imum#p4648
I can see how faster updates might be a problem with the more verbose ASCII-based formats (HTTP GET, etc.) and/or when communicating through a radio module or Dashbox, but I'll be using plain hardwired serial, and the more compact BIN32-NET (8) format, which at 429 bytes per packet, and 1 packet/sec should occupy less than 25% of even a 19200 bps line's capacity.Teken wrote: ↑ "Some of the release notes for the COM 2.37 ...
- Packet send interval minimum value set to 3 seconds. There was an issue where some customers would set this value too low and the GEM could not process the packets fast enough. This caused the GEM not to respond to commands or to the Setup Page. If a l If a lower packet send interval is required, this may be obtained by using a special command via terminal."
I won't be using the built-in web page interface, and will hardly ever send any commands to the GEM once it's placed in service. So, it would be no problem it takes a few tries at 1 pkt/sec for ^^^SYSOFF to be recognized. Also, none of the 1-wire sensors or pulse counters will be active, in case that helps with CPU loading.
^^^RQSTST -> 00000000
^^^RQSPST -> 0000
Running Com firmware 4.36, ENG firmware 1.49, which appear to be the latest.