April 2023 - pacsat-dev - mailman.amsat.org

RSSI / Signal generator
by Chris Thompson 29 Apr '23

29 Apr '23

I ran a test that Rich suggested. Specifically I used an HP signal generator to produce test signals of -50dBm to -90dBm. The received RSSI at the AX5043 is within 1 - 2dB. This suggests that the antenna connection, matching circuitry and filter are all working. The signal is getting to the chip as expected. Tuning the signal up/down does not improve things. So the chip does seem to be on the right frequency. I also ran the "test freq" function (after modifying it to work with the AX25 code). It transmits on the receive frequency, and it seems to be correct within a kHz or so. So this leaves us, as expected, with some sort of register setup issue. Given it is worse on 2m than 70cm it is perhaps a bandwidth or frequency acquisition issue. 73 Chris -- Chris E. Thompson chrisethompson(a)gmail.com g0kla(a)arrl.net

1 0

Re: More RSSI
by Chris Thompson 29 Apr '23

29 Apr '23

Ok, I see that. I'm running that routine, so I just need to subtract 255 to get it into dBm. I will do that and then repeat the test that Rich described with a calibrated signal level. To see that it is receiving as expected. 73 Chris On Fri, Apr 28, 2023 at 4:09 PM Burns Fisher (AMSAT) via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Ok, I see. Yes, get_rssi does just what Rich says--it treats the byte as > signed and expands it to 16 bits. It then subtracts 64 to get the correct > RSSI value. But then it adds 255 to ensure that the value is a positive > unsigned value which it can send via telemetry. Then FoxTelem (which can > once again deal with negative numbers) subtracts off the 255 to again get > the value that Rich described. > > The console command "get rssi" also subtracts off the 255 and should give > the same number that FoxTelem would if we were using it. > > 73, > > Burns Fisher, WB1FJ > *AMSAT(R) Engineering -- Flight Software* > > > On Fri, Apr 28, 2023 at 3:58 PM Burns Fisher (AMSAT) <wb1fj(a)fisher.cc> > wrote: > >> Yes, I think get_rssi does some of that and then -255 does the rest, but >> it also involves converting from 8 to 16 bits and back, so I need to think >> about it. >> >> 73, >> >> Burns Fisher, WB1FJ >> *AMSAT(R) Engineering -- Flight Software* >> >> >> On Fri, Apr 28, 2023 at 3:56 PM Rich Gopstein via pacsat-dev < >> pacsat-dev(a)amsat.org> wrote: >> >>> This was from an old email to Burns: >>> >>> >>> I found this on the ONSEMI forums: >>> >>> AX-RadioLAB code sets the RSSIREFERENCE 64 dB (called RSSIOFFSET) higher >>> than the correct value and then subtracts 64 dB when reading out the RSSI >>> value. (And also corrects RSSIABSTHR by 64). This is to prevent wrap around >>> at -128 dBm, since the RSSI register is only 8 bit. >>> >>> So, it sounds like we're seeing the RSSI as 64dB higher than it really >>> is... >>> >>> ----------------------------------------------------------- >>> >>> pacsat-dev mailing list -- pacsat-dev(a)amsat.org >>> View archives of this mailing list at >>> https://mailman.amsat.org/hyperkitty/list/[email protected] >>> To unsubscribe send an email to pacsat-dev-leave(a)amsat.org >>> Manage all of your AMSAT-NA mailing list preferences at >>> https://mailman.amsat.org >>> >> > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at > https://mailman.amsat.org/hyperkitty/list/[email protected] > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org > -- Chris E. Thompson chrisethompson(a)gmail.com g0kla(a)arrl.net

1 0

Re: More RSSI
by Burns Fisher (AMSAT) 28 Apr '23

28 Apr '23

