# Omnipod Looping

**URL:** <https://forum.fudiabetes.org/t/omnipod-looping/8012>\
**Category:** Type 1 & LADA\
**Tags:** dexcom, omnipod\
**Created:** [July 30, 2019, 4:26pm UTC](https://forum.fudiabetes.org/t/omnipod-looping/8012 "2019-07-30T16:26:34Z")\
**Posts on this page:** 1\
**Showing post:** 28

<div class="post-metadata">

**Author:** ![dm61](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fudiabetes.org/dm61/32/1602_2.png) [@dm61](https://forum.fudiabetes.org/u/dm61)\
**Post date:** [July 31, 2019, 1:03am UTC](https://forum.fudiabetes.org/t/omnipod-looping/8012/28 "2019-07-31T01:03:26Z")

</div>

> [@Running with OmniLoop](https://forum.fudiabetes.org/t/running-with-omniloop/7533/161):
>
> add support for the temp basal,

There are two somewhat different solutions to what I think you and @Eric are looking for:

1. A version of temp override that would only adjust basal but would not alter ISF or CR, otherwise Loop would continue to do its closed-loop as usual, or

2. PDM-style command to the pod to do a certain temp basal for a certain amount of time, during which Loop would not make any further alterations.

Approach 1 would likely be easier to code, and I think I might be able to give it a try - will let you know if I make any progress. Approach 2 is more complicated because it would require going down to the pod driver code (which I would not be able to do, since it is more complicated, and I do not even use pods, so could not do any testing). But, there is an [open Loop issue](https://github.com/LoopKit/Loop/issues/937) that has lots of interested users, so maybe Pete or someone else will have it included to Loop at some point.

---

_[View the full topic](https://forum.fudiabetes.org/t/omnipod-looping/8012)._
