Help_ HAI Omni Pro II Initial Set-up

[t_garp]

HI guys,

I've tried everything and I can't seem to get my keypad to respond to any inputs.

Everytime I try to press a key on it, it says enter code and I enter the default code "1111" I even tried the Master code I entered into the software. It barely accepts my inputs, I try to enter a command, and then it just starts beeping like crazy and will not accept my inputs.

I am able to connect to the board via the PC Access software. But the keypad is just not working...

 

[pete_c]

Make sure your the wires which connect are OK. Think two are for power and two are used for communications.

CONSOLE SETUP
The console has different operating options that can be setup from the console to the user's preference. If more than one console
is being used, it is required that you give each console a different address. You can change the address of a console through the
console setup mode.
To enter the console setup mode, simultaneously press and hold the 4 and up arrow (^) for approximately 1 second. The console
will beep 5 times and enter the setup mode. The top line of the display will indicate what you are doing, followed by the current
setting. The bottom line will show a menu of your options. To the lower right corner of the display is the direction arrow(s).
Where possible, the up (↑), down (↓), and two-headed (􀂦) arrow characters are shown on the console display to indicate which
arrow keys may be pressed at that time. Press the down arrow (V) key to advance to the next item. Press the up arrow (^) key to
go back to the previous item.

CONSOLE ADDRESS
If you are installing more than one console, each console must be set to a different address. The default address setting is (1) -
this is adequate if only one console is being used. The choices at the bottom are 1-16. When making your choice, choose an
address between 1-16, then press the # (pound) key.
SOUNDER
If you wish not to hear the beeper in the console for any reason, the sounder option can be turned off. Select (0) for OFF or (1)
for ON, then press the # key.
KEY CLICK
The sounder makes a click every time a key is pressed. This option may also be turned off. Select (0) for OFF or (1) for ON,
then press the # key.
KEY BACKLIGHT
The keys on the console keypad are lit. The keys can be never lit, always lit, or only lit when the LCD display is lit. Select (0)
OFF, (1) for ON, or (2) TIMED, then press the # key.

EXIT SETUP MODE
To exit Setup Mode, press and hold the 4 and up arrow (^) keys simultaneously for about 1 second. The console will return to
normal operation. You may need to press (*) to restore the display.

 

[ASIHome]

As far as asking for the code no matter what button you press. It will do this if "High Security" mode is turned on.

 

[t_garp]

Thanks for the suggestions above, however, no dice.

I can access the setup menu from the keypad no problem and set the keypad adress to 1.

If I try to arm the system or do any other action, it just keeps beeping like crazy and does not accept my code inputs...This is very frustrating...

 

[ano]

The keypad and the panel constantly communicate back and forth with each other when its working. And either its communicating or it isn't. If it ISN'T communicating then the keyboard should display a communication error. Are you saying you DON'T get a communication error on the keyboard but its still not working? Double and triple check your wiring. If its still not working, call HAI and ask for technical support.

 

[HAI_fjh]

I am sorry you are having problems but a little more specific info would be helpful in resolving this problem...

When you say "beeping like crazy" is there any pattern to the beeps, like when you press a button you get 2 short beeps, or three short beeps, or a constant regular beeping?

Is there any error message displayed on the console?

I am also unsure what "barely accepts my inputs" means? Do you have to enter them quickly or something? Also what commands are you trying to enter?

I am not trying to be difficult but specific beep patterns and messages would help us quickly resolve this problem...

Let's start with the basics:

Since I did not see any mention of a "no controller data" message and you said it was asking for a code, then as ano mentioned it sounds like the console is communicating with the controller so I don't suspect a communications problem at this point.

The next thing to look at tis the configuration. If you have the high security mode enabled then you will be prompted for a code for everything... Are you using areas? Are you trying to command a unit that is in a different are from the console? Are you trying to control or view the status of something that is unnamed?

What model and firmware version is your controller?

I am sure is is something simple that got overlooked and can be easily resolved.

 

[mc85]

Did you make sure each keypad is using a different address.

 

[t_garp]

I am sorry you are having problems but a little more specific info would be helpful in resolving this problem...

When you say "beeping like crazy" is there any pattern to the beeps, like when you press a button you get 2 short beeps, or three short beeps, or a constant regular beeping?

Is there any error message displayed on the console?