Yes, I think get_rssi does some of that and then -255 does the rest, but it also involves converting from 8 to 16 bits and back, so I need to think about it. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Fri, Apr 28, 2023 at 3:56 PM Rich Gopstein via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > This was from an old email to Burns: > > > I found this on the ONSEMI forums: > > AX-RadioLAB code sets the RSSIREFERENCE 64 dB (called RSSIOFFSET) higher > than the correct value and then subtracts 64 dB when reading out the RSSI > value. (And also corrects RSSIABSTHR by 64). This is to prevent wrap around > at -128 dBm, since the RSSI register is only 8 bit. > > So, it sounds like we're seeing the RSSI as 64dB higher than it really > is... > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at > https://mailman.amsat.org/hyperkitty/list/[email protected] > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org >

1 1

More RSSI
by Rich Gopstein 28 Apr '23

28 Apr '23

This was from an old email to Burns: I found this on the ONSEMI forums: AX-RadioLAB code sets the RSSIREFERENCE 64 dB (called RSSIOFFSET) higher than the correct value and then subtracts 64 dB when reading out the RSSI value. (And also corrects RSSIABSTHR by 64). This is to prevent wrap around at -128 dBm, since the RSSI register is only 8 bit. So, it sounds like we're seeing the RSSI as 64dB higher than it really is...

1 0

Fwd: ax5043 RSSI calibration
by Rich Gopstein 28 Apr '23

28 Apr '23

FYI... ---------- Forwarded message --------- From: Rich Gopstein <rich(a)ourowndomain.com> Date: Sun, Feb 28, 2021, 5:04 PM Subject: Re: ax5043 RSSI calibration To: Burns Fisher (AMSAT) <wb1fj(a)fisher.cc>, Zach Metzinger < zmetzing(a)pobox.com>, Eric Skoog <eric.n.skoog(a)gmail.com> And I just double checked the secondary ax5043 again - and it varied in the -97 to -90 range with a dummy load, but didn't go any lower than that. Note that on my board, I don't have mmcx connectors, only coax soldered to the board with SMA connectors on the other end, so maybe that's the problem? Rich On Sun, Feb 28, 2021 at 4:51 PM Rich Gopstein <rich(a)ourowndomain.com> wrote: > Sorry - you're right - I just checked my notes again, and one of my two > ax5043's did go down to -115 with a dummy load. The other only went down > to -90 or so. > > Rich > > > On Sun, Feb 28, 2021 at 4:50 PM Burns Fisher (AMSAT) <wb1fj(a)fisher.cc> > wrote: > >> Hmm. Odd. With no signal being sent at all, I'm at -114 or so. Do you >> get that kind of value with no signal in the air? >> >> Good to know it is pretty good though. And on the other end, we are >> unlikely to get a signal as strong as -27! >> >> Thanks for checking! >> >> 73, >> >> Burns Fisher, WB1FJ >> *AMSAT(R) Flight Software* >> >> >> On Sun, Feb 28, 2021 at 4:44 PM Rich Gopstein <rich(a)ourowndomain.com> >> wrote: >> >>> Using the new "get rssi" command, I checked the calibration of the RSSI >>> when driven with my HP signal generator tuned to the input frequency. >>> >>> The reported values closely (within 2-3 dBm) matched the generated power >>> between -90 dBm and -30 dBm. -27 dBm was the largest RSSI value reported >>> by the ax5043 even with increasing input power. >>> >>> One of the two ax5043s was able to go down to -97 dBm, the other one >>> only went down to -90 dBm (more or less). >>> >>> Rich >>> >>>

1 0

Re: AX5043 deafness
by Rich Gopstein 28 Apr '23

28 Apr '23

