WiFi and BLE 2.4Ghz with separate PCB antennas on a single deviceā¦ raises some warnings.
Is there proper co-existence protocol between the two or is it a āsend and hope for the bestā arrangement?
I also wonder what are the plans for the ATECC508A because it has public key Elliptic Curve crypto.
@jmarcelino/ @Epyon, TTN GW designer here Your concerns are valid and complicate the cert process. A co-existence protocol can be implemented if it is deemed necessary.
The ATECC508A will be activated later to provide an additional layer of security ( since firmware over the air updates are difficult/wasteful/impossible with LoRaWAN). Updating physical hardware over the air is still difficult in these days and ages therefore we included it already
@Epyon, the SD card is there as a bullet proof method of updating the firmware of the Gateway. For the not so faint of heart it is even possible to host a website on it
The design document is just a block diagram, very much the same as one that was released months agoā¦
When will we see a full design package, Hardware? Software??
With the product delayed by many months now, you should of had lots and lots of time to consider what form of open license to useā¦ why are you waiting for the last hour for this???
also: the US FCC certification was given on 3 Mar 2017, when will you ship USA units??? as they should not be in the RED certification delay that you are waiting for?
I think PIC24 runs the lora gateway and PIC32 runs the packet forwarder.
The same separation as used in lattest https://github.com/Lora-net/picoGW_mcu both MCUs conected by a UART or USB, this time interface delays are not as critical as SPI between SX130x and lora-gateway
The PIC24 on the gateway module is there for house-keeping and as a wrapper around the SX1301, making it a certifiable module. It also provides the USB interface, but initially only UART is enabled. But its not a packet forwarder - the PIC32 handles that.