EZIO8SA in an inaccessible location 2008-07-06T14:48:35+00:00

HOME Forums Input/Output EZIOxx EZIO8SA in an inaccessible location

Viewing 7 posts - 16 through 22 (of 22 total)
  • Author
    Posts
  • Anonymous
    Post count: 408

    Thanks for the quick check. We will keep looking into this.

    Anonymous
    Post count: 1001

    I had just discovered where the first Set button link record was actually written when I got the new Post notice about 1.78. Hoped you had already discovered the new PLM was in your stock but 1.78 link Display starts at 0FF8, failing to show the 3 Set button links which start at 3FF8. Sorry I was not able to get the information to you sooner. I scanned the entire PLM memory starting at 0000, stopping at 0FFF looking for the Set button links. When I did not find them I started looking higher. Then remembered that the new PLMs were advertising support for a much larger number of links. Calculated the memory must be 16K on the newer PLMs and started my next scans at the top of the larger memory. There was my first Set button link. Each lower 8 byte increment showed my other 2 Set button links.

    Anonymous
    Post count: 408

    We have confirmed what you state, that there appears to be a change in the mapping for PLM versions. You have to love surprises.

    We are looking over the protocol and we will have a solution out quickly.

    Grif,

    Thanks for the work on your side – you are invaluable on these forums.

    Anonymous
    Post count: 35

    Paul, can you verify the firmware number where the change in mappings occurs? 0x63 seems to be 0xFF8 for the first link record. I assume the PLMs using 0x3FF8 are newer?

    Anonymous
    Post count: 408

    We have contacted Smarthome and are working with them to understand the PLM versions and memory mapping of each – especially when it was changed.

    We are working hard on this, and will have something soon.

    Anonymous
    Post count: 18

    @pauln wrote:

    We have contacted Smarthome and are working with them to understand the PLM versions and memory mapping of each – especially when it was changed.

    We are working hard on this, and will have something soon.

    Any news ?

    Anonymous
    Post count: 256

    Sorry for the confusion. Let me add to it: the size of the memory does not coincide with the PLM firmware rev. level. It seems that we have some PLM 62 with both the small and the large memory, starting the database at different locations.
    We will be changing the utility to allow for the different sizes. We are also looking into an auto-sizing capability for our EZSrve firmware.

Viewing 7 posts - 16 through 22 (of 22 total)
  • You must be logged in to reply to this topic.