Posts: 1,255
Threads: 219
Joined: May 2007
Reputation:
0
03-28-2015, 07:00 PM
(This post was last modified: 03-29-2015, 10:41 AM by juwi_uk.)
Hi,
If I do a HM learn on my HM WiFi it reads the eeprom and I can map counters and flags etc. I can write back these changes to the eeprom and at runtime all looks to be OK and I can see values changing (in my Object Matrix BTW!! :0)).
What is confusing me though is that if I re-read the eeprom then the configuration returned is blank in comfigurator. Surely this isn\'t correct behaviour?
I\'m using latest firmware\'s for HM/Eth3 and comfigurator.
Julian
Posts: 5,952
Threads: 871
Joined: Apr 2006
Reputation:
2
That cannot be correct
When you learn, comfigurator is giving a read from eeprom command as well
Can you send the IO Monitor when read gives a blank result?
Posts: 5,952
Threads: 871
Joined: Apr 2006
Reputation:
2
Thanks, this seems to be a problem withComfigurator from 3.7.6 onwards
Posts: 1,255
Threads: 219
Joined: May 2007
Reputation:
0
Quite possibly as I haven\'t done a HM learn for a few versions now.
When do you think a fix will be available?
J
Posts: 5,952
Threads: 871
Joined: Apr 2006
Reputation:
2
We found that this is due to a difference in handling between the heatmiser firmware after 7.035 and Comfigurator after 3.7.6
The Heatmiser module data is obtained by learning and it is read only so never changes except by learning
When Comfigurator after 3.7.6 writes to EEPROM it does a global Erase of the EEPROM before writing the mapping data so it erases the module data (DCBs) as well
Only the mapping data is used by the UCM/HM and the module data is for information only
Read from EEPROM thus causes the modules tab to be blank
The solution I propose is to remove the Read from EEPROM button so that if you need to refresh the modules tab, just do a Learn again. Read from EEPROM does not realy have much use
Posts: 1,255
Threads: 219
Joined: May 2007
Reputation:
0
How is this different from ZWave as this also has module info that is \"learned\" and doesn\'t change unless you do a learn again. Here I can happily still Read from Eeprom and write back without issues so cant you use the same method?
Personally I\'d rather the Read worked as I find the Learn pretty flaky at times and you may have to do 2 or 3 times before it fetches the config correctly from HM.
Julian
Posts: 619
Threads: 62
Joined: Jan 2007
Reputation:
1
I agree with Julian on the Read/Learn issue. I tested both my ZWave and Universal and they worked fine.
Ingo
Posts: 5,952
Threads: 871
Joined: Apr 2006
Reputation:
2
The difference is that zwave and universal have only the one mapping tab which is read/write. When you write to EEPROM, the whoiiole table is written to EEPROM and read from eeprom reads it back
Heatmiser has another modules tab which is read only, and is for information only. Write to EEPROM erases this tab
Do you have the need for a separate Read from EEPROM button when the Learn button does exactly the same thing?
Posts: 1,255
Threads: 219
Joined: May 2007
Reputation:
0
03-31-2015, 08:58 PM
(This post was last modified: 03-31-2015, 08:58 PM by juwi_uk.)
Unless I\'m missing something, Learn and Read-Eeprom are meant to be different functions.
LEARN - Interrogate the Heatmiser Thermostat to get the config, store this in the Eeprom and read the Eeprom into Comfigurator.
READ Eeprom - Fetch the previous config into Comfigurator without re-interrogating the HM Thermostat (This can be the flaky bit requiring a few attempts IMHO)
Julian
Posts: 5,952
Threads: 871
Joined: Apr 2006
Reputation:
2
Learn obtains the Module information from the Heatmiser modules and \"reads from eeprom\" into the Heatmiser tab.
Read from EEPROM just reads from EEPROM
Hence Learn encompasses all the REA from EEPROM functions so you are not losing out n anything
