eBay Auction (no reserve)

[T.Jackson]

Hi Paul,

I made a custom serial cable with only the tx, rx and earth connected for the PC comms. This goes direct to the 3 way block on the main PCB. I was having an issue with the 'standard' serial cable I had (that worked with the Serial IO Controller) going via the front D socket. I'm not sure why, but I never got a connection working (all connectivity was checked and fine).

Just having a look at the schematic of the alarm for you. First thing I've picked up on is that it's showing TX and RX reversed at the D9 connector (probably an error on my behalf, I'm renowned for making silly little mistakes like this)

The PC software works but seems very intermittent ... sometimes the alarm responds to commands, other times it doesn't. My gut feel is there is a handshaking problem somewhere down the line.

This is a bug in the software which I'm aware of. Unfortunately the prospects of repairing it are impossible -- the source code no longer exists, and I no longer own an electronics laboratory in a million dollar house at Dural. In fact, I don't even own a soldering iron anymore (no plans on replacing it either) I do apologize for this rather annoying imperfection.

I then built the keypad. When connected to the front dpad the LED comes on and you get a crescendo tone indicating power up. I set up codes for each of the 4 users in the Zone Config GUI and the Tx / Rx light came on when OK was hit suggesting they were being sent to the PIC. When I hit a numeric button on the keypad (PC serial cable disconnected from PC), you get a single beep. When you hit arm or disarm ... you get 4 beeps like a D D D D. I never see the Tx / Rx light flicker suggesting no comms ... and I never get a different arm / disarm tone regardless of whether I put the right or wrong code in.

If my memory serves me well -- I don't think that the TX / RX led was programmed to operate with the keypad. Clearly there is an error on the schematic on pg 30 of the magazine, showing TX and RX reversed with respects to the terminal block. If this isn't the problem -- I strongly suggest triple checking for things like; dry solder joints, loose wires, dead pics (or similar components) Persevere with it Paul, the system certainly does work okay with the exception of a few quirks here and there. There are no known issues with the keypad.

Trent Jackson

[T.Jackson]

Paul,

I might also add that, that bug is really only apparent on really fast systems running XP. The Windows-based software was developed / tested on a PIII system running Win 98. I suggest trying it out on an older, slower system running 98 to try and improve things.

I contemplated an update to correct some issues quite sometime ago before the source code was lost. Unfortunately, it was never carried out, because prior to that I spent over a fortnight updating the software for the PC-Controlled Mains Switch, Silicon Chip publications completely ignored the update. (the current version on their website isn't even compatible with the revised hardware) Two weeks of my time wasted. So I hope you can understand why it hasn't been fixed. They will never get anymore work from me.

Trent Jackson

[pgamble]

I have two PCs ... and they are both high end XP ones. I have no access to any older PC technology I'm afraid.

If I could get the keypad side of things working it wouldn't be too much of an issue. Assuming that I can get the alarm config right by just trying each send from the PC s/w multiple times until it took .... I will just use the alarm with the keypad and SMS controller (which I already have built, tested and boxed ready).

I have tried reversing the tx/rx on the four way connector in the keypad unit (which would obviously do the same thing as swapping on the front panel.

Unfortunately all I ever get is a dddd whenever I hit the arm / disarm button. It responds so quickly with the dddd it makes me wonder if it is even waiting for a response from the main alarm which is odd in itself.

Can you remember what tones it is supposed to make ?

i.e. if you put in a correct code, what tone should it make ?
if you put in an incorrect code, what tone should it make ?
and is there a tone for a communications issue (like I suspect I have ... ) ?

Are any of the tones you remember the dddd ?

As regards the s/w, am I correct in thinking that the keypad codes you setup in zone config are completely independent of the users created in access control ? I have one owner setup in access control and I have tried setting the keypad codes to 0000, 1111, 2222, 3333 respectively. I have ensured that following hitting ok on zone config that the tx/rx led shows activity ... this makes me assume that the codes are being stored in the eprom correctly.

Have checked for dry joints .... all good connections. Have also tried different PICs in both main alarm and keypad ... and also swapped both crystals for new ones.

Although I struggled previously to understand your frustrations with SC ... my recent experiences with EPE have led me to sympathise.

If there is anything you can do to help I'd hugely appreciate it.

Best regards

Paul.

[T.Jackson]

Unfortunately all I ever get is a dddd whenever I hit the arm / disarm button. It responds so quickly with the dddd it makes me wonder if it is even waiting for a response from the main alarm which is odd in itself.

Can you remember what tones it is supposed to make ?

i.e. if you put in a correct code, what tone should it make ?
if you put in an incorrect code, what tone should it make ?
and is there a tone for a communications issue (like I suspect I have ... ) ?

Are any of the tones you remember the dddd ?

As regards the s/w, am I correct in thinking that the keypad codes you setup in zone config are completely independent of the users created in access control ? I have one owner setup in access control and I have tried setting the keypad codes to 0000, 1111, 2222, 3333 respectively. I have ensured that following hitting ok on zone config that the tx/rx led shows activity ... this makes me assume that the codes are being stored in the eprom correctly.

You should be getting a single chirp each time you press a key (much like the "beep" you hear on the ATM machines) If the code is correct a brief melody is played (similar to the one that you hear when it's first powered up / initialized. However, if the code is invalid you will get the series of 4 chirps ("dddd")

There have been so many revisions of the firmware for this thing, more than I've had hot dinners over the course of these past few years. I do hope that SC have the correct version on their website.

If I were you Paul I'd trying programming the system on a slower win 9x machine. It's possible that the data in the eeprom is incorrect, the bug, as previously discussed, in the windows software is at the core of things and doesn't only just effect control over the system from the PC side of the equation.

The system was half implemented on a Win 98 machine around 2002 and finalized in 2005 when SC requested it. I hope this gives you some form of direction with it Paul.

Regards,

Trent Jackson

[T.Jackson]

Paul,

I might add also that Silicon Chip publications didn't ask me for permission to reproduce that project, they didn't give me any clue that it was going to be reproduced in EPE. If I had been informed I would have made the appropriate people aware of some of the issues with the project, plus the fact that these problems can't be rectified, because the source code longer exists.

Trent Jackson

[skimask]

I might add also that Silicon Chip publications didn't ask me for permission to reproduce that project, they didn't give me any clue that it was going to be reproduced in EPE. If I had been informed I would have made the appropriate people aware of some of the issues with the project, plus the fact that these problems can't be rectified, because the source code longer exists.

Maybe you can get the AU Secret Service after them eh?

[T.Jackson]

No, they're too busy getting ready to chase someone else.