I am also unsure what "barely accepts my inputs" means? Do you have to enter them quickly or something? Also what commands are you trying to enter?

I am not trying to be difficult but specific beep patterns and messages would help us quickly resolve this problem...

Let's start with the basics:

Since I did not see any mention of a "no controller data" message and you said it was asking for a code, then as ano mentioned it sounds like the console is communicating with the controller so I don't suspect a communications problem at this point.

The next thing to look at tis the configuration. If you have the high security mode enabled then you will be prompted for a code for everything... Are you using areas? Are you trying to command a unit that is in a different are from the console? Are you trying to control or view the status of something that is unnamed?

What model and firmware version is your controller?

I am sure is is something simple that got overlooked and can be easily resolved.

I have seen the No Controller Data00 Message, but only after I try to change a configuration, such as changing the keypad's address.

I only have 1 keypad installed. (I am going to test all the wires again today).

The keypad beeps thre times per second constanly!

As for barely accepting inputs, in between beeps, I can sometimes get a key input to respond

 

[t_garp]

OK,

I checked the wires and all appear to work...The kay pad displays the time and date and say System OK.

If i try to press any action key or to arm the system, It says Enter Disarm Code while beeping 3 times per second. It is at this point that the key pad becomes unresponsive and does not really accept inputs.

To stop the beeping, I press cancel many times and then is return to the System OK screen.

A slight diffirence now that I played with the yellow wire that when I set the console address by pressing 4 & ^, it says No Controller Data01 (instead on Data00) upon exiting.

any help is appreciated.

 

[t_garp]

Ok,

NOW I got it to work! Hallelujah!!!

The problem was that I had the B&B RS-232 adaptor coneected to the keypad input (This is the converter required for an ELAN home systems touchscreen to interfacr with HAI) however, I did not yet hook it to the ELAn and it was just randomly on...

Hopefully next weekend I will get to programming the ELAN interface...hoowever, the fact that the interface adaptor is causing a conflict is worrying me...so that when I do finally connect it, it may go haywire again...

Anyone else run into this between HAI & ELAN?

 

[HAI_fjh]

The ELAN is an important detail...

We have detailed instructions about how to set this up in our Application Directory document. You might want to get the latest version from our Knowledge Base.

The ELAN can connect to our console bus, but the console bus is RS-485, not RS-232. The recommended adapter is the B&B Electronics model 485SD9TB which is a DB9 to RS-485 adapter.

Anyhow get the document from our knowledge base and you should be able to get it working.

 

[je1058]

I seem to be having the same problem... Tried to post it in a new topic here and refrence this post, but it appears after I drafted the long post, it wouldn't allow me to, since I'm new, so I'm posting here instead... hope that's ok...

I have a new house which I wired while it was being built. Have 3 keypads on the OPII and all 3 were doing the 3 fast beeps each second thing while advising no controller data (with a 0 or 1 at the end). I was able to use arrow up+4 to program and number each keypad. I removed each keypad from their locations in the walls and went straight to the OPII circuit board and hooked them up. The first worked fine and I was able to program the OPII's time, date, etc. The other 2 didn't work, still advised the controller problem.

So I went to the basement keypad wall location, as it's a straight shot, about 45' of Cat5 and I can see the circuit board from it and know there's no shorts... Still had the same problem.

So I thought perhaps something was up with the Cat5 and I used the tracer wires to match their solid colored wires, to double-up on both ends and still had the same problem. I also tested each wire run for shorts and there are none.

I've pretty much disconnected EVERYTHING from the OPII board, except power and keypads that I'm testing.

Have any clues? Anything else I need to check?

 

[HAI_fjh]

IMPORTANT: Make all connections with the panel powered down, and don't forget to disconnect the battery too. In fact just leave the battery disconnected while testing.

First I would confirm proper operation of each keypad:

Disconnect everything from the console buss.

Connect the first console directly to the console buss using a short cable. Configure the console address and verify that it functions normally by navigating a few menus. If the keypad is displaying the controller status and is responding appropriately to button presses then it should be OK.

Repeat the process for each console, connecting only 1 at a time.

If one does not work, contact technical support and see about getting it replaced. You must have working keypads.

You mentioned the second 2 failed. Having 2 out of 3 keypads fail is EXTREMELY unusual. The keypad has a very reliable track record.

