Jeti RFID Battery-logger

onki wrote: Hi Tero,

I was contacted by a french hobby friend who is using both the charger BID2NFC solution and your on board battery RFID "detector". Since the memory format of your solution and the 1:1 BID memory mapping of BID2NFC is not compatble this doesn't work together.
Do you see a way to combine both in order to close the circle. This would allow wireless parameter exchange at the BID-charger as well as battery detection in the model.

Have you been in contact with Ralf who made the BID2NFC code?

Best regards
Onki

I asked this from you few days ago: www.jetiforum.de/index.php/lua-fuer-die-...gger?start=108#70643

The BID2NFC uses memory-blocks from "all over the place", I could not see the factual blocks used and that is why I asked this from you.

Basically there is only option: One of us needs to move some used memory blocks to others. RFID-Sensor uses blocks 4 and 5. (These are once already moved away from BID2NFC's way). From the code if I read it correctly it uses a lot of blocks and I can't really understand why.

I do not want to change blocks used in RFID-battery, that would mean all users who built or bought RFID-Sensors would need to make their tags again. I do not see that as an option.

Dear Tero,

AFAIK is the memory structure on the Mifare tag is a 1:1 mapping of the original BID chip to keep it simple.
BID is using 1k I2C EEPROMS and they are probably mapped 1:1 to the chip.
According to Ralf the BID data is just using 255 Byte. Since battery parameters are generic and not manufacturer specific It would make sense to define a format and try to map the BID data to this format. But I have no idea how complex that is. In addition existing data must be converted which makes it even more complex.

I will contact Ralf to find out if this is possible.
To have both on one tag it might be useful to shift content to higher blocks and allow both to be saved on one chip.
Best regards
Onki

From the info the user sent I got a picture that BID2NFC writes the whole card, that is strange.

RFID-Sensor battery-size bug is fixed, sensor is back in shop and guide on update available here www.rc-thoughts.com/2017/01/how-to-update-rfid-sensor/

If you have built or bought one and use batteries larger than 8192 mAh you need to update the sensor.

onki wrote: Dear Tero,

AFAIK is the memory structure on the Mifare tag is a 1:1 mapping of the original BID chip to keep it simple.
BID is using 1k I2C EEPROMS and they are probably mapped 1:1 to the chip.
According to Ralf the BID data is just using 255 Byte. Since battery parameters are generic and not manufacturer specific It would make sense to define a format and try to map the BID data to this format. But I have no idea how complex that is. In addition existing data must be converted which makes it even more complex.

I will contact Ralf to find out if this is possible.
To have both on one tag it might be useful to shift content to higher blocks and allow both to be saved on one chip.
Best regards
Onki

This is now fixed, Paul tested and it works. I'll update some details on site soon.

Ok, thanks to Paul this is now tested to be fully compatible with Robbe BID2NFC. I changed memory allocation for "RC-Thoughts" tag-information.

Unfortunately this also means the tags needs to be written again but that is a small price to pay for 100% compatibility.

Big thanks to Paul for testing!