RF100 / RF300 OSI model

[embed101]

Does anybody know how the Synapse devices work corresponding to the OSI Model?

I think it is important to know where on the model every part works.
there is:
- Hardware
- Firmware that contains standard settings and is able to run python..
- Somewhere in between is SNAP
- And of course there is the personal made python script.


Manny thanks to those who could fill me in!

[gvoce]

See if this document answers your question ....
http://www.synapse-wireless.com/docu...duct-Brief.pdf

Specific details on each module can be found in the SNAP reference manual and the individual data sheets and product briefs.

http://www.synapse-wireless.com/snap
http://www.synapse-wireless.com/snap...ents/rf-engine

[Jheath]

Does anybody know how the Synapse devices work corresponding to the OSI Model!

The SNAP firmware is much more than just a software stack compiled into a large piece of code. Instead, it acts as a network operating system that exposes a script level piece (via virtual machine) that allows the user to define their own application functionality.

This stretches across all levels of the OSI model.

Keep in mind SNAP runs across all types of network (TCP/IP, Serial, PLC, RF)

The lower layers (Physical, Link) are provided by the specific radio or other chipset related to each particular network (SNAP controls this from the sense it programs the hardware).

The upper layers (Network thru Presentation) are internal to SNAP with the Application layer exposed to SNAPpy scripts.

That being said, the user (via script) can impact each layer by configuring different elements. One example is being able to configure Carrier Sense and Collision Detection on the radio from application scripts.


Think of SNAP as an OS for embedded devices (network front end + microcontrollers)

[embed101]

Thank you Jheath,

Your answer was exactly what i was looking for! The documents Gvoce posted kind of acknowledge this. Which makes it even better!

Thanks again.