It seems that most Propeller 2 products, projects, and applications will include a connection to the internet in some way. Of the early product examples we've seen, each has included the ESP32 - just like we saw in yesterday's Propeller 2 Live Forum - Peter Jakacki Presents P2D2 presentation. Two other product design efforts I'm aware of also include an ESP32 (one in remote environmental sensing, another for machine control).
I imagine many of us have knowledge around both the ESP32 and the P2.
Parallax would like to offer a Spin2 object (and ESP32 firmware) for our customers which is easy to use, reliable, and fully (enough) featured. The internet already has so many examples with ESP32 - a quick look turned up this interesting site Random Nerd Tutorials
and others. GitHub is loaded with examples as well from an active community of developers, often around the Arduino. The ESP32 module is a dual-core processor and it runs Arduino firmware, too.
How to proceed with creating a useful interface for the P2 is currently beyond my current level of understanding. @Jeff Martin
has far more knowledge on the subject and @JonnyMac
has included this as an important addition to our list of needed objects.
Some of the thoughts I have about it:
Do we really only need a Spin2/PASM object if we can use the Arduino firmware and libraries?
It seems that the Arduino ESP32 firmware does what would be commonly needed for the Propeller - except for the "more of it, faster" part to satisfy the P2's many I/Os and high baudrate capability. Could existing firmware be leveraged for our use, or is it already useful?
What uses would the P2 present that are already not provided for by other processors?
Many examples I see are fairly simple and very useful: activate an alarm, send an e-mail, turn things on and off. These can be easily achieved with current examples and hardware.
What does the Propeller 2 community need in a ESP32 object?
Parallax needs to sell P2 chips to applications that have some potential. If the needs are limited to detecting your dog with RFID and counting doggy-door clicks, this has already been solved. If you're making a product, what are your exact needs?
As mentioned above, we're willing to support an effort but we're not sure that it's actually needed or how we'd define the scope of work to be done. We'd like this to be easy for our customers to use and properly supported.
To move forward, perhaps it makes sense to schedule this topic as a Propeller 2 Live Forum - Early Adopter Series. Or, you can place your thoughts here. How do we move forward with IoT for the P2?