Starting a device

[PeteK]

I'm having a problem getting my Insteon device to start when starting LinuxMCE.  I can start the executable correctly by executing

/usr/pluto/bin/Insteon -d 63


63 is the device number of the Insteon Interface.  It won't run correctly if I don't add the -d parameter.  I'm not sure this is correct, but  I got it working this way and haven't gotten around to looking at this until now. 

The LMCE launch manager tries to launch the device, but the status window says that it timed out waiting for the Insteon device to register.

The device logs shows:

== ATTEMPT FRESH START ==
1   11/25/07 14:24:07   /usr/pluto/bin/Spawn_Device.sh 63 (spawning-device)   21116 Dev: 63; Already Running list: 15,16,17,18,27,37,
== FRESH START ==
1   11/25/07 14:24:07   /usr/pluto/bin/Spawn_Device.sh 63 (spawning-device)   device: 63 ip: localhost cmd_line: Insteon
0   11/25/07 14:24:07   63 (spawning-device)   Entering 63
========== NEW LOG SECTION ==========
1   11/25/07 14:24:07   63 (spawning-device)   Starting... 1
1   11/25/07 14:24:07   63 (spawning-device)   Found ./Insteon
Return code: 126
3   11/25/07 14:24:07   63 (spawning-device)   Device died... count=1/50 dev=63
Sun Nov 25 14:24:07 PST 2007 died
========== NEW LOG SECTION ==========


I need to get this working for release, so any help is appreciated.

[bulek]

Got any logs ?

Did you specify Binary to run properly ?

HTH,

regards,

Bulek.

[PeteK]

That's the only log I dug up so far.

I'm not 100% certain what you mean by specifying the Binary to run properly.  The permissions match the rest of the binaries in the usr/pluto/bin/directory.

Any ideas on where else to look?

[darrenmason]

All devices will need the device ID passed to it, otherwise they are unable to determine which device instance you want to start.
The device may not be registering itself properly with DCE router.

Is your constructor calling its ancestor constructor?

Is getConfig() returning true?

I assume that it is doing what you want when run from the command line (with the device id passed in).

I think the launch manager monitors returns codes and kills devices if they are not good. I believe this is what you are seeing in your log.
Try and find what is giving you a return code of 126?

[PeteK]

The constructor in the Insteon.cpp file (originally generated using DCEGen) does not call any ancestor constructors, but looking at the Zwave, code, that constructor does not do so either.

GetConfig() returns true;

It is in fact behaving correctly when run from the command line with the device ID passed in.

I notice the main file is calling Connect() which is not one that is part of the Insteon class (it must be a member function of a parent class but I can't find the function definition.  However, the function is returning true (at least when I call it from the command line) which looks to be correct.