HOME › Forums › General › Feedback to Smartenit › ZBPCM Home Automation PCM Interface
-
AuthorPosts
-
AnonymousInactiveMay 30, 2013 at 7:12 pmPost count: 1
Greetings,
I just purchased a ZBPCM Home Automation PCM Interface for use with my Insteon network. A Mac user using the Indigo Mac interface 5.1.8.
The results of the conversation are as follows:
May 30, 2013 9:50:21 AM
PowerLinc Linking – entered discovery linking mode (240 seconds)
PowerLinc Linking – received module button pressed from 1E.7E.4B
PowerLinc Linking – syncing PowerLinc links (address 13.1F.99)
PowerLinc Linking – . . adding: INSTEON plc link to controller 1E.7E.4B, flags 03, group 01, data 00 00 FF
PowerLinc Linking – . . adding: (not added — probably already exists)
PowerLinc Linking – sync complete
PowerLinc Linking – PowerLinc links updated
PowerLinc Linking – sending engine version request to 1E.7E.4B
PowerLinc Linking – received engine version 02 from 1E.7E.4B
PowerLinc Linking – sending id request for device information to 1E.7E.4B
PowerLinc Linking – received id request response from 1E.7E.4B
PowerLinc Linking – retrieving firmware version
Error firmware version address is unknown (should be in device table)
Error Linking – no match found for device type ID 2304 with firmware version 00
Error linking failed
PowerLinc Linking – entered discovery linking mode (240 seconds)
PowerLinc Linking – exited linking modeAs you can see the ZBPCM returns a firmware version of 00. Is this normal/correct?
My Indigo tech: “On closer inspection of your Event Log snippet it looks like the problem is the module isn’t reporting a valid firmware version (it is reporting 00). Either your module is in a bad state (or maybe it is a malfunctioning), or the manufacturer neglected to set a firmware version in the module when they created it.
Thanks in advance for your assistance.AnonymousInactiveDecember 17, 2013 at 12:42 amPost count: 146Hello Jeff,
I believe this has been taken care of already…but I just noticed that it hasn’t been answered yet on the forum. So I’ll answer it, in case others have the same question.
It sounds like it might have been that the PLM wasn’t communicating with the daughter card, so the PLM may have needed to be replaced.
The ZBPCM, as the majority of our products has a SmartLabs PLM as the base of the unit and then we add a daughter card to the PLM to make it whatever device we want to. In some cases the PLM stops communicating with the daughter card and that is when the firmware version would show incorrectly.
I hope that helps.
-
AuthorPosts
- You must be logged in to reply to this topic.