Hi Alf,
thanks a lot for the documents – that's just what I looked for :)
Is it okay to publish the PDF file, containing the schematic, on the
internet as part of the board's description or is that information/ file
confidential?
Best regards
Matthias
On 08/28/2016 09:37 PM, Alf Petter Mossevi
Hi,
can you check if this is https://github.com/RIOT-OS/RIOT/issues/5467?
> Why or how can a node be removed from ncache? Why the node does not
automatically reconnect with BR?
As the implementer of the neighbor discovery I can say this: because
the neighbor discovery is sh** ;-). It was written
Hi,
I'm using two SAMR21, one with BR (on A) and the other (on B) with
gnrc_networking example.
I'm on April release.
Switch on A (border router) then switch on B, I'm able to send UDP
message from Linux to 2001:db8 address of B.
If I try to send lot of data (every 100ms), it works for a while and
Hi Neo,
has it already clarified? I'm not sure I got the problem, but let's have
a look at the following code lines.
https://github.com/RIOT-OS/RIOT/blob/master/drivers/at86rf2xx/at86rf2xx.c#L202
at86rf2xx_tx_load() is called with an offset parameter and it writes the
SRAM at position offset
Hi Loïc,
your experiment to substitute Aversive++ with RIOT as HW abstraction
looks great to me.
Its nice to see an example of coordinated actuators steered by a remote
wireless RIOT node.
Actually I would love to see your robot running on the ground.
I think its a really nice example for a o
