From: [email protected] To: [email protected] Subject: RE: [Shimmer-users] Bluetooth unique identifier Date: Fri, 19 Aug 2011 17:06:13 +0000 ben thanks for the clarification. Yes, i am referring to the IDChip unique identifier, not the BT MAC address. Chris > Date: Fri, 19 Aug 2011 12:47:31 -0400 > Subject: Re: [Shimmer-users] Bluetooth unique identifier > From: [email protected] > To: [email protected] > CC: [email protected] > > They are different chips. BT identifier (MAC) is provided by the > module supplier. It can be changed via software interface. > > The IDChip is a fixed address associated with the Shimmer unit. > > Some people order Shimmers w/o Bluetooth or leave the module powered > off so this scheme has its merits. > > -Ben > > On Fri, Aug 19, 2011 at 12:33 PM, Chris B <[email protected]> wrote: > > Dear all > > I have found, in my own apps and also the shimmer contrib apps such as > > JustFatLogging (by noting the SD card directory names that are created), > > that the hex identifier given using a IDChip.read(longAddress) call does not > > match up with the unique identifier given in Windows Bluetooth device > > properties (which is the one written on the back of the motes). What could > > be the reason for this discrepancy? Aren't the unique identifiers constant, > > or can they change? > > thanks > > Chris > > _______________________________________________ > > Shimmer-users mailing list > > [email protected] > > https://lists.eecs.harvard.edu/mailman/listinfo/shimmer-users > > > >
_______________________________________________ Shimmer-users mailing list [email protected] https://lists.eecs.harvard.edu/mailman/listinfo/shimmer-users
