After all the recent merges, it does not seem to compile... about wifly-shield HOT 57 CLOSED

Same here, I get:

arduino-1.5.2\libraries\WiFly\SpiUart.cpp:240: error: unterminated #if

from wifly-shield.

Thanks for the first fix but I get the same errors after the first fix. I really need this ASAP ugh. This isn't good.

from wifly-shield.

I went back to this commit and it compiled for the Uno but not the Due.

https://github.com/sparkfun/WiFly-Shield/tree/ca519e349221e1de0184133cf8039487052d9533

I get this on the Due

WiFlyDevice.cpp: In member function 'boolean WiFlyDevice::enterCommandMode(boolean)':
WiFlyDevice.cpp:132: error: 'PSTR' was not declared in this scope
WiFlyDevice.cpp: In member function 'boolean WiFlyDevice::softwareReboot(boolean)':
WiFlyDevice.cpp:253: error: 'PSTR' was not declared in this scope
WiFlyDevice.cpp: In member function 'void WiFlyDevice::requireFlowControl()':
WiFly\WiFlyDevice.cpp:378: error: 'PSTR' was not declared in this scope
WiFly\WiFlyDevice.cpp: In member function 'void WiFlyDevice::setConfiguration(boolean)':
WiFly\WiFlyDevice.cpp:416: error: 'PSTR' was not declared in this scope
WiFly\WiFlyDevice.cpp: In member function 'void WiFlyDevice::setAdhocParams()':
WiFly\WiFlyDevice.cpp:461: error: 'PSTR' was not declared in this scope
WiFlyDevice.cpp: In member function 'boolean WiFlyDevice::createAdHocNetwork(const char_)':
WiFly\WiFlyDevice.cpp:488: error: 'PSTR' was not declared in this scope
WiFlyDevice.cpp: In member function 'boolean WiFlyDevice::join(const char_)':
WiFly\WiFlyDevice.cpp:526: error: 'PSTR' was not declared in this scope
WiFly\WiFlyDevice.cpp: In member function 'boolean WiFlyDevice::join(const char_, const char_, boolean)':
WiFly\WiFlyDevice.cpp:547: error: 'PSTR' was not declared in this scope
WiFly\WiFlyDevice.cpp: In member function 'const char* WiFlyDevice::ip()':
WiFly\WiFlyDevice.cpp:581: error: 'PSTR' was not declared in this scope
WiFly\WiFlyDevice.cpp: In member function 'long int WiFlyDevice::getTime()':
WiFly\WiFlyDevice.cpp:669: error: 'PSTR' was not declared in this scope

from wifly-shield.

I got it to compile adding this to WiFly.h

#define PSTR(x)  x

Found it here

arduino/Arduino#1317

from wifly-shield.

I think I am done wasting my afternoon. Data that comes back from the WiFly is corrupt. For example IP: 1ÿÿÿÿÿÿÿÿÿÿÿÿÿÿ

from wifly-shield.

@FriedCircuits In the mean time, you are welcome to use my most stable branch. It makes some changes to the configuration that is automatically set, to make it a more stable client. One thing to keep in mind, is that if you are not using the external antenna, you must change (or remove) line 426 of WiFlyDevice.cpp.

https://github.com/dubhunter/WiFly-Shield/tree/client-hardening

Hopefully the recent activity here means we will have an actual maintainer (fingers crossed), since despite my branch being the most stable one I've used, still could be more stable. (It seems to randomly have issues after 500-1000 requests.)

from wifly-shield.

Thanks. I will check it out. Yeah I can't use the external antenna because the cap for the connector is 1/2 soldered. Still waiting to hear from support. I am trying to port code over from using Ethernet. I am so close, ugh. Here is the Ethernet version: https://github.com/FriedCircuits/LED_Twitter_Due

from wifly-shield.

Didn't compile for me Arduino 1.5.2

WiFlyClient.cpp:41: error: 'Client' has not been declared
WiFlyClient.cpp: In function 'size_t write(byte)':
WiFlyClient.cpp:47: error: 'WiFly' was not declared in this scope
WiFlyClient.cpp: At global scope:
WiFlyClient.cpp:54: error: 'Client' has not been declared
WiFlyClient.cpp: In function 'size_t write(const char)':
WiFlyClient.cpp:60: error: 'WiFly' was not declared in this scope
WiFlyClient.cpp: At global scope:
WiFlyClient.cpp:67: error: 'Client' has not been declared
WiFlyClient.cpp: In function 'size_t write(const uint8_t, size_t)':
WiFlyClient.cpp:73: error: '_WiFly' was not declared in this scope
WiFlyClient.cpp: At global scope:
WiFlyClient.cpp:79: error: expected constructor, destructor, or type conversion before '.' token
WiFlyClient.cpp:82: error: expected unqualified-id before 'if'
WiFlyClient.cpp:88: error: expected constructor, destructor, or type conversion before '.' token
WiFlyClient.cpp:90: error: expected unqualified-id before 'if'
WiFlyClient.cpp:93: error: expected unqualified-id before 'else'

