Few DCERouter-device socket connections questions

[bulek]

Hi,

I'd kindly ask if anyone has any more insight into following quoted messages and whether they are harmful and should be debugged what causes them ...

1. Timeout on PING
DCERouter sends PING string and waits for PING_TIMEOUT (that is defined as 5 - what units does this mean) ?

#define PING_TIMEOUT      5

Also: I see that Dcerouter sends many PINGs in short time intervals - intentional ? Why is one response not enough ? Or is maybe my driver taking too much time ro response...

2. Socket::ReceiveString2 ReceiveData failed

01   03/20/09 12:41:41.919      Socket::ReceiveData-a 0xa9935038 failed ret 0 <0x6d4edb90>
05   03/20/09 12:41:41.919      Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 159 127.0.0.1 dev 501 <0x6d4edb90>
05   03/20/09 12:41:41.919      Router::RemoveAndDeleteSocket 0xa9935038 501 <0x6d4edb90>
05   03/20/09 12:41:41.919      Socket::SendData socket is invalid <0x674e1b90>
05   03/20/09 12:41:41.919      Socket::SendMessage *failed to send* type 9 id 0 from 0 to 501 <0x674e1b90>
05   03/20/09 12:41:41.919      Socket 0xa9935038 failure sending message to device 501 <0x674e1b90>
05   03/20/09 12:41:41.919      Router::RemoveAndDeleteSocket 0xa9935038 501 <0x674e1b90>

What is DCERouter expecting in return.. If I understand right, it can send any data through non-active socket, but maybe it's expecting something in return ?

3. Can false  setting for house mode cause device disconnect ?

08   03/20/09 12:41:42.762      Received Message from 501 (Cybro-2 / Closet/Storage Space) to 13 (Security Plug-in / Living Room/Family Room), type 1 id 19 Command:Set House Mode, retry none, parameters: <0x6e4efb90>
08   03/20/09 12:41:42.762        Parameter 5(Value To Assign): 0 <0x6e4efb90>
08   03/20/09 12:41:42.762        Parameter 17(PK_Users): 7 <0x6e4efb90>
08   03/20/09 12:41:42.762        Parameter 99(Password): 1234 <0x6e4efb90>
08   03/20/09 12:41:42.762        Parameter 100(PK_DeviceGroup): 0 <0x6e4efb90>
08   03/20/09 12:41:42.762        Parameter 101(Handling Instructions): W <0x6e4efb90>

....

05   03/20/09 12:41:42.775      The target device 701 (routed to 501) has not registered. <0xb6becb90>
05   03/20/09 12:41:42.775      The target device 701 (routed to 501) has not registered. <0xb6becb90>
05   03/20/09 12:41:42.775      The target device 658 (routed to 501) has not registered. <0xb6becb90>
05   03/20/09 12:41:42.775      The target device 536 (routed to 501) has not registered. <0xb6becb90>
05   03/20/09 12:41:42.775      The target device 658 (routed to 501) has not registered. <0xb6becb90>
05   03/20/09 12:41:42.775      The target device 537 (routed to 501) has not registered. <0xb6becb90>
05   03/20/09 12:41:42.775      The target device 538 (routed to 501) has not registered. <0xb6becb90>
01   03/20/09 12:41:42.777      Attempt to set invalid house mode: 0 <0x870d7b90>
05   03/20/09 12:41:42.779      Removing socket 1701080899, ourstanding refercences: 1380917287 <0x6d4edb90>

I wonder if invalid house mode can cause device disconnection ? Or is last entry cause by any other previous entry (I haven't found anything that could associate with such action) ?


Thanks in advance,

regards,

Bulek.

[ddamron]

it looks to me like the above log is correct.
Device 501 sends a SET HOUSE MODE to 13.  all fine. (regardless of the params)
then, below, it seems as if a command is being sent to a child of 501
ie device 701 (routed to 501) has not registered.
501 may well work, but 701 may not.

I'm not able to look up the parameters of cmd19 atm, but I'm guessing param 5 (House Mode) 0 is invalid.

Also, the "removing Socket" line, look at the object ID... 0xb6becb90
that is different from the above "cmd 19" line... 0x0x6e4efb90
hence I believe all is right.



HTH

Dan