Hi Tom,
I find the (not so) recent step of Digi to open-source Rabbit development a
very good idea. However, for an open-source project to strive it needs some
guidance. Have you thought what new developments you (or Digi, or other people
in this group) would want to see in the future? Do you have a roadmap that you
can share?
All the best,
Mircea
Rabbit development direction
Started by ●November 5, 2018
Reply by ●November 9, 20182018-11-09
Mircea,
I have a fairly limited role with the software. Digi has hired me to do some of the maintenance, like updating to TLS 1.2 and implementing fixes for the KRACK WPA vulnerability. I’m not personally using Rabbit hardware on any projects, and actually selected a Cypress Semiconductor board for a recent hobby project.
If anyone is interested, I have some leftover hardware from a hand-held, battery-powered RCM2200-based product I built and sold. Take a look at http://www.sniffter.com/ to see what it looks like. I probably have a dozen units I’d be willing to sell and can provide schematics and some DC 8.61 code to drive it.
I can’t really share anything about the future Rabbit product line. You’ll have to look for announcements of both new and EOL (end of life) Rabbit products and make your own decisions as to what’s coming up. If there’s something you’d like to see, you’ll have to talk to your sales rep or get in touch with Digi’s product management.
I’ve been working on Digi’s XBee Cellular and XBee3 RF product lines, including implementation of MicroPython on those products so customers can run Python code alongside the radio’s firmware. I think there are some exciting product development possibilities there.
-Tom
> On Nov 5, 2018, at 1:03 PM, m...@neacsu.net [rabbit-semi] wrote:
> Hi Tom,
>
> I find the (not so) recent step of Digi to open-source Rabbit development a very good idea. However, for an open-source project to strive it needs some guidance. Have you thought what new developments you (or Digi, or other people in this group) would want to see in the future? Do you have a roadmap that you can share?
> All the best,
>
> Mircea
>
I have a fairly limited role with the software. Digi has hired me to do some of the maintenance, like updating to TLS 1.2 and implementing fixes for the KRACK WPA vulnerability. I’m not personally using Rabbit hardware on any projects, and actually selected a Cypress Semiconductor board for a recent hobby project.
If anyone is interested, I have some leftover hardware from a hand-held, battery-powered RCM2200-based product I built and sold. Take a look at http://www.sniffter.com/ to see what it looks like. I probably have a dozen units I’d be willing to sell and can provide schematics and some DC 8.61 code to drive it.
I can’t really share anything about the future Rabbit product line. You’ll have to look for announcements of both new and EOL (end of life) Rabbit products and make your own decisions as to what’s coming up. If there’s something you’d like to see, you’ll have to talk to your sales rep or get in touch with Digi’s product management.
I’ve been working on Digi’s XBee Cellular and XBee3 RF product lines, including implementation of MicroPython on those products so customers can run Python code alongside the radio’s firmware. I think there are some exciting product development possibilities there.
-Tom
> On Nov 5, 2018, at 1:03 PM, m...@neacsu.net [rabbit-semi] wrote:
> Hi Tom,
>
> I find the (not so) recent step of Digi to open-source Rabbit development a very good idea. However, for an open-source project to strive it needs some guidance. Have you thought what new developments you (or Digi, or other people in this group) would want to see in the future? Do you have a roadmap that you can share?
> All the best,
>
> Mircea
>