Even though you think the frequency is correct, you might try adjusting the xmit frequency up and down slightly to see if that has an effect. On Fri, Apr 28, 2023, 2:12 PM Chris Thompson via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Yep, good idea Rich. > > In my test setup the RSSI for 70cm is about 180. For 2m it is 200. > Maybe it is too strong and causing distortion? Do we know the valid range? > To test I put in 10dB and then 20dB of attenuation and dropped it to 190 > and then 180 but it is not more reliable. The background noise is > hovering around 150. > > 73 > Chris > > On Fri, Apr 28, 2023 at 12:10 PM Rich Gopstein via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> For fun, you can check the RSSI while receiving on both bands. Might >> tell you something... >> >> On Fri, Apr 28, 2023 at 12:04 PM Jim McCullers via pacsat-dev < >> pacsat-dev(a)amsat.org> wrote: >> >>> Chris, >>> >>> >>> >>> I assume you are referring to packets you are generating locally. >>> >>> I’ve only tested with the Pi boards and noticed no difference with >>> locally generated signals between the 70cm board and the 2-meter board >>> after getting the frequency correct. >>> >>> My 2-meter Pi board appear a bit deaf on signals from the local APRS >>> digipeters. >>> >>> >>> >>> Guess I need to get the LaunchPad set up. >>> >>> >>> >>> I’ll review the schematic on the daughter board but the schematic should >>> be identical to the Pi schematic. >>> >>> >>> >>> Let me explore. >>> >>> >>> >>> 73 >>> >>> >>> >>> Jim >>> >>> >>> >>> Jim, >>> >>> >>> >>> I have the AX5043 working on 145.835. It ranges correctly and receives >>> packets. At least it receives them some of the time. It seems to be quite >>> deaf compared to wje it was working on 436.8, which is my 70cm RX >>> frequency. That receives every packet without error. >>> >>> >>> >>> I had the same issue on 70cms until you told me to tweak the frequency. >>> But with the TXCO it seems to be right on frequency. I ran a test to TX on >>> the RX frequency and it seems to be correct according to my TinySA. >>> >>> >>> >>> thoughts? >>> >>> >>> >>> 73 >>> >>> Chris >>> >>> >>> >>> -- >>> >>> Chris E. Thompson >>> chrisethompson(a)gmail.com >>> g0kla(a)arrl.net >>> >>> ----------------------------------------------------------- >>> >>> pacsat-dev mailing list -- pacsat-dev(a)amsat.org >>> View archives of this mailing list at >>> https://mailman.amsat.org/hyperkitty/list/[email protected] >>> To unsubscribe send an email to pacsat-dev-leave(a)amsat.org >>> Manage all of your AMSAT-NA mailing list preferences at >>> https://mailman.amsat.org >>> >> >> ----------------------------------------------------------- >> >> pacsat-dev mailing list -- pacsat-dev(a)amsat.org >> View archives of this mailing list at >> https://mailman.amsat.org/hyperkitty/list/[email protected] >> To unsubscribe send an email to pacsat-dev-leave(a)amsat.org >> Manage all of your AMSAT-NA mailing list preferences at >> https://mailman.amsat.org >> > > > -- > Chris E. Thompson > chrisethompson(a)gmail.com > g0kla(a)arrl.net > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at > https://mailman.amsat.org/hyperkitty/list/[email protected] > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org >

1 0

Re: AX5043 deafness
by Burns Fisher (AMSAT) 28 Apr '23

28 Apr '23

I'll look when I get back. I could be wrong, but I thought I had done it on Golf. If so, Rich must have told me how. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Fri, Apr 28, 2023 at 2:39 PM Jim McCullers via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Burns, > > > > How do you do the conversion? I was looking at the datasheet last night > and thinking about this issue. > > In Jonathan’s Pi code I believe he prints out the raw register value. > > I believe the datasheet indicates each step in the register is x db or dbm > but no indication that I saw as to where 0dbm resides in the values. > > Research topic for the weekend. > > > > Jim McCullers > > WA4CWI > > > > > > *From:* Chris Thompson via pacsat-dev <pacsat-dev(a)amsat.org> > *Sent:* Friday, April 28, 2023 1:32 PM > *To:* Burns Fisher (AMSAT) <wb1fj(a)fisher.cc> > *Cc:* pacsat-dev(a)amsat.org > *Subject:* [pacsat-dev] Re: AX5043 deafness > > > > These are the raw RSSI values I think. It is the direct value from > the AX5043_RSSI register. The data sheet does say it is in dB, but that > makes little sense to me. > > > > 73 > > Chris > > > > On Fri, Apr 28, 2023 at 2:26 PM Burns Fisher (AMSAT) via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > > I wonder if I have the conversion wrong for RSSI? I'd think it would be > NEGATIVE. As I recall in orbit we wanted the reception to be around > -100dBm. > > > > 73, > > > > Burns Fisher, WB1FJ > > *AMSAT**(R) **Engineering -- Flight Software* > > > > > > On Fri, Apr 28, 2023 at 2:12 PM Chris Thompson via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > > Yep, good idea Rich. > > > > In my test setup the RSSI for 70cm is about 180. For 2m it is 200. > Maybe it is too strong and causing distortion? Do we know the valid range? > > To test I put in 10dB and then 20dB of attenuation and dropped it to 190 > and then 180 but it is not more reliable. The background noise is > hovering around 150. > > > > 73 > > Chris > > > > On Fri, Apr 28, 2023 at 12:10 PM Rich Gopstein via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > > For fun, you can check the RSSI while receiving on both bands. Might tell > you something... > > > > On Fri, Apr 28, 2023 at 12:04 PM Jim McCullers via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > > Chris, > > > > I assume you are referring to packets you are generating locally. > > I’ve only tested with the Pi boards and noticed no difference with locally > generated signals between the 70cm board and the 2-meter board after > getting the frequency correct. > > My 2-meter Pi board appear a bit deaf on signals from the local APRS > digipeters. > > > > Guess I need to get the LaunchPad set up. > > > > I’ll review the schematic on the daughter board but the schematic should > be identical to the Pi schematic. > > > > Let me explore. > > > > 73 > > > > Jim > > > > Jim, > > > > I have the AX5043 working on 145.835. It ranges correctly and receives > packets. At least it receives them some of the time. It seems to be quite > deaf compared to wje it was working on 436.8, which is my 70cm RX > frequency That receives every packet without error. > > > > I had the same issue on 70cms until you told me to tweak the frequency. > But with the TXCO it seems to be right on frequency. I ran a test to TX on > the RX frequency and it seems to be correct according to my TinySA. > > > > thoughts? > > > > 73 > > Chris > > > > -- > > Chris E. Thompson > chrisethompson(a)gmail.com > g0kla(a)arrl.net > > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at > https://mailman.amsat.org/hyperkitty/list/[email protected] > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org > > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at > https://mailman.amsat.org/hyperkitty/list/[email protected] > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org > > > > > -- > > Chris E. Thompson > chrisethompson(a)gmail.com > g0kla(a)arrl.net > > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at > https://mailman.amsat.org/hyperkitty/list/[email protected] > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org > > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at > https://mailman.amsat.org/hyperkitty/list/[email protected] > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org > > > > > -- > > Chris E. Thompson > chrisethompson(a)gmail.com > g0kla(a)arrl.net > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at > https://mailman.amsat.org/hyperkitty/list/[email protected] > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org >

1 0

Re: AX5043 deafness
by Jim McCullers 28 Apr '23

28 Apr '23

