Announcement

Collapse
No announcement yet.

Discussion for GamePort+ Plugin Version 2.7.0......New!

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • ldragon99
    replied
    How do I set this up. Do I need to delete the old script? Is there any docs for it?

    Leave a comment:


  • electron
    replied
    I posted the first public beta of my new software:

    http://www.cocoontech.com/index.php?showtopic=228

    ---
    Do you cocoon?
    http://www.CocoonTech.com

    Leave a comment:


  • Michael McSharry
    replied
    I'm not certain if there is a design intent or this is just how it has evolved, but my understanding is as follows:

    An Input type plugin can be an IO type or an X10 type. IO types deal in DeviceValues and X10 types deal in ON/OFF/DIM/... commands/status.

    An X10 device uses the X10Event callback which will set the DeviceStatus and not geneate a SETIO, but can generate a ReceiveX10 event callback(&H1) as well as a State Change event callback (&H4).

    An X10 device, as an output, responds to the ExecX10 command. This generates a SETIO which the plugin used to output the command. TransmitX10 (&H16) and perhaps a State Change event callback (&H4) will be produced. Note that the TransmitX10 event and the SETIO calls are not generated when a SetDeviceStatus are used, hence no output is produced on a SetDeviceStatus.

    An IO device informs HS of an input change with the ValueChange callback. This will let HS change the deviceValue without producing a SETIO call back to the plugins. I forget if the State Change (&H4) event may be geneated.

    An IO devcice, as an output, responds to a SetDeviceValue command. This will generate a SETIO call to which the plugin will service by output of the value. Same memory lapse on the State Change (&H4) event.

    Since the SETIO call is made for both X10 and IO device output commands to a plugin, it is up to the plugin to decipher if it is going to respond to the command (ON/OFF etc) or to the value/brightness parameters. I'm fuzzy on a good decode strategy for the general case since I've seen a variety of combinations occur.

    From a GUI control perspective, if there are only two states it is best viewed as a device that can respond to ON and OFF commands. If it has more than two states then it needs to be controlled as enumerated values which shows up 2 levels lower in the GUI control interface. Just a human-factor difference. From the web view all buttons are at the same level. Only the labeling changes.

    With all this being said, I think what is desired is button inputs to look like ON/OFF commands for which the state is maintained as DeviceStatus. For joystick inputs these are analog and maintained as DeviceValue.

    The button state should be able to be communicated to HS via the X10Event. This will change the status, generate a Callback for the button press (&H1), and a callback for the state change (&H4).

    The joystick update should be done via the ValueChange callback.


    Now that I have gone through this description I can see that the ExecX10 for a button input will work, but conveys the wrong information since it will produce an X10Tansmit event (&H10). The use of the X10Event is most closely aligned with event notification associated with the change of an external input. Don't be confused with the "X10" part of these commands since they apply to any signal that behaves according to ON/OFF type status criteria.


    Of course the above is my view of how the system should function in a predictable manner. There are various combination of commands and callbacks that can be used to achieve any pluign-specific control action. With a variety of plugin authors I'm certain a hodgepodge of techniques are being used.

    Leave a comment:


  • electron
    replied
    Michael,

    You will like the new program, One thing I do have to mention is that it is no longer a plugin. It is a seperate exe using the activeX interface to talk to Homeseer, this way it can run in it's own thread (very important if you have 9 gameports like I do), but it can also run as a standalone app without Homeseer, and execute a batch file when either ON/OFF have been received. I am really liking the way this is going, I hope you guys will too. Should I allow one to select the mode how to notify HS (Exec10/SetDeviceStatus), or doesn't it make sense at all to support setdevicestatus? I agree with your logic, just making sure I am not missing out on anything.

    About the super trigger, this is the constant I added:

    Const EV_TYPE_STRING_CHANGE = &H40

    then you can use HSEvent to process device string changes:

    parm(0) = EV_TYPE_STRING_CHANGE
    parm(1) = device's house code and unit code (string)
    parm(2) = Value of the string that the device is being set to.

    ---
    http://www.CocoonTech.com

    Leave a comment:


  • Michael McSharry
    replied
    Second request on gameport. When a button press is detected then use the ExecX10 or X10Event methods to inform HS rather than the SetDeviceStatus. This will provide greater flexibiltiy in event triggering. The button press is really an external event that occurred rather than just a status change.

    Leave a comment:


  • Michael McSharry
    replied
    I would like to see a mechanism by which events (value changes) can be triggered based upon a change in the analog input. Filtering would be necessary to eliminate noise and drift. In my case the amount of change is not important as that can be detemined by the event handler.

    Dan, On a totally different subject...
    I've tried to make the String change callback work and have not had any luck with V188 of HS. I've tried the bit value of 64 and 128 to select this callback option, but never any HSEvent generated. All the other bits 1, 2, 4, 8, 16, and 32 do provide the desired callbacks. What setup do you use in SuperTrigger to get the callback to the plugin?

    Leave a comment:


  • electron
    replied
    not having any problems, I made changes to this plugin to support 4 ports, and other people are using it without problems, the new one I am writing is totally different, should be more flexible, and has many new options.

    ---
    http://www.CocoonTech.com

    Leave a comment:


  • ldragon99
    replied
    That is great to hear. I look forward to the updated version. And more importantly... My wife looks forward to it.

    Are you having the same issues with this script?

    Leave a comment:


  • electron
    replied
    I am currently working on a totally new gameport processor (written from scratch) for Homeseer, which will have many more features, and will support unlimited # of gameports (limit is set by the OS), it should be ready soon since I need it really bad too.

    ---
    http://www.CocoonTech.com

    Leave a comment:


  • ldragon99
    replied
    When I first installed this script my WAF went way up. I have it set up with magnetic contacts on all doors and windows. We spend most of our evenings down in the recroom (Basement) so it is nice to know when the front door opens. We have an alarm with a really loud bell. However being the CRAZY NA person I am I changed that so HS announces that "The front door has been opened". My wife thought that it would be nice if it did that for all doors and windows, so set it up.

    NOW THE PROBLEM. For some unkown reason, HS starts running all scripts asociated with the gameport script. So I hear:

    The front door has been opened
    the patio door has been opened
    the living room window has been opened
    etc... for all 12 sensors.

    Really annoying at 3:00am, then 3:45 am, them 5:00am. I am sure you get the message.

    Also If I open an event, (Even one that has nothing to do with the game port script) I get the same thing.

    I would really appreciate any help people can give. I am sure everyone would agree that when The WAF is high, we have to climb mountains to keep it there in this game.. lol

    PLEASE HELP

    Leave a comment:


  • ldragon99
    replied
    I am having alot of problems with this pluging eatting and keeping alot of the resources on my system. Is anyone else having this problem, or did they. Is there a fix?

    I love the plug in but everything else runs really slow. especially my HSP

    Leave a comment:


  • ldragon99
    replied
    I have installed the script and have 8 devices for each gameport. I am using 4 gameports. I can use devices 1 to 4 on each with no problem but I am usure how to use the last 4. What pins control it and how do I set this up?

    Leave a comment:


  • ldragon99
    replied
    Is there a way to change the plug in to use a house code that is used. I want to use a code A. For scripting and orginization. Is there a way to do this?

    Leave a comment:


  • StePhan
    replied
    <BLOCKQUOTE class="ip-ubbcode-quote"><font size="-1">quote:</font><HR>Originally posted by Aaron:
    I think it would be cool to hear some ways people are using (or planning to use) this powerful plug-in.

    Please post.

    --
    Aaron<HR></BLOCKQUOTE>

    Tells Me When the Garage Door Open Close
    but if I try to turn the master bedroom light off
    and the garage door is open the light comes back on
    here is the script I use
    <pre class="ip-ubbcode-code-pre">
    sub main()
    if hs.ison("\1") then 'The Garage Door
    hs.writelog "Warning","Garage Door Still Open"
    hs.WaitSecs 10
    hs.Speak "Warning! The garage door still open!"
    hs.ExecX10ByName "Master Bedroom Lights", "On"
    end if
    end sub
    </pre>

    StePhan McKillen

    My Pages

    [This message was edited by StePhan on Thu, 25 December 2003 at 05:52 AM.]

    Leave a comment:


  • Guest's Avatar
    Guest replied
    I think it would be cool to hear some ways people are using (or planning to use) this powerful plug-in.

    Please post.

    --
    Aaron

    Leave a comment:

Working...
X