Feb. 11, 2011
The current API (Version 1.6.2) is online here:
A new ONE-NET release is on the horizon. If you have a suggestion for a new message type, please post it in the forum.
We're planning a ONE-NET video series that will augment and supplement our Seminars. We’ll post the videos to You Tube as well, so they’ll be easy to share.
The first video will be an overview but will be followed up by specific, in-depth videos on different subjects.
Subjects on the table for now include:
- Transceivers: Current list, the importance of interoperability and what makes them ONE-NET compliant.
- Security: Encryption, Nonces, etc.
- Link Budget: why is this important
If you have any suggestions for topics, please post your responses in the General Comments section of the forum.
Vladimir Kostritsa is officially a ONE-NET Code Monster as he's ported the MSP430. His work can be viewed in the the forum.
Vladimir states: "The client based on CC430F6137 works. Both ‘AUTO’ and ‘SERIAL’ (no CLI) modes are OK. I tested ‘invite’, ‘peer’, ‘single’, ‘data rate test’, ‘remove device’ and ‘unassign peer’ commands. Everything looks good. Did not tested user’s pins yet, but will do it shortly.
We wanted to thank Future for hosting the ONE-NET seminar. There were some really interesting applications being discussed which we hope to report on in the coming weeks. Look for more seminars soon!
|Page 1 of 5|
|Encryption is integral to the ONE-NET protocol as there are no unencrypted modes. While the default encryption is XTEA2, an alternate ID tag allows extension to future algorithms.|