Burns, How do you do the conversion? I was looking at the datasheet last night and thinking about this issue. In Jonathan’s Pi code I believe he prints out the raw register value. I believe the datasheet indicates each step in the register is x db or dbm but no indication that I saw as to where 0dbm resides in the values. Research topic for the weekend. Jim McCullers WA4CWI From: Chris Thompson via pacsat-dev <pacsat-dev(a)amsat.org> Sent: Friday, April 28, 2023 1:32 PM To: Burns Fisher (AMSAT) <wb1fj(a)fisher.cc> Cc: pacsat-dev(a)amsat.org Subject: [pacsat-dev] Re: AX5043 deafness These are the raw RSSI values I think. It is the direct value from the AX5043_RSSI register. The data sheet does say it is in dB, but that makes little sense to me. 73 Chris On Fri, Apr 28, 2023 at 2:26 PM Burns Fisher (AMSAT) via pacsat-dev <pacsat-dev(a)amsat.org <mailto:[email protected]> > wrote: I wonder if I have the conversion wrong for RSSI? I'd think it would be NEGATIVE. As I recall in orbit we wanted the reception to be around -100dBm. 73, Burns Fisher, WB1FJ AMSAT(R) Engineering -- Flight Software On Fri, Apr 28, 2023 at 2:12 PM Chris Thompson via pacsat-dev <pacsat-dev(a)amsat.org <mailto:[email protected]> > wrote: Yep, good idea Rich. In my test setup the RSSI for 70cm is about 180. For 2m it is 200. Maybe it is too strong and causing distortion? Do we know the valid range? To test I put in 10dB and then 20dB of attenuation and dropped it to 190 and then 180 but it is not more reliable. The background noise is hovering around 150. 73 Chris On Fri, Apr 28, 2023 at 12:10 PM Rich Gopstein via pacsat-dev <pacsat-dev(a)amsat.org <mailto:[email protected]> > wrote: For fun, you can check the RSSI while receiving on both bands. Might tell you something... On Fri, Apr 28, 2023 at 12:04 PM Jim McCullers via pacsat-dev <pacsat-dev(a)amsat.org <mailto:[email protected]> > wrote: Chris, I assume you are referring to packets you are generating locally. I’ve only tested with the Pi boards and noticed no difference with locally generated signals between the 70cm board and the 2-meter board after getting the frequency correct. My 2-meter Pi board appear a bit deaf on signals from the local APRS digipeters. Guess I need to get the LaunchPad set up. I’ll review the schematic on the daughter board but the schematic should be identical to the Pi schematic. Let me explore. 73 Jim Jim, I have the AX5043 working on 145.835. It ranges correctly and receives packets. At least it receives them some of the time. It seems to be quite deaf compared to wje it was working on 436.8, which is my 70cm RX frequency That receives every packet without error. I had the same issue on 70cms until you told me to tweak the frequency. But with the TXCO it seems to be right on frequency. I ran a test to TX on the RX frequency and it seems to be correct according to my TinySA. thoughts? 73 Chris -- Chris E. Thompson chrisethompson(a)gmail.com <mailto:[email protected]> g0kla(a)arrl.net <mailto:[email protected]> ----------------------------------------------------------- pacsat-dev mailing list -- pacsat-dev(a)amsat.org <mailto:[email protected]> View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected] To unsubscribe send an email to pacsat-dev-leave(a)amsat.org <mailto:[email protected]> Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org ----------------------------------------------------------- pacsat-dev mailing list -- pacsat-dev(a)amsat.org <mailto:[email protected]> View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected] To unsubscribe send an email to pacsat-dev-leave(a)amsat.org <mailto:[email protected]> Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org -- Chris E. Thompson chrisethompson(a)gmail.com <mailto:[email protected]> g0kla(a)arrl.net <mailto:[email protected]> ----------------------------------------------------------- pacsat-dev mailing list -- pacsat-dev(a)amsat.org <mailto:[email protected]> View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected] To unsubscribe send an email to pacsat-dev-leave(a)amsat.org <mailto:[email protected]> Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org ----------------------------------------------------------- pacsat-dev mailing list -- pacsat-dev(a)amsat.org <mailto:[email protected]> View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected] To unsubscribe send an email to pacsat-dev-leave(a)amsat.org <mailto:[email protected]> Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org -- Chris E. Thompson chrisethompson(a)gmail.com <mailto:[email protected]> g0kla(a)arrl.net <mailto:[email protected]>

1 0

Main updated
by Chris Thompson 28 Apr '23

28 Apr '23

Ok, I checked in and merged the code into main that works with the Booster Pack. This is setup to work on 2m and 70cm as expected, but note that I am getting poor reception on 2m. If anyone else can test this it would be great. I can provide detailed instructions if someone wants to try. 73 Chris -- Chris E. Thompson chrisethompson(a)gmail.com g0kla(a)arrl.net

1 0

Re: AX5043 deafness
by Chris Thompson 28 Apr '23

28 Apr '23

These are the raw RSSI values I think. It is the direct value from the AX5043_RSSI register. The data sheet does say it is in dB, but that makes little sense to me. 73 Chris On Fri, Apr 28, 2023 at 2:26 PM Burns Fisher (AMSAT) via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > I wonder if I have the conversion wrong for RSSI? I'd think it would be > NEGATIVE. As I recall in orbit we wanted the reception to be around > -100dBm. > > 73, > > Burns Fisher, WB1FJ > *AMSAT(R) Engineering -- Flight Software* > > > On Fri, Apr 28, 2023 at 2:12 PM Chris Thompson via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> Yep, good idea Rich. >> >> In my test setup the RSSI for 70cm is about 180. For 2m it is 200. >> Maybe it is too strong and causing distortion? Do we know the valid range? >> To test I put in 10dB and then 20dB of attenuation and dropped it to 190 >> and then 180 but it is not more reliable. The background noise is >> hovering around 150. >> >> 73 >> Chris >> >> On Fri, Apr 28, 2023 at 12:10 PM Rich Gopstein via pacsat-dev < >> pacsat-dev(a)amsat.org> wrote: >> >>> For fun, you can check the RSSI while receiving on both bands. Might >>> tell you something... >>> >>> On Fri, Apr 28, 2023 at 12:04 PM Jim McCullers via pacsat-dev < >>> pacsat-dev(a)amsat.org> wrote: >>> >>>> Chris, >>>> >>>> >>>> >>>> I assume you are referring to packets you are generating locally. >>>> >>>> I’ve only tested with the Pi boards and noticed no difference with >>>> locally generated signals between the 70cm board and the 2-meter board >>>> after getting the frequency correct. >>>> >>>> My 2-meter Pi board appear a bit deaf on signals from the local APRS >>>> digipeters. >>>> >>>> >>>> >>>> Guess I need to get the LaunchPad set up. >>>> >>>> >>>> >>>> I’ll review the schematic on the daughter board but the schematic >>>> should be identical to the Pi schematic. >>>> >>>> >>>> >>>> Let me explore. >>>> >>>> >>>> >>>> 73 >>>> >>>> >>>> >>>> Jim >>>> >>>> >>>> >>>> Jim, >>>> >>>> >>>> >>>> I have the AX5043 working on 145.835. It ranges correctly and receives >>>> packets. At least it receives them some of the time. It seems to be quite >>>> deaf compared to wje it was working on 436.8, which is my 70cm RX >>>> frequency. That receives every packet without error. >>>> >>>> >>>> >>>> I had the same issue on 70cms until you told me to tweak the >>>> frequency. But with the TXCO it seems to be right on frequency. I ran a >>>> test to TX on the RX frequency and it seems to be correct according to my >>>> TinySA. >>>> >>>> >>>> >>>> thoughts? >>>> >>>> >>>> >>>> 73 >>>> >>>> Chris >>>> >>>> >>>> >>>> -- >>>> >>>> Chris E. Thompson >>>> chrisethompson(a)gmail.com >>>> g0kla(a)arrl.net >>>> >>>> ----------------------------------------------------------- >>>> >>>> pacsat-dev mailing list -- pacsat-dev(a)amsat.org >>>> View archives of this mailing list at >>>> https://mailman.amsat.org/hyperkitty/list/[email protected] >>>> To unsubscribe send an email to pacsat-dev-leave(a)amsat.org >>>> Manage all of your AMSAT-NA mailing list preferences at >>>> https://mailman.amsat.org >>>> >>> >>> ----------------------------------------------------------- >>> >>> pacsat-dev mailing list -- pacsat-dev(a)amsat.org >>> View archives of this mailing list at >>> https://mailman.amsat.org/hyperkitty/list/[email protected] >>> To unsubscribe send an email to pacsat-dev-leave(a)amsat.org >>> Manage all of your AMSAT-NA mailing list preferences at >>> https://mailman.amsat.org >>> >> >> >> -- >> Chris E. Thompson >> chrisethompson(a)gmail.com >> g0kla(a)arrl.net >> >> ----------------------------------------------------------- >> >> pacsat-dev mailing list -- pacsat-dev(a)amsat.org >> View archives of this mailing list at >> https://mailman.amsat.org/hyperkitty/list/[email protected] >> To unsubscribe send an email to pacsat-dev-leave(a)amsat.org >> Manage all of your AMSAT-NA mailing list preferences at >> https://mailman.amsat.org >> > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at > https://mailman.amsat.org/hyperkitty/list/[email protected] > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org > -- Chris E. Thompson chrisethompson(a)gmail.com g0kla(a)arrl.net

1 0