Fluorescent project
Page last updated
04 Nov 2016, by
jonathan mulvaine.
4
replies
mbed has an https://developer.mbed.org/teams/mbed-os-examples/code/mbed-os-example-client/ example which seems quite similar to a border router example hosted at https://github.com/ARMmbed/k64f-border-router
It is hard to tell what needs to be done to have a working border router secure or unsecure. Note: if it is unsecure, some web services will not allow a connection. I have succeeded at connecting 1 device to https://connector.mbed.com/ However, that sample used IPv4 and doesn't appear to run a mesh also. Also, I do not know how much "routing" we would have to encode in a border router or if the implemented library would handle that.
4 comments on Fluorescent project:
Currently trying to get the mbed-os-example-client to use IPv6.
from simpleclient.h
//Select network stack mode: IPv4 or IPv6
M2MInterface::NetworkStack NETWORK_STACK = M2MInterface::LwIP_IPv6;
does not cause the Ethernet to connect on IPv6
This is taken from the mcr20a-rf-driver
# Example RF driver for Freescale 802.15.4 transceivers #
Support for:
* MCR20A
This driver is used with 6LoWPAN stack.
- Edit the mbed_app.json file to reflect configurations. This appears to include what type of device this object will be, RF type, Mesh type, Router/Host type, etc.
- "network-interface" for ETHERNET, or MESH_THREAD
- "mesh_radio_type" for MCR20
- "target.features_add" for MESH_ROUTER or other...
... I am led to believe at this point that getting a version from GitHub is the way to go. This may REQUIRE using the Command Line Interpreter. I tried once to import a project from a downloaded zip file, that was not a success. so...
- GitHub account
- CLI
- Learn what next...
Please log in to post comments.
Currently trying to get the mbed-os-example-client to use IPv6.
from simpleclient.h
does not cause the Ethernet to connect on IPv6