 Show Posts
|
|
Pages: [1] 2
|
|
2
|
Using Arduino / Networking, Protocols, and Devices / Re: WiFly Breakout vs WiFly Shield?
|
on: December 10, 2011, 02:17:10 pm
|
|
Hi,
The WiFly breakout board interfaces with 4 pins (Rx, Tx, Gnd, 3.3v) and communicates via the Arduino's UART.
the WiFly Shield uses more pins and communicates via the Arduino's SPI pins.
Each uses different libraries as a result. Programming model differs as well (one day soon they will merge).
Both end up at an RN-131/RN-171 chip.
There are of course other more minor differences but the above are the major items.
Cheers,
|
|
|
|
|
3
|
Using Arduino / Programming Questions / Re: Time from computer to Uno
|
on: December 10, 2011, 01:05:41 am
|
|
The suggestions provided by other posters are refined, elegant, effective and efficient. Please consider their responses respectfully.
For an over-kill approach, get a WiFly, configure it to your local wlan and favorite ntp server, and it will automatically set time on the Arduino.
Then you'll have both a mobile wifi-enabled Arduino and a curious urge to wave a sledgehammer around while grunting.
Sorry, full moon this Friday night.
|
|
|
|
|
4
|
Using Arduino / Programming Questions / Re: Continually re-entering setup()
|
on: December 10, 2011, 12:49:55 am
|
|
Hey ljd2,
Sorry to hear that the constrained-memory issues are causing grief... very familiar with those while writing the WiFlySerial library.
On the plus side - there are learning opportunities for memory management in constrained spaces.
The WiFly preparation functions do take a certain space (ok, an unseemly heap) of their own during initialization; most of that allocation is released after completing the setup() function.
Once setup is done, not sure why you'd want to revisit the topic during loop(). Which setup function are you trying to use in loop() and why?
Cheers,
|
|
|
|
|
6
|
Using Arduino / Programming Questions / Re: EEPROM write more than 256 bytes
|
on: April 29, 2011, 10:44:45 am
|
|
... the 28K limit given 32K of flash memory had me going sideways as well ...
It turns out the 'other' 4K is consumed by the bootloader. It has to go somewhere - and flash memory is where it resides.
So ... for most of us, the Uno really provides 28K usable flash memory space.
Really nifty/advanced users could over-write or replace the bootloader, but you'd have to have a really compelling reason to drive through that zone of complexity.
|
|
|
|
|
10
|
Community / Exhibition / Gallery / Re: Menu Manager
|
on: April 17, 2011, 11:13:30 pm
|
|
luidr,
Thanks for the suggestion - quite the compliment!
To prevent my ego from getting too large too quickly, I'll invite code criticism so that what eventually gets posted is reasonably clean.
Cheers,
|
|
|
|
|
12
|
Community / Exhibition / Gallery / Re: Menu Manager
|
on: April 16, 2011, 12:00:06 pm
|
|
Hi luidr,
Very neat projects on your site!
Slightly different applications for each of the two menu systems, each has its own strengths.
The way yours handles inputs is cool.
Mine is more oriented to terminals in this version.
Anyway, the more these get exposure, the more the community benefits from choice and example.
Cheers,
|
|
|
|
|
13
|
Community / Exhibition / Gallery / Menu Manager
|
on: April 14, 2011, 01:11:03 pm
|
A "simple" menu manager is now available at http://arduinology.tumblr.com/MenuSampleIt was created because ... I wanted to be able to control different options within a larger project. Perhaps others have a similar need. It is not necessarily a canonical or the best possible model, but is working sufficiently well for the project's needs. Comments welcome - give it a try! Cheers, |
|
|
|
|
| Arduino Forum :: Members :: tjw7