Posted on Leave a comment

iDiab.dev – Tools test aplication

First test – proof-of-concept for development using Xamarine and distribution via FlightTest and Google Play Store.

Application doing almost nothing 🙂 only scan for available BLE devices.

Google acceptance time – 2h
Apple acceptance time – 38h

Android version: https://play.google.com/store/apps/details…

iOS version: https://testflight.apple.com/join/9ZdJKUPr

Please comment about installation, dificulties, etc in both versions.

Posted on 3 Comments

iDiab.dev – New Initiative

In the last days or even months, the whole community of diabetics and their families has been (and still is) exposed to hard tests. New types of sensors with encrypted access (Freestyle Libre), changes in existing service procedures that do not allow further use of equipment (new G6 model), blocking the use of applications (Spike) – these are just examples.

There is no point in considering and wondering what the reasons for these changes were. It is important to look into the future, draw conclusions from what is happening and take appropriate actions so that in the future this type of situation will not happen again.

My idea is as follows:

To create an application that will be the “sum” of existing ones.

It is not about “re-inventing the wheel”, but about gathering what is offered today in DIY applications serving diabetics in one new app which will be available on all equipment platforms – Android, iOS, Windows, etc.

The new application will be available as it is today for existing ones, but the whole of its source will be published as “open-source” on Github. Thanks to this – in emergency situations everyone will be able, thanks to free software environments, to create it for themselves and install it on their own devices – exactly as it is today with Loop or xDrip applications.

It will cover all available in existing applications such as xDrip+, Spike, Glimp, Loop, AAPS, OpenAPS, etc. also “internal devices”: elements of CGM systems, insulin pumps, glucometers as well as all types of our “processors” existing today – smartphones, smartwatches, smartband, etc. The ability of all of today’s functionalities based on data exchange by Nightscout and other similar servers will be preserved.

An additional effect will be the unification of transmission protocols, data exchange, cooperation with other applications, different devices, etc.

The new application – it will not only be one progam, but at least three:

  • Application “tools” – used to activate sensors, restart transmitters or other technical activities
  • Application “lite” – a simple, basic version
  • Application “full” – a full version with all possibilities.

The order of creation as follows:

  1. Tools
  2. Light Version
  3. Full Version

So far, thousands of hours and days devoted by developers and volunteers creating existing applications today and the fact that virtually all of their sources are available in the form of open-source – will allow work to progress quickly.

All results of this initiative will also be open-source and get published on the web on a current basis.

There is a lot to do. For the results to be quick – I have to spend all my time without dealing with other topics – also without any other “work for living”. Since I have practically finished works on decoding Libre 2 / Pro / H sensors – I can start this topic.

I do not have the necessary financial “stocks” myself to be able to devote myself completely and permanently to this work – I am launching the opportunity of social support by declaring even minimal, but permanent, monthly financial support through the Patreonus platform.

Here is the link to my Patreonus page: https://www.patreon.com/idiabdev

Benefits from this is for everybody, those who will financially support and who not – free and available for all diabetes DIY applications.

The project starts today, without waiting of – if and how many such financial support declarations will be.

I will publish current information on this blog and on a specially created FB group (information about this and other Internet locations related to this project will be published here and in FB groups devoted to this subject).

FB Group: https://www.facebook.com/groups/idiab.dev/

Direct e-mail contact: mailto:info@idiab.dev

I am open for cooperation with all of community developers to help, improve and organize all work in thos project to be fast and smooth. So I am inviting all of you to cooperate 🙂

I am very curious about your opinions, comments and suggestions on this subject.

A few words about me:
My name is Marek Macner, I live in Poland and for several years I have been developing equipment and software for DIY for diabetics.
Professionally – software and equipment for aerial photography, for many years I developed software for state administration (systems for car registration and issuing driving licenses) and managed telecommunications companies – data transmission via satellites.

Posted on Leave a comment

New sensors Libre….

(English version below)

Last year (2018) new types of sensors Freestyle Libre-Libre 2, Libre Pro, Libre H and Libre US 14-Day appeared on the market. It's good and bad. Well-because the development of technology and increasing its availability is good for the diabetics community, and bad-because these new sensors do not support currently available solutions allowing for the self-construction of CGM systems.

Practically since their emergence-an international team of developers creating applications such as Spike, xDrip, Nightscout, loops closed in which this team I have a pleasure to attend from the beginning-began work on their decoding and Enabling them to cooperate with them.

The work ended in the last days (except for the Libre US 14-day sensor, which is still ongoing). Fortunately, we managed to solve all the problems with these new sensors. Unfortunately-it is necessary to replace the internal software in the intermediary devices, ie in MiaoMiao, BluCon, GNSentry, my transmitters, etc. Some of them allow this update by the user, others will need to refer to the manufacturers.

At the present time, we are talking to all manufacturers about the necessary changes and on what rules these changes will be made.

In relation to the manufacturers, we have adopted simple rules-the same for all:

  1. Existing in firmware protocols-remain unchanged
  2. Each manufacturer is obliged (if he wants his device to work with new sensors) introduce a new protocol "bleDiab-L" which the specification receives from us. This is a very simple transmission protocol and adapting the current software should not take more than 1 working day for the manufacturer.
  3. After the introduction of this protocol the manufacturer has to provide us with several such modified devices to check, test whether everything is OK.
  4. All existing producers have not participated in any costs or activities related to our work-we provide them with a new protocol without any effort on their part. Only if they wanted to apply it in their own applications-other than xDrip, Spike, Glimp – we require them to make a financial grant to the Nightscout Foundation in any of their established values.

All the work performed by the development team was and is implemented as a "non-profit" action. None of us in this respect received any gratification and the whole result is for the open-source community available free of charge.

Here, I would like to thank all the projects involved: programmers, people who gave us test sensors, application testers.

(Link to a file describing the protocol and the requirements for device manufacturers-here)

(English version)

Last year (2018) new types of Freestyle Libre-Libre 2, Libre Pro, Libre H and Libre US 14-day sensors appeared on the market. This is both good and bad. Good-because the development of technology and increasing its availability is good for the diabetic community, and bad-because these new sensors are not currently supported in the available solutions allowing for the independent construction of CGM systems.

Practically from the moment of their appearance-an international team of programmers creating applications such as Spike, xDrip, Nightscout, closed loops in which I have the pleasure to participate from the beginning-began work on their decoding and enabling Cooperation with those sensors.

The work ended in the last days (with the exception of the Libre US 14-day sensor, which is still underway). Fortunately, all problems with these new sensors have been solved. Unfortunately-It is necessary to replace the new, updated internal software in intermediary devices, i.e. in MiaoMiao, BluCon, GNSentry, my transmitters, etc. Some of them allow such updating by the user, others will have to be sent back to the manufacturers.

At the moment-we are conducting talks with all manufacturers regarding the necessary changes and on what terms these changes will be introduced.

We have adopted simple rules for manufacturers-the same for everyone:

  1. Protocols existing in the firmware-remain unchanged
  2. Every manufacturer is obliged (if he wants his device to work with new sensors) to introduce a new "bleDiab-L" protocol, which he receives from us. It is a very simple transmission protocol and it should not take more than 1 business day for the manufacturer to adapt the current software.
  3. After entering this protocol, the manufacturer is to provide us with several modified devices to check, test if everything is OK.
  4. All current manufacturers have not participated in any costs or activities related to our work-we provide them with a new protocol without any expenditure on their part. Only if they want to apply it in their own applications-other than xDrip, Spike, Glimp-we require them to make a financial grant to the Nightscout Foundation in any decided by them value.

All the work carried out by the team of developers has been performed as a "non-profit" activity. None of us have received any gratification for this and the whole result is for the community creating open-source software available free of charge.

At this point, I would like to thank everyone involved in this project: developers, people who gave us sensors for tests, application testers.

(Link to the file with protocol description and requirements for device manufacturers-here)