Open tglaria opened 11 years ago
rime was never tested.
ipv4 (i.e. compiling without UIP_CONF_IPv6) needs some tweaking in contiki-main.c and on a network bridge. But should work in principle.
On Mon, Feb 18, 2013 at 5:57 PM, Philipp M. Scholl <notifications@github.com
wrote:
ipv4 (i.e. compiling without UIP_CONF_IPv6) needs some tweaking in contiki-main.c and on a network bridge. But should work in principle.
I want to make use of the 'smaller' comunication stack, since I won't be using IP for now. Is there a noticeable difference between using one or the other? I need it make wireless synchronisation (with differences in the µs).
Atte. Tomás Ángel Glaría López
rime supports more wireless-sensor network like comm primitives but you loose IP interoperability (kind of, you can also run it on top of UDP, which at least let's you use your PC's TCP/IP stack to some extent).
For time synchornization, you might wanna check out these repositories: https://github.com/hopfgarten/jnode-applications (the sync master and slave app, test apps for the syncing) and the modified contiki branch (look for changes in uip6.c, uip.c and clock.[hc]): https://github.com/hopfgarten/contiki-jn51xx
It implements time synchronization based on ICMP Timestamps, i.e. the slave just listens for ICMP Timestamp packets (with a uint64_t timestamp from hrclock_time()) and changes its local clock accordingly.
A simple code does work in simulations (the examples actually), but can't make them work with the develpment boards.
Is something not implemented yet or it should be working out of the box?
Also, can the code be compiled WITHOUT the UIP CONF IPV6 flag?