Author Topic: User bytes in beacon Issue  (Read 185 times)

Nick_W

  • Full Member
  • ***
  • Posts: 215
    • View Profile
User bytes in beacon Issue
« on: August 31, 2016, 08:22:28 pm »
Hi,

As you may be aware, I have been experimenting with encoding information in the "user bytes" (4 of them) in the beacon. An excellent way of extending battery life.

Mc-Abe commented elsewhere
Quote

3: This was missed in the release notes. If there is no data in the beacon, it sends the version/type of module, this was mostly meant to be used by us to provide support but here is an explanation of the format for your reference:
Code: [Select]
byte[0] = 0x01 ------------------> Device Type for mcMod110
byte[1] = 0x07 = 7 ----------+
byte[2..3] = 0x016D = 365----+---> 0.7-365

Which I did note, but did not realize that byte 1 was the module type.

This new feature now makes embedding data in the "User Bytes" difficult, as I have no way of telling if a module is publishing my data or yours.

If these are indeed "User Bytes" then you should not be publishing anything in them, as they are reserved for the user.

I also believe this information is redundant, as the module type and version are published in other beacons (at least they were displayed before the "User Bytes" started carrying this information.

Can I ask that this feature be removed? So that we can have the user bytes back? Or add a way (another byte?) for us to tell if the bytes contain user data or system data.

The problem is that when a module boots, I will interpret its data as some valid (but wrong) value, until the first valid data is loaded into the beacon. This is inconsistent behavior for something defined as "User Bytes".

Thanks.

Share on Facebook Share on Twitter


kbrooking

  • Full Member
  • ***
  • Posts: 104
    • View Profile
Re: User bytes in beacon Issue
« Reply #1 on: November 26, 2016, 06:55:28 pm »
Hello Nick, I know this is a rather old post but, I have began to experiment with beacons as well and was wondering if this isues was ever resolved?

Nick_W

  • Full Member
  • ***
  • Posts: 215
    • View Profile
Re: User bytes in beacon Issue
« Reply #2 on: November 26, 2016, 11:31:42 pm »
I haven't heard anything specific about this, but the latest firmware now publishes 0000 in the user bytes (not the firmware version). So I think this problem is solved for me.

mc-John

  • Global Moderator
  • Full Member
  • *****
  • Posts: 212
    • View Profile
Re: User bytes in beacon Issue
« Reply #3 on: November 28, 2016, 09:34:54 am »
Yes this has been solved, meaning initially the beacon data will be zeroes. You can change it and it is very simple to see, just open the beacon form.