Next verify the cabling:

Connect the first cable run to the console buss and the other end to a known good console. Verify proper operation.

You mentioned using CAT-5 cable. The keypads draw very little current so there is no need to double up the wires. Since you only need 4 wires you can just use the colored wire of each CAT-5 pair. If you really want to double up the wire you can treat each pair as a single wire.

After you have verified proper operation of the first run, disconnect it and follow the same procedure for the second run and finally the third run.

Once each run has been verified independently you should be able to hook them all up and it should work.

By testing each component independently you should be able to isolate the trouble and fix it. 99.9% of the time it is a wiring problem, so triple check all of your connections.

So in general hookup and verify one thing at a time. Resolve any problems before moving on.

 

[je1058]

OK... I went back and unhooked everything from the board and started over. I also gathered all the keypads and noticed that the one keypad that did work (using it because it's surface mount and the others are flush) was a Lumina 33A00. The two that didn't work are 11A01-1. I even tried an extra 11A01-1 I had and it did the same thing and didn't work either... https://picasaweb.google.com/lh/photo/ZWBhsA2WavOe3rLgtBU82drvDQgIhVnOQGLzo8K9B48?feat=directlink
Here's another pic of them not working (without flash): https://picasaweb.google.com/lh/photo/SYfOZyTKnuAmOGPoBQe_rtrvDQgIhVnOQGLzo8K9B48?feat=directlink
(With flash on): https://picasaweb.google.com/lh/photo/uPFIImqHt2KQC-qVodGRG9rvDQgIhVnOQGLzo8K9B48?feat=directlink

The console that DOES work is the Lumina console, a 33A00: https://picasaweb.google.com/lh/photo/YomEjgSFgmZY65Z6ogRZrtrvDQgIhVnOQGLzo8K9B48?feat=directlink

I hooked all three consoles up within two feet of the main board to eliminate the variable of bad wiring.
For the consoles that didn't work, I kept getting: "NO CONTROLLER DATA00" as the error. If I hit the "*" it didn't stop the beeping. The beeping was 2 per second. If I hit the "OFF" button, I would get the 3 beeps per second and it wouldn't accept entries.

I also inspected the main board, in case there was soemthing that had fallen across a trace or component. I didn't see anything odd except for a trace which was cut and a diode inserted, here's a pic of it: https://picasaweb.google.com/lh/photo/aqu279sRzwC5orNVt9od4NrvDQgIhVnOQGLzo8K9B48?feat=directlink
I did go back and take pix of the main board to include the chips, as I changed out firmware chip prior to starting: https://picasaweb.google.com/lh/photo/O1-RuWI4NGGwV_a2J2Z6yNrvDQgIhVnOQGLzo8K9B48?feat=directlink Is the install of the EPROM not correct? Is the version incorrect? The missing chip is how I got it, should there be one there?

Here is a pic of the numbers on the main board: https://picasaweb.google.com/lh/photo/q0iz9fvOv-EYBWwJPqx6tNrvDQgIhVnOQGLzo8K9B48?feat=directlink
Here is a pic of the main board itself: https://picasaweb.google.com/lh/photo/gjblYk9evQUoMAEoDeJtEtrvDQgIhVnOQGLzo8K9B48?feat=directlink

It appears that the 11A01-1 isn't compatible with this OPII, but the Lumina 33A00 is. When using eh 33A00 I can set time and get the OPII to respond.

I am going to send a copy of this to HAI as well, just to get moving on a resolution to the problem... In case one of you works for HAI and sees this twice... THANKS!

 

[HAI_fjh]

If any console works then the console buss is ok and I would not worry about traces or repairs on the controller board.

If you hook up the console with nothing else on the buss and it still doesn't work, then the console is probably defective. You did not specifically state that you tried them one at a time...

The 11A01-1 is compatible with the OmniPro II. This is the older model console with the green back light and smaller buttons. The 33A00 is the newer model console with the blue back light and the slightly larger buttons. Both series "speak" the same console buss protocol and work with any Omni or Lumina controller. The Lumina console has 2 extra buttons and the text on the faceplate is different, but it also uses the same protocol. So you can mix and match either console with either controller.

It looks like some pretty old hardware. Pulls? In any case it should still work. I would recommend upgrading your firmware to the latest version and getting some working consoles before proceeding.