The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

RE: Re: Rabbit 2000


  • Subject: RE: Re: Rabbit 2000
  • From: "Paul Smith" <ukha@xxxxxxxxxxxxx>
  • Date: Fri, 31 Mar 2006 14:41:53 +0100

>
> That's encouraging then, it sounds like your code is OK, and the
> pulses look nice and clean too. How are you powering the pulse
> conditioning circuit? A bit obvious, but are the grounds common (are
> you using the same power supply for the rabbit and the pulse
conditioner?)
>
> Patrick
>

Yes, all grounds commend and I'm drawing power from the rabbit dev board.
Basically I have the following:-

LDR stuck to meter, driving transistor, output from this goes into
7414(Schmitt trigger) the output from here triggers the 555 monostable.
This is then connected to PB3 on the rabbit dev board. My code then counts
each time it detects a change and then every 60 secs tries loads a PHP page
which dumps the data into mysql, if this fails the counts aren't reset.
They are only reset when the data has been successfully loaded.

I also am able to calculate the time between pulses so I could get a
semi-real-time reading. Thanks must go to Kevin H for this. However I've
yet to work out what to do with this bit of information.

I used to drive a pc serial port directly with the LDR, but would lose
counts when the server reboots which I why I'm trying to get rabbit to do
it for me.

This has all be done by the poke & hope method as I'm not a born
programmer or circuit designer.

Regards


Paul





--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.1.384 / Virus Database: 268.3.3/298 - Release Date: 30/03/2006




UKHA_D Main Index | UKHA_D Thread Index | UKHA_D Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.