The Figure shows how programs could be positioned in the microprocessors. Generally there are several options where to place the code for an application. The easiest way is to develop only on the Particle and connect no other board. Applications could be routers, beacons or applications using the ball switch like chairs. The next possibility is to use the Ssimp as the sensory extension of the Particle. The code would still be completely placed in the Particle. Instead of the Ssimp the breakout board with any sensor of your choice is possible, too. (Make sure to include the appropriate files for your add on boards and to call the init functions to initialise them correctly. If you use your own add-on board, make sure your initialisation is correct and proceeded in an early state of the program)
Next choice is to use the Spart sensor board as a stand alone. You could e.g. connect it to the serial board and send sensor values to a RS232 on a PC or PALM. You could even connect the Spart to bus like I2C if you provide the necessary code.
If you want to use the Particle together with the Spart, this can be done in two ways. The first is to distribute the application on both of the processor in the way you like it. You then have to provide a data connection between the processor in your software. The second and easy to use way is to run the “RPC Server” on the Particle (RPC: remote procedure call). The enables you to use most of the functions of the ACL layer of the RF protocol on the Spart via a remote call. You write your application on the Spart and call an ACL function via your RPC Client. The advantage of programming in this style is to have a multiprocessor environment. You will not be interrupted by the RF protocol stack like on the Particle.