Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Regarding the question of receiving data. #113

Open
BG7UHS opened this issue Sep 11, 2021 · 6 comments
Open

Regarding the question of receiving data. #113

BG7UHS opened this issue Sep 11, 2021 · 6 comments

Comments

@BG7UHS
Copy link

BG7UHS commented Sep 11, 2021

Is there a better way to make the received data more accurate?
I am using the receiving py script:

from rflib import *
d = RfCat()
d.setModeIDLE
d.setMdmModulation(MOD_ASK_OOK)
d.setFreq(315000000)
d.setMdmDRate(3500)
d.setMaxPower()
d.lowball()
d.RFlisten()

Screenshot_20210902-162731891__01

The data received in this way is basically irregular. Occasionally, a correct piece of data will be received. Did I do something wrong?

@atlas0fd00m
Copy link
Owner

lowball is intended to make it as easy as possible to receive whatever data is out there.... it's not intended for accuracy.
don't use lowball mode, but rather set an appropriate SyncWord and other Packetizer (Pkt* and Mdm* functions) settings to appropriately match what's being transmitted.

@Crsarmv7l
Copy link
Contributor

Crsarmv7l commented Jun 11, 2023

Old issue and probably obsolete, but I have found that using d.calculatePktChanBW() and filtering by RSSI < 90 helps a ton. You aren't going to be able to really analyze captures (use an rtlsdr for that), but I have had great success and accuracy with capture/replay using those.

@BG7UHS
Copy link
Author

BG7UHS commented Jun 14, 2023

Old issue and probably obsolete, but I have found that using d.calculatePktChanBW() and filtering by RSSI < 90 helps a ton. You aren't going to be able to really analyze captures (use an rtlsdr for that), but I have had great success and accuracy with capture/replay using those.

Can I see the code you wrote?

@Crsarmv7l
Copy link
Contributor

Old issue and probably obsolete, but I have found that using d.calculatePktChanBW() and filtering by RSSI < 90 helps a ton. You aren't going to be able to really analyze captures (use an rtlsdr for that), but I have had great success and accuracy with capture/replay using those.

Can I see the code you wrote?

Sure. It is by no means perfect, but it works well for me
https://github.com/Crsarmv7l/DaikonTools-for-Yardstick-One/blob/main/DaikonRX.py

@Crsarmv7l
Copy link
Contributor

Crsarmv7l commented Nov 2, 2023

Coming back to this, mainly to say how wrong I was. If you know the signal you are looking for, you can filter and decode it, without resorting to an RSSI filter (still need one if you don't know the signal you are looking for). With the YS1 on a fixed freq, with a fixed datarate I was able to recognize, capture, decode and display 3 different brands of weather sensors only using software to filter and using lowball. Sure you aren't going to catch every single one, but you will grab many of them.

Built some other "decoders" for a variety of other protocols. This tool keeps surprising me and it is so satisfying to use

@atlas0fd00m
Copy link
Owner

thanks @Crsarmv7l ! i'm glad you are being fulfilled with the tooling, both RfCat and your custom tooling!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants