Author Topic: Wireless mailbox sensor  (Read 5163 times)

SuperRoach

  • Newbie
  • *
  • Posts: 3
Wireless mailbox sensor
« on: February 23, 2013, 09:37:39 pm »
Having seen the wireless sensor net post (http://digistump.com/board/index.php/topic,148.0.html) , I would like to build some basic wireless sensors myself for fun.

Given that I have some digisparks spare, why not! I'm thinking of getting the cheapest RF sensor possible. What should I look at to get one, and then wire it up?

Ultimately I would like to power it near a mailbox with another one receiving data, but to start off I'd like to have two digisparks wirelessly sending sensor data across.



Bluebie

  • Sr. Member
  • ****
  • Posts: 486
Re: Wireless mailbox sensor
« Reply #1 on: February 24, 2013, 03:25:13 pm »
It's pretty easy to use digisparks to send wireless sensor data via 433mhz OOK transmitters which can be found on ebay for a dollar or two each. It's more difficult getting digisparks to receieve those messages at the moment - but if you use a regular arduino as your receiver it should be fine. :)

SuperRoach

  • Newbie
  • *
  • Posts: 3
Re: Wireless mailbox sensor
« Reply #2 on: February 26, 2013, 02:17:34 am »
Thanks for the heads up :)

Is receiving a problem due to the memory for the digispark, or something else?

Bluebie

  • Sr. Member
  • ****
  • Posts: 486
Re: Wireless mailbox sensor
« Reply #3 on: February 27, 2013, 04:30:11 am »
It's just that the libraries which handle those things aren't yet digispark compatible - they use some features the arduino CPU has which the Digispark either doesn't have or has in different incompatible forms.

Mark

  • Full Member
  • ***
  • Posts: 196
Re: Wireless mailbox sensor
« Reply #4 on: February 27, 2013, 06:54:04 am »
Jenna
Can the RCSwitch library be modified to work.
 
I commented out the rx functions in the version I uploaded here.
http://digistump.com/board/index.php/topic,371.0.html
 
I note the RCSwitch team have ATtiny mentioned but with the Rx disabled.
To my uneducated eyes they don't appear to use much tricky stuff in it.
 
 
If it could be made to work, then the ability to send and receive a code in protocol 1 would be useful.
 
Mark