iPad IOS support
AE5QB
Posts: 3
Any chance that Parallax will come out with an iPad app that supports the Basic Stamp Editor? I have several Boe-Bots in my classroom and we are a 1:1 iPad classroom. I don't have any windows based systems to program the things except for my personal laptop. It would nice to see iPad and IOS support for these products.
Comments
There is some work underway to use the xBee WiFi module from Digi since any IOS program can open an internet "socket" and transfer data over it. You'd need the WiFi module and some kind of microcontroller to interface from the xBee to the Stamp for downloading a program. This still would involve a lot of development and some significant cost on a per iPad / per Stamp basis, but probably is more feasible than the serial interface version. The current project is for the Propeller using a web-based compiler / assembler, the xBee WiFi module, and a simple interface from the xBee module to the Propeller board (like the Propeller Activity Board or Propeller Board of Education which already have an xBee socket). A Propeller Activity Board plus xBee WiFi module would cost about $50 + $33 = $83.
I've got to answer with an explanation around the Propeller before I say "yes" or "no" to your inquiry, around the BASIC Stamp.
We are currently in the middle of designing an iOS interface for the iPad for the Propeller (ActivityBot). It's a wireless interface using XBee on the robot side, without additional hardware hanging off the iPad. Our efforts have been a two-step process. The first step was to get a functional downloader working where you can select your own code and download (no editing). With this part working we're now looking into porting Simple IDE to iOS. There's also a bit of detail around it right here: http://www.parallax.com/news/2014-03-18/parallax-support-ipadiphone-based-propeller-application-downloads-propeller
So there are three parts to making this work with Propeller:
1. Downloader (working)
2. Downloader and code editing (in process)
3. Hardware changes to Propeller Activity Board (TBD, still trying to get away without a co-processor)
We have to finish the Propeller work first with iOS, and then we can look into the BASIC Stamp. However, the Propeller has far more complex issues in terms of program size, timing requirements, and file management. We think that if we can finish this with the Propeller then the BASIC Stamp would be quite easy to support on iOS. The tokenizer is written in C and Jeff has already compiled it in X-Code. However, nothing comes free in terms of hardware - we'd need to make a new Board of Education that has a WiFi socket. You can see how the steps add up.
If all goes well, we'd have a turnkey solution for your class by this time next year. We're working on it, as fast as we can, but the issues are often complex - especially if we want it to be simple for the user.
Please feel free to check back in with us on this item.
Ken Gracey
KI6HBT
This is a not a logical reply to the content of the thread and the second such reply from a new member.
Ken,
Can you elaborate on item 3. above ?
Yes. 3. We will need to connect the XBee socket Tx/Rx/RST to three Propeller pins and provide a physical switch to go from WiFi to USB programming and back and forth. We will not need a co-processor to do this job.
In regards to #2, the developer Mike Westerfield of ByteWorks (he's on these forums) needed to take a short break but this week he reported positive progress on the actual edit/compiling aspect. I have no idea how it works, but it seems like he's got the whole GCC toolchain running on the iPad. Soon we shall find out.
Ken Gracey
Does this problem apply to any mobile device? So would you encounter the same thing if you did this on an Android device?
I understand this may be a stupid question, but I would like to use my android device to build a remote controller for my Arlo, and would like to know if I am getting into something over my head .
I think I have a solution to download without a link RST (DTR) line. If the NPN.R.C is replaced with a 74AUP1T58 (~10c) then the HW can support either RST via RXD or RST via DTR.
It then just needs a small change to the send end at the DTR time, to add a Break String.
More detail @
http://forums.parallax.com/showthread.php/156842-Xilinx-port-started...?p=1287492&viewfull=1#post1287492