Skip to content

Priming and Deploying New Pod (Lytrix)

Jump to bottom Edit New page
Joe Moran edited this page Sep 16, 2018 · 29 revisions

Numbers taken from physical POD on the backside

  • LOT: L43298
  • TID: 0391578
  • PM: 0714-L60207 (not needed yet)

Package ID when communicating with POD

  • Previous ID:1f05e708
  • Newly created ID: 1f05e709

1. Pairing

"2017-12-28T20:46:37.321135 ID1:ffffffff PTYPE:PDM SEQ:26 ID2:ffffffff B9:00 BLEN:6 BODY:07041f05e7090343 CRC:ce", 
"2017-12-28T20:46:37.331135 ID1:ffffffff PTYPE:POD SEQ:27 ID2:ffffffff B9:04 BLEN:23 BODY:011502070002070002020000a9220005f99a9a1f05e7090348 CRC:67", 
"2017-12-28T20:46:37.368877 ID1:ffffffff PTYPE:ACK SEQ:28 ID2:1f05e709 CRC:31",

Assign ID 07 Command

07 04 1f05e709 0343

  • 07 Assign ID command
  • 04 length of message
  • 1f05e709 new serialised ID
  • 0343 Unknown

Pod 01 Response with mlen $15

01 15 020700 020700 02 02 0000a922 0005f99a 9a 1f05e709 0348

  • 01 Response command
  • 15 message length
  • 020700 PM version 2.7.0
  • 020700 PI version 2.7.0
  • 02 always 3
  • 02 Pod progress (2 = tank fill succeeded)
  • 0000a922 43298 (LOT)
  • 0005f99a 0391578 (TID)
  • 9a (ggssssss=10011010) 2-bit gain = 2, 6-bit rss = $1a
  • 1f05e709 new serialised ID
  • 0348 16-bit message checksum

2. Setup Pod

"2017-12-28T20:46:38.145216 ID1:ffffffff PTYPE:PDM SEQ:29 ID2:ffffffff B9:00 BLEN:21 BODY:03131f05e70914040c1c11142d0000a9220005f99a83f0 CRC:22", 
"2017-12-28T20:46:38.215429 ID1:ffffffff PTYPE:POD SEQ:30 ID2:ffffffff B9:04 BLEN:29 BODY:011b13881008340a5002070002070002030000a9220005f99a CRC:7b", 
"2017-12-28T20:46:38.234370 ID1:ffffffff PTYPE:ACK SEQ:31 ID2:1f05e709 CRC:97", 
"2017-12-28T20:46:38.352014 ID1:ffffffff PTYPE:CON SEQ:00 CON:1f05e70980b3 CRC:c9", 
"2017-12-28T20:46:38.358137 ID1:ffffffff PTYPE:ACK SEQ:01 ID2:1f05e709 CRC:f7",

Setup Pod 03 Command

PDM SEND NEW ID + LOT+TID

03 13 1f05e709 14 04 0c1c11142d 0000a922 0005f99a 83f0
  • 03 Setup Pod command
  • 13 Length of message
  • 1f05e709 Newly created ID
  • 14 unknown, B9 or byte to indicate datetime format?
  • 04 length of following message: date time, lot, did, checksum
  • 0c 1c 11 14 2d : 12-28-17 20:45 (month-day-year hour:minute)
  • 0000a922 : 43298 (LOT)
  • 0005f99a : 0391578 (TID)
  • 83f0 16-bit message Checksum

Pod 01 Response with mlen $1b:

01 1b 13881008340a50 020700 020700 02 03 0000a922 0005f99a
  • 01 Response command
  • 1b message length = 27 bytes
  • 13881008340a50 Fixed bytes
  • 020700 PM version 2.7.0
  • 020700 PI version 2.7.0
  • 02 always 2
  • 03 Pod Progress (3 = Pairing success)
  • 0000a922 43298 (LOT)
  • 0005f99a 0391578 (TID)

3. Priming

"2017-12-28T20:46:38.744120 ID1:1f05e709 PTYPE:PDM SEQ:02 ID2:1f05e709 B9:08 BLEN:12 BODY:190ae3b052654c00009601028056 CRC:24", 
"2017-12-28T20:46:39.085393 ID1:1f05e709 PTYPE:POD SEQ:03 ID2:1f05e709 B9:0c BLEN:10 BODY:1d0300001000000003ff83a2 CRC:cf", 
"2017-12-28T20:46:39.119818 ID1:1f05e709 PTYPE:ACK SEQ:04 ID2:1f05e709 CRC:4d", 
"2017-12-28T20:46:39.452720 ID1:1f05e709 PTYPE:PDM SEQ:05 ID2:1f05e709 B9:10 BLEN:12 BODY:190a27d6d6b87837000508020280 CRC:9e", 
"2017-12-28T20:46:39.849992 ID1:1f05e709 PTYPE:POD SEQ:06 ID2:1f05e709 B9:14 BLEN:10 BODY:1d0300002000000003ff8233 CRC:bd", 
"2017-12-28T20:46:39.859723 ID1:1f05e709 PTYPE:ACK SEQ:07 ID2:1f05e709 CRC:eb", 
"2017-12-28T20:46:40.240839 ID1:1f05e709 PTYPE:PDM SEQ:08 ID2:1f05e709 B9:18 BLEN:31 BODY:1a0e244f342d02010a0101a000340034170d000208000186a0 CRC:6e", 
"2017-12-28T20:46:40.588725 ID1:1f05e709 PTYPE:ACK SEQ:09 ID2:1f05e709 CRC:b9", 
"2017-12-28T20:46:40.769775 ID1:1f05e709 PTYPE:CON SEQ:10 CON:00000000000000cd CRC:8f", 
"2017-12-28T20:46:40.843776 ID1:1f05e709 PTYPE:POD SEQ:11 ID2:1f05e709 B9:1c BLEN:10 BODY:1d4400003034000003ff013a CRC:ab", 
"2017-12-28T20:46:40.985906 ID1:1f05e709 PTYPE:ACK SEQ:12 ID2:1f05e709 CRC:54"

1a 0e 244f342d 02 010a 01 01a0 0034 0034 17 0d 0002 0800 01 86a0

  • 1a Insulin schedule
  • 0e length
  • 244f342d Nonce
  • 02 Bolus
  • 010a Checksum
  • 01 Duration 1x30min
  • 01a0 FieldA
  • 0034 UnitRate (34=52)
  • '0034` UnitRateSchedule (00=1x)(34=52) 52x0,05 = 2,6 U
  • 17 Bolus
  • 0d length
  • 0002 unknown
  • 0800 unknown
  • 01 unknown
  • '86a0` unknown

4. Ready to Insert status

"2017-12-28T20:47:35.544512 ID1:1f05e709 PTYPE:PDM SEQ:13 ID2:1f05e709 B9:20 BLEN:12 BODY:190afd1c449e380010a40302812b CRC:b1", 
"2017-12-28T20:47:35.613013 ID1:1f05e709 PTYPE:POD SEQ:14 ID2:1f05e709 B9:24 BLEN:10 BODY:1d0500174000000007ff831e CRC:02", 
"2017-12-28T20:47:35.615085 ID1:1f05e709 PTYPE:ACK SEQ:15 ID2:1f05e709 CRC:f2"

5. Setting basal schedule

"2017-12-28T20:48:26.077526 ID1:1f05e709 PTYPE:PDM SEQ:16 ID2:1f05e709 B9:a8 BLEN:50 BODY:1a1436e07d2b00031f2916e800047009f00bb00bb00a131a40 CRC:b6", 
"2017-12-28T20:48:26.355714 ID1:1f05e709 PTYPE:PDM SEQ:16 ID2:1f05e709 B9:a8 BLEN:50 BODY:1a1436e07d2b00031f2916e800047009f00bb00bb00a131a40 CRC:b6", 
"2017-12-28T20:48:26.483319 ID1:1f05e709 PTYPE:ACK SEQ:17 ID2:1f05e709 CRC:92", 
"2017-12-28T20:48:26.762316 ID1:1f05e709 PTYPE:PDM SEQ:18 ID2:1f05e709 B9:a8 BLEN:50 BODY:1a1436e07d2b00031f2916e800047009f00bb00bb00a131a40 CRC:be", 
"2017-12-28T20:48:26.987755 ID1:1f05e709 PTYPE:CON SEQ:20 CON:02028100c65d4002d001312d000c0800f9b07404b00112a8800306 CRC:f7", 
"2017-12-28T20:48:27.059854 ID1:1f05e709 PTYPE:POD SEQ:21 ID2:1f05e709 B9:2c BLEN:10 BODY:1d160017500000000bff82f6 CRC:29", 
"2017-12-28T20:48:27.471412 ID1:1f05e709 PTYPE:POD SEQ:21 ID2:1f05e709 B9:2c BLEN:10 BODY:1d160017500000000bff82f6 CRC:29", 
"2017-12-28T20:48:27.718834 ID1:1f05e709 PTYPE:ACK SEQ:24 ID2:1f05e709 CRC:e9", 
"2017-12-28T20:48:27.961784 ID1:1f05e709 PTYPE:POD SEQ:26 ID2:1f05e709 B9:34 BLEN:10 BODY:1d160017600000000bff8367 CRC:52", 
"2017-12-28T20:48:28.083371 ID1:1f05e709 PTYPE:POD SEQ:26 ID2:1f05e709 B9:34 BLEN:10 BODY:1d160017600000000bff8367 CRC:52",

6. Insert needle

"2017-12-28T20:48:28.204086 ID1:1f05e709 PTYPE:PDM SEQ:28 ID2:1f05e709 B9:38 BLEN:31 BODY:1a0ebe8be6c4020065010050000a000a170d000064000186a0 CRC:f4", 
"2017-12-28T20:48:28.325382 ID1:1f05e709 PTYPE:ACK SEQ:29 ID2:1f05e709 CRC:04", 
"2017-12-28T20:48:28.495954 ID1:1f05e709 PTYPE:CON SEQ:30 CON:0000000000000236 CRC:2c", 
"2017-12-28T20:48:28.575802 ID1:1f05e709 PTYPE:POD SEQ:31 ID2:1f05e709 B9:3c BLEN:10 BODY:1d570017700a00000bff0201 CRC:d0", 
"2017-12-28T20:48:28.702085 ID1:1f05e709 PTYPE:POD SEQ:31 ID2:1f05e709 B9:3c BLEN:10 BODY:1d570017700a00000bff0201 CRC:d0", 
"2017-12-28T20:48:28.706578 ID1:1f05e709 PTYPE:ACK SEQ:00 ID2:1f05e709 CRC:c2"

7. Acknowledge correct insertion

"2017-12-28T20:48:52.059873 ID1:1f05e709 PTYPE:PDM SEQ:01 ID2:1f05e709 B9:00 BLEN:3 BODY:0e0100803a CRC:fa", 
"2017-12-28T20:48:52.389836 ID1:1f05e709 PTYPE:PDM SEQ:01 ID2:1f05e709 B9:00 BLEN:3 BODY:0e0100803a CRC:fa", 
"2017-12-28T20:48:52.427536 ID1:1f05e709 PTYPE:POD SEQ:02 ID2:1f05e709 B9:04 BLEN:10 BODY:1d18001c700000000bff8084 CRC:62", 
"2017-12-28T20:48:52.446092 ID1:1f05e709 PTYPE:ACK SEQ:03 ID2:1f05e709 CRC:64"
Add a custom footer

Communications

Reference

Message decoding

Device drivers

Hardware

Clone this wiki locally