Page 1 of 13 12311 ... LastLast
Results 1 to 10 of 123

Thread: Ocelot PLugin Update to V4 - Help?

  1. #1
    Join Date
    Jan 2004
    Posts
    362

    Default Ocelot PLugin Update to V4 - Help?

    Okay, after using Neil's GREAT Ocelot plugin for many months, are we ready to update the ADI Ocelot/Leopard users to G4?

    My best guess is that we can copy the format used by the W800RF32 and then create some LUA code. That is where I might need some help!

    We need to be able to Receive and Send X10, Send IR, Get and Set Variables, and ?? Anyone else want to add their wish list?

    So, Ron or Neil, can you send me the source code that you have so far?

    It would appear that the Ocelot plugin would be a good compliment, and would be as easy as the Generic X10 plugin.

    Any help would be great!
    Todd Reed
    Ocelot Automation Rookie

  2. #2
    Join Date
    Dec 2001
    Posts
    11,560

  3. #3
    Join Date
    Dec 2001
    Posts
    11,560

    Default

    try this for getting x10....

    please in the serial dir. restart g4. goto serial and assign to the right port.

    send some x10, check the console
    Attached Files Attached Files

  4. #4
    Join Date
    Jan 2004
    Posts
    362

    Default Updated Ocelot Protocol

    Here is the updated Ocelot Protocol, with Leopard commands and several that were left out of the link listed above.

    I will test the LUA you sent.
    Attached Files Attached Files
    Todd Reed
    Ocelot Automation Rookie

  5. #5
    Join Date
    Jan 2004
    Posts
    362

    Default Roadmap!

    Mike,

    Can I get a road map of this development process?

    Something like...
    1) Connect to device using Serial Plugin, get comms working, then Receive X10 activity, and use as an events.
    2) Create DUI form, Send X10 as an action.
    3) Add IR functions
    4) Add Variable functions
    5) Wrap up packing, and write help files!

    What will the end result be?
    How user friendly?
    Where will various commands be found?

    Thanks!
    Todd Reed
    Ocelot Automation Rookie

  6. #6
    Join Date
    Dec 2001
    Posts
    11,560

    Default

    That's about it.

    I will give you a hand getting started and some of the difficult stuff but the rest will be up to you... :-?

  7. #7
    Join Date
    Jan 2004
    Posts
    362

    Default

    Great!

    I have figured out how to create the DUI form, and place it on the tree, but now I have to make the HC/UC/FC fields usable, and send actions to the Ocelot...

    I assume I can use the same Ocelot PluginID = 156?

    I'll keep reading...
    Todd Reed
    Ocelot Automation Rookie

  8. #8
    Join Date
    Jan 2004
    Posts
    362

    Default

    Okay, I tried the LUA code.

    I have configured it to a USB to Com4 adapter, so I can see it polling!

    Nothing in the console window...

    Then, I tried some Serial Send actions and it started to fill the console with errors...
    Todd Reed
    Ocelot Automation Rookie

  9. #9
    Join Date
    May 2004
    Location
    Cardigan, UK
    Posts
    9,278

    Default

    First of all, what sort of errors?

    Try setting LogLevel = 0 in your serial device[/quote]
    --Rob

  10. #10
    Join Date
    Jan 2004
    Posts
    362

    Default

    With Loglevel = 0, I get...

    Code:
    Welcome to Promixis Girder 4.0!
    Serial:  ADI Ocelot :  Opened Device: ADI Ocelot  Port: 4  Settings: 9600 N 0 8 0
    Serial:  ADI Ocelot :  Callback Installed  1
    Serial:  ADI Ocelot :  Command queued:  C8 38 00 00 00 00 00 30      8.....0  at postion  1
    Serial:  ADI Ocelot :  Simple Send:   C8 38 00 00 00 00 00 30      8.....0
    Serial:  ADI Ocelot :  Simple Receive:  Data  15 00 15      ...  Code:  0
    Serial:  ADI Ocelot :  Command queued:  C8 38 00 00 00 00 00 30      8.....0  at postion  1
    Serial:  ADI Ocelot :  Simple Send:   C8 38 00 00 00 00 00 30      8.....0
    Serial:  ADI Ocelot :  Simple Receive:  Data  15 00 15      ...  Code:  0
    Serial:  ADI Ocelot :  Command queued:  C8 38 00 00 00 00 00 30      8.....0  at postion  1
    Timer (pcall):  ...OGRAM FILES\PROMIXIS\GIRDER\/plugins/serial/init.lua:267: Timer already destroyed
    stack traceback:
        [C]: in function `Arm'
        ...OGRAM FILES\PROMIXIS\GIRDER\/plugins/serial/init.lua:267: in function `SendCommand'
        ...OGRAM FILES\PROMIXIS\GIRDER\/plugins/serial/init.lua:423: in function `SendCommand'
        ...RAM FILES\PROMIXIS\GIRDER\/plugins/serial/Ocelot.lua:92: in function `SendCommand'
        ...RAM FILES\PROMIXIS\GIRDER\/plugins/serial/Ocelot.lua:134: in function `GetX10'
        ...RAM FILES\PROMIXIS\GIRDER\/plugins/serial/Ocelot.lua&#58;62&#58; in function <...RAM FILES\PROMIXIS\GIRDER\/plugins/serial/Ocelot.lua&#58;62>
    The three lines; Simple send, Simple receive, Command qued - repeat over and over. I assume this is correct.

    I start the events and send an A9/On and an A9/Off command. Then stop events and look at the console.

    When I stop and start events, it doesn't always stop the polling. Sometimes with events stopped, it keeps filling the console!
    Todd Reed
    Ocelot Automation Rookie

Page 1 of 13 12311 ... LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •