From: Scott R. <sc...@th...> - 2004-02-07 14:10:45
|
I spent a bit more time with this this morning... it turns out that in my rush to try Bruce's suggestion before heading out the door, i got the code a bit wrong. looks like send_x10_data lives in Serial_Item, so i updated my X10_Items.pm with: &Serial_Item::send_x10_data($self->{interface}, 'X' . $self->{x10_id} . 'ON') if $self->{type} =~ /preset2/i and $state =~ /^(\d+)\%/; unfortunately, that didn't do the trick either. looking at my outgoing X10 with x10 errata set to 4, I only see: outgoing data=XN7N&P33 (or whatever &P%%) I'm not seeing the ON command being sent to N7. shouldn't the effect of &Serial_Item::send_x10_data() be seen in the log window if x10 errata is at 4? s:r On Fri, 06 Feb 2004 17:46:12 -0500, Scott Reston wrote: >nope. no dice. i did need to make one small change = i added &main::send_x10_data in place of &send_x10_data > >but it still acted the 'strange' way. > >s:r > >On Wed, 4 Feb 2004 21:31:06 -0600, Bruce Winter wrote: > >> >>I didn't test this, but should give you a start of something to try. In >>lib/X10_Items.pm, try adding the last lines here: >> >> >> $self->SUPER::set($state, $set_by); >> >> # Some presetable devices, like the 6381, will remain addressed >> # after a preset command and will and accept subsequent unrelated >> # commands unless they are set to ON. >> &send_x10_data($self->{interface}, 'X' . $self->{x10_id} . 'ON') if >> $self->{type} =~ /preset2/i and $state =~ /^(\d+)\%/; >> >> >>Then use an item type of preset2. Or you could use a model number instead >>of the not-so-inventive name of preset2, but this might be better if we run >>into similar issues on other devices, and you would need to update the >>preset test further up in that code. >> >>Hmmm, what do you currently have coded for your item type? If not lm14 or >>preset, you might be running code you don't need, which was ment for >>non-presetable devices. >> >>Bruce >> >> >> >> >>------------------------------------------------------- >>The SF.Net email is sponsored by EclipseCon 2004 >>Premiere Conference on Open Tools Development and Integration >>See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. >>http://www.eclipsecon.org/osdn >>________________________________________________________ >>To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365 >> > > > > > > >------------------------------------------------------- >The SF.Net email is sponsored by EclipseCon 2004 >Premiere Conference on Open Tools Development and Integration >See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. >http://www.eclipsecon.org/osdn >________________________________________________________ >To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365 > |