PDA

View Full Version : Ocelot PLugin Update to V4 - Help?



Todd Reed
March 23rd, 2006, 09:16 PM
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!

Promixis
March 24th, 2006, 06:02 AM
http://www.appdig.com/Serprot/CPUXA_Protocol.pdf

Promixis
March 24th, 2006, 06:52 AM
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

Todd Reed
March 24th, 2006, 09:24 AM
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.

Todd Reed
March 24th, 2006, 02:49 PM
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!

Promixis
March 24th, 2006, 02:59 PM
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... :-?

Todd Reed
March 24th, 2006, 04:25 PM
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
March 24th, 2006, 10:11 PM
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...

Rob H
March 25th, 2006, 03:26 AM
First of all, what sort of errors?

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

Todd Reed
March 25th, 2006, 10:29 AM
With Loglevel = 0, I get...


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!

Rob H
March 25th, 2006, 11:52 AM
I need to see your current version of Ocelot.lua since those line numbers don't tie up with the one that Mike posted earlier.

Todd Reed
March 25th, 2006, 01:12 PM
Rob, see attached

My two comments are:

Checksum looks bad, 30 hex is 48 decimal, should this be 0 or 256?

Simple Receive is 15,00,15 which is 21,0,21 decimal - Should be 6,0,6 per protocol

hoox
March 25th, 2006, 01:53 PM
Todd,

I'd suggest to test with another command than GetX10.
Sef published a protocol on his site, telling this one didn't work as documented...

Todd Reed
March 25th, 2006, 02:29 PM
I got some updates from Guy at the ADI forum.

If SEF has his protocol, or you have links, please post! I asked for SEF's source code but have not heard from SEF.

I am sure he has worked through all these issues! :)

hoox
March 25th, 2006, 02:49 PM
http://neilgoodman.com (Projects/Ocelot Serial Protocol)

Rob H
March 25th, 2006, 02:56 PM
Yes, the checksum looks to me as though it should be 0 for that command. And of course that is exactly what the checksum calculates, however it is just being added as a '0' to the string which is 48 decimal.

Change the line in SendCommand to


command = command .. string.char&#40;checksum&#41;


And see where we go from there

Todd Reed
March 25th, 2006, 03:11 PM
Wow! Thanks for all the help!!


Welcome to Promixis Girder 4.0!
Serial&#58; ADI Ocelot &#58; Opened Device&#58; ADI Ocelot Port&#58; 4 Settings&#58; 9600 N 0 8 0
Serial&#58; ADI Ocelot &#58; Callback Installed 1
Timer &#40;pcall&#41;&#58; ...RAM FILES\PROMIXIS\GIRDER\/plugins/serial/Ocelot.lua&#58;90&#58; attempt to index global `String' &#40;a nil value&#41;
stack traceback&#58;
...RAM FILES\PROMIXIS\GIRDER\/plugins/serial/Ocelot.lua&#58;90&#58; in function `SendCommand'
...RAM FILES\PROMIXIS\GIRDER\/plugins/serial/Ocelot.lua&#58;134&#58; 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>


Thanks for the link to the protocol...

Promixis
March 25th, 2006, 03:26 PM
its string NOT String.

Todd Reed
March 25th, 2006, 05:24 PM
Ha ha, I am laughing Mike, cause I saw that a bit later... Got it!!

Results look closer, see below.


