Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    josevicns
    @josevicns
    @rafaelruizena conseguiste bajar a 0.6.3?
    rafaelruizena
    @rafaelruizena
    @josevicns descargarlo si , crear el repositorio tambien, pero validar el repositorio no, soy muy novato
    josevicns
    @josevicns
    @rafaelruizena eso me pasa a mi, pero más, lo descargo, pero no se que mas hacer
    gracias a que tengo otro que si va bien con la 0.6.3 ... habría forma de clonarlos?
    rafaelruizena
    @rafaelruizena
    @josevicns no lo se, si lo consigues dimelo
    @josevicns enviame un privado
    chrisdex
    @chrisdex
    Hello everyone.... if you were in the market for a new smartwatch/running watch ... which one would you choose in light of OpenAPS compatibility ?
    cmdillon77
    @cmdillon77
    @ecc1 Ive ben attemping to put gnarl on a heltec LoRa_32 V2 board using a Mac, Catlina 10.15.7 and i can get o idf.py build step but I cannot flash to the board. please see the out put below. Have you come across this before? i have followed the advice on uploading driver and FTDi driver from web but i get no joy Traceback (most recent call last):
    File "/opt/esp/idf/components/esptool_py/esptool/esptool.py", line 3422, in <module>
    _main()
    File "/opt/esp/idf/components/esptool_py/esptool/esptool.py", line 3415, in _main
    main()
    File "/opt/esp/idf/components/esptool_py/esptool/esptool.py", line 3079, in main
    esp = chip_class(each_port, initial_baud, args.trace)
    File "/opt/esp/idf/components/esptool_py/esptool/esptool.py", line 261, in init
    self._port = serial.serial_for_url(port)
    File "/opt/esp/python_env/idf4.1_py3.6_env/lib/python3.6/site-packages/serial/init.py", line 90, in serial_for_url
    instance.open()
    File "/opt/esp/python_env/idf4.1_py3.6_env/lib/python3.6/site-packages/serial/serialposix.py", line 325, in open
    raise SerialException(msg.errno, "could not open port {}: {}".format(self._port, msg))
    serial.serialutil.SerialException: [Errno 2] could not open port /dev/cu.usbserial-0001: [Errno 2] No such file or directory: '/dev/cu.usbserial-0001'
    esptool.py failed with exit code 1
    root@12a2f74962ac:/project#
    Eric
    @ecc1
    @cmdillon77 I don't have any experience with using Macs for ESP32 development, and it doesn't look like this has anything to do with GNARL, but with detecting the USB serial device on the Mac. Does the Arduino environment work correctly for you?
    BTW, it's unlikely that a V2 module will work, sorry (different/missing connections to the radio DIO lines)
    Matthew Phillippi
    @Phillippi2_gitlab
    I've been investigating getting the omnipod dash working with OpenAPS on the Raspberry Pi. Omnipod's PDM is android tablet based on the Samsung Galaxy J3. It's likely that the PDM and the pod communicate through Bluetooth. Is it possible to adapt OpenAPS to communicate with the pump over Bluetooth?
    If so, that will open up the Dash for use in closed loops, using openaps
    tzachi-dar
    @tzachi-dar
    @Phillippi2_gitlab have you been able to connect with the PDM and make it work? if so, pi will also be able to do it.
    Matthew Phillippi
    @Phillippi2_gitlab
    No. I do not, yet, have a dash. The reference open APS is focused on communicating through radio. I'm looking to adapt it to use Bluetooth, instead.
    Eric
    @ecc1
    @Phillippi2_gitlab openaps calls out to standalone command-line programs to interact with the pump (readhistory and mdt, for example), so if you can make similar commands for the dash it should be feasible. I'd recommend following the Loop devs since they built the eros RF protocol support and are presumably all over the dash too
    Matthew Phillippi
    @Phillippi2_gitlab
    @ecc1 Can you link me to their work? I haven't been to find it
    Eric
    @ecc1
    @Phillippi2_gitlab I may have been too optimistic -- this indicates that their Dash work isn't being done in the open: https://loopkit.github.io/loopdocs/faqs/omnipod-faqs/ But maybe there are other reverse engineering efforts out there, I don't follow it closely
    Matthew Phillippi
    @Phillippi2_gitlab
    Sometimes Tidepool waits until they get the drivers stable before releasing the code for it.
    David Klapan
    @dklapan_twitter
    Hi there, is there an simple option how to temporarily turn off Auto bolus either by Values on Heroku or somehow other?
    I need to keep the communication between Pi and the pump for the manual bolus entry, meals and other but for few days need to stop auto basal (it's basal wrong word in previous message) to see if my basal rates are meet with my metabolism
    Foxy7
    @Foxy7
    @dklapan_twitter this looks like a questions for the Intend-to-bolus channel. https://gitter.im/nightscout/intend-to-bolus
    Kyle Cooke
    @saty9

    @ecc1 do you think that this would already be a problem if I only wanted to implement basal adjustment functionality? I can't imagine that's already too hard for the ESP32, but then, I have yet to take a closer look at the OpenAPS source. I might just try to see how far I can get using uPython/Espruino for development speed and then port it over to C/Arduino C++

    did anything come of this if not I would be interested in writing a rust implementation to run on esp32s

    Eric
    @ecc1
    @saty9 I ported a fair amount of the Go code to C for the ESP32 here: github.com/ecc1/gnarl
    It's capable of a simple closed-loop already (that part isn't fully published on github though)
    But a safer language like Rust would be very interesting
    Kyle Cooke
    @saty9
    Ah I thought that was a communication proxy only I'll take another look and see if there is a nice segment I can try and split out and replicate
    Eric
    @ecc1
    The lib/medtronic library has code for communicating with the pump. It needs a radio layer (lib/radio) which is for the LoRa radio on the TTGO board targeted by the GNARL project. Luckily it works well in non-LoRa mode for communicating with MDT pumps
    Kyle Cooke
    @saty9
    I'm particularly interested in omnipods but happy to contribute to other stuff
    Eric
    @ecc1
    That radio might be able to talk to pods too (it supports 2FSK modulation) but I didn't try. If you get it to work, please let me know / send patches
    Kyle Cooke
    @saty9
    Where in the codebase is the closed loop stuff I'm mostly finding communication stuff and main loop on a cursory look
    Eric
    @ecc1
    sorry, I haven't pushed the closed loop code to github out of concern for liability etc. But there's code to fetch pump history, and pump commands like set_temp_basal, for someone who wants to experiment on their own
    Kyle Cooke
    @saty9
    Ah fair enough
    ijustlovemath
    @ijustlovemath
    Hey all! is anyone here well versed in using the G6 Receiver's serial command grammar? I'm trying to understand the "System Time" and "Display Time", and why they might be different than the time set on the receiver
    Eric
    @ecc1

    @ijustlovemath if it's the same approach that the G4 used, then it's based on this:

    //      SystemTime = RTC + SystemTimeOffset
    //      DisplayTime = SystemTime + DisplayTimeOffset

    The actual commands to read and set the clock use the display time offset value.

    ijustlovemath
    @ijustlovemath
    @ecc1 I understand that much, what I'm having trouble figuring out is why my receivers are reporting a different timestamp than what's currently set -- a few hours different
    I believe 3 hours behind what's showing on the display
    Eric
    @ecc1
    exactly 3 hours? that sounds like a time zone issue
    ijustlovemath
    @ijustlovemath
    yes, but the device itself does not have a time zone
    it seems to have "jumped" time zones since the last time I used it, and I cannot understand why, and how to figure out which TZ it thinks it's using
    Also side note, have the CRC algorithm parameters changed recently? One of my receivers is passing CRC and the other is not
    ijustlovemath
    @ijustlovemath
    Eric
    @ecc1
    I've only worked with the G4 receiver, and that was several years ago
    ijustlovemath
    @ijustlovemath
    Okay. If anyone has worked with the G6 and knows more about this stuff, feel free to tag me!
    Jens Heuschkel
    @juehv
    @ijustlovemath Last year I had a student project on communicating with G6 transmitters. Maybe this helps: https://github.com/TheEpicBigBoss/Dexcom-ESP32-Reader
    Here another student using the Espressig IDE: https://github.com/BlindGuard/dexcom-g6-reader
    ijustlovemath
    @ijustlovemath
    @juehv thanks for that! There may be something in there I can use :) So did they change the CRC between transmitter firmware revisions? Or did they just change the data format and use the same CRC? I see there's some kind of switch in there for a certain revision triggering different code
    Jens Heuschkel
    @juehv
    I have no idea .. didn't have the time to check the code yet :D
    tremor
    @tremor
    @ijustlovemath I added the Project with a Output to an ePaper/eInk - LilyGo T-Watch ePaper, see https://github.com/tremor/Dexcom-ESP32-Reader