Acknowledging tokens on WiTilt

Howdy,

I’ve been messing with these WiTilt modules a few days now… I’m liking the possibilities alot.

But I’ve found some discrepancies between your datasheet, the code, and the functioning of these modules. I wonder if you could confirm what I’m seeing.

The datasheet/code suggests that the WiTilt will keep transmitting a packet up to 3 times (if running from batteries) before failing, if no acknowledge is received. To test this, I’ve disabled acknowledgement in my receiverboard and configured the code to echo every byte received (even if the packet number matches a previous packet).

I don’t see any repetition of packet numbers - suggesting the WiTilt only transmits each packet once.

This isn’t such a problem, but I’ve noticed another discrepancy that is a little troubling for me. Each RF device is supposed to respond to the ‘255’ token by adjusting onboard settings (rf channel, power level, etc.) but this doesn’t feature in the WiTilt code I’ve downloaded. I would really like to be able to remotely change channel numbers for each device.

Of course I could reprogram the WiTilt boards, but I’m just wondering if I’m missing something???

Thanks heaps. Love ya work.

Sorry, we’ve been off in lala land for the past few days. I’m not familiar with the witilt code (one o’ Nate’s babies), but I’ll see if I can get an answer for you.

Pete

Hey Matt,

Couple things - the WiTilt was pretty exceptional in its day. Wireless Acceleration readings in a mini form factor. Unfortunately Spark Fun is not known for it’s marketing so we’ve only sold 20-30 units without plans on carrying it much longer.

I’m willing to help you out as much as possible, but everything is in the firmware: http://www.sparkfun.com/datasheets/Acce … ilt-v1.zip

http://www.sparkfun.com/datasheets/Acce … rd-v01.zip

Packet transmission is attempted 3 times (send_packet function).

The WiTilt board uses a stripped down version of the ol’ SMiRF protocol. Stripped down in that the WiTilt wakes up, yells out its two acceleration readings (3 trys) and goes back to sleep (10Hz). The WiTilt does not listen for remote reconfiguration commands.

The firmware should give you a good starting point to adapt it to your needs. I just never figured the button would be just as good to change the channel as it would be to try to implement a remote reconfiguration (gotta try ot yell at the WiTilt until it wakes up, issue the command while it’s awake, and attempt not to loose the link).

-Nathan

Hey Nathan,

It’s a real shame to hear that the WiTilt was just a flash in the pan… I’ve been recommending it to a few people. It’s a very novel and useful idea to combine some form of A/D converter and transmission system with devices that will be used in free space (accelerometers, gyroscopes)…

As for marketing… are you aware how many webpages reference your portable rotary telephone? I see it appearing on all sorts of gadget blogs, like Make Magazine and maybe Gizmodo…

Maybe you could publish a few neat projects for some of your more specialised products… Our own personal use for your WiTilt is in creating musical ‘toys’, such as beach balls, that audiences can interact with to influence algorithmically-generated music… We’ll be sure to publish details of our collection with as much kudos to sparkfun as possible. Will let you know.

Perhaps you could try wireless again later with the newer 3-axis, or gyroscope devices? Who wouldn’t want one of those?

Thanks again.

Matt

How cool is that! I love the applications our customers come up with!

The rotary phone is killing us at the moment (in a good way). Got a call from Paris newspaper on Tuesday morning. They needed photos.

Who knew two years worth of RF, Accelerometer, cellular, and GPS development would be over-shadowed by a toy? The rotary phone is getting quite a lot of press…

-Nathan