from wifly-shield.

Well, like I said, its the most stable version yet...but I really hope Sparkfun steps up to the plate, because the WiFly shield has never been fully stable, and for $90, it f*cking should be.

from wifly-shield.

Whoops, I'm still on 1.0.1. If you want to get it working today, you may have to downgrade.

from wifly-shield.

Also, my branch is still using the old directory structure...make sure to compensate for that.

from wifly-shield.

Yeah no kidding. At this point I may just stick with Ethernet and bridge it on my netbook.

It should compile, I tried setting board to Uno as well. I can't downgrade since I am using Arduino Due. I have both 1.0.3 and 1.5.2 installed.

from wifly-shield.

You are using the client-hardening branch right? Not master? Since I pulled sparkfun's into my master last night, its still bad.

from wifly-shield.

1.0.3 and 1.0.1 should be compatible I would think.

from wifly-shield.

Yeah I downloaded the link you gave.

from wifly-shield.

I can test with 1.0.3, one sec

from wifly-shield.

Yeah, Ethernet is a champ. I can't use it for my project, because it's in a waterproof case outside, and I can't have wires running around.

from wifly-shield.

Yeah, it compiled for 1.0.3. So something in 1.5.2.

from wifly-shield.

It depends on the built in Ethernet libs, which often change with Arduino. Its been a major PITA in the past. Once again, I'm hoping Sparkfun takes charge, brings it up to date. And makes it stable!

From everything I've read, the RN-131C is very reliable, so all the problems seem to come down to the Library.

from wifly-shield.

The code here mostly works. I got the server example to work. It seems like sending to the module works but receiving doesn't. Like the IP doesn't display and the example client that searches google gets back corrupted data. Problem is I have a week to get this done. I doubt SFE will work on it that soon.

from wifly-shield.

I had a WiFly Xbee but it died and Roving won't replace it.

from wifly-shield.

How was that device, stability wise?

from wifly-shield.

I'm not sure if my branch will work in server mode, the config is optimized for client mode.

from wifly-shield.

It was fine, just needed a reboot once in awhile. I was using it for this project: http://www.mobilewill.us/2013/02/wifi-thermostat-control-part-1.html

Now its like the firmware is toast. At first I could leave it off for a few hours and then it would work for like 5 min.

from wifly-shield.

Client mode is all I need. Need to pull tweets.

from wifly-shield.

Here is the project I need it for: http://www.mobilewill.us/2013/04/led-matrix-wedding-and-twitter.html

from wifly-shield.

Cool I'll take a look later, but need to work on some other things in the mean time.

If it helps, here is the sketch that is running the client-hardening branch (right next to me) https://github.com/dubhunter/ArduinoSketches/blob/master/hyduino_wireless/hyduino_wireless.ino

from wifly-shield.

Thanks, yeah I think I am going to work on another project and come back to this.

from wifly-shield.

BTW, nice chatting with you William, my name is Will.

from wifly-shield.

Same, Will.

from wifly-shield.

Cool project, it looks like something I've been working on for a while now. Here is an old pic http://instagram.com/p/UIUSoyv1Cd/, but its an SMS marquee, that I was going to hook to twitter too, when it hasn't received an SMS in a while.

from wifly-shield.

Nice, what are using to drive it. I found an Android app to act as a SMS to Twitter gateway. So people can use both.

from wifly-shield.

For the hardware, its an Arduino Mega w/ a custom shield to connect all the matrices.

For the software, its using my library for Notifyr (a push like service), a simple web server script to send events to Notifyr, and Twilio. Twilio receives SMS, sends it to my server, which proxies to Notifyr, which the Arduino is listening to for events. Super fast (no polling), and very reliable.

Here is the Library https://github.com/dubhunter/ArduinoNotifyrClient (it even works very well wi WiFly). I would be using it on my current project, but I need bi-directional communication, and the stupid WiFly can only handle one at a time.

from wifly-shield.

Here is the web server proxy code. https://github.com/dubhunter/sms-led-sign/blob/master/dbdApp/controllers/Sms.php

