Hello everyone!

Just got my Pronto NG 7000. Having tried to create my first remote layout, I ran into a problem. When setting up the X10 light and appliance control for my house I could not successfully create the propper IR codes even with the code generator program advertised throughout these forums. I am using an Ocelot interfaced with a PC to control my X10 devices. Ocelot can recieve and send IR and RF signals and the signal LED on the ocelot uint indicates that it is recieving IR commands fomr my Pronto. However, probably due to invalid IR codes, I can not eyt operate my lighting and appliances.

I am wondering if any of you have solved this problem and succeeded in using your Pronto Pro NG 7000 to control X10 devices around your home. If so - how did you manage to do it? What software and/or hardware am I missing?

I tried searching the forums here for an answer but did not find anything that addresses my problem completely. Any and all adivce and help is greatly appreciated!

Thanksin advance,

I have an Ocelot and when I tested it with the Pronto 3000/7000 it worked fine. You can assign "any" ir code's to run your X10 lighting. You just assign in the ocelot menu what you want that IR code to do for your X10 device (dim, bright, off, on, delay for set time and run command, etc).

I don't have the Ocelot up and running right now, but it did what it is suppose to with the Pronto's.

The Ocelot does not respond automatically to any IR code and ABSOLUTELY NOTHING in the documentation for CodeGen™ should lead anyone to believe otherwise. The Ocelot is not mentioned anywhere in the CodeGen™ documentation nor can it be selected within the program itself. And, CodeGen™ is free so your claim that it is "advertised throughout these forums" is rather misleading.

You must learn IR codes with the Ocelot and then you must program it to respond to those IR codes. I guess someone who couldn't bother to read the CodeGen™ documentation is also unlikely to read the Ocelot documentation.

You can use any codes you wish (as long as they do not conflict with others) to control your lights. The more codes you ask the Ocelot to recognize, the slower is its response as it must look through that number of codes for a match. Sony codes tend to be shorter and work well as triggers for this type of activity.

Dave Houston
CodeGenPro™

|

*sigh* And there I thought that this forum would actually be flame (even if subtle) free... I did not mean to mislead or upset anyone. English is my third language and, sometimes, I run into alittle difficulty of clearly conveying my thoughts in writing.

Thanks for your advice.

And I thought people using a free application would not complain that it cannot remove warts nor cure cancer.

I spent a lot of time writing and updating the application and I spend a lot of time providing free support for it. I don't think it's too much to ask that users read the documentation before posting disparaging comments about it.

Not that I wish to drag the argument out even further, but I just want to make a simple point. I was not trying to complain about your program that is obviously well-made and ver useful. I was simply describing my setup and what I wqas using in order to make sure that those who would like to ofer advise would know exactly what I use. I was not attacking your product - I was simply mentioning that I was using it and to which results.

I do not know how anybody could possibly interpret your post as anything other than a complaint that CodeGen™ was giving you "invalid IR codes". All of the codes generated by CodeGen™ have been thoroughly tested using a TS1000 and the target hardware. All are valid. There hasn't been a verified bug report in about a year.

FACT: CodeGen™ does not purport to generate codes that trigger the Ocelot to send X-10 commands. Had you read the CodeGen™ documentation, you would know this.

FACT: The Ocelot can neither send nor receive RF. Had you read the Ocelot documentation, you would know this.

FACT: The Ocelot does not interpret any IR inputs but merely responds to them in the way it is programmed (by the user) to respond. If it has not been programmed to respond to a specific "learned" IR code, it will do nothing beyond blinking an LED. Had you read the Ocelot documentation, you would know this.

Instead of reading any of the documentation, you post a message implying that CodeGen™ was at fault and then accuse me of flaming you.

A search of the Files area revealed that there is a PCF with Ocelot IR codes here:

[Link: remotecentral.com]

and a CCF with Ocelot IR Codes here

[Link: remotecentral.com]

Peter,

I am probably one of the five most knowledgeable people on the planet when it comes to the Ocelot (and three of the five work for Applied Digital). I helped them (before the Ocelot was introduced) to refine their RS232 interface and improve their X-10 features. Believe me, while the Ocelot can learn almost any IR code with a carrier of 38kHz ±5kHz, unless there have been very recent changes, there are NONE preloaded into it and there are NONE that it can recognize and react to without a user written Ocelot ladder logic program.

Any CCF or PCF file that has "Ocelot" codes will require the user to extract the codes from the CCF or PCF, convert them to ADI's LIR format and paste them into an LIR file (Applied Digital's IR file) using a utility application from ADI. Then the Ocelot must still be programmed to respond when it recognizes the codes (if it recognizes them).

The Ocelot can learn and store 1024 IR codes. It can play them back or can trigger other actions when it receives a code that it has in its memory. It does the latter by searching through its learned IR memory area for a code that matches the received code.

The Ocelot only does X-10 PLC via a PL513, PSC04, PSC05, TW523, TW7223, XM10E or XM10U (all X-10 manufactured TTL level interfaces that require dedicated higher level processor time to send/receive X-10 PLC commands). It does not receive or send any RF. The Ocelot uses a single PIC to handle both IR and X-10 so it can only do one at a time, missing any inputs while busy sending either IR or X-10 PLC.

While the Ocelot design is about five years old, it remains one of the most powerful and flexible Home Automation controllers on the market, offering far more expansion capabilities and far more "bang for the buck" than anything else.

The files you referenced will only further confuse a noobie.

Dave Houston
CodeGenPro™

Dave,

I am in Oregon and all my stuff is from and in the US

Wow I am pretty confused. You definately know more about this stuff than anyone. I have a very simple set up and need some help. In my theatre (downstairs) I have a TSU2000 and an IR543 controling some lutron swithes. Everything works well but the remote has to point at the IR543 to work it (line of sight IR issue).

NOW, I just remodeled the kitchen and bought a TSU3000 and the RF extender. I want to control a stack of electronics in the living room since I can now hear them in the open floor plan and I want to conrol all the lights with X10 in the kitchen and the living room. I like the idea of RF so I don't have to point at the box to do it but I quess the RF extender will take care of that issue..

Am I missing anything?

Thanks for you help in advance...
Todd

I'm confused. The IR543 will send X-10 PLC commands over the powerlines to X-10 switches and modules but it will not control the Lutron switches so I assume you control them with IR.


You have probably reached the limit of what you can control with the IR543. You can use the IR output from the extender to control the IR543, an IR543AH (all 16 housecodes), or an Ocelot. You will need to teach the Ocelot IR codes and program it to respond to them.

If you are handy, you can convert the IR543 to an IR543AH.

I've written a brief application note comparing the IR543, IR543AH & Ocelot. It has links to other resources.