Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Ghost
@ghost~5a16cbf1d73408ce4f7ff683
@ecc1, @infoneo can you give link to working cheenise boards with cc1110 please? I have an issue with my boards with firmware. My SmartRF04EB did not see any board. I tried different connections, different PC's (ubuntu and windows) but results are same. "no taeget detected"
Eric
@ecc1
@d3xr I have only used CC1111 modules, from TI and ciseco/wireless things. I've bought
... cheap CC1101 (SPI only) modules from China, but then had to replace the crystals
Ghost
@ghost~5a16cbf1d73408ce4f7ff683
I know about replacing crystals, it is not a problem.
infoneo
@infoneo
@d3xr https://www.aliexpress.com/item/CC1110-868-wireless-module-CC1110-868Mhz-wireless-meter-reading-module/32823543187.html I must say, that quality of these modules isn't good. Some time ago I've ordered two modules, the first was faulty (lack some elements on pcb) the second was ok, but the range (with replaced crystal) wasn't so good like SRF. I think in present days Eric's solution with rfm69 modules is cheaper and easier
Ghost
@ghost~5a16cbf1d73408ce4f7ff683
@ecc1 Hi Eric! Please can you give link or small description about installing RFM69 for totally noobs?
Eric
@ecc1

@d3xr these are good starting points:
https://learn.sparkfun.com/tutorials/rfm69hcw-hookup-guide
https://learn.adafruit.com/adafruit-rfm69hcw-and-rfm96-rfm95-rfm98-lora-packet-padio-breakouts/pinouts

Once you're familiar with the pinout, the Go code assumes this hookup:

GPIO #    header pin #    direction    pullup?    name    active    description
23    16    input        RFM69_DIO0    high    RFM69 receive interrupt
24    18    output        RFM69_RST    high    RFM69 reset
8    24            SPI0_CE0_N        
9    21            SPI0_MISO        
10    19            SPI0_MOSI        
11    23            SPI0_SCLK

(This assumes you're connecting to a Raspberry Pi. If you're connecting to an Edison, let me know and I'll post those connections.)

Eric
@ecc1
@bewest Ben, on the off chance that you can still reply to this kind of thing: what is the VCNTR history page for on MDT pumps (and what does that name mean)?
Ghost
@ghost~5a16cbf1d73408ce4f7ff683
@ecc1 hmm.. I will connect to nanopi air. http://wiki.friendlyarm.com/wiki/index.php/NanoPi_NEO_Air#Layout I think it's like Pi?
Ghost
@ghost~5a16cbf1d73408ce4f7ff683
@ecc1 sorry it's me now. I've connected modules. Now I need to setup Go and run your script, right?
Eric
@ecc1
You can try the precompiled binaries in the ARM/SPI tarball in the latest release. There's an experimental branch of openaps that will download and use that in your loop. But if that doesn't work, you might need to compile a low level test program to check that it's connected correctly
Ghost
@ghost~5a16cbf1d73408ce4f7ff683
Eric
@ecc1
it will probably be easier for you to visit the hardware-dev room and ask about running the Go branch of oref0; that handles all the download and setup, I think
alimhassam
@alimhassam
@d3xr to install the oref0 go branch you can follow the instructions here (look for instructions on testing a feature branch) : http://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/update-your-rig.html#alternative-step-1a-dev-to-get-on-dev-branch-to-test-even-more-recently-added-new-stuff
the branch you want to install is 0.7.0-dev
if you run the oref0-setup script from that branch it'll download @ecc1 medtronic go binaries
Ghost
@ghost~5a16cbf1d73408ce4f7ff683
@alimhassam great thanks! @ecc1 ok I'll move to hardware-dev room.
ttroutman
@ttroutman
8dBi rubber duck connected directly to the Explorer board with no additional filtering in the path produced the greatest range results I've been able to create. It actually worked from one room to another room - wifi doesn't do even that in this house b/c the walls are 24" rock. Wish I had more time to drop a lot of actual data but I just don't, it just seems like a useful finding and I'm reporting in and signing out. https://www.amazon.com/gp/product/B01FV1DBSA/ref=oh_aui_search_detailpage?ie=UTF8&psc=1 .
Scott Leibrand
@scottleibrand
that goes with the U.FL Mini PCI to RP-SMA Pigtail Antenna WiFi Cable?
garykidd
@garykidd
I wonder if I ran an antenna to the top of my roof
Scott Leibrand
@scottleibrand
just don't try to be directly under the antenna: if it's highly directional, it'll radiate very little straight up and straight down in the direction it's pointing
ttroutman
@ttroutman
Correct. U.FL Mini PCI to RP-SMA Pigtail Antenna WiFi Cable - https://www.amazon.com/gp/product/B005UWD0EG/ref=oh_aui_search_detailpage?ie=UTF8&psc=1
This was not expected, I'd dorked around with filters, LNA's, the two watt amp, etc. and finally just connected the antenna directly, which I'd been scared off due to the description that the Explorer had minimal or maybe no filtering. Kaboom, good range.
Eric
@ecc1
You connected your rig to a 2W amp? Respect!
Jon Cluck
@cluckj
wow
Jens Heuschkel
@juehv

hey guys (and especially @ecc1 :D ). I'm trying to update my loop rig to PI0 + rfm69 along with the go implementation. I compiled the medtronic package and mdt and sniff. But I'm not sure with the wiring since I found no hint what pins should be used. I tried to figure it out from the code and came up with SPI+EN0+GPIO23. But it's not working and I'm stuck now.

First I tried the sniff cmd with:

 $ ./sniff           13:12:25.422805 connected to RFM69HCW radio on /dev/spidev0.0
13:12:25.422898 setting frequency to 868.000

but it runs forever, although there is communication between the old rig and the pump + the enlite sensor... After 15 min or so I tried the mdt command:

 $ ./mdt model
2018/06/02 15:13:37 connected to RFM69HCW radio on /dev/spidev0.0
2018/06/02 15:13:37 setting frequency to 868.000
2018/06/02 15:13:39 waking pump
2018/06/02 15:13:52 no response to wakeup

Any suggestions ?

Jens Heuschkel
@juehv
Ok looks like I did a stupid beginner mistak ... again :/ .. I ran mmtune and found a slidely different frequency where it runs just fine
But I'm still unsure with the wiring. I don't have rst connected and I have no idea what this d0 connection is good for
Eric
@ecc1
@juehv RFM69 reset should be wired to Pi GPIO 24 (header pin 18), and RFM69 DIO0 (used as a receive interrupt) should be wired to Pi GPIO 23 (header pin 16). The output from sniff and mdt says you've already gotten the SPI lines wired correctly.
I don't know if the openaps setup will try to recompile things; if it does, it probably won't work because it doesn't add the "-tags rfm69" to the Go build and install commands
So you can either hack that into your copy of the setup script, or recompile things afterwards and overwrite what openaps did
Jens Heuschkel
@juehv
@ecc1 Ok cool. Thanks for the hint with the oref setup!
Jens Heuschkel
@juehv
is there any pull-up or pull-down needed for the reset
Eric
@ecc1
no, it's just wired directly
Garrett Webb
@garetis
Hello! I had built a rig a couple years ago with an old 712 I had, but the pump ended up breaking and I've been manual for a while. I've recently gotten a new compatible pump and am getting back into it. Things have changed a bit, and I'm trying to stitch a rig together an offline night rig with my Pi3/TI-C1111/G5. Seems this combination is not preferred and the docs aren't too helpful for this. I'm think I'm having some issues with my autotune and preflight and looking for a little knowledge from people smarter than I am.
Specifically, I've gone through the docs to install mmeowlink (with these instructions: https://github.com/oskarpearson/mmeowlink/wiki/Installing-MMeowlink), but when I run openaps use pump mmtune I get the error that it's an invalid choice... Just fyi I didn't flash this c111, I sent it off and someone else did a long time ago. It was working for a bit with my old rig.
Dana Lewis
@danamlewis
@garetis I would repost in ITB - more eyeballs there. Also, which version of oref0 are you installing?
Garrett Webb
@garetis
Thanks @danalewis, Honestly, I'm not sure. I'd assume the most recent one? I looked in some of the setting files but not sure where to go to look that up. Figured since I was having radio issues this was a better place, but I'll check in with ITB for this
Dana Lewis
@danamlewis
If you're following the docs, that's master. But yup ITB will have more helpers
naboull1
@naboull1
hey guys does anyon know what he d3 and d4 lights are for on the explorer hat?
Eric
@ecc1

@naboull1 from the schematic ( https://github.com/EnhancedRadioDevices/Explorer-HAT/blob/master/Rev%20B/Schematic/Explorer%20Board%20HAT%20Rev%20B%20Schematic.pdf ) you can see they are connected to the CC1110 pins P2_3 and P2_4.

It looks like the firmware ( https://github.com/ps2/subg_rfspy ) uses D4 for a radio diagnostic and D3 for a UART diagnostic.

naboull1
@naboull1
could it mean a bad thing if they are on?
some reason im not getting any signals from my pump and noticed they are on
so im reinstalling the sd card from scratch now, and im going to put a fresh battery in and see if it works again
Eric
@ecc1
I'd ask other HAT users in i-t-b rather than this channel
naboull1
@naboull1
no problem thanks
Jens Heuschkel
@juehv
@naboull1 mine is blinking every now and then but not glowing constantly
naboull1
@naboull1
sweet thank you
Scott Leibrand
@scottleibrand
replied in ITB already, but the short version is that those lights being constantly dimly lit means you have a problem with the cc1110 firmware and need to re-flash it with ccprog
Abigail Cember
@acember
Hi everyone, I'm repeatedly getting this error: "mmeowlink.exceptions.CommsException: No acknowledgement from pump on wakeup. Is it out of range or is the battery too low?"
My pump had a full battery and was literally touching the rig, so neither or those suggestions apply. My mmtune was giving numbers as big as -38, so that wasn't the problem either. I'm also a PiHAT user, but I figured I would ask here as well, since the error specifically says it's being thrown by mmeowlink.