-
Notifications
You must be signed in to change notification settings - Fork 8
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
mixer not working #10
Comments
revert the mhz to hz patch, this is where the math breaks, I have it working correctly once i removed those changes in my fork |
Just tried your Code @thex1le , there is a missing bracket in line 388, but even after fixing that, the mixer doesen't seem to work. I used a DC 3.05 and my SDR isn't showing anything on 1.29ghz when i enter a mixer frequency of 1110mhz on startup of the Chat app. The master branch shows the Signal allways on 2.4ghz because of the mixer issue :) |
Interesting, I had it tuned to different channels with that change. What
port are you using? on the board? You need to use the LNB port if recall,
not the direct. Direct doesn't go through the mixer. The RTL.com
documentation is wrong.
…On Mon, Dec 23, 2019 at 5:42 PM Manuel ***@***.***> wrote:
revert the mhz to hz patch, this is where the math breaks, I have it
working correctly once i removed those changes in my fork
Just tried your Code @thex1le <https://github.com/thex1le> , there is a
missing bracket in line 388, but even after fixing that, the mixer doesen't
seem to work. I used a DC 3.05 and my SDR isn't showing anything on 1.29ghz
when i enter a mixer frequency of 1110mhz on startup of the Chat app.
The master branch shows the Signal allways on 2.4ghz because of the mixer
issue :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#10?email_source=notifications&email_token=ABA3TUJMP2H6PYKFWCNUBE3Q2E5DVA5CNFSM4FGIQUIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHSB4CA#issuecomment-568598024>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABA3TULTUJATNZP4UKM6XFTQ2E5DVANCNFSM4FGIQUIA>
.
|
Thanks for the fast reply, i am using the only Port that is on the 3.05 :) |
Interesting, Yeah I have a version 3.03 and have two ports. Your likely
picking up bleeds over on the board if you still see any 2.4ghz, the board
is not shielded particularly well.
What're your plans for the board? and I take it that you're saying its
working now for you?
…On Mon, Dec 23, 2019 at 7:37 PM Manuel ***@***.***> wrote:
Interesting, I had it tuned to different channels with that change. What
port are you using? on the board? You need to use the LNB port if recall,
not the direct. Direct doesn't go through the mixer. The RTL.com
documentation is wrong.
… <#m_-2318316658776269007_>
On Mon, Dec 23, 2019 at 5:42 PM Manuel *@*.***> wrote: revert the mhz to
hz patch, this is where the math breaks, I have it working correctly once i
removed those changes in my fork Just tried your Code @thex1le
<https://github.com/thex1le> https://github.com/thex1le , there is a
missing bracket in line 388, but even after fixing that, the mixer doesen't
seem to work. I used a DC 3.05 and my SDR isn't showing anything on 1.29ghz
when i enter a mixer frequency of 1110mhz on startup of the Chat app. The
master branch shows the Signal allways on 2.4ghz because of the mixer issue
:) — You are receiving this because you were mentioned. Reply to this email
directly, view it on GitHub <#10
<#10>?email_source=notifications&email_token=ABA3TUJMP2H6PYKFWCNUBE3Q2E5DVA5CNFSM4FGIQUIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHSB4CA#issuecomment-568598024>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABA3TULTUJATNZP4UKM6XFTQ2E5DVANCNFSM4FGIQUIA
.
Thanks for the fast reply, i am using the only Port that is on the 3.05 :)
I can see that the Signal at 2.4ghz is gone with your version (or at least
very weak) so it seems to activate the mixer route in some way.
https://othernet.is/products/dreamcatcher-v3-05
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#10?email_source=notifications&email_token=ABA3TUOBTEH6VPEF3NYGHDDQ2FKU7A5CNFSM4FGIQUIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHSF3VA#issuecomment-568614356>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABA3TULGVWEGHD3M5S7W7MDQ2FKU7ANCNFSM4FGIQUIA>
.
|
Just Playing with them around right now, also have a 3.03 listening to the EU Beam right now. I think i will give the 3.03 a try tomorrow on armbian. The master Branch Chat works with the 3.05, but it is stuck at 2.4ghz or whatever i can set the SX1280 Chip to (RX_FREQUENCY variable), what is only +/- 100mhz or so. I used your version (after the bracket fix) on one of my DC 3.05 and wasn't able to find the Signal on my SDR. Maybe i will try tomorrow if the chat works with your version between both DC 3.05s.
|
Yeah ill have to go back and look at the bracket thing, yeah changing
RX-FREQ doesn't actually do anything because the lora chip can only do
2.4ghz. Its the mixer that matters.
SO long as you set the mixer in hz you should be able to find it with your
SDR, that's how I tested it. If you want to submit a patch for the bracket
ill be happy to roll it in. Happy someone else is getting use out of this.
Cheers!
…On Mon, Dec 23, 2019 at 7:58 PM Manuel ***@***.***> wrote:
Just Playing with them around right now, also have a 3.03 listening to the
EU Beam right now. I think i will give the 3.03 a try tomorrow on armbian.
The master Branch Chat works with the 3.05, but it is stuck at 2.4ghz or
whatever i can set the SX1280 Chip to (RX_FREQUENCY variable), what is only
+/- 100mhz or so.
I used your version (after the bracket fix) on one of my DC 3.05 and
wasn't able to find the Signal on my SDR. Maybe i will try tomorrow if the
chat works with your version between both DC 3.05s.
Interesting, Yeah I have a version 3.03 and have two ports. Your likely
picking up bleeds over on the board if you still see any 2.4ghz, the board
is not shielded particularly well. What're your plans for the board? and I
take it that you're saying its working now for you?
… <#m_-822798747997543724_>
On Mon, Dec 23, 2019 at 7:37 PM Manuel *@*.*> wrote: Interesting, I had
it tuned to different channels with that change. What port are you using?
on the board? You need to use the LNB port if recall, not the direct.
Direct doesn't go through the mixer. The RTL.com documentation is wrong. …
<#m_-2318316658776269007_> On Mon, Dec 23, 2019 at 5:42 PM Manuel @.*>
wrote: revert the mhz to hz patch, this is where the math breaks, I have it
working correctly once i removed those changes in my fork Just tried your
Code @thex1le <https://github.com/thex1le> https://github.com/thex1le
https://github.com/thex1le , there is a missing bracket in line 388, but
even after fixing that, the mixer doesen't seem to work. I used a DC 3.05
and my SDR isn't showing anything on 1.29ghz when i enter a mixer frequency
of 1110mhz on startup of the Chat app. The master branch shows the Signal
allways on 2.4ghz because of the mixer issue :) — You are receiving this
because you were mentioned. Reply to this email directly, view it on GitHub
<#10
<#10>
<#10
<#10>>?email_source=notifications&email_token=ABA3TUJMP2H6PYKFWCNUBE3Q2E5DVA5CNFSM4FGIQUIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHSB4CA#issuecomment-568598024>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABA3TULTUJATNZP4UKM6XFTQ2E5DVANCNFSM4FGIQUIA
. Thanks for the fast reply, i am using the only Port that is on the 3.05
:) I can see that the Signal at 2.4ghz is gone with your version (or at
least very weak) so it seems to activate the mixer route in some way.
https://othernet.is/products/dreamcatcher-v3-05 — You are receiving this
because you were mentioned. Reply to this email directly, view it on GitHub
<#10
<#10>?email_source=notifications&email_token=ABA3TUOBTEH6VPEF3NYGHDDQ2FKU7A5CNFSM4FGIQUIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHSF3VA#issuecomment-568614356>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABA3TULGVWEGHD3M5S7W7MDQ2FKU7ANCNFSM4FGIQUIA
.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#10?email_source=notifications&email_token=ABA3TUMZAVECS2RGPID2LMTQ2FNDRA5CNFSM4FGIQUIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHSGO4I#issuecomment-568616817>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABA3TUL5X2RSZFOIZL3KONTQ2FNDRANCNFSM4FGIQUIA>
.
|
If you want i can push my little fix to your repo, just need permission for that :) Or i can send you the file if you wnat, otherwise it really is only a single Bracket in line 388, i think you can fix it by yourself very fast as well. UPDATE: If you fix the Bracket error it seems to work. The Signal after the mixer is just very weak so i didn't see it on my sdr that easily. merry Christmas :P
|
Sure whats your username?
…On Tue, Dec 24, 2019 at 5:47 AM Manuel ***@***.***> wrote:
If you want i can push my little fix to your repo, just need permission
for that :)
Yeah ill have to go back and look at the bracket thing, yeah changing
RX-FREQ doesn't actually do anything because the lora chip can only do
2.4ghz. Its the mixer that matters. SO long as you set the mixer in hz you
should be able to find it with your SDR, that's how I tested it. If you
want to submit a patch for the bracket ill be happy to roll it in. Happy
someone else is getting use out of this. Cheers!
… <#m_6070244469252560281_>
On Mon, Dec 23, 2019 at 7:58 PM Manuel *@*.**> wrote: Just Playing with
them around right now, also have a 3.03 listening to the EU Beam right now.
I think i will give the 3.03 a try tomorrow on armbian. The master Branch
Chat works with the 3.05, but it is stuck at 2.4ghz or whatever i can set
the SX1280 Chip to (RX_FREQUENCY variable), what is only +/- 100mhz or so.
I used your version (after the bracket fix) on one of my DC 3.05 and wasn't
able to find the Signal on my SDR. Maybe i will try tomorrow if the chat
works with your version between both DC 3.05s. Interesting, Yeah I have a
version 3.03 and have two ports. Your likely picking up bleeds over on the
board if you still see any 2.4ghz, the board is not shielded particularly
well. What're your plans for the board? and I take it that you're saying
its working now for you? … <#m_-822798747997543724_> On Mon, Dec 23, 2019
at 7:37 PM Manuel @.> wrote: Interesting, I had it tuned to different
channels with that change. What port are you using? on the board? You need
to use the LNB port if recall, not the direct. Direct doesn't go through
the mixer. The RTL.com documentation is wrong. … <#m_-2318316658776269007_>
On Mon, Dec 23, 2019 at 5:42 PM Manuel @.*> wrote: revert the mhz to hz
patch, this is where the math breaks, I have it working correctly once i
removed those changes in my fork Just tried your Code @thex1le
<https://github.com/thex1le> https://github.com/thex1le
https://github.com/thex1le https://github.com/thex1le , there is a
missing bracket in line 388, but even after fixing that, the mixer doesen't
seem to work. I used a DC 3.05 and my SDR isn't showing anything on 1.29ghz
when i enter a mixer frequency of 1110mhz on startup of the Chat app. The
master branch shows the Signal allways on 2.4ghz because of the mixer issue
:) — You are receiving this because you were mentioned. Reply to this email
directly, view it on GitHub <#10
<#10>
<#10
<#10>>
<#10
<#10>
<#10
<#10>>>?email_source=notifications&email_token=ABA3TUJMP2H6PYKFWCNUBE3Q2E5DVA5CNFSM4FGIQUIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHSB4CA#issuecomment-568598024>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABA3TULTUJATNZP4UKM6XFTQ2E5DVANCNFSM4FGIQUIA
. Thanks for the fast reply, i am using the only Port that is on the 3.05
:) I can see that the Signal at 2.4ghz is gone with your version (or at
least very weak) so it seems to activate the mixer route in some way.
https://othernet.is/products/dreamcatcher-v3-05 — You are receiving this
because you were mentioned. Reply to this email directly, view it on GitHub
<#10
<#10>
<#10
<#10>>?email_source=notifications&email_token=ABA3TUOBTEH6VPEF3NYGHDDQ2FKU7A5CNFSM4FGIQUIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHSF3VA#issuecomment-568614356>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABA3TULGVWEGHD3M5S7W7MDQ2FKU7ANCNFSM4FGIQUIA
. — You are receiving this because you were mentioned. Reply to this email
directly, view it on GitHub <#10
<#10>?email_source=notifications&email_token=ABA3TUMZAVECS2RGPID2LMTQ2FNDRA5CNFSM4FGIQUIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHSGO4I#issuecomment-568616817>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABA3TUL5X2RSZFOIZL3KONTQ2FNDRANCNFSM4FGIQUIA
.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#10?email_source=notifications&email_token=ABA3TUMVZCUCA6WEQWXKBJLQ2HSCVA5CNFSM4FGIQUIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHTADLA#issuecomment-568721836>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABA3TUM6IVICPYIRZESNKR3Q2HSCVANCNFSM4FGIQUIA>
.
|
Username is Tysonpower (https://github.com/Tysonpower) :)
Am 25.12.2019 00:09:32 schrieb thex1le <notifications@github.com>:
Sure whats your username?
On Tue, Dec 24, 2019 at 5:47 AM Manuel ***@***.***> wrote:
If you want i can push my little fix to your repo, just need permission
for that :)
Yeah ill have to go back and look at the bracket thing, yeah changing
RX-FREQ doesn't actually do anything because the lora chip can only do
2.4ghz. Its the mixer that matters. SO long as you set the mixer in hz you
should be able to find it with your SDR, that's how I tested it. If you
want to submit a patch for the bracket ill be happy to roll it in. Happy
someone else is getting use out of this. Cheers!
… <#m_6070244469252560281_>
On Mon, Dec 23, 2019 at 7:58 PM Manuel *@*.**> wrote: Just Playing with
them around right now, also have a 3.03 listening to the EU Beam right now.
I think i will give the 3.03 a try tomorrow on armbian. The master Branch
Chat works with the 3.05, but it is stuck at 2.4ghz or whatever i can set
the SX1280 Chip to (RX_FREQUENCY variable), what is only +/- 100mhz or so.
I used your version (after the bracket fix) on one of my DC 3.05 and wasn't
able to find the Signal on my SDR. Maybe i will try tomorrow if the chat
works with your version between both DC 3.05s. Interesting, Yeah I have a
version 3.03 and have two ports. Your likely picking up bleeds over on the
board if you still see any 2.4ghz, the board is not shielded particularly
well. What're your plans for the board? and I take it that you're saying
its working now for you? … <#m_-822798747997543724_> On Mon, Dec 23, 2019
at 7:37 PM Manuel @.> wrote: Interesting, I had it tuned to different
channels with that change. What port are you using? on the board? You need
to use the LNB port if recall, not the direct. Direct doesn't go through
the mixer. The RTL.com documentation is wrong. … <#m_-2318316658776269007_>
On Mon, Dec 23, 2019 at 5:42 PM Manuel @.*> wrote: revert the mhz to hz
patch, this is where the math breaks, I have it working correctly once i
removed those changes in my fork Just tried your Code @thex1le
<https://github.com/thex1le> https://github.com/thex1le
https://github.com/thex1le https://github.com/thex1le , there is a
missing bracket in line 388, but even after fixing that, the mixer doesen't
seem to work. I used a DC 3.05 and my SDR isn't showing anything on 1.29ghz
when i enter a mixer frequency of 1110mhz on startup of the Chat app. The
master branch shows the Signal allways on 2.4ghz because of the mixer issue
:) — You are receiving this because you were mentioned. Reply to this email
directly, view it on GitHub <#10
<#10>
<#10
<#10>>
<#10
<#10>
<#10
<#10>>>?email_source=notifications&email_token=ABA3TUJMP2H6PYKFWCNUBE3Q2E5DVA5CNFSM4FGIQUIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHSB4CA#issuecomment-568598024>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABA3TULTUJATNZP4UKM6XFTQ2E5DVANCNFSM4FGIQUIA
. Thanks for the fast reply, i am using the only Port that is on the 3.05
:) I can see that the Signal at 2.4ghz is gone with your version (or at
least very weak) so it seems to activate the mixer route in some way.
https://othernet.is/products/dreamcatcher-v3-05 — You are receiving this
because you were mentioned. Reply to this email directly, view it on GitHub
<#10
<#10>
<#10
<#10>>?email_source=notifications&email_token=ABA3TUOBTEH6VPEF3NYGHDDQ2FKU7A5CNFSM4FGIQUIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHSF3VA#issuecomment-568614356>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABA3TULGVWEGHD3M5S7W7MDQ2FKU7ANCNFSM4FGIQUIA
. — You are receiving this because you were mentioned. Reply to this email
directly, view it on GitHub <#10
<#10>?email_source=notifications&email_token=ABA3TUMZAVECS2RGPID2LMTQ2FNDRA5CNFSM4FGIQUIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHSGO4I#issuecomment-568616817>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABA3TUL5X2RSZFOIZL3KONTQ2FNDRANCNFSM4FGIQUIA
.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#10?email_source=notifications&email_token=ABA3TUMVZCUCA6WEQWXKBJLQ2HSCVA5CNFSM4FGIQUIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHTADLA#issuecomment-568721836>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABA3TUM6IVICPYIRZESNKR3Q2HSCVANCNFSM4FGIQUIA>
.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub [#10?email_source=notifications&email_token=ADG3XU4GG7X2WQFVRGULVULQ2KJCZA5CNFSM4FGIQUIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHTVRXQ#issuecomment-568809694], or unsubscribe [https://github.com/notifications/unsubscribe-auth/ADG3XU3MSLTOUHSA7T6CIADQ2KJCZANCNFSM4FGIQUIA].
|
… On Tue, Dec 24, 2019 at 6:15 PM Manuel ***@***.***> wrote:
Username is Tysonpower (https://github.com/Tysonpower) :)
Am 25.12.2019 00:09:32 schrieb thex1le ***@***.***>:
Sure whats your username?
On Tue, Dec 24, 2019 at 5:47 AM Manuel ***@***.***> wrote:
> If you want i can push my little fix to your repo, just need permission
> for that :)
>
> Yeah ill have to go back and look at the bracket thing, yeah changing
> RX-FREQ doesn't actually do anything because the lora chip can only do
> 2.4ghz. Its the mixer that matters. SO long as you set the mixer in hz
you
> should be able to find it with your SDR, that's how I tested it. If you
> want to submit a patch for the bracket ill be happy to roll it in. Happy
> someone else is getting use out of this. Cheers!
> … <#m_6070244469252560281_>
> On Mon, Dec 23, 2019 at 7:58 PM Manuel *@*.**> wrote: Just Playing with
> them around right now, also have a 3.03 listening to the EU Beam right
now.
> I think i will give the 3.03 a try tomorrow on armbian. The master Branch
> Chat works with the 3.05, but it is stuck at 2.4ghz or whatever i can set
> the SX1280 Chip to (RX_FREQUENCY variable), what is only +/- 100mhz or
so.
> I used your version (after the bracket fix) on one of my DC 3.05 and
wasn't
> able to find the Signal on my SDR. Maybe i will try tomorrow if the chat
> works with your version between both DC 3.05s. Interesting, Yeah I have a
> version 3.03 and have two ports. Your likely picking up bleeds over on
the
> board if you still see any 2.4ghz, the board is not shielded particularly
> well. What're your plans for the board? and I take it that you're saying
> its working now for you? … <#m_-822798747997543724_> On Mon, Dec 23, 2019
> at 7:37 PM Manuel @.> wrote: Interesting, I had it tuned to different
> channels with that change. What port are you using? on the board? You
need
> to use the LNB port if recall, not the direct. Direct doesn't go through
> the mixer. The RTL.com documentation is wrong. …
<#m_-2318316658776269007_>
> On Mon, Dec 23, 2019 at 5:42 PM Manuel @.*> wrote: revert the mhz to hz
> patch, this is where the math breaks, I have it working correctly once i
> removed those changes in my fork Just tried your Code @thex1le
> <https://github.com/thex1le> https://github.com/thex1le
> https://github.com/thex1le https://github.com/thex1le , there is a
> missing bracket in line 388, but even after fixing that, the mixer
doesen't
> seem to work. I used a DC 3.05 and my SDR isn't showing anything on
1.29ghz
> when i enter a mixer frequency of 1110mhz on startup of the Chat app. The
> master branch shows the Signal allways on 2.4ghz because of the mixer
issue
> :) — You are receiving this because you were mentioned. Reply to this
email
> directly, view it on GitHub <#10
> <
#10>
> <#10
> <
#10>>
> <#10
> <
#10>
> <#10
> <
#10
>>>?email_source=notifications&email_token=ABA3TUJMP2H6PYKFWCNUBE3Q2E5DVA5CNFSM4FGIQUIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHSB4CA#issuecomment-568598024>,
> or unsubscribe
>
https://github.com/notifications/unsubscribe-auth/ABA3TULTUJATNZP4UKM6XFTQ2E5DVANCNFSM4FGIQUIA
> . Thanks for the fast reply, i am using the only Port that is on the 3.05
> :) I can see that the Signal at 2.4ghz is gone with your version (or at
> least very weak) so it seems to activate the mixer route in some way.
> https://othernet.is/products/dreamcatcher-v3-05 — You are receiving this
> because you were mentioned. Reply to this email directly, view it on
GitHub
> <#10
> <
#10>
> <#10
> <
#10
>>?email_source=notifications&email_token=ABA3TUOBTEH6VPEF3NYGHDDQ2FKU7A5CNFSM4FGIQUIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHSF3VA#issuecomment-568614356>,
> or unsubscribe
>
https://github.com/notifications/unsubscribe-auth/ABA3TULGVWEGHD3M5S7W7MDQ2FKU7ANCNFSM4FGIQUIA
> . — You are receiving this because you were mentioned. Reply to this
email
> directly, view it on GitHub <#10
> <
#10
>?email_source=notifications&email_token=ABA3TUMZAVECS2RGPID2LMTQ2FNDRA5CNFSM4FGIQUIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHSGO4I#issuecomment-568616817>,
> or unsubscribe
>
https://github.com/notifications/unsubscribe-auth/ABA3TUL5X2RSZFOIZL3KONTQ2FNDRANCNFSM4FGIQUIA
> .
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <
#10?email_source=notifications&email_token=ABA3TUMVZCUCA6WEQWXKBJLQ2HSCVA5CNFSM4FGIQUIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHTADLA#issuecomment-568721836
>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/ABA3TUM6IVICPYIRZESNKR3Q2HSCVANCNFSM4FGIQUIA
>
> .
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub [
#10?email_source=notifications&email_token=ADG3XU4GG7X2WQFVRGULVULQ2KJCZA5CNFSM4FGIQUIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHTVRXQ#issuecomment-568809694],
or unsubscribe [
https://github.com/notifications/unsubscribe-auth/ADG3XU3MSLTOUHSA7T6CIADQ2KJCZANCNFSM4FGIQUIA].
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#10?email_source=notifications&email_token=ABA3TUOOIR6DYPFQ4HJQSVLQ2KJYNA5CNFSM4FGIQUIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHTVT3Q#issuecomment-568809966>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABA3TUPLFURC6YQFCTYGQNLQ2KJYNANCNFSM4FGIQUIA>
.
|
Great, just made my commit with the little fix. A bit new to GIT but it worked :)
|
Git is the greatest most frustrating thing that I can't live without. When
in doubt if you screw up your git repo, delete it and pull down a new copy.
…On Tue, Dec 24, 2019 at 7:34 PM Manuel ***@***.***> wrote:
Great, just made my commit with the little fix. A bit new to GIT but it
worked :)
Done, https://github.com/thex1le/Dreamcatcher-Packet-Tester/invitations
… <#m_858395066408188012_>
On Tue, Dec 24, 2019 at 6:15 PM Manuel *@*.*> wrote: Username is
Tysonpower (https://github.com/Tysonpower <https://github.com/Tysonpower>)
:) Am 25.12.2019 00:09:32 schrieb thex1le @.*>: Sure whats your username?
On Tue, Dec 24, 2019 at 5:47 AM Manuel *@*.*> wrote: > If you want i can
push my little fix to your repo, just need permission > for that :) > >
Yeah ill have to go back and look at the bracket thing, yeah changing >
RX-FREQ doesn't actually do anything because the lora chip can only do >
2.4ghz. Its the mixer that matters. SO long as you set the mixer in hz you
> should be able to find it with your SDR, that's how I tested it. If you >
want to submit a patch for the bracket ill be happy to roll it in. Happy >
someone else is getting use out of this. Cheers! > …
<#m_6070244469252560281_> > On Mon, Dec 23, 2019 at 7:58 PM Manuel @.>
wrote: Just Playing with > them around right now, also have a 3.03
listening to the EU Beam right now. > I think i will give the 3.03 a try
tomorrow on armbian. The master Branch > Chat works with the 3.05, but it
is stuck at 2.4ghz or whatever i can set > the SX1280 Chip to (RX_FREQUENCY
variable), what is only +/- 100mhz or so. > I used your version (after the
bracket fix) on one of my DC 3.05 and wasn't > able to find the Signal on
my SDR. Maybe i will try tomorrow if the chat > works with your version
between both DC 3.05s. Interesting, Yeah I have a > version 3.03 and have
two ports. Your likely picking up bleeds over on the > board if you still
see any 2.4ghz, the board is not shielded particularly > well. What're your
plans for the board? and I take it that you're saying > its working now for
you? … <#m_-822798747997543724_> On Mon, Dec 23, 2019 > at 7:37 PM Manuel
@.> wrote: Interesting, I had it tuned to different > channels with that
change. What port are you using? on the board? You need > to use the LNB
port if recall, not the direct. Direct doesn't go through > the mixer. The
RTL.com documentation is wrong. … <#m_-2318316658776269007_> > On Mon, Dec
23, 2019 at 5:42 PM Manuel @.*> wrote: revert the mhz to hz > patch, this
is where the math breaks, I have it working correctly once i > removed
those changes in my fork Just tried your Code @thex1le
<https://github.com/thex1le> > https://github.com/thex1le
https://github.com/thex1le > https://github.com/thex1le
https://github.com/thex1le , there is a > missing bracket in line 388,
but even after fixing that, the mixer doesen't > seem to work. I used a DC
3.05 and my SDR isn't showing anything on 1.29ghz > when i enter a mixer
frequency of 1110mhz on startup of the Chat app. The > master branch shows
the Signal allways on 2.4ghz because of the mixer issue > :) — You are
receiving this because you were mentioned. Reply to this email > directly,
view it on GitHub <#10
<#10>
> < #10
<#10>>
> <#10
<#10>
> < #10
<#10>>>
> <#10
<#10>
> < #10
<#10>>
> <#10
<#10>
> < #10
<#10>
>>>?email_source=notifications&email_token=ABA3TUJMP2H6PYKFWCNUBE3Q2E5DVA5CNFSM4FGIQUIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHSB4CA#issuecomment-568598024>,
> or unsubscribe >
https://github.com/notifications/unsubscribe-auth/ABA3TULTUJATNZP4UKM6XFTQ2E5DVANCNFSM4FGIQUIA
> . Thanks for the fast reply, i am using the only Port that is on the 3.05
> :) I can see that the Signal at 2.4ghz is gone with your version (or at >
least very weak) so it seems to activate the mixer route in some way. >
https://othernet.is/products/dreamcatcher-v3-05 — You are receiving this
> because you were mentioned. Reply to this email directly, view it on
GitHub > <#10
<#10>
> < #10
<#10>>
> <#10
<#10>
> < #10
<#10>
>>?email_source=notifications&email_token=ABA3TUOBTEH6VPEF3NYGHDDQ2FKU7A5CNFSM4FGIQUIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHSF3VA#issuecomment-568614356>,
> or unsubscribe >
https://github.com/notifications/unsubscribe-auth/ABA3TULGVWEGHD3M5S7W7MDQ2FKU7ANCNFSM4FGIQUIA
> . — You are receiving this because you were mentioned. Reply to this
email > directly, view it on GitHub <#10
<#10>
> < #10
<#10>
>?email_source=notifications&email_token=ABA3TUMZAVECS2RGPID2LMTQ2FNDRA5CNFSM4FGIQUIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHSGO4I#issuecomment-568616817>,
> or unsubscribe >
https://github.com/notifications/unsubscribe-auth/ABA3TUL5X2RSZFOIZL3KONTQ2FNDRANCNFSM4FGIQUIA
> . > > — > You are receiving this because you were mentioned. > Reply to
this email directly, view it on GitHub > < #10
<#10>?email_source=notifications&email_token=ABA3TUMVZCUCA6WEQWXKBJLQ2HSCVA5CNFSM4FGIQUIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHTADLA#issuecomment-568721836
>, > or unsubscribe > <
https://github.com/notifications/unsubscribe-auth/ABA3TUM6IVICPYIRZESNKR3Q2HSCVANCNFSM4FGIQUIA
> > . > — You are receiving this because you commented. Reply to this email
directly, view it on GitHub [ #10
<#10>?email_source=notifications&email_token=ADG3XU4GG7X2WQFVRGULVULQ2KJCZA5CNFSM4FGIQUIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHTVRXQ#issuecomment-568809694],
or unsubscribe [
https://github.com/notifications/unsubscribe-auth/ADG3XU3MSLTOUHSA7T6CIADQ2KJCZANCNFSM4FGIQUIA].
— You are receiving this because you were mentioned. Reply to this email
directly, view it on GitHub <#10
<#10>?email_source=notifications&email_token=ABA3TUOOIR6DYPFQ4HJQSVLQ2KJYNA5CNFSM4FGIQUIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHTVT3Q#issuecomment-568809966>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABA3TUPLFURC6YQFCTYGQNLQ2KJYNANCNFSM4FGIQUIA
.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#10?email_source=notifications&email_token=ABA3TUKRC5LQLFRC5J2QRZDQ2KTBPA5CNFSM4FGIQUIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHTWVZI#issuecomment-568814309>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABA3TULTG3MDIQXRTWKSPWDQ2KTBPANCNFSM4FGIQUIA>
.
|
looks like from the spectrum analyzer evaluations of the latest, updated code
only LoRa leakage, no mixed signal, no LO leakage can observed...
The text was updated successfully, but these errors were encountered: