ps2/rileylink

Sub-1 GHz to BLE bridge hardware and firmware

rileylink's Issues

R9 - where is it?

I can find R9 on the PCB, silk screen or in Eagle but it is on the parts list. What am I missing? Thanks!

Split app from the firmware

Hi Guys,

I am getting a lot of messages from the repository. Would it be possible to split the GlucoseLink app from the firmware of the RileyLink. Would be great and it will be much clearer for me when the RileyLink needs to be updated.

Cheers,
Fokko

TileⓇ emulation feature?

What about having the Riley also act as a Tile locator? Here is a library that might help.

https://github.com/bachya/pytile

ERROR WHEN ESTABLISHING THE PROFILE WITH ORANGELINK PRO

I am using Medtronic 754 with AAPS 3.1.0.3 dev F, and with Rileylink without problems, but I have bought a backup OrangeLink Pro c, updated with the latest available firmware and once linked with AAPS everything works except if I modify the profile and I try to activate NOT ESTABLISHED, constantly getting the error "Unable to establish the basal profile". I've tried creating new profiles, and it won't let me set them either, but if you change basal rates and send SMB,...

The voltage converter design should follow recommendations from the datasheet

http://www.ti.com/lit/ds/symlink/tps63031.pdf #11.2

in particular the placement of the capacitors could be better.

Also I wonder how the induction coil was chosen? It seems to be 7x the internal resistance than the recommended types in the datasheet (0.7 Ohm vs. 0.1 Ohm or less).

(I have a problem with the tps chip getting really hot, but still keeping voltage - I'm theorizing there is some stray capacitance/inductance with some bad feedback. Everything else works.)

722 2.4A Set Clock fails

Tried setting clock with RileyLink on a Medtronic 722 Firmware Version 2.4A.
error result:

UnexpectedResponse(MinimedKit.PumpMessage(packetType: MinimedKit.PacketType.Carelink, address: <725960>, messageType: MinimedKit.MessageType.EmptyHistoryPage, messageBody: MinimedKit.UnknownMessageBody(rxData: <0c>)), MinimedKit.PumpMessage(packetType: MinimedKit.PacketType.Carelink, address: <725960>, messageType: MinimedKit.MessageType.ChangeTime, messageBody: MinimedKit.ChangeTimeCarelinkMessageBody))

Set clock also failed through mmeowlink / OpenAPS TI stick.
I haven't tried this directly with Carelink stick yet.

Parts list

Hi there

4 of the parts in bom.csv are obsolete on Digikey.com. I have been in touch with Digikey and they have provided part numbers for replacement products. Will you accept a pull request for an updated bom.csv and confirm the specs of the 4 new parts if I make the edit?

Thanks

Mike

app: feature to configure pump as mysentry broadcast (pair)

MySentry has the user put the pump into a discovery mode, where it broadcasts packets including the pump id. The MySentry sends a response with its own id, which the pump then adds to its list of devices it accepts queries from. The pump also then starts broadcasting pump status messages every five minutes.

The screen should walk the user through this process, using a paired RileyLink, and display status updates as it receives packets from the pump and verifies it can talk to the pump.

Antenna 433MHz for omnipod rileylink in parts list

For the omnipod rileylink, it is a 433 MHz antenna but there is no branch omnipod where the antenna is replaced in the csv in the hardware folder. I am not sure which antenna is used to build the riley.

semver for ble113 firmware

Mouser Project for UK/UE Rileylink

Hi

Attached is a Mouser project with enough components to make about 5 UK/EU Rilelylinks with a bunch of the cheap components spare (enough to lose / burn out / keep for later)

Note - it will not work in the USA as I've changed the Balun and Antenna as described at https://github.com/ps2/rileylink/tree/master/hardware#868mhz-eu-version

I'm not 100% sure the components are all correct yet - but if they are, it should ease ordering for other people, since they don't have to select from 27,000+ capacitor models.. Feedback on my selections is welcome. My one concern is it seems some of the capacitors in the diagram are electrolytic - but I couldn't find electrolytic capacitors in those ranges. I also had to switch the LEDs, as I couldn't find the model referenced.

http://www.mouser.com/ProjectManager/ProjectDetail.aspx?AccessID=2316caefe4

Once I know this works, I'll submit a PR and update the BOM

Oskar

add bluetooth device serial # to guarantee binding to unique device.

bigger ble pads

bluetooth board part in eagle needs to be a bit bigger. Extend the pads out a little. Probably 1mm on the left and right side. This will allow hand soldering and better smt soldering with no bubbles

documentation

Can you highlight the specific register settings that make this work with the Medtronic pumps?

Now I have found R9...

I see R4 is right above it but not listed in the parts list. I am building a 433Mhz board. Anything to be done here? Thank you

Send ACK for all `a2` packets

Should we keep track of paired MySentry IDs, then?

Provide battery voltage

It would be great to have a way to ask rileylink for the voltage of the internal battery to alert users when it needs to be charged. Not sure if that's possible with the current hardware or would need some changes?

update switch

Switch should be fixed also it's a little off.

button

Remove reset

unique id

Expose a unique id as an attribute, based off of the internal unique bluetooth id.

https://bluegiga.zendesk.com/entries/72030216--HOW-TO-Get-a-BLE-peripheral-MAC-address-with-iOS-and-CoreBluetooth

This id can be used for traceability, to determine what happened after issues occur.

Use pump TZ instead of local TZ for parsing events.

Primary issues in NightscoutUploadKit

BOM for 433 MHz version

Hi Pete,

I have a question concerning the 433 MHz version. Do you have a bom.csv for this version ?

OtherwiseI just have to change the antenna and the balun, right? I see this version https://getrileylink.org/product/rileylink433 so if you have the component ref it will be great.

Thank you for your job :)

Power failure

Hi, I've using RileyLink and Loop since 1/20/2017. In the past few days Loop has not been connecting (indicated by red circle) and I realized that RileyLink is not holding a charge. Starting today it doesn't appear to be working at all, even when plugged in.

I saw there is an update coming. Question: Do I need to buy another one, or will a replacement be sent automatically? If I buy another, of course I'd like to have the new version.

Thanks!

semver for cc1110 firmware

This should also be made visible as a bluetooth attribute

Packet decoding will need to account for pump model

There are a lot of folks now with hardware that plan to talk to X22 pumps, which have about a dozen encoding differences across major packets. The most common one is when decoding insulin amounts, since the X22 and X23+ have different stroke sizes. However, there are other cases where bytes are in different offsets.

One approach that should work would be to create a family of PumpModel classes with an index by model string, and a family of Message classes to handle the decoding. MinimedPacket should continue to be agnostic to the intricacies of the message data and focus on RF encoding/decoding and validation.

Thoughts?

I have trouble with the rileylink

Thank you very much for such open-source project. I'm going to follow your steps to make my own rileylink, but the pump doesn't respond in time. I'd like to debug the link between the CC1110 and my pump, but it seems the protocol of Medtronic 722 is not available on the Internet. So I wonder if there are some basic commands I can send to the pump to test the wireless link ? Thanks a lot !!!

Firmware question

Thank you for answering my questions, this should be it. For background, I have built one RileyLink and it didn't work - the BLE and C1110 were not talking to each other.

Am on my second today and want to make sure I don't miss any steps. This is what I followed up load the firmware last time:

https://getrileylink.org/wp-content/uploads/2018/08/RileyLink-Firmware-Update-August-2018.pdf

Is this everything?

Thanks again.