hi francesco,

i have the same problem , can you please tell me where can i find where tv
can find the variable sent by Clock ( in which file/line)
and where the clock (in Clock code ( in which file/line)) is putting the
value and sending it to the TV



thanks in advance,
regards
Sana

2009/4/8 Francesco Furfari <[email protected]>

> Hi
>
> did you use Date instead of Time data type with the Clock?
> Let me a couple of days to check if the problem is in the converter.
>
>
> regards,
> francesco
>
> chihi asma wrote:
>
>> Thanks Francesco,
>>
>> I tried to resolve the problem but I still have the same error, the TV
>> can't get the date correctly from the remote clock.
>> Can anyone help me?
>>
>> Thanks in advance
>>
>> Asma
>>
>>
>>
>>
>> ________________________________
>> De : Francesco Furfari <[email protected]>
>> À : [email protected]
>> Envoyé le : Jeudi, 2 Avril 2009, 14h06mn 27s
>> Objet : Re: Problem with upnp examples
>>
>> hello,
>>
>> if I remember well, it should be a problem of data types used in the
>> examples, actually the clock sends time events, not dates event. We
>> continued to  used the same types used by Cyberlink devices (that's time or
>> string I don't remember perfectly now) , but the TV uses a Date type. So
>> converting the long in a date causes problems with remote devices.
>>
>> regards,
>> francesco
>>
>> chihi asma wrote:
>>
>>> Hi,
>>>
>>> I'm testing felix upnp examples on  a pc and an embedded system. On the
>>> PC, I'm running the base driver, the tester, the tv and the clock. On the
>>> embedded system, I'm running the clock.
>>> - The devices on the PC communicate normaly, the TV displays the date of
>>> the clock  correctly.
>>> - However, when I start the clock on the embedded system, the tester of
>>> the PC detects it but the TV displays the date incorrectly.
>>>
>>> Can anyone tell me whats wrong? Thanks in advance.
>>>
>>> Asma
>>>
>>>
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to