NR Loaded
Welcome to Promixis Girder 4.0!
Serial&#58; ADI Ocelot &#58; Opened Device&#58; ADI Ocelot Port&#58; 4 Settings&#58; 9600 N 0 8 0
Serial&#58; ADI Ocelot &#58; Callback Installed 1
Serial&#58; ADI Ocelot &#58; Command queued&#58; C8 60 00 00 00 00 00 28 `.....&#40; at postion 1
Serial&#58; ADI Ocelot &#58; Simple Send&#58; C8 60 00 00 00 00 00 28 `.....&#40;
Serial&#58; ADI Ocelot &#58; Simple Receive&#58; Data 06 00 06 FF FF ... Code&#58; 0
Serial&#58; ADI Ocelot &#58; Command queued&#58; C8 60 00 00 00 00 00 28 `.....&#40; at postion 1
Serial&#58; ADI Ocelot &#58; Simple Send&#58; C8 60 00 00 00 00 00 28 `.....&#40;
Serial&#58; ADI Ocelot &#58; Simple Receive&#58; Data 06 00 06 FF FF ... Code&#58; 0
Serial&#58; ADI Ocelot &#58; Command queued&#58; C8 60 00 00 00 00 00 28 `.....&#40; at postion 1
Serial&#58; ADI Ocelot &#58; Simple Send&#58; C8 60 00 00 00 00 00 28 `.....&#40;
Serial&#58; ADI Ocelot &#58; Simple Receive&#58; Data 06 00 06 00 08 ..... Code&#58; 0
Serial&#58; ADI Ocelot &#58; Command queued&#58; C8 60 00 00 00 00 00 28 `.....&#40; at postion 1
Serial&#58; ADI Ocelot &#58; Simple Send&#58; C8 60 00 00 00 00 00 28 `.....&#40;
Serial&#58; ADI Ocelot &#58; Simple Receive&#58; Data 06 00 06 00 48 ....H Code&#58; 0
Serial&#58; ADI Ocelot &#58; Command queued&#58; C8 60 00 00 00 00 00 28 `.....&#40; at postion 1
Serial&#58; ADI Ocelot &#58; Simple Send&#58; C8 60 00 00 00 00 00 28 `.....&#40;
Serial&#58; ADI Ocelot &#58; Simple Receive&#58; Data 06 00 06 00 13 ..... Code&#58; 0
Serial&#58; ADI Ocelot &#58; Command queued&#58; C8 60 00 00 00 00 00 28 `.....&#40; at postion 1
Serial&#58; ADI Ocelot &#58; Simple Send&#58; C8 60 00 00 00 00 00 28 `.....&#40;
Serial&#58; ADI Ocelot &#58; Simple Receive&#58; Data 06 00 06 FF FF ... Code&#58; 0
Serial&#58; ADI Ocelot &#58; Command queued&#58; C8 60 00 00 00 00 00 28 `.....&#40; at postion 1
Serial&#58; ADI Ocelot &#58; Simple Send&#58; C8 60 00 00 00 00 00 28 `.....&#40;
Serial&#58; ADI Ocelot &#58; Simple Receive&#58; Data 06 00 06 FF FF ... Code&#58; 0
Serial&#58; ADI Ocelot &#58; Command queued&#58; C8 60 00 00 00 00 00 28 `.....&#40; at postion 1
Serial&#58; ADI Ocelot &#58; Simple Send&#58; C8 60 00 00 00 00 00 28 `.....&#40;
Serial&#58; ADI Ocelot &#58; Simple Receive&#58; Data 06 00 06 00 08 ..... Code&#58; 0
Serial&#58; ADI Ocelot &#58; Command queued&#58; C8 60 00 00 00 00 00 28 `.....&#40; at postion 1
Serial&#58; ADI Ocelot &#58; Simple Send&#58; C8 60 00 00 00 00 00 28 `.....&#40;
Serial&#58; ADI Ocelot &#58; Simple Receive&#58; Data 06 00 06 00 88 .... Code&#58; 0
Serial&#58; ADI Ocelot &#58; Command queued&#58; C8 60 00 00 00 00 00 28 `.....&#40; at postion 1
Serial&#58; ADI Ocelot &#58; Simple Send&#58; C8 60 00 00 00 00 00 28 `.....&#40;
Serial&#58; ADI Ocelot &#58; Simple Receive&#58; Data 06 00 06 00 12 ..... Code&#58; 0
Serial&#58; ADI Ocelot &#58; Command queued&#58; C8 60 00 00 00 00 00 28 `.....&#40; at postion 1
Serial&#58; ADI Ocelot &#58; Simple Send&#58; C8 60 00 00 00 00 00 28 `.....&#40;
Serial&#58; ADI Ocelot &#58; Simple Receive&#58; Data 06 00 06 FF FF ... Code&#58; 0
Serial&#58; ADI Ocelot &#58; Command queued&#58; C8 60 00 00 00 00 00 28 `.....&#40; at postion 1
Serial&#58; ADI Ocelot &#58; Simple Send&#58; C8 60 00 00 00 00 00 28 `.....&#40;
Serial&#58; ADI Ocelot &#58; Simple Receive&#58; Data 06 00 06 FF FF ... Code&#58; 0
Serial&#58; ADI Ocelot &#58; Command queued&#58; C8 60 00 00 00 00 00 28 `.....&#40; at postion 1
Timer &#40;pcall&#41;&#58; ...OGRAM FILES\PROMIXIS\GIRDER\/plugins/serial/init.lua&#58;267&#58; Timer already destroyed
stack traceback&#58;
&#91;C&#93;&#58; in function `Arm'
...OGRAM FILES\PROMIXIS\GIRDER\/plugins/serial/init.lua&#58;267&#58; in function `SendCommand'
...OGRAM FILES\PROMIXIS\GIRDER\/plugins/serial/init.lua&#58;423&#58; in function `SendCommand'
...RAM FILES\PROMIXIS\GIRDER\/plugins/serial/Ocelot.lua&#58;92&#58; in function `SendCommand'
...RAM FILES\PROMIXIS\GIRDER\/plugins/serial/Ocelot.lua&#58;134&#58; 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>


Checksum = 28 hex, (40) looks okay.
Receive 06 00 06 FF FF (6,0,6,255,255) looks okay.
So you get several FF FF combo's until an X10 is sent.

Then for A9 Off you get three data sets:
06 00 06 00 08 = A9
06 00 06 00 48 = ??
06 00 06 00 13 = AOff

For A9 On you get these:
06 00 06 00 08 = A9
06 00 06 00 88 = ??
06 00 06 00 12 = AOn

Then the errors!

Also, I need the full function set for X10/Ocelot for the Dim, Bright, all on, all off, etc...

Thanks, all...

Rob H
March 25th, 2006, 05:44 PM
I'm a little worried that you are getting a Code value of 0 - that's not really supposed to happen.

Mind you, I'm not entirely happy with this being CB_FIXEDLENGTH and a ReceiveFixedLength of 512. That may account for the Code of 0.

Mike? Ron?

Promixis
March 25th, 2006, 08:30 PM
I'm a little worried that you are getting a Code value of 0 - that's not really supposed to happen.

Mind you, I'm not entirely happy with this being CB_FIXEDLENGTH and a ReceiveFixedLength of 512. That may account for the Code of 0.

Mike? Ron?

There is not start/stop byte or fixed length that I can see - so just picked a fixed length and catch the incomplete response time out??

Rob H
March 26th, 2006, 02:13 AM
Fair enough, but where does the Code 0 come from? Is that expected?

Promixis
March 26th, 2006, 06:43 AM
Fair enough, but where does the Code 0 come from? Is that expected?

yes, i clear that bit :)

Rob H
March 26th, 2006, 08:19 AM
Ah, I see

Todd Reed
March 26th, 2006, 10:34 AM
You talking about at the end of each receive line?

And, where would it "Print" the HC KC message, because I don't see this anywhere?

And, why the errors when you stop events?

How about trying a send X10 action?

hoox
March 26th, 2006, 11:55 AM
Todd,

About the errors when you disable events, it can come from the PollingTimer that is recurring.

You could consider to avoid polling for x10, I/O and IR by setting Ocelot Parameters 15, 16, 17 to 1.
It will automatically send a serial message including hc, kc or uc when receiving or transmitting something.

Then you only need to watch for those headers:

I/O status changed = 255
X10rx = 254
X10tx = 251
IRrx = 253
IRtx = 252

Promixis
March 26th, 2006, 04:12 PM
Todd,

About the errors when you disable events, it can come from the PollingTimer that is recurring.

You could consider to avoid polling for x10, I/O and IR by setting Ocelot Parameters 15, 16, 17 to 1.
It will automatically send a serial message including hc, kc or uc when receiving or transmitting something.

Then you only need to watch for those headers:

I/O status changed = 255
X10rx = 254
X10tx = 251
IRrx = 253
IRtx = 252

