On Thu, 2007-10-04 at 11:48 +0200, Volker Christian wrote: > On Thursday 04 October 2007, Patrick Shirkey wrote: > > ... > > The device is running windows CE 5.0 > > > > > It will be a very strange behavious if your device initially starts > > > talking to vdccm and disconnect a view seconds. Maybe there is a firewall > > > running somehow which prevents vdccm sending the "ping" packages to the > > > device and/or prevents receiving the "pong" packages back. Try to start > > > vdccm with "-d 5 -s 2" and have a look at the output of vdccm - every 2 > > > seconds a ping-package should be send to the device and the corresponding > > > "pong" package should be received. If this isn't the case you have some > > > fundamental connection problems to you device. > > > > I have disabled the firewall and the device works if the dccm.sh script > > is in place. > > > > > > vdccm -d 5 -s 2 -f -i > > [static void Utils::runScripts(std::string, std::string):230] Running > > script: /home/patrick/.synce/scripts/dccm.sh start > > [bool WindowsCEDevice::handleEvent():184] Header: 0 > > [bool WindowsCEDevice::handleEvent():186] initialization package > > [bool WindowsCEDevice::handleEvent():184] Header: 100 > > [bool WindowsCEDevice::handleInfoMessage(uint32_t):93] this is an > > information message > > [bool ConnectionFileManager::_writeConnectionFile(std::string, const > > WindowsCEDeviceBase*):117] Writing > > client-file: /home/patrick/.synce/192.168.131.129 > > [bool ConnectionFileManager::_writeConnectionFile(std::string, const > > WindowsCEDeviceBase*):117] Writing > > client-file: /home/patrick/.synce/active_connection > > [static void Utils::runScripts(std::string, std::string):230] Running > > script: /home/patrick/.synce/scripts/dccm.sh connect > > [void DeviceManager::addConnectedDevice(WindowsCEDeviceBase*):85] Device > > connected: 192.168.131.129 > > [bool WindowsCEDevice::handleEvent():184] Header: 305419896 > > [bool WindowsCEDevice::handleEvent():188] this is a ping reply > > [bool WindowsCEDevice::handleEvent():184] Header: 305419896 > > [bool WindowsCEDevice::handleEvent():188] this is a ping reply > > [bool WindowsCEDevice::handleEvent():184] Header: 305419896 > > [bool WindowsCEDevice::handleEvent():188] this is a ping reply > > [bool WindowsCEDevice::handleEvent():184] Header: 305419896 > > [bool WindowsCEDevice::handleEvent():188] this is a ping reply > > [bool WindowsCEDevice::handleEvent():184] Header: 305419896 > > [bool WindowsCEDevice::handleEvent():188] this is a ping reply > > [bool WindowsCEDevice::handleEvent():184] Header: 305419896 > > [bool WindowsCEDevice::handleEvent():188] this is a ping reply > > [bool WindowsCEDevice::handleEvent():184] Header: 305419896 > > [bool WindowsCEDevice::handleEvent():188] this is a ping reply > > [bool WindowsCEDevice::handleEvent():184] Header: 305419896 > > [bool WindowsCEDevice::handleEvent():188] this is a ping reply > > Ok, this looks like ok. Vdccm sends and receives those ping-pong packages. > Thus, vdccm is not the reason, why you device disconnects after some time.
Cool, So if the dccm.sh script is unnecessary when not running raki is it just a simple matter of disabling the check in code to get past that step? Cheers. -- Patrick Shirkey Boost Hardware Ltd. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ SynCE-Devel mailing list SynCE-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synce-devel
