Hi Bob:
Thanks for your kindly reply.
you might want to make sure you have the latest timercore app loaded on the PLC. The SDM should be able to load that. I don't have the exact instructions for that here at work, but they're probably posted somewhere.
Can you tell me more detail? what is SDM ? what exactly the timercoreapp affects the transmission between PC to PLC?
I used SmartLabs Device Manager (may be the SDM you mentioned) and typed the following "dl=insteon.net:timercoreapp12" to download the timercoreapp12. and It get back to me the successful message. So I think there is newest timercoreapp in my PLC. But I still not getting to goal from ilink. Please advise.
It looks like you're using the kernel driver. Because it read the firmware version, reading from the PLC is working. It's just the writing that is failing. This may be a problem with the iplc driver and you're specific kernel version or might be something with the PLC.
I've stopped using the iplc driver in favor of the HIDDEV driver. You might want to try the HIDDEV driver. Assuming you have HID support in your kernel. To switch, you'll have to change the source slightly and recompile. To change icmd.c look for a line that looks like this:
Code:
if ((iplc = ilib_open(USE_IPLC, "/dev/usb/iplc0")) != NULL) {
and change it to look like this:
Code:
if ((iplc = ilib_open(USE_HIDDEV, "/dev/hiddev0")) != NULL) {
You'll have to unplug the PLC, rmmod the iplc driver, then plug the PLC back in. The HID driver should take control of the PLC. To run the programs with a user account (not root), the /dev/hiddev0 device will need to have both read and write access set for that user.
I had tried to use HIDDEV to drive the PLC. but I seems a little bit worse than that I using IPLC. following is the message from icmd.
# ./icmd -v 04.bb.b5 FAST_OFF
Timeout in ihid_cts (0)
Timeout waiting for PLC to echo data.
Command failed
Sending command 0x14 0x00 to 04.bb.b5
Timeout in ihid_cts (0)
Timeout waiting for PLC to echo data.
Timeout in ihid_cts (0)
Timeout waiting for PLC to echo data.
Timeout in ihid_cts (0)
Timeout waiting for PLC to echo data.
Timeout in ihid_cts (0)
Timeout in ihid_cts (0)
Timeout in ihid_cts (0)
Timeout in ihid_cts (0)
Timeout in ihid_cts (0)
Timeout in ihid_cts (0)
Timeout in ihid_cts (0)
Timeout in ihid_cts (0)
Timeout waiting for PLC to echo data.
Timeout in ihid_cts (0)
Timeout waiting for PLC to echo data.
Timeout in ihid_cts (0)
Timeout waiting for PLC to echo data.
255
I think that could be something err in my kernel USB HID.
I am using CentOS 4.5 with kernel 2.6.9-55.EL come with CentOS 4.5.
Could you please tell me your kernel version and what OS you are using. Thank you.
By the way. the following raw message is dump from SALad IDE that successful send the message to PLC and make the LAMPLINC light up.
Could you please help to find some clue about what different between SALad IDE and ilink. Thanks in advance.
T:02 40 01 A1 00 09 FB E4 07 F9 EB 04 BB B5 00 12 00
S:02 02 40 00 00 00 00 00
S:03 01 A1 00 00 00 00 00
R:
R:02 40
S:03 09 FB E4 00 00 00 00
S:03 07 F9 EB 00 00 00 00
R:
R:01
R:A1 00
R:
S:03 04 BB B5 00 00 00 00
S:03 00 12 00 00 00 00 00
R:09
R:
R:
R:
R:06
T:02 46 01 42 10 9F
S:03 01 42 10 00 00 00 00
R:
R:02
R:46
S:01 9F 00 00 00 00 00 00
R:
R:01 42
R:10
R:
R:9F 06
R:02
R:45 04
R:02
R:4F 04 04
R:BB B5 07 F9
R:EB 20 12 00
With My Best Regards
Tye