Changing NETID in DnJoin does not have effect

[ghost]

Issue

Despite Iss#6 being closed, the NETID parameter in dn_qsl_connect seems to have no effect on the joining process of the mote.

What I did

With build f00317305189b1868c581c0565f45b23eea80d6c, the following parameters were changed in TestDnJoin

#define NETID           25
#define JOINKEY         NULL
#define BANDWIDTH_MS            0
#define SRC_PORT        0

And performed Test TU_SH/DnJoin_Cli_Op_B. The test still succeed, despite expecting the test to fail (as the NETID should not match between DP and NM

What Needs to be Done

Investigate why this is happening.

[ghost]

Hypothesis

Mote is currently configured in some way such that: "join to the first network detected"

[ghost]

Mote API Not Functional

Join success from previous tests was because of CLI and not API

Proof

DP	CLI	NM	Joined ?
Blank	Connected	Connected	Yes
Blank	NC	Connected	No

The Mote still joins to the network without a DuinioPro join command (sent through API).

We can see a waveform riding on the TX line (DN --> DP) for some reason

[ghost]

Dusty Auto Join

Seems like Dusty module is joining by itself (even without CLI)

See commit 1f0b6588d2abffc2de52ce173343cdbf727342f4;

The 'sends' do nothing, and the LED is held on true (indicating attempting to join still)

Potentially need to re-flash to ensure its a slave and not its own master