from wifly-shield.

Yeah I was using the Mega but too slow for scrolling text. Funny you mention twilio, I have been coming across it lately. I was going to use it till I found the Android gateway app.

from wifly-shield.

Well I am biased, since I work there. But it is super duper awesome (and simple). On a challenge from my brother-in-law...after getting an Arduino to trigger my DSLR camera shutter, I SMS enabled it in under 20 mins.

from wifly-shield.

And I'm only using the Mega to drive that many matrices (to handle 168 characters). Otherwise I wouldn't, but I'm also not doing scrolling.

from wifly-shield.

I like your way of doing it. Easier to read without scrolling.

from wifly-shield.

Well, besides the panels being a bit expensive, it is not done because I ran into power issues (which I'm very close to solving), because I'm an SE, not an EE.

Those panels draw a LOT of power.

from wifly-shield.

Here is what happened to my WiFly shield. Look at the cap by the antenna connector.

I bet they do. My 8 isn't too bad. I can run from USB but it runs a bit dimmer. I use my USB Tester\OLED Backpack to keep tabs on it.

from wifly-shield.

Is that a glob of solder on the left inside of it?

Also, if you are interested, here is Arduino sketch for the LED Matrix https://github.com/dubhunter/ArduinoSketches/blob/master/twilio_marquee_notifyr/twilio_marquee_notifyr.ino

from wifly-shield.

The cap looks like it tombstoned when they reflowed it and no one saw it before it was shipped out. That white cap will move if you barely touch it. It supposed to be parallel to the connector.

from wifly-shield.

Oh man, well hopefully the sparkfun folks read this thread on Monday and help with the library and help you with a new board.

Good news is, the chip antenna is pretty good. I only have to use the external antenna because of my enclosure.

from wifly-shield.

Yeah, I emailed them Thursday night but haven't heard back.

Thats good to hear. The plan it to use my phone as a hotspot at the wedding.

from wifly-shield.

I got your version to compile. I still had to add "#define PSTR(x) x" to WiFly.h.

I guess the IDE doesn't like having multiple versions of the same library.

Still same problem with replies.

connecting...
1ÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
connected

Supposed to show current IP Address.

from wifly-shield.

Finally! I stopped trying to worry about getting the IP and your library was able to do a Google search and return the results with readable text.

from wifly-shield.

You are a lifesaver. Its works! I can't believe it!

Able to connect to to Twitter.

from wifly-shield.

Glad to help!

from wifly-shield.

Hey guys, sorry for the delay in getting back to you. This shield is designed to work with the Uno board footprint, not the Due, first of all, so just keep that in mind when working with this hardware. It's not plug and play compatible. Unfortunately, also related to this is that the 1.5 release of Arduino is still in beta version, and we've seen a lot of bugs with that environment for many different libraries. We are working on getting everything up to date as possible, but considering how much everything changed moving from v023 to v1.0, we don't want to get too ahead of ourselves until we know what the final changes are going to look like.

FriedCircuits, I'm hoping you emailed tech support at [email protected]. They should be able to get back to you today or tomorrow and get you sorted out with your shield. They've been slammed with students emailing about final projects (as always happens this time of year), so I'm guessing that may be the source of the delay.

from wifly-shield.

No problem. I jumpered over the needed pins. Yeah I know how that is, I was on the user beta team for the Due last year. It coming along pretty good.

Thanks, I had emailed customer services, but I went ahead and emailed Tech Support as well. I am just in a time crunch right now, but it looks like Will's library will work.

from wifly-shield.

At least it compiles on UNO and MEGA 2560

from wifly-shield.

Sweet, I will have to try it. I think the only you may need for Arduino 1.5.2 is adding "#define PSTR(x) x" to WiFly.h.

from wifly-shield.

Does this library work at 38400?

from wifly-shield.

I've never been able to run it above 9600...

My $0.02

from wifly-shield.

Thanks, it seems I am having reliability issues on the connection. Doesn't always download the same number of tweets. Like it times out.

Not as clean at Ethernet and when I test on a hotspot probably be worse.

from wifly-shield.

BTW, @ToniCorinne, after merging #24, it does indeed compile, but never finishes initializing...

Did something else change? I keep having to revert to my branch to get things to work at all.

from wifly-shield.

There wasn't anything that should have affected the hanging issue. I didn't run into a problem myself, but my files were doing some odd things during testing initially, so it may have just not been running correctly on my computer. You may want to try checking out some other libraries in the mean time if it's really giving you issues.

from wifly-shield.