A Christmas Bonus! Thanks to our partners, MCM Electronics and Infineon, we're expanding the number of RoadTesters from 5 to 20!
To conclude an exciting 2014, element14 in collaboration with Infineon and the Eclipse Foundation is pleased to announce a RoadTest Plus which we've entitled "The Internet of Holiday Lights".
Each selected competitor will receive the following package of items:
Infineon Lighting RGB LED Arduino Shield
Arduino Yún
Arduino Uno
Blogging Challenge
Each RoadTester will be tasked with creating a holiday lighting IoT application and blogging at least 3 times about their project. The final submission date will be Friday, January 23, 2015.
Provision of outstanding, compelling and inventive community and blog content.
The Grand Prize
CEL Robox 3D Printer
The Grand Prize Winner will receive a CEL Robox 3D Printer. This future proof and stylish 3D printer was recently cited by Yahoo! as one of the Best Tech Gifts of 2014. This prize is worth £849 / $1330 / €1070!.
All those who finish their projects will receive...
Internet of Things with the Arduino Yún
All finalists who finish their projects will receive a copy of Internet of Things with the Arduino Yún by Marco Schwarz. This book provides inspirational projects and information so that the finalists can take their Internet of Things exploration with the Arduino Yún even further in 2015.
Terms & Conditions
RoadTesters will be selected based on the quality of the application; we expect a full and complete description of:
Why you want to test these products? and...
Your approach to blogging about the ensuing project.
RoadTesters are required to produce:
A full, comprehensive and well thought out review
A minimum of 3 blog posts about these product(s) in the Arduino section of element14. (These are due by Friday, January 23, 2015)
Failure to provide the review and blogs within the above time-scale will result in the enrollee being excluded from future Road Tests.
As I said in my above post, I am happy DoctorCDF allowed the extra time as with all the hard work everyone has put in it would be a shame to miss some of it due to technical difficulties, I hope you where able to get it all uploaded now
I ran into a loads of problems with the uploads here because apparently there have been policy changes at my ISP and their service has totally messed up. It took 6 1/2 hours to get a 10 minute video up and then YouTube started fussing about the content etc.
I am very greatful to @doctorcdf for the extension in deadline and apologize for the inconvenience caused.
no problems been seen reported in the community that I have observed or experienced by me but it is nice to see some latitude with the final entries as so many people have put so much effort into this one, would be a shame to miss the final entries due to a technical issue
We've had reports of technical difficulties uploading videos - as a result, we'll give a 24 hours grace period to the finalists should they experience these problems in their locale. Thanks again.
as I want to include some launch pads in the Holiday Light project
I have all the code added to the OOB project but it is alluding me as to how it will connect to the local wan or internet as that project seems to be an access point for connecting from a smart device or something to the card and I can not seem to find a way to have it establish the connection outbound
you did not cover setting up the SSID or password etc for the WIFI and I can not find info from TI to do it either so if you would be so kind to let me know it would be appreciated
Assuming you are using V 1.9.1, The API for the callback shows:
Subscription Callback
If the client is used to subscribe to topics, a callback function must be provided in the constructor. This function
is called when new messages arrive at the client.
The callback function has the following signature:
void callback(char* topic, byte* payload, unsigned int length)
Parameters
topic – the topic the message arrived on (char*)
payload – the message payload (byte array)
length – the length of the message payload (unsigned int)
Internally, the client uses the same buffer for both inbound and outbound
messages. After the callback function returns, or if a call to either publish
or subscribe is made from within the callback function, the topic
and payload values passed to the function will be overwritten. The application
should create its own copy of the values if they are required beyond this.
So I cannot see why you do not have the first parameter being the specific topic.
know what the topic is, all attempts so far have not printed or provided the topic name,
If I use the standard mosquito subscription under Linux I simply subscribe with a -v in the command line for a verbose response but of course that's not going to work on Arduino
If you subscribe using a wild card so for example topic = thebreadboard\# and I publish both thebreadboard\temp=35 and publish thebreadboard\humidity=35, how do you determine the Topic for the message that arrives?,
I can do this with the PubSubClient.h library but so far the eclipse library has eluded me for this