[root@localhost ilink2]# ./ilink
Error opening device
Querying Bedroom ControlLinc
Segmentation fault
[root@localhost ilink2]#
The first line there, "error opening device" means that the program never was able to connect with the PowerLinc. If you see that, don't even bother trying anything else.johnnynine said:I entered all of my devices including the PowerLinc and a ControlLinc.
When I choose Discover existing Scenes the program crashes and I get:
Code:[root@localhost ilink2]# ./ilink Error opening device Querying Bedroom ControlLinc Segmentation fault [root@localhost ilink2]#
Then when I run ilink again it fails to initialize the PowerLinc.
I then have to reboot (ie. reboot the linux virtual machine) to get ilink to communicate with the powerlinc.
Johnny
How do I unload the usb driver? Do I run an application or just unlplug the PLC?bpwwer said:You might have to go throught the steps again to get the USB driver working. (unload usb driver, re-attach plc, run detach, load driver).
Yeah, the interaction between the driver, the PLC and the OS doesn't work quite as well as it all should.johnnynine said:How do I unload the usb driver? Do I run an application or just unlplug the PLC?bpwwer said:You might have to go throught the steps again to get the USB driver working. (unload usb driver, re-attach plc, run detach, load driver).
You're right, it doens't do any error checking to prevent the same device from being entered twice. I thought about that at one point and then forgot. I'll add it to the list of things to fix. Delete device is implemented. It should remove the device from all scenes and from all the drop down boxes. I'll have to look into what it's doing. It isn't saving a device that was deleted but the device seems to stay in the drop down boxes.ginigma said:1. I can manually add a device and discover a device Ok. However, I found that if I add the same device a second time, it will let me. Perhaps some error checking based on device address would help. If I select the device from the Device Programming dropdown and click Delete Device, nothing happens.
List Linktable doesn't actually do anything yet. I was thinking it would query the device for the actual link table. Right now it will display what the program thinks the link table should be. This is what is suppose to get sent to the device when you program a device.ginigma said:2. If I select a device (from the Device Programming dropdown) and click List Linktable, nothing happens. No error message or console message. In general, it doesn't look like any of the Device Programming buttons are working. [edit: After discovering existing scenes, when selecting a device, it had information in the list. Deleting a device from the list produced a Segmentation fault.]
You're talking about discover device? Good thing someone is testing it. So far I've only tested with one Icon dimmer switch. I'll try some more devices and see if I can track this down.ginigma said:3. During discovery, it read a SwitchLinc V2 ver2.2 as a "PowerLinc V2 pre 1.6" and Firmware "0.1". I also received 20 "** (ilink:31630): CRITICAL **: file pango-layout.c: line 1773 (pango_layout_get_cursor_pos): assertion `index >= 0 && index <= layout->length' failed" messages in the console window.
Correct. Another enhancement would be to limit the group numbers selectable based on the device type listed as scene controller. Delete device from scene didn't work? I'll have to look into that.ginigma said:4. During Discover existing scenes, it queried my devices. I added a device to a scene, but couldn't delete it from the scene. Not sure what's going on. Are Scene Group #'s supposed to correspond to the controller type, e.g. a ControLinc would have scenes 1-5, a SwitchLinc would only have 1 scene, etc?
You're right, it should but doesn't yet. I started adding in code to keep track of changes and such so that save and save as work right. Hey, at least it lets you save it!ginigma said:5. File -> Save always prompts for a filename. Shouldn't it save to the current open file? Only File -> Save As should prompt for a filename.
Thanks. I'm glad you like it and appreciate the feedback. Once I got all my devices programmed (using the command line version), I've been somewhat reluctant to try too many things using the GUI version. Mostly I've been adding new features. I have a keypadlinc configuration dialog somewhat working (needs testing) and have started on the code to program timers into the PLC. I guess I ought to step back and do some bug fixes :angry:ginigma said:In general I'm pleased with what this program will be able to do. I started using PowerHome to create scenes, but that is overkill for my needs right now. ilink is (will be) perfect.
I've started compiling a FAQ based on Q&A in this thread and my own "fooling around." I'll post a link here in a couple days.
I don't think I've tried this recently, I'll have to look into it. I don't think any of my changes yesterday directly effect this.johnnynine said:Delete Scene gives me a Segmentation fault.
I did a number of file saves yesterday and didn't see this. Probably a scene is messed up and causing problems. I'll look at the save code and try to make it more robust. I'd suggest making backup copies or saving to a new file name for now. That way you won't lose everything.johnnynine said:Save gave me a segmentation fault and I my old saved file was replaces with a new one with comments in it only.
I think this can only happen if the PLC stops communicating. I had this problem a lot when I was trying to use libusb to talk with the PLC. Since I switched to using the usb driver, I haven't had this problem. It is interesting that you see it when trying to read from the KeypadLinc. While I do see some corruption in messages back from remote devices, I haven't had mine lock up.johnnynine said:Selecting Discover Scenes after entering all of my devices (except the powerlinc) I got:
[root@localhost ilink2]# ./ilink
Querying KeypadLinc
Timeout in usb_cts (0)
Timeout in usb_cts (0)
Timeout in usb_cts (0)
That's a good idea. It probably isn't too hard to do but youi'll have to remember the order that discovered them in when you go to rename them. But I guess that's not really my problemjohnnynine said:On the plus side, Device Discovery worked. It would be nice it it would auto add the device and allow rename later so we could add more than 1 at a time.
Device Control also worked fine.
The weather wasn't very nice yesterday so I had some time to write code. Otherwise, it's an hour here and there. I need more spare timeginigma said:Thanks for the info Bob. I just received a KPL yesterday and I'm hoping to have some time to fool around with it this week. Unfortunately my real job keeps getting in the way of me working on HA.
I second this. It would be a great time saver to discover all the devices without all that walking back and forth.That's a good idea. It probably isn't too hard to do but youi'll have to remember the order that discovered them in when you go to rename them. But I guess that's not really my problem(johnnynine @ Mar 5 2006, 10:08 PM)
On the plus side, Device Discovery worked. It would be nice it it would auto add the device and allow rename later so we could add more than 1 at a time.
Device Control also worked fine.