Re: Re: TSC.cmd / id

[Kevin Hawkins <yahoogroupskh@xxxxxxxxxxxxxx>]

Hi Per,

I have spent some time today reading through the TSC specification
and I too have some questions about it's implementation - bear with me
whilst I progress this...  I haven't forgotten.

Kevin

Per wrote:
> Kevin,
>
> No worries, we all have real life stuff to handle :)
>
> Regarding the UID and subaddress; I would expect the UID to extend to
the subaddress; how elese do you address it with the UID in the TSC.cmd
block?
>
> Regards,
>
> Per
>
> --- In xAP_developer@xxxxxxx, Kevin Hawkins <yahoogroupskh@...>
wrote:
>
>> Hi Per,
>>
>>     Haven't forgotten - just away from home a bit - and very busy
-
>> should get some feedback on those TSC messages to you  shortly -
>> hopefully some others will too ...
>>
>>     I understand about the pin better now - as I assume the
'output' and
>> the internal sensor might present different values they will have
to be
>> two different endpoints, one an input and one an output  - maybe
as a
>> hierarchical sub addresses
>>
>>        :output1.pin   and  :output1.sense
>>
>>     The xAP spec places some restrictions on the logical address ,
I
>> don't believe this extends to the sub address portion however -
maybe
>> Patrick can confirm ?
>>
>> "As a consequence of the fact that the logical name uniquely
identifies
>> a device (or software application), there are constraints imposed
on the
>> allocation of logical names. If a device exists on the xAP network
with
>> a logical name a.b.c, a second device may not use the logical name
>> a.b.c.d. "
>>
>>      cheers Kevin
>>
>> Per wrote:
>>
>>> The two-way I/O pin is a standard open drain I/O with added
internal sensor used in most ICs. See Figure 11 in http://datasheets.maxim-ic.com/en/ds/DS2406.pdf
>>>
>>> You're right of course regarding the BSC block; shamefull I
didn't get that right.
>>>
>>> // Per
>>>
>>>
>>>
>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>
>



------------------------------------