Author Topic: Implementing a Si1000 based wireless receiver for Davis ISS data (Read 38892 times)

kspark99 · « **Reply #75 on:** July 28, 2016, 05:41:48 PM »

I'm trying to do this with a raspberry pi and a SI1000 (with a SI210x UART controller). I get this feedback when I try to update the firmware on my radio:

uploading to port /dev/ttyUSB0
Connecting to /dev/ttyUSB0
Traceback (most recent call last):
File "./uploader.py", line 278, in <module>
if not up.check():
File "./uploader.py", line 237, in check
self.autosync()
File "./uploader.py", line 197, in autosync
import fdpexpect, time
ImportError: No module named fdpexpect

Any ideas? I'm concerned its not getting past the SI210x USB to UART controller.

wylee · « **Reply #76 on:** July 28, 2016, 07:26:55 PM »

Quote from: kspark99 on July 28, 2016, 05:41:48 PM

I'm trying to do this with a raspberry pi and a SI1000 (with a SI210x UART controller). I get this feedback when I try to update the firmware on my radio:

uploading to port /dev/ttyUSB0
Connecting to /dev/ttyUSB0
Traceback (most recent call last):
File "./uploader.py", line 278, in <module>
if not up.check():
File "./uploader.py", line 237, in check
self.autosync()
File "./uploader.py", line 197, in autosync
import fdpexpect, time
ImportError: No module named fdpexpect

Any ideas? I'm concerned its not getting past the SI210x USB to UART controller.

You'll need to make these updates:
https://github.com/tridge/DavisSi1000/pull/3/commits/a6432fc33ad35e4e1e6c9bd0975f3154110a7812

Which hardware version of Raspberry Pi are you running?

wylee · « **Reply #77 on:** July 28, 2016, 07:33:42 PM »

...and if you don't have pexpect installed yet, something like this:

sudo apt-get install python-pexpect

(pexpect is required to run the firmware uploader for the Si1000 radio)

kspark99 · « **Reply #78 on:** July 29, 2016, 01:00:08 AM »

I really appreciate you helping me on this. I'm using a RPI 2B with the latest Raspian (I just installed all updates today).

I'm still having problems, but I'm not sure if I've got everything in the right spot. I only had the uploader.py and firmware on my pi, so I'm now trying to get the entire github structure onto my device. I'm still a noob at Linux, so I'm stumbling thru this.

wylee · « **Reply #79 on:** July 29, 2016, 01:14:13 AM »

Quote from: kspark99 on July 29, 2016, 01:00:08 AM

I really appreciate you helping me on this. I'm using a RPI 2B with the latest Raspian (I just installed all updates today).

I'm still having problems, but I'm not sure if I've got everything in the right spot. I only had the uploader.py and firmware on my pi, so I'm now trying to get the entire github structure onto my device. I'm still a noob at Linux, so I'm stumbling thru this.

You don't need everything; Tridge prebuilt the harder stuff.

I'm pretty sure all I needed was:
Si1000.py driver for weewx
radio~hm_trp.ihx firmware
uploader.py firmware loading tool

I don't think I ever got the firmware to load using the 2B version; definitely not with Wheezy. I used my laptop originally but I think I did get it to work on my 3B Pi running Raspbian Jessie when I had to replace the Si1000 radio.

mr_compsci · « **Reply #80 on:** January 18, 2017, 03:35:04 PM »

I had no problems compiling the new firmware on a Raspberry Pi and uploading it to the telemetry radio, but it does not find my Vantage Pro2 ISS after several days:

Searching 8576 at 918906951 Hz
Searching 8577 at 918906951 Hz
Searching 8578 at 918906951 Hz
Searching 8579 at 918906951 Hz
Searching 8580 at 912383941 Hz
Searching 8581 at 912383941 Hz
Searching 8582 at 912383941 Hz
Searching 8583 at 912383941 Hz
Searching 8584 at 912383941 Hz

I moved the Pi to within a few feet of the ISS temporarily and it still was unable to find it. I am using the "YKS 3DR Radio Telemetry Kit 915Mhz Module Open Source for APM 2.6 2.8 Pixhawk RC Quadcopter" from Amazon which is based on the HM-TRP module. I tried swapping antennas in case the first one was bad. I have not tried updating the firmware on the second radio since it doesn't have USB, but I do have a FTDI TTL interface and could try that as a next step.

I have no idea how to troubleshoot this. Does anyone have any suggestions?

kspark99 · « **Reply #81 on:** January 19, 2017, 12:53:06 AM »

I used my windows laptop to verify that the radio was hopping correctly by using a serial monitor (I used HyperSerialPort). I couldn't figure anything out on the Pi to monitor the port. Once I was sure that worked on my windows box, I found several items I had to change in a couple of the config files to get Weewx to work. Once those were fixed, it connected and has run like a champ since August.