I didn't see that in the protocol guide anywhere :x

Todd Reed
March 26th, 2006, 05:57 PM
Me neither!!
(That is why Neil would be best doing this, I am such a rookie!!)

Below is a link that I got from the ADI forum, that explains even more...

http://www.appdigusers.com/forum/showflat.php/Cat/0/Number/187402/an/0/page/0#Post187402

What I am really looking for is:

"06 00 06 HC UC" - where UC is 40=1 On, 41=2 On, 43=3 On, etc and 80=1 Off, 81=2 Off, etc...

So we just need to look for UC>39 and <256 capture that HC UC.

BTW, where did Hoox find all this??

hoox
March 27th, 2006, 02:53 AM
It can be found at the last pages of http://www.appdig.com/manual/Ocelot-2.pdf

For now, you must set these parameters from C-Max, but it should be possible to do it from your plugin later.
From C-Max : Comms/Attach to Controller/Controller Utility/Retrieve Controller Parameters

Now if you send A9 OFF with an external controller, you receive two short consecutive messages like this:
FE 00 08 (rxX10 A 9)
FE 00 13 (rxX10 A OFF)

You can try with something like that:

Todd Reed
March 27th, 2006, 09:47 AM
Hoox,

Won't that interfear with the CMAX application? IE once set, you can still get online with CMAX?

And, shouldn't line 161 be:

if hc ~= 255 and kc ~= 255 then


See most recent protocol...

Thanks!

hoox
March 27th, 2006, 06:31 PM
Not sure what you mean about CMAX, but :
- The parameters don't affect it.
- Of course, the Serial plugin and CMAX can't use the COM port at the same time.
Mike certainly knows if it's possible to open/close the COM port to will. Then TaskCreate plugin may suffice to switch when needed...

You're correct about line 161, but you don't need the GetX10 function when Auto X10 is activated!
Change also line 156 to :

if string.sub&#40;self.LastCommand.Command, 1, 7&#41; == GetX10 then
or it will never be true as the checksum is included in self.LastCommand.Command!

Todd Reed
March 28th, 2006, 12:04 AM
Okay, that works, I see the commands in the console.
I assume we can now grap the data and use in an event.


Welcome to Promixis Girder 4.0!
Serial&#58; ADI Ocelot &#58; Opened Device&#58; ADI Ocelot Port&#58; 4 Settings&#58; 9600 N 0 8 0
Serial&#58; ADI Ocelot &#58; Callback Installed 1
Serial&#58; ADI Ocelot &#58; Simple Receive&#58; Data FE 00 08 .. Code&#58; 0
Received X10 &#58; A9 Off
Serial&#58; ADI Ocelot &#58; Simple Receive&#58; Data FE 00 13 .. Code&#58; 0
Serial&#58; ADI Ocelot &#58; Simple Receive&#58; Data FE 00 08 .. Code&#58; 0
Received X10 &#58; A9 On
Serial&#58; ADI Ocelot &#58; Simple Receive&#58; Data FE 00 12 .. Code&#58; 0
Serial&#58; ADI Ocelot &#58; Simple Receive&#58; Data FE 00 08 .. Code&#58; 0
Received X10 &#58; A9 Off
Serial&#58; ADI Ocelot &#58; Simple Receive&#58; Data FE 00 13 .. Code&#58; 0
Serial&#58; ADI Ocelot &#58; Simple Receive&#58; Data FE 00 08 .. Code&#58; 0
Received X10 &#58; A9 On
Serial&#58; ADI Ocelot &#58; Simple Receive&#58; Data FE 00 12 .. Code&#58; 0


I played with trying to send X10, but I am confused! :(
How do I tie the DUI form actions in the Ocelot_UI.lua to the Serial Ocelot.lua file?

...more reading...!

hoox
March 28th, 2006, 05:43 AM
It's up to you to choose the way events will be sent (One for each X10 command or not, separate all this in payloads...)

What's your problem with sending X10 ? Is it passing variables to your function?

For the DUI, I think it's safer to finish you serial script, defining all needed functions and parameters, before starting designing, but:


The simplest way of linking the controls to the script is to set the Field property of the control to ... an Action parameter (iValue1-3; bValue1-3; sValue1-3 or (for numbers only) lValue1-3) for Actions or Conditionals.

As you can see, there is 12 easily usable parameters in your Action DUI.
If you need more, you can use the Lua Field for your Controls, it can be more complicated.
So, to keep it simple if you need more than 12 parameters, just make a new Action page (it needs a new Action Subtype number).

And you can call your Serial script functions from the DUI script with something like (assuming you added GetVariable(VarNum)):
local v = Ocelot:GetVariable(3)

Promixis
March 28th, 2006, 08:41 AM
Todd,

We should do all x10 sending and receiving by the existing x10 device manager.

I will supply you with a function that you call when you get an x10 command pair... ie either HC UC or HC FC.

Then you will need to create a function the x10 device manager can call...

ie. Send X10 (HC,UC/FC)

HC = housecode
UC = unitcode
FC = function code

Todd Reed
March 28th, 2006, 05:56 PM
For example, how do I send a simple X10 HC/UC command? :roll:

I know how to create the DUI form. :wink:

I think I need a "Treescript.Action[xx]" in my Treescript LUA file.
(similar to Treescript.Action=[52] in file X10_UI.LUA)

And

I think I need a "Send X10" function in my Serial LUA file. :-?
(similar to "SendX10 = function" in file PowerLincSerial.LUA)

Then, add to this mix, Mike's suggestions of using the X10 Device Manager (examples or links or documentation on this?)

:-?

Todd Reed
March 30th, 2006, 12:16 AM
Okay, I'm stuck! :cry:

I have been looking at all the included Serial and Treescript LUA files, and I can't figure out how to parse, or connect between them.

Not much online help for the LUA librarys. Only two Serial.lua files that deal with X10, and they do it totally different, and only one sends X10.

If I had access to all the X10 functions in the DLL maybe that would help (or confuse!)

What I need is a complete example with a single function like sending HC/UC/FC commands. With Treescript.lua and Serial.lua files that work and details on how to use X10 Device manager...

Or, maybe this plugin is best left to Ron and Mike...

Promixis
March 30th, 2006, 06:29 AM
Todd, sorry, we just have alot of things on our plate right now...

1. you need to have the ocelot call the x10 event handler when new command pairs arrive...





X10&#58;ReceiveEvent &#40;hc,uc,fc&#41; -- event input from any x10 device, using standard x10, HC = A..P , UC = 1..16 and FC = text description of FC




-- standard list of x10 function codes
local FunctionCodes = &#123;
"ALL UNITS OFF",
"ALL UNITS ON",
"ON",
"OFF",
"DIM",
"BRIGHT",
"ALL LIGHTS OFF",
"EXTENDED CODE",
"HAIL REQUEST",
"PRESET DIM HIGH",
"PRESET DIM LOW",
"EXTENDED DATA",
"STATUS ON",
"STATUS OFF",
"STATUS REQUEST",
&#125;



next, to use the X10 Action Tree to send commands you need to provide me with a function to call - something like




Ocelot&#58;Send &#40;hc,uc,fc&#41;

Todd Reed
March 30th, 2006, 04:25 PM
Thanks Mike, I know you are busy!!

So, do I need to convert my received X10 and call this as alpha:
X10:ReceiveEvent (D,4,ON) Or what does "X10:ReceiveEvent (hc,uc,fc)" need for (hc, uc, fc) format?

And, will you be modifying the X10_UI to accommodate the Ocelot send?
IE: send to the X10 layer, and also to the Ocelot.lua?

And, hoox, I tried sending some raw Serial commands to the Ocelot.

A9 Off
Dec - 200 55 00 88 01 0 0 88
Hex - C8 37 00 58 01 00 00 58
Monitoring in LUA window, works fine, light turns off, see in response window

A9 On
Dec - 200 55 00 48 01 0 0 48
Hex - C8 37 00 30 01 00 00 30 does nothing?
Monitoring in LUA window, light does nothing, but I do see in "A9-On" in LUA monitor

Have you tested the "On" commands? It seems like the above A9 On does not work on the Ocelot... So this combined send technique may not work.

Promixis
March 30th, 2006, 04:38 PM
Todd,

the function PREFER's command pairs..

ie HC/UC or HC/FC

just leave the missing value as a nil.

HC must be a character A..P

UC must be a number or character 1..16

FC must be one of the text strings above.

You can send UC and FC at the same time but the plugin cannot track commands that do A1,A4,A3 AON

Todd Reed
March 30th, 2006, 06:03 PM
Like this...?



elseif string.sub &#40;data,1,1&#41; == RxX10 then -- Received X10 &#40;Ocelot Parameter 15 must be = 1&#41;

local h = string.byte &#40;data,2&#41; --House code
local k = string.byte &#40;data,3&#41; --Unit or Key code

if tonumber&#40;k&#41; < 16 then
UnitCode = kc&#91;'#' .. k&#93;
else
print&#40;'Received X10 &#58; ' .. hc&#91;'#' .. h&#93; .. UnitCode .. ' ' .. kc&#91;'#' .. k&#93;&#41;
X10&#58;ReceiveEvent &#40;hc,'',kc&#41;
end

Promixis
March 31st, 2006, 09:13 AM
Todd,

I am not sure what that will do....

with a command pair, there always a housecode and either a unit code or function code. you must figure out what the ocelot is sending - may show some output here. the missing uc/fc must be sent to the x10 manager as nil not ''.

hoox
March 31st, 2006, 07:25 PM
Todd,

as you guess, your raw sendings seems to have wrong uc/kc values...

here's a script that can send simple X10 commands (including groups), and pass received commands to X10 device manager.
You may have to adapt it to your needs.

I didn't figure out how to use Preset Dim. :-?
Do you have an example of serial command for that ?

Promixis
March 31st, 2006, 07:45 PM
do you have a device that supports preset dim?

hoox
March 31st, 2006, 08:07 PM
Yes, it's a PCS Style device, not Leviton. (And it works with CMAX)

Promixis
March 31st, 2006, 08:35 PM
use

X10:Level (hc,uc,level) -- level in percent

but we have to implement a send command in the x10 file for the ocelot

hoox
March 31st, 2006, 08:49 PM
Never mind Mike, now it's fine with Send Leviton X-10 Preset Dim from Ocelot Protocol ! :roll:

Todd Reed
April 1st, 2006, 12:25 AM
hoox,

You must have an Ocelot, cause you're making a heck of a lot more progress than I am!! I'm still trying to figure out when (hc, uc, fc, rc) is in Hex, String, or Decimal... :oops:

Your sample files seem to work. If you send commands like your GML example "Ocelot:SendX10 ('A','9', 'ON')" Thank you!! :D

I am trying to copy the X10 style in the Ocelot UI, which captures hc, uc, fc as decimal values. So when I set the UI form to: "M 3 On" it is giving me "12 2 1"

How do I convert these back to text before I send them to "Ocelot:SendX10(hc,uc,fc,rc)"?

And do I need the single quotes, and the extra space between uc and fc?

Promixis
April 1st, 2006, 07:11 AM
Todd,

I would use the X10 ui stuff. Why recreate it?

Terry, do I have been looking for how to send leviton extended commands to add to the x10 device manager. it currently on supports the PCS and Smarthome type of preset dims.

Todd Reed
April 1st, 2006, 08:44 AM
That is fine.

Then hoox need's to reconfig his "sendX10" for the existing X10UI data. Or add another version, keep one for raw data, and another one for the X10UI. And you will be providing the call from X10UI to that?

I was trying to learn the UI stuff, so I could add the IR, and Variable manipulation stuff later on... :)

hoox
April 1st, 2006, 10:40 AM
Correct me if I'm wrong Mike, but is this function (from my current script) what you need?:
Ocelot:SendX10(hc, uc, fc, rc)

If so it may work as it is with X10 UI when you'll have implemented it.
But I don't understand where the device selection will be... Add will we need a new X10.lua or a totaly new Girder version ?

Todd, the quotes are needed for hc, uc, fc not for rc. The spaces doesn't matter.
I think it's how X10 Device manager works...

Todd Reed
April 1st, 2006, 01:18 PM
I think the X10UI sends decimal, that is why I asked for the conversion or two calls.

I added a print statement to see it, and "M3 On" shows as 12 2 1

hoox
April 2nd, 2006, 09:45 AM
Can you give more details?
Adding ie to treescript.Action[52] near line 881:

print&#40;hc,uc,fc,rc&#41;

Shows: M 3 ON 1

Promixis
April 2nd, 2006, 03:12 PM
Ok, attached is an updated x10 file. drop it in the luascripts dir. You will need to delete this file with the next g4 release.

This file will call a function you have to create




Oclelot.Send &#40;hc,uc,fc,rc&#41;



you will have to interpret the parameters to whatever the ocelot needs.

hc = 'A' to 'P'
uc = 1 to 16
fc = one of the strings above
rc - you may ignore this.


your function must be able to handle nil arguments for uc and fc

ie. it might get

hc/uc

or

hc/fc

a traditional x10 command pair. this is the way most x10 devices accept commands anyways.

hoox
April 2nd, 2006, 05:26 PM
Mike, can you please change line 1044 from


Oclelot.Send &#40;hc,uc,fc,rc&#41;

to

Ocelot&#58;SendX10 &#40;hc,uc,fc,rc&#41;

as it works like a charm.

Thanks!

Promixis
April 2nd, 2006, 08:16 PM
Mike, can you please change line 1044 from


Oclelot.Send &#40;hc,uc,fc,rc&#41;

to

Ocelot&#58;SendX10 &#40;hc,uc,fc,rc&#41;

as it works like a charm.

Thanks!

sure, do you have receive working?

Todd Reed
April 2nd, 2006, 09:27 PM
It works for me when I select LUA:X10 as the event and then use the X10 device manager to select a device! :D

And hoox, the IR send works in your GML example format!

Next, getvar and setvar... :o

Promixis
April 2nd, 2006, 09:28 PM
It works for me when I select LUA:X10 as the event and then use the X10 device manager to select a device! :D

And hoox, the IR send works in your GML example format!

Next, getvar and setvar... :ook, just to clarify, you guys got send and receive working right?

hoox
April 3rd, 2006, 12:46 AM
Yes Mike, the X10 part is fine.

Todd, I've most of the other functions working (just missing some for the modules)
I'll send you that when it's finished.

Todd Reed
April 3rd, 2006, 11:34 AM
hoox, you're making great progress!
I assume you have not messed with the UI yet?

And mike, is there any more documentation on the Treescript plugin... :cry:

I tried using the X10UI.LUA as an example, but so far the only thing I have confirmed is how weak my LUA skills are!!

I will keep trying...

Todd Reed
April 3rd, 2006, 02:25 PM
As a training tool... :lol:

I want to create a DUI page for the Ocelot send IR action.

I want a single spin box to select the IR command "0" to "1023"
I will need to split it into a Low bit and High bit.
IE: IR#-115 would be IRL=15 and IRH=01
IE: IR#-4 would be IRL=04 and IRH=00

I want a simple edit box to enter the amount of times to send the IR
(could be a spin box with 1 to 6 times preset...) Default to 1

Then send to Ocelot using:
"Ocelot:SendIR('irl','irh', rc)"

IE: Ocelot:SendIR('03','00', 2) would send IR#0003 - (2) times

Promixis
April 4th, 2006, 04:05 AM
Todd,

The x10 ui is fairly complex.

Something like the GC IR send might be a better eg.

Todd Reed
April 4th, 2006, 10:22 PM
Okay, I took a look, and then created this. But it does not even show up in the tree... :cry:


--&#91;&#91;

Ocelot Actions

--&#93;&#93;

--&#91;&#91;

Send IR
bValue1 = IR#

--&#93;&#93;

treescript.Action&#91;242&#93;=&#123;&#125;
treescript.Action&#91;242&#93;.OnAction=function &#40; Action, Event &#41;
irl = Ocelot.ir &#40;Action.bValue1&#41;
Ocelot&#58;SendIR &#40;irl, '0', 1&#41;
return true, 'Ocelot IR Sent'
end

&#125;

return "Ocelot.xml"

Rob H
April 5th, 2006, 04:47 AM
Where did you put that file? It should go in the plugins\treescript directory.

And do you have a corresponding action page in Ocelot.xml?

