Zigbit Bitcloud migration question

Go To Last Post
5 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi,

My company has a product line that generally communicates over a serial link but occasionally we get asked to have Zigbee communications.  In the past we have used the Atmel (or Meshnetics) ATZB-24-A2 module with Bitcloud and SerialNet.  This allowed us to drop a daughtercard onto our system and communicate over a UART with little knowledge of Zigbee or Atmel products but the ATZB-24-A2 near its end of life (if its not there already). 

 

I'm looking into substituting the ATZB-X0-256-3-0-C into our system but it seems that there is no way for us to communicate with it using AT commands (or some other simple protocol).  The closest thing I can find is the ZappSI which requires us to port code to our host microcontroller (not Atmel).  This is doable but with such little volume of sales I'd prefer not spend a lot of effort on this.  I know I'm basically saying I want Zigbee with little effort but the previous module allowed me to do it.  Are there any options that I'm missing that would simplify the migration to the new module?

 

Also, the latest bitcloud version (3.2) comes with a number of precompiled evaluation tools but they are all in .hex format while the pc bootloader tool requires .srec. Am I missing something?

Thanks,

Justin

 

 

This topic has a solution.
Last Edited: Fri. Oct 16, 2015 - 12:26 AM
This reply has been marked as the solution. 
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 1

SerialNet is dead. And ZappSi is not great either. There is no BitCloud for Xmega, so ATZB-X0-256-3-0-C is not supported. You need to look at ATZB-S0 (based on ATmega256RFR2).

 

Are you asked to have ZigBee because it is wireless, or because your customers what to use your product with existing ZigBee infrastructure? Just for wireless stuff there are plenty of other solutions. But If you really need ZigBee and interoperability with other vendors, then it is a whole different story and SerialNet won't be the answer anyway.

 

Those files are for programming with JTAG. Bootloader is useless if you don't have a JTAG cable anyway, since none of the boards come with bootloader preprogrammed.

NOTE: I no longer actively read this forum. Please ask your question on www.eevblog.com/forum if you want my answer.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Thanks for the response.  To answer your question, Zigbee was the method of choice but we are not at this time going to integrate with other vendors equipment.  Its essentially a peer to peer network where we control both sides, so Zigbee characteristics were not necessary needed.  Its a weird dynamic but it is what it is.   

 

So there is no way to use the Atmel module as essentially a serial to Zigbee bridge like the previous modules without creating custom firmware?

 

Thanks again,

Justin

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 1

No there is not , but there is a Peer2Peer application in the Lightweight Mesh stack. It is a transparent UART channel out of the box.

NOTE: I no longer actively read this forum. Please ask your question on www.eevblog.com/forum if you want my answer.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi Justin

 

Atmel just released SerialNet for mega256RFR2 and its modules. You can get it from Atmel Gallery (Wireless category) in Atmel Studio or download from the web: http://www.atmel.com/devices/ATmega256RFR2-ZigBit-Wireless-Module.aspx?t...