Description: Particle’s IoT (Internet of Things) hardware development board, the Photon, provides everything you need to build a connected project. Particle has combined a powerful 120Mhz ARM Cortex M3 micro-controller with a Broadcom Wi-Fi chip in a tiny thumbnail-sized module called the PØ (P-Zero). The Photon Kit includes a Photon with headers, a shiny white mini-breadboard, a USB-micro cable, and a couple of extra surprises to help you start building right away.
These specific Photons come without headers, making them best for surface mounting and special applications. The Photon is not only powerful, but easy to use. The small form factor is ideal for IoT projects with cloud-connectivity. To get you started quickly, Particle has added a rock solid 3.3VDC SMPS power supply, RF and user interface components to the PØ all on a small single-sided PCB.
Your Photon comes with access to the Particle Cloud, a free cloud service. The Particle Cloud has some great features for building connected projects, including over-the-air firmware updates, an easy-to-use REST API, and firmware development supported by web and local IDEs.
Based on 2 ratings:
1 of 1 found this helpful:
The Particle Photon has a unique and responsive cloud environment which is easy to use. I like the cloud API that gives you simple access to functions and variables within your program. The initial setup can be a bit of a hassle but once you have it on your network and have it claimed the process gets easier. The example code and libraries are very helpful in learning how to program the device. I have one project fully implemented and deployed and have a few more planned that will include the Photon.
1 of 4 found this helpful:
These are nice units, the hardware is very good, and remote code updates work great, but the limitations are quite serious:
1) There is no local compilation option – even if you work with source on your computer, it has to be sent to the cloud to be compiled.
2) The direct cloud options for data transfer are severely limited in terms of bandwidth.. one update a second is about as good as it gets.
3) The single microcontroller solution means that there can be significant delays between execution of the code in loop() while the Photon does it’s own work. Nothing happens for some seconds when the Photon has to reconnect to the Internet for instance.
4) calling digitalWrite() before setting pinMode() to output has no effect, so you have to change the pinMode() to output before you can set its state – this results in unwanted and unnecessary glitches in the signal when transitioning from a high-z state to output high or low.
5) the external VREF for the ADCs is not exposed, which is limiting.