Todd Reed
April 5th, 2006, 09:09 AM
Yes, Ocelot UI.lua is in treescript dir.
Yes, there is an Ocelot.xml in UI directory
Yes there is Ocelot.lua in Serial directory
The DUI has several forms, and this one (Action #242) has a single spinbox for the "bValue1" input.

Could it be that there is extra DUI pages, with no reference in the xml?

Promixis
April 5th, 2006, 09:17 AM
Yes, Ocelot UI.lua is in treescript dir.
Yes, there is an Ocelot.xml in UI directory
Yes there is Ocelot.lua in Serial directory
The DUI has several forms, and this one (Action #242) has a single spinbox for the "bValue1" input.

Could it be that there is extra DUI pages, with no reference in the xml?

attach your lua and xml files here

Todd Reed
April 5th, 2006, 09:04 PM
See attached. Maybe this could become a Treescript tutorial... "For Dummies" :lol:

Todd Reed
April 5th, 2006, 09:07 PM
And the XML
(It would only allow two files...)

Todd Reed
April 5th, 2006, 10:46 PM
Sorry :oops:

Second to last command "}" does not need to be there...!

So, basic SendIR DUI works. :D

Promixis
April 6th, 2006, 06:57 AM
great, did we assign action numbers yet?

Todd Reed
April 6th, 2006, 08:51 AM
No, but we need a bank of 10 probably...

Mike, I get these errors using X10-Work.lua you sent. And I noticed in one spot in the devices you don't list the Ocelot...



--using "Device Send"--
TreeScript &#40;gir_event&#41;&#58; ...ROGRAM FILES\PROMIXIS\GIRDER\\luascript\x10-work.lua&#58;1044&#58; attempt to index global `Oclelot' &#40;a nil value&#41;
stack traceback&#58;
...ROGRAM FILES\PROMIXIS\GIRDER\\luascript\x10-work.lua&#58;1044&#58; in function `SendDirect'
...ROGRAM FILES\PROMIXIS\GIRDER\\luascript\x10-work.lua&#58;1353&#58; in function `Command'
...FILES\PROMIXIS\GIRDER\/plugins/treescript/x10 UI.lua&#58;736&#58; in function <...FILES\PROMIXIS\GIRDER\/plugins/treescript/x10 UI.lua&#58;705>

--Using HC/UC Send--
TreeScript &#40;gir_event&#41;&#58; ...ROGRAM FILES\PROMIXIS\GIRDER\\luascript\x10-work.lua&#58;1044&#58; attempt to index global `Oclelot' &#40;a nil value&#41;
stack traceback&#58;
...ROGRAM FILES\PROMIXIS\GIRDER\\luascript\x10-work.lua&#58;1044&#58; in function `SendDirect'
...ROGRAM FILES\PROMIXIS\GIRDER\\luascript\x10-work.lua&#58;1017&#58; in function `Send'
...FILES\PROMIXIS\GIRDER\/plugins/treescript/x10 UI.lua&#58;898&#58; in function <...FILES\PROMIXIS\GIRDER\/plugins/treescript/x10 UI.lua&#58;883>


looks like a typo Oclelot vs Ocelot. Just change line 1044.

Todd Reed
April 6th, 2006, 11:00 AM
Yep, after I read hoox's note again... It works!

Lastly, can we add a logger message "X10 hc uc fc sent" instead of "Treescript ok"?

Better yet, "DEVICE X10 hc uc fc Sent" so we know where it is coming from...

hoox, how you doing on the Ocelot.lua? I don't have a SECU-IR to test, but I do have a std SECU-16 module.

I will keep working on the UI, but maybe we need to assign the action numbers...

Todd

Todd Reed
April 11th, 2006, 02:54 PM
Mike,

Do you want to add the Send X10 Preset levels to the X10 UI, or do you want me to take a stab at it?

I don't have a unit to test it with so... :cry:

hoox
April 11th, 2006, 07:49 PM
In fact, Mike, if you could add this line at the top of the LevelDirect function in x10-work.lua (line 1107):


if Ocelot then Ocelot&#58;PresetDim&#40;hc,uc,level&#41; return end;

This would prevent Todd to make a crime!

Todd Reed
April 12th, 2006, 04:11 PM
Okay, both SendIR functions work with repeats. :D
Now on to the Set variables and timers!

Before I go much farther... would it help the G3.3 to G4 upgrade path to use the same function names as Neil's previous plugin?? I may need some help here... :wink:

I am starting to figure it out, but is there a specific relevance for the iValuex, bValuex, sValuex, lValuex??

I read that L = number only and S=string only. What about "i" and "b" Values?

Also, for debug purposes, where is the best place to add dynamic responses, such as.. return true = "error message" Which LUA file, and which command...?

There are 4 message areas I know of; two in the lower frame of Girder, the gir.LogMessage commands and the print (text) to show in the LUA console. I want to best utilize these... :wink:

Todd Reed
April 12th, 2006, 07:38 PM
Test this version... with these working (I think)!

SendIR, SendRemoteIR, SetVar, SetTimer, SetRelay

I still get "Relay=nil" on the lua console, but it works...?

Promixis
April 13th, 2006, 10:23 AM
In fact, Mike, if you could add this line at the top of the LevelDirect function in x10-work.lua (line 1107):


if Ocelot then Ocelot&#58;PresetDim&#40;hc,uc,level&#41; return end;

This would prevent Todd to make a crime!

Terry, not sure why this is needed here? Whats not working?

hoox
April 13th, 2006, 09:22 PM
Mike, when using the standard Level in 'Device Command' Action, the Ocelot's SendX10(hc,uc,fc,rc) function receives (for 51.6%):


A 2 nil 1
and

K nil PRESET DIM HIGH 1

If it seems good for you, no need to change anything...
My devices probably don't use this system, so I'll use the Ocelot:PresetDim directly from Lua.

Todd, your UI is working here, thanks!
The iValue, bValue, sValue had a specific type (maybe integer, boolean and string) in old Girder versions. In Girder4 they can be of any type (except lValue).

Promixis
April 14th, 2006, 06:42 AM
Mike, when using the standard Level in 'Device Command' Action, the Ocelot's SendX10(hc,uc,fc,rc) function receives (for 51.6%):


A 2 nil 1
and

K nil PRESET DIM HIGH 1

If it seems good for you, no need to change anything...
My devices probably don't use this system, so I'll use the Ocelot:PresetDim directly from Lua.

Todd, your UI is working here, thanks!
The iValue, bValue, sValue had a specific type (maybe integer, boolean and string) in old Girder versions. In Girder4 they can be of any type (except lValue).

the send looks good. you have to have a device that does preset dim..

Todd Reed
April 14th, 2006, 05:40 PM
I wanted to create a simple Config DUI page that would call the "SetCPUXAParam(15,1) --Auto X10" functions. So the user could go to this page and check the three check boxes, then hit apply. This would then call the three functions as listed below, to send those parameters to the Ocelot.

I made the page and used this code, and it shows up, but I will have to test it more tonight at home with the Ocelot... I check the boxes, then hit Apply, but when I go back, they are unchecked...



treescript.Config&#91;140&#93;=&#123;&#125;
treescript.Config&#91;140&#93;.OnEvent=function &#40; Index, Action, Controls, Control, ID1, ID2 &#41;
if &#40; ID1 == 1 &#41; then -- devn
Controls.autoX10.Checked=1
Ocelot&#58;SetCPUXAParam&#40;15,1&#41; --Auto X10
print &#40;'Parameter 15 set to 1'&#41;
end

if &#40; ID1 == 2 &#41; then -- devn
Controls.autoIO.Checked=1
Ocelot&#58;SetCPUXAParam&#40;16,1&#41; --Auto I/O
print &#40;'Parameter 16 set to 1'&#41;
end

if &#40; ID1 == 3 &#41; then -- devn
Controls.autoIR.Checked=1
Ocelot&#58;SetCPUXAParam&#40;17,1&#41; --Auto IR
print &#40;'Parameter 17 set to 1'&#41;
end
end


Would this work? And how can I add an Icon to the "Automation Config" list?

Promixis
April 14th, 2006, 06:28 PM
you need to store the values in the on apply and then restore them in the onshow method.

right click the folder in the designer tree to assign the icon

Todd Reed
April 15th, 2006, 12:32 AM
Mike, any hints? If it is alot to do, maybe later...

It does work, but it resets the form when you open it. Which is okay, since you only do this once to config the Ocelot (unless you manually reset to zero). So if I put text on the form to explain, it might be fine.

I tested hoox's update tonight, and the DUI and all seems okay! :D :D

I can't test the Speak module, or SECU16IR but we are very close!!

The only issue is that when I open Cmax when Girder is running, I get a major lockup!! It opens Cmax and about 30 small error boxes, so I ctrl-alt-del to close Cmax... :cry:

I will start documenting the plugin, any preferred method? I can use MS Word and make a PDF, then send it all to John Hind?

Todd Reed
April 15th, 2006, 05:23 PM
hoox,

I rem'd out the SetCPUparam statements and added a wait command and now when I start Cmax, I can see the commands in the console and it works!

I tried a PM but it stays in my outbox, (and I don't know how to send it from there...)

So here are the files...

Todd Reed
April 17th, 2006, 10:01 PM
Mike (or others)

We are trying this to enable the action list based on the presence of the Ocelot, but they never show up.



if not Ocelot then return false, 'Ocelot not present' end


We think it is because the UI loads before Serial plugin...?

Help...

Todd Reed
May 1st, 2006, 10:57 AM
Okay, testing is going good, almost done!

What are we doing with X10 Preset Dim?

Do I need a DUI page??

Promixis
May 1st, 2006, 10:59 AM
Okay, testing is going good, almost done!

What are we doing with X10 Preset Dim?

Do I need a DUI page??

No, this is on the x10 action page.

What kind of switches do you have that do preset dim?

Todd Reed
May 1st, 2006, 11:03 AM
Mike,

I do not have any of these units! :oops:

Yet!!!!!!!!

So, I can not test...

But I do not see a preset dim command?

hoox
May 1st, 2006, 03:16 PM
Mike, can you please tell us what is the function called by x10.lua for Ocelot, so that we can update the serial script?
Thanks!

Todd Reed
May 3rd, 2006, 06:59 PM
Mike,

Help us out here, we're almost done...

I have a 20 page manual for the plugin, send me an email and I will forward a copy... to you or John Hind.

TR

Promixis
May 3rd, 2006, 07:38 PM
Mike,

Help us out here, we're almost done...

I have a 20 page manual for the plugin, send me an email and I will forward a copy... to you or John Hind.

TR

Hi Todd, I am sorry

What do you need exactly?

Todd Reed
May 3rd, 2006, 08:30 PM
See above.

hoox had some issues with most recent 4.0.4.10 update, if X10-work.lua is deleted... SendX10 does not work.

And, I need the Preset dim function resolved. I don't see it on the X10 page...

I also noticed that the Ocelot is not listed in the "GetProvider" function in X10-work.lua ...

Thanks!

hoox
May 3rd, 2006, 09:47 PM
Just to mention that Ocelot:PresetDim is a Leviton Dim type. Maybe should we rename it...

Promixis
May 4th, 2006, 05:42 AM
Just to mention that Ocelot:PresetDim is a Leviton Dim type. Maybe should we rename it...

Yes, call it LevitonDim.

Parameters should be housecode,unitcode,level

with level in %

I am missing this functionality for the other X10 interfaces....

Do you guys know the X10 sequences that need to be sent?

Fixed: UI re not listing the Ocelot.

Todd Reed
May 4th, 2006, 10:20 AM
This is what we're using...



PresetDim = function (self, hc, uc, level) --level=dim level %

uc = string.upper(tostring(uc))
level = tonumber(level)
if (level > 100) then level = 100 end;
local SLevel = level --level in %
level = math.ceil(level*0.63) --(64 light levels)

if hc and uc then
PresetDim = convert (200,97,string.byte (HC[hc]),string.byte (UC[uc]),level,49,0)
self:SendCommand (PresetDim .. CalculateCheckSum (PresetDim))
X10:ReceiveEvent (hc,uc,nil) -- X10 Device Manager
local d = X10:FindDevice (X10.events.last.hc, X10.events.last.uc)
if SLevel < 50 then d:UpdateX10 (11, SLevel) else d:UpdateX10 (10, SLevel) end;
X10:GirderEvent (X10.events.last.hc, X10.events.last.uc, 'LEVEL', SLevel)
end

end,


Leviton units can be one of 64 levels, and PCS type can be one of 32 levels.
We send Leviton type as a percentage to the Ocelot.

Promixis
May 4th, 2006, 11:10 AM
ok, thanks.

i will need to find out how to send leviton dim commands using the other x10 providers...

hoox
May 4th, 2006, 07:55 PM
Yes, call it LevitonDim.

OK, I changed it to:


LevitonDim = function (self, hc, uc, level)



Fixed: UI re not listing the Ocelot.

Thanks for this Mike, but the main problem about standard X10 commands is still unsolved:
About a month ago, you sent us an "x10-work.lua" file with these instructions:


Ok, attached is an updated x10 file. drop it in the luascripts dir. You will need to delete this file with the next g4 release.
This file will call a function you have to create

Code:

Oclelot.Send (hc,uc,fc,rc)

The working function we use in "x10-work.lua" is in fact:


Ocelot:SendX10 (hc,uc,fc,rc)

Until now, we kept this script in the luascript directory, and all was well for X10.

According to your instructions, I removed "x10-work.lua" an made a fresh install of Girder 4.0.4.11, so now it's the precompiled script "x10.lua" that handles X10, right?

What happens now when using an X10 Action, is that a "Send" function is called in ocelot.lua.
It's no big deal, I added this function in ocelot.lua to see the received parameters:


Send = function (self, hc, uc, fc, rc)
print(hc, uc, fc, rc)
end,

When sending A3 OFF with a "Device Command" Action, I see in Lua Console:

3 OFF 1 nil
As you can see, the House Code is not included. THAT is the main problem!

So, we would actually need that:
- You check the code in x10.lua to see if "hc" is there for the Ocelot:Send function.
- If you don't mind, change the name from "Ocelot:Send" to "Ocelot:SendX10" as the Ocelot have other "Send..." options.

Thank you!

Promixis
May 4th, 2006, 09:22 PM
ok, above stuff should be fixed.

added leviton send if device suports this dim type.

anyone know what to send for leviton dims when using the PowerLinc devices?

hoox
May 4th, 2006, 11:13 PM
Mike,

This file as all what we needed.
I just had to temporaly modify the x10 UI.lua to have the 'Level' command appear in Device Command Action.


if d.Abilities.Dim == 3 or d.Abilities.Dim == 4 then
Controls.cmd.Strings = Controls.cmd.Strings .. 'Level\n'
end

I presume that you already made it in a way or another.
Everything works now, thanks again for the fast fix.

For the PowerLinc, did you try what's said in the last page of http://www.smarthome.com/manuals/1132-A.pdf ?

Todd Reed
May 4th, 2006, 11:57 PM
mike,
I got the X10 work.lua loaded, are we going to keep using this?

hoox,
can you send me updates when Preset dim is complete?

Then I will update the manual.

Thanks guys...

Promixis
May 5th, 2006, 06:17 AM
we will move this file into the standard x10 stuff once you give me the ok.

Todd Reed
May 7th, 2006, 06:39 PM
Working good here, so I would say go for it!

Make sure you get hoox's X10 UI stuff...

Promixis
May 9th, 2006, 12:18 AM
Good!

Terry, what is the UI stuff?

Todd Reed
May 9th, 2006, 08:06 AM
Mike,

See Terry's post above...



if d.Abilities.Dim == 3 or d.Abilities.Dim == 4 then
Controls.cmd.Strings = Controls.cmd.Strings .. 'Level\n'
end


Or something like it.

hoox
May 9th, 2006, 06:27 PM
Yes Mike,
I just wanted to make sure that you updated the X10 Actions (mainly Action 50) to support Leviton Dim: In the current UI, selecting Leviton Dim for a device, in X10 Device Manager settings, shows only On, Off, Dim and Bright Commands in 'Device Command' Action.
(The OnShow method in Action 50 would also need to be changed, as Leviton Dim as 64 light levels, not 32...)

Promixis
May 10th, 2006, 09:43 AM
ok guys, please try...

hoox
May 10th, 2006, 07:02 PM
Great, it works!

Promixis
May 10th, 2006, 07:57 PM
Great, it works!

Phew ;)

I still can't figure out what bits to put on the powerline for the leviton dim using the powerlinc.

hoox
May 10th, 2006, 09:51 PM
Mike,
AFAIK you should send in the same data frame:
[hc] [EXTENDED CODE] [uc] [DimLevel] [0x31]

Todd Reed
May 10th, 2006, 11:59 PM
Mike,

I tried loading all three files in the last X10-work.Zip, now X10 actions are gone, and X10 device manager DUI is wacked!

So, I reloaded G4.0.4.11 and the old X10_work.lua to get X10 back...

Hummmm...


Todd

hoox
May 11th, 2006, 01:37 AM
Todd, I have to admit that I tested after changing line 73 in x10-work.lua to a comment :

--require ('DeviceManager.X10.Provider')
else, 'DeviceManager.X10.Provider' is not found, stopping X10 load here...

Mike, I'm sorry if this gave me false 'good' results, but is it really required to test the UI?

Promixis
May 11th, 2006, 08:23 AM
No.

Actually set the local 'work' to false at the top of the x10-work file. This will remove this dependancy.

Todd Reed
May 11th, 2006, 11:42 PM
That did it!

I have updated the plugin manual if anyone wants to review it (besides hoox!)

So, the Ocelot Plugin Beta can be released for testing with the next G4 version (with X10 updated)!!

Todd

Promixis
May 12th, 2006, 09:25 AM
ok, can you post the manual?

Todd Reed
May 12th, 2006, 10:08 PM
nope, it's 22 pages and 1.7mb!! Lot's of pics...

What pic format would make it smaller??

Todd Reed
May 30th, 2006, 11:39 PM
Mike,

Is the X10 updated in G4.0.5 and ready for our plugin?

I noticed rpal uploaded his version as well. Did he get a different plugin ID?

Let me know what you want to do.

Todd

rpal
May 31st, 2006, 12:36 AM
Todd let me know if could I help you.

hoox
May 31st, 2006, 04:34 AM
Mike,
the x10 update in Girder 4.0.5 works, thanks.
But it seems that the updated "x10 UI.lua" was not included (making LevitonDim not showing)
Is this normal?

rpal
May 31st, 2006, 06:53 AM
where's the 4.0.5?

Promixis
May 31st, 2006, 08:08 AM
Mike,
the x10 update in Girder 4.0.5 works, thanks.
But it seems that the updated "x10 UI.lua" was not included (making LevitonDim not showing)
Is this normal?

will check with Ron. Does it work using the x10 ui.lua file above?

hoox
May 31st, 2006, 06:00 PM
Yes Mike, it's ok with your above file.

rpal, 4.0.5 is easy to find: First forum (Announcements), first post, first page.

Todd Reed
May 31st, 2006, 11:22 PM
Let me try this one, less then 1mb!

If it loads, then we should post when you are ready Hoox and Mike :-)

When I get a chance I will post a link to my web page with the full manual!

hoox
June 18th, 2006, 02:06 PM
Todd,

the plugin goes fine with Girder 4.0.5.1. Is it also ok for you?

Todd Reed
June 19th, 2006, 02:28 PM
Sorry, I have been swamped with stuff...
But, I will have some time this week to test!

I say, go ahead and post!


Todd

Todd Reed
June 19th, 2006, 10:39 PM
Okay! Updated to 4.0.5.1 and the new updates.

Looks good, let's load it!!

Can you do this?

Thanks,

Todd