Kurt
KMISAINT3 on Wunderground.com

mr_compsci · « **Reply #82 on:** January 20, 2017, 11:04:08 AM »

Monitoring on the Pi wasn't an issue for me. I used the console.py script in the tools folder or you can also use screen, 'screen /dev/ttyUSB0 57600' with control-a + a to exit.

It shows that the radio is changing frequencies but never locks on to the ISS. I don't know where to go from here to diagnose the issue.

runahue · « **Reply #83 on:** January 27, 2017, 08:01:31 AM »

Hello my friends.

I want try to use a si1000 receiver with my Davis Vue ISS.
Links to si1000 receivers in Davis si1000 github are broken: https://github.com/tridge/DavisSi1000
Please... could yo help me to find an adecuate si1000 receiver? (i prefer in europe)

A lot of thank's

kspark99 · « **Reply #84 on:** January 27, 2017, 08:56:22 PM »

Here's what I used. I bought it off of Amazon.
YKS 3DR Radio Telemetry Kit 915Mhz Module Open Source for APM 2.6 2.8 Pixhawk RC Quadcopter

https://www.amazon.com/gp/product/B0196LF6PW/ref=oh_aui_detailpage_o08_s01?ie=UTF8&psc=1

I programmed it using a mission planning software pack for drones. I had to program it on my windows machine but run it on a Raspberry Pi.

runahue · « **Reply #85 on:** January 28, 2017, 02:50:40 PM »

A lot of thank's
I will have a look at it !

runahue · « **Reply #86 on:** March 18, 2017, 09:55:08 AM »

I don't find exactly this one on Amazon Spain.

Which one of these ones do you think is the most adecuate?

https://www.amazon.es/Sunfounder-Telemetry-915Mhz-Quadcopter-Multirotor/dp/B01KNYO9S6/ref=sr_1_1?ie=UTF8&qid=1489844938&sr=8-1&keywords=3dr+telemetry+915

https://www.amazon.es/Dimart-Single-3Drobotics-Telemetry-915Mhz/dp/B01ALERCY6/ref=sr_1_4?ie=UTF8&qid=1489844938&sr=8-4&keywords=3dr+telemetry+915

A lot of thank's

kspark99 · « **Reply #87 on:** March 18, 2017, 10:36:08 AM »

Either of those should work. The only question I have is which3DR chip is on them? I can't tell, and their specs don't say. But they both look just like my set. Sometimes you just have to take the leap of faith.

Good luck!

Kurt

runahue · « **Reply #88 on:** March 19, 2017, 05:11:59 PM »

A lot of thank's-
My si1000 will be received in 2 or 3 days.

Where could i download updated si1000 driver for weewx? (i will use with weewx 3.7.0)
Also.... firmware utility to use with an updated raspbian.

A lot of thank's

Devonian · « **Reply #89 on:** March 19, 2017, 05:32:40 PM »

All you should need is here
https://github.com/tridge/DavisSi1000

Nigel.

runahue · « **Reply #90 on:** March 19, 2017, 05:36:27 PM »

Nigel: my Linux knowing is not the best. Can't I download them with patches and modifications applied?

Enviado desde mi SM-G930F mediante Tapatalk

Devonian · « **Reply #91 on:** March 20, 2017, 05:28:22 AM »

Sorry, I can't help much further as I never implemented this, I just followed it as I was going to do it this way.
You will need to know some basic Linux, especially as you are using WeeWX.

I ended up using my console with a data logger attached, but instead of a USB cabled connection, I made it over RF using xbee modules to connect my VP2 console to the computer which is located several metres away.

Nigel.

runahue · « **Reply #92 on:** March 20, 2017, 11:44:17 AM »

Trying compile firmware:

CC radio/radio.c
radio/radio.c:604: error 98: conflict with previous definition of 'scale_uint32' for attribute 'type'
from type 'unsigned-long-int function ( unsigned-long-int fixed, unsigned-long-int fixed) fixed'
to type 'unsigned-long-int function ( unsigned-long-int pdata, unsigned-long-int pdata) fixed'
radio/radio.c:654: error 98: conflict with previous definition of 'set_frequency_registers' for attribute 'type'
from type 'void function ( unsigned-long-int fixed) fixed'
to type 'void function ( unsigned-long-int pdata) fixed'
include/rules.mk:100: recipe for target 'obj/rfd900a/radio~rfd900a/radio.rel' failed
make[1]: *** [obj/rfd900a/radio~rfd900a/radio.rel] Error 1
make[1]: Leaving directory '/root/DavisSi1000/Firmware'
Makefile:96: recipe for target 'build~radio~rfd900a' failed
make: *** [build~radio~rfd900a] Error 2

runahue · « **Reply #93 on:** March 21, 2017, 11:14:43 AM »

Hello again friends:

Another question:
I am in Spain and using an European ISS.
Is anybody running this si1000 driver with european ISS Frequencies.

I think i must compile a new firmware changing frequencys on freq_hopping.c .
Is this ok?

runahue · « **Reply #94 on:** March 21, 2017, 11:27:22 AM »

I know this post is 4 years ago.

Franzz: did you finish this work about the european ISS?

Quote from: franzz on October 29, 2013, 02:37:55 PM

Quote from: DeKay on October 28, 2013, 11:36:46 PM
People playing with this stuff should keep in mind that these frequencies might vary a tiny bit from one console to another (I think). I believe the console keeps track of the frequency errors it measures between itself and the ISS and applies that as an offset as it does its thing, so different combinations of consoles and ISS's will give slightly different frequencies. Because of this, it is very likely that you would get slightly different numbers if you re-sniffed the register settings.

That's an interesting point. I will sniff the register setting process again if the temperature difference between console and transmitter crytal oscillator is a little bit higher. In this case it could be that there is a temperature drift between the crystal oscillators.
What I can also do is to check if the AFC register will be read out by console. According to the datasheet this register value gives the information how to change the frequency registers to compensate drifts.
One point which doesn't match with the "vary of tiny bit theory" is, that the frequency register settings are taken from the same pool if you are using more than one transmitter. In my case I have 2 different transmitters (ISS and one add. temp/hum. sensor). Both of them are hopping in the same frequeny pool. It could be that the crystal osc. have the same frequency drift or there is no frequency correction.

BR
franzz

Gyre · « **Reply #95 on:** May 02, 2017, 11:56:17 AM »

Quote from: mr_compsci on January 18, 2017, 03:35:04 PM

I had no problems compiling the new firmware on a Raspberry Pi and uploading it to the telemetry radio, but it does not find my Vantage Pro2 ISS after several days:

Searching 8576 at 918906951 Hz
Searching 8577 at 918906951 Hz
Searching 8578 at 918906951 Hz
Searching 8579 at 918906951 Hz
Searching 8580 at 912383941 Hz
Searching 8581 at 912383941 Hz
Searching 8582 at 912383941 Hz
Searching 8583 at 912383941 Hz
Searching 8584 at 912383941 Hz

I moved the Pi to within a few feet of the ISS temporarily and it still was unable to find it. I am using the "YKS 3DR Radio Telemetry Kit 915Mhz Module Open Source for APM 2.6 2.8 Pixhawk RC Quadcopter" from Amazon which is based on the HM-TRP module. I tried swapping antennas in case the first one was bad. I have not tried updating the firmware on the second radio since it doesn't have USB, but I do have a FTDI TTL interface and could try that as a next step.

I have no idea how to troubleshoot this. Does anyone have any suggestions?

Just wondering if you ever got this figured out?
I am experiencing the same issue.
The si1000 will periodically lock on once in a while for a single transmission, and then continue listening to that frequency for several more iterations before changing frequency.

mr_compsci · « **Reply #96 on:** May 02, 2017, 12:01:36 PM »

Quote from: Gyre on May 02, 2017, 11:56:17 AM

Just wondering if you ever got this figured out?
I am experiencing the same issue.
The si1000 will periodically lock on once in a while for a single transmission, and then continue listening to that frequency for several more iterations before changing frequency.

No, I don't have any idea how to troubleshoot this issue further so I have given up. I'm planning to give-in and pay Davis $50 to "upgrade" my old data logging module to work with my new console.

Gyre · « **Reply #97 on:** May 02, 2017, 07:10:49 PM »

Success.
Tridge's Github instructions didn't work for me. try loading the radio-hm_trp.ihx. instead.

No idea why it's (radio-hm_trp.ihx) struck out but the radio-rfd900a.ihx did not work at all for me.
this started working once the garbled first few strings started arriving.

K3HTK · « **Reply #98 on:** June 08, 2017, 06:30:13 PM »

I am not having any luck whatsoever with any of the firmware files. Not sure what is going on. I can connect to the 3DR Si1000 usb dongle just fine and watch as it searches through the 900 MHz range, but have let it sit now for 8+ hours trying each of the firmware types available and no luck.... I am a little late to the game on this project, so hoping maybe someone can provide some guidance and validate this should still work or maybe I am missing something.

Uploader works fine, console.py works fine. Just not getting a lock on any frequency....

Thanks!
Ed

kobuki · « **Reply #99 on:** June 08, 2017, 06:39:48 PM »

Guys, sorry to bark in, and I don't want to deter anyone from using a Si1000 radio, but instead of giving up on the alternative solutions, there exists 2 other fine solutions. The older one is based on Ti chips (CC1101), the other is on RFM69. Just search for it on the forums. Use this as starter. Or I can just blatantly link to my repo here. Have fun!

News:

Author Topic: Implementing a Si1000 based wireless receiver for Davis ISS data (Read 38892 times)