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/pacsat-dev@amsat.org >>> 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/pacsat-dev@amsat.org > 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/pacsat-dev@amsat.org > 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/pacsat-dev@amsat.org >>> 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/pacsat-dev@amsat.org >> 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/pacsat-dev@amsat.org > 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/pacsat-dev@amsat.org > 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/pacsat-dev@amsat.org > 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/pacsat-dev@amsat.org > 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/pacsat-dev@amsat.org > 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/pacsat-dev@amsat.org > 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:pacsat-dev@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 <mailto:pacsat-dev@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 <mailto:pacsat-dev@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 <mailto:pacsat-dev@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 <mailto:chrisethompson@gmail.com> g0kla(a)arrl.net <mailto:g0kla@arrl.net> ----------------------------------------------------------- pacsat-dev mailing list -- pacsat-dev(a)amsat.org <mailto:pacsat-dev@amsat.org> View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org To unsubscribe send an email to pacsat-dev-leave(a)amsat.org <mailto:pacsat-dev-leave@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 <mailto:pacsat-dev@amsat.org> View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org To unsubscribe send an email to pacsat-dev-leave(a)amsat.org <mailto:pacsat-dev-leave@amsat.org> Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org -- Chris E. Thompson chrisethompson(a)gmail.com <mailto:chrisethompson@gmail.com> g0kla(a)arrl.net <mailto:g0kla@arrl.net> ----------------------------------------------------------- pacsat-dev mailing list -- pacsat-dev(a)amsat.org <mailto:pacsat-dev@amsat.org> View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org To unsubscribe send an email to pacsat-dev-leave(a)amsat.org <mailto:pacsat-dev-leave@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 <mailto:pacsat-dev@amsat.org> View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org To unsubscribe send an email to pacsat-dev-leave(a)amsat.org <mailto:pacsat-dev-leave@amsat.org> Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org -- Chris E. Thompson chrisethompson(a)gmail.com <mailto:chrisethompson@gmail.com> g0kla(a)arrl.net <mailto:g0kla@arrl.net>

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/pacsat-dev@amsat.org >>>> 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/pacsat-dev@amsat.org >>> 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/pacsat-dev@amsat.org >> 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/pacsat-dev@amsat.org > 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: AX5043 deafness
by Burns Fisher (AMSAT) 28 Apr '23

28 Apr '23

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/pacsat-dev@amsat.org >>> 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/pacsat-dev@amsat.org >> 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/pacsat-dev@amsat.org > 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 Chris Thompson 28 Apr '23

28 Apr '23

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/pacsat-dev@amsat.org >> 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/pacsat-dev@amsat.org > 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: AX5043 deafness
by Rich Gopstein 28 Apr '23

28 Apr '23

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/pacsat-dev@amsat.org > 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

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:chrisethompson@gmail.com> g0kla(a)arrl.net <mailto:g0kla@arrl.net>

1 0

AX5043 deafness
by Chris Thompson 28 Apr '23

28 Apr '23

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

1 0

Interrupts on the PACSAT software
by Burns Fisher (AMSAT) 28 Apr '23

28 Apr '23

Chris asked me about adding an interrupt in the PACSAT software. I answered him, (the answer is the same for PACSAT and Golf) but then realized that this is probably not well documented anywhere. So for now, I cut and pasted the email to him and put it in a document in PacSatDocs/refernce (since it is originally a Golf and even Fox thing, I'll put the source there eventually). This is not an emergency for you to read unless you are adding GPIOs or interrupts. It sounds complex, but it is sort of a reasonably simple abstraction of GPIOs and interrupt that works on both the LIHU and the RT-IHU. The complexity comes because the two processors not only interrupt stuff that is quite different from each other, but not really the same as the abstraction itself! 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*

1 0

Re: Inductor
by Jim McCullers 28 Apr '23

28 Apr '23

Thanks Chris. I don’t have any 91s here in any size and will get an order on the way. I need an extra header as well to replace one that didn’t go well. I’ll mail Burns one or two with plenty of tape so that they won’t get lost in the envelope. That will delay the shipment of the final board but good catch. Thanks. My Jonathan board ranged well with a 100nh and I forgot the very early discussion on the 91nh. 73, Jim McCullers WA4CWI Jim, I changed the inductor to 91nH and now it ranges from 137MHz to 151MHz. Seems good. I agree from your other email that the exact value will be dependent on the layout of the final board and stray inductance etc. BTW, I didn't have the 91nH in the right size (only 82 and 100). So I had to squish in the next size up. But that seems to work. 73 Chris -- Chris E. Thompson chrisethompson(a)gmail.com <mailto:chrisethompson@gmail.com> g0kla(a)arrl.net <mailto:g0kla@arrl.net>

1 0

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

28 Apr '23

Speaking of "the next size up", Rich, in testing with the "Jonathan board" actually hand-wound an inductor with something like #22 wire around a pencil. I tried to do that and solder it on, but had no luck. Even that wire is huge compared to the pads :-) 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Fri, Apr 28, 2023 at 9:26 AM Chris Thompson via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Jim, > > I changed the inductor to 91nH and now it ranges from 137MHz to 151MHz. > Seems good. I agree from your other email that the exact value will be > dependent on the layout of the final board and stray inductance etc. > > BTW, I didn't have the 91nH in the right size (only 82 and 100). So I had > to squish in the next size up. But that seems to work. > > 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/pacsat-dev@amsat.org > 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

Inductor
by Chris Thompson 28 Apr '23

28 Apr '23

Jim, I changed the inductor to 91nH and now it ranges from 137MHz to 151MHz. Seems good. I agree from your other email that the exact value will be dependent on the layout of the final board and stray inductance etc. BTW, I didn't have the 91nH in the right size (only 82 and 100). So I had to squish in the next size up. But that seems to work. 73 Chris -- Chris E. Thompson chrisethompson(a)gmail.com g0kla(a)arrl.net

1 0

Re: Serial line on pacsat
by Corey Minyard 27 Apr '23

27 Apr '23

On Fri, Apr 28, 2023 at 01:29:19AM +0000, Burns Fisher (AMSAT) via pacsat-dev wrote: > 1) The pins to use on the launchpad are j2 pin 3 (RX) and 4 (Tx). Nearby, > J3 pin 2 is ground. Note that each row is a different "J" number on the > board, and the count 1,2,3 etc from the USB connector end. Jim numbered > them on his schematic somewhat more sensibly, but they don't match the > board. Looking at the launchpad schematic, are you sure that's not J3? -corey

2 3

Serial line on pacsat
by Burns Fisher (AMSAT) 27 Apr '23

27 Apr '23

1) The pins to use on the launchpad are j2 pin 3 (RX) and 4 (Tx). Nearby, J3 pin 2 is ground. Note that each row is a different "J" number on the board, and the count 1,2,3 etc from the USB connector end. Jim numbered them on his schematic somewhat more sensibly, but they don't match the board. 2) This is not using the N2HET. It is using a regular SCI UART. 3) There is a lot of code that can be removed to reduce confusion, and someday I'll do that. The N2HET is not used at all. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*

1 0

Re: AX5043
by Rich Gopstein 27 Apr '23

27 Apr '23

Just be aware that the Single-Ended pin is XMIT only. Only the differential pins can do both receive and xmit. Rich On Thu, Apr 27, 2023 at 6:26 PM Burns Fisher (AMSAT) via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Just FYI (and Zach may have comments) I don't know about differential > first not, but the fact that the 5043 and switch between them means that > the single ended output can be optimized for one band while the > differential can be optimized for another band. That's how one RT-IHU > processor can do either Rx or Tx (but not simultaneously) on two different > bands with the same 5043. > > 73, > > Burns Fisher, WB1FJ > *AMSAT(R) Engineering -- Flight Software* > > > On Thu, Apr 27, 2023 at 10:14 AM Jim McCullers via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> The bandpass filter and LNA would proceed this circuit. >> Most LNAs I'm familiar with are single ended output. >> Differential input is a bit of an oddity for an RF interface. I'm certain >> someone had a reason. >> >> In our instance we will have a bandpass filter followed by an LNA followed >> by a 1:4 splitter for the four receivers. >> Each receiver will require some form of single end to differential >> converter. >> >> 73, >> >> Jim McCullers >> WA4CWI >> >> >> >> On Thu, Apr 27, 2023 at 03:14:21AM +0000, Jim McCullers via pacsat-dev >> wrote: >> > Attached is a document that I prepared to describe work I've done with >> > AX5043 to create a receiver with a reduced component count. >> > >> > I'll post it to github later. >> >> Just curious, I'm not an expert on RF, but where does the LNA fit in here? >> It seems like you could do the conversion from single-ended to >> differential >> using an LNA if you were already using one. >> >> I've only played with single-ended designs, so this is something >> completely >> different for me. >> >> -corey >> >> >> ----------------------------------------------------------- >> >> pacsat-dev mailing list -- pacsat-dev(a)amsat.org >> View archives of this mailing list at >> https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org >> 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/pacsat-dev@amsat.org > 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
by Burns Fisher (AMSAT) 27 Apr '23

27 Apr '23

Just FYI (and Zach may have comments) I don't know about differential first not, but the fact that the 5043 and switch between them means that the single ended output can be optimized for one band while the differential can be optimized for another band. That's how one RT-IHU processor can do either Rx or Tx (but not simultaneously) on two different bands with the same 5043. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Thu, Apr 27, 2023 at 10:14 AM Jim McCullers via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > The bandpass filter and LNA would proceed this circuit. > Most LNAs I'm familiar with are single ended output. > Differential input is a bit of an oddity for an RF interface. I'm certain > someone had a reason. > > In our instance we will have a bandpass filter followed by an LNA followed > by a 1:4 splitter for the four receivers. > Each receiver will require some form of single end to differential > converter. > > 73, > > Jim McCullers > WA4CWI > > > > On Thu, Apr 27, 2023 at 03:14:21AM +0000, Jim McCullers via pacsat-dev > wrote: > > Attached is a document that I prepared to describe work I've done with > > AX5043 to create a receiver with a reduced component count. > > > > I'll post it to github later. > > Just curious, I'm not an expert on RF, but where does the LNA fit in here? > It seems like you could do the conversion from single-ended to differential > using an LNA if you were already using one. > > I've only played with single-ended designs, so this is something completely > different for me. > > -corey > > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at > https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org > 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

Pacsat dev mtg 4/27/2023
by Bill 27 Apr '23

27 Apr '23

Pacsat dev mtg 4/27/2023 Thu, Apr 27, 2023 7:00 PM - 9:00 PM (CDT) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/797343613 You can also dial in using your phone. (For supported devices, tap a one-touch number below to join instantly.) United States: +1 (408) 650-3123 - One-touch: tel:+14086503123,,797343613# Access Code: 797-343-613 Join from a video-conferencing room or system. Dial in or type: 67.217.95.2 or inroomlink.goto.com Meeting ID: 797 343 613 Or dial directly: 797343613(a)67.217.95.2 or 67.217.95.2##797343613 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0

Re: AX5043
by Corey Minyard 27 Apr '23

27 Apr '23

On Thu, Apr 27, 2023 at 03:14:21AM +0000, Jim McCullers via pacsat-dev wrote: > Attached is a document that I prepared to describe work I've done with > AX5043 to create a receiver with a reduced component count. > > I'll post it to github later. Just curious, I'm not an expert on RF, but where does the LNA fit in here? It seems like you could do the conversion from single-ended to differential using an LNA if you were already using one. I've only played with single-ended designs, so this is something completely different for me. -corey

2 1

Re: AX5043
by Bob Stricklin 27 Apr '23

27 Apr '23

This looks good Jim. Nice job collecting the data and putting it all together. Bob On Apr 26, 2023, at 10:14 PM, Jim McCullers via pacsat-dev <pacsat-dev(a)amsat.org<mailto:pacsat-dev@amsat.org>> wrote: Attached is a document that I prepared to describe work I’ve done with AX5043 to create a receiver with a reduced component count. I’ll post it to github later. Jim McCullers WA4CWI <AX5043 Receiver Impedence Matching.pdf> ----------------------------------------------------------- pacsat-dev mailing list -- pacsat-dev(a)amsat.org<mailto:pacsat-dev@amsat.org> View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org To unsubscribe send an email to pacsat-dev-leave(a)amsat.org<mailto:pacsat-dev-leave@amsat.org> Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org<https://mailman.amsat.org/>

1 0

Re: AX5043
by Jonathan Brandenburg 26 Apr '23

26 Apr '23

If you're willing, this looks like a fantastic presentation for the AMSAT Symposium! (often around the 3rd weekend of October). I'm going to study if more this evening! Jonathan On 4/26/23 22:14, Jim McCullers via pacsat-dev wrote: > > Attached is a document that I prepared to describe work I’ve done with > AX5043 to create a receiver with a reduced component count. > > I’ll post it to github later. > > Jim McCullers > > WA4CWI > > > ----------------------------------------------------------- > > pacsat-dev mailing list --pacsat-dev(a)amsat.org > View archives of this mailing list athttps://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org > To unsubscribe send an email topacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences athttps://mailman.amsat.org -- Jonathan Brandenburg Radio Amateur Satellite Corporation 1-214-213-1066

1 0

AX5043
by Jim McCullers 26 Apr '23

26 Apr '23

Attached is a document that I prepared to describe work I've done with AX5043 to create a receiver with a reduced component count. I'll post it to github later. Jim McCullers WA4CWI

1 0

Re: Serial port on Launchpad?
by Burns Fisher (AMSAT) 22 Apr '23

22 Apr '23

Yes Jim’s board has use some on all 4 of those inner groups of pins. New launchpads have headers on 2 of those sets On Sat, Apr 22, 2023 at 8:20 PM Corey Minyard via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > >Do you have one of Jim’s cards? If so the serial line is a 3 pin header. > >If not I don’t remember the pins on the Launchpad. I can dig it up > tomorrow > >if no one has it tonight. It’s 38k4 btw > > I do not have one yet, I think one is coming soon. I'll still need to > install a header on the launchpad to hook it up, right? > > -corey > > >On Sat, Apr 22, 2023 at 7:53 PM Corey Minyard via pacsat-dev < > >pacsat-dev(a)amsat.org> wrote: > > >> I have the current Pacsat software loaded and running, but how do I hook > >> the serial port to the board. The "normal" serial port on the USB > >> interface doesn't seem to work, and IIRC the serial port used by the > >> Pacsat software goes through some other interface. How do you hook it > >> up? > > On Sat, Apr 22, 2023 at 6:52 PM Corey Minyard <minyard(a)acm.org> wrote: > > > > I have the current Pacsat software loaded and running, but how do I hook > > the serial port to the board. The "normal" serial port on the USB > > interface doesn't seem to work, and IIRC the serial port used by the > > Pacsat software goes through some other interface. How do you hook it > > up? > > > > Thanks, > > > > -corey > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at > https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org > 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 > -- 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*

1 0

Serial port on Launchpad?
by Corey Minyard 22 Apr '23

22 Apr '23

I have the current Pacsat software loaded and running, but how do I hook the serial port to the board. The "normal" serial port on the USB interface doesn't seem to work, and IIRC the serial port used by the Pacsat software goes through some other interface. How do you hook it up? Thanks, -corey

1 1

Re: Serial port on Launchpad?
by Burns Fisher (AMSAT) 22 Apr '23

22 Apr '23

Do you have one of Jim’s cards? If so the serial line is a 3 pin header. If not I don’t remember the pins on the Launchpad. I can dig it up tomorrow if no one has it tonight. It’s 38k4 btw On Sat, Apr 22, 2023 at 7:53 PM Corey Minyard via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > I have the current Pacsat software loaded and running, but how do I hook > the serial port to the board. The "normal" serial port on the USB > interface doesn't seem to work, and IIRC the serial port used by the > Pacsat software goes through some other interface. How do you hook it > up? > > Thanks, > > -corey > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at > https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org > 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 > -- 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*

1 0

Re: Ok, auto-sizing is merged to main
by Chris Thompson 22 Apr '23

22 Apr '23

Great to hear. I ifdef'ed out the MRAM code. We can completely remove it in the next edit. I just left it there temporarily in case I had trouble with the file system. But it seems to work really well so all that code is no longer needed. 73 Chris On Sat, Apr 22, 2023, 17:06 Burns Fisher (AMSAT) via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Chris, I removed your change for the address size since it should no > longer be needed. I also left in the change that someone made to ifdef out > "NumberOfFiles and MRAMFiles in the configuration partition of the MRAM > (that leaves a lot more space!) > > 73, > > Burns Fisher, WB1FJ > *AMSAT(R) Engineering -- Flight Software* > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at > https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org > 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

Ok, auto-sizing is merged to main
by Burns Fisher (AMSAT) 22 Apr '23

22 Apr '23

Chris, I removed your change for the address size since it should no longer be needed. I also left in the change that someone made to ifdef out "NumberOfFiles and MRAMFiles in the configuration partition of the MRAM (that leaves a lot more space!) 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*

1 0

Updates to software for MRAM
by Burns Fisher (AMSAT) 22 Apr '23

22 Apr '23

Hi, I've spent a couple days trying to figure out how to determine automatically whether the MRAM needs an address size of 2 or 3. I think I have finally done it, although I am not very happy. This is really only when we have multiple MRAM sizes flying around developers. The size should be coded permanently for flight. I've also started using the MRAM config data version number. This should be changed if you change anything in the config storage. That will force users to re-init the MRAM. Believe me, before I put this into Fox I spent ages trying to figure out what was wrong when a new software release was placed on an IHU that had been using an older version. I've also updated the version number for the software. I think it is important to do this. It was 0.0a. I've changed it to 0.1a. The first number refers to the satellite it is being built for (0 is nothing special yet), the second number is a somewhat major change, the letter is a minor change. All this code is currently in my branch: BFLaunchPadBoard. I'll do more testing and then move it to 'main'. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*

1 0

Serial port on Launchpad?
by Corey Minyard 21 Apr '23

21 Apr '23

I have the current Pacsat software loaded and running, but how do I hook the serial port to the board. The "normal" serial port on the USB interface doesn't seem to work, and IIRC the serial port used by the Pacsat software goes through some other interface. How do you hook it up? Thanks, -corey

1 0

Pacsat dev mtg 4/20/2023
by Bill 20 Apr '23

20 Apr '23

Pacsat dev mtg 4/20/2023 Thu, Apr 20, 2023 7:00 PM - 9:00 PM (CDT) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/294997261 You can also dial in using your phone. (For supported devices, tap a one-touch number below to join instantly.) United States: +1 (224) 501-3412 - One-touch: tel:+12245013412,,294997261# Access Code: 294-997-261 Join from a video-conferencing room or system. Dial in or type: 67.217.95.2 or inroomlink.goto.com Meeting ID: 294 997 261 Or dial directly: 294997261(a)67.217.95.2 or 67.217.95.2##294997261 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0

Re: My status
by Jim McCullers 20 Apr '23

20 Apr '23

Enjoy the game and thanks for everything. Green wire clashes with the OSH-Park purple. Now I see the need for white! Since you will not be at the meeting tonight, do we need larger MRAM’s, at least on some of the boards. Next series up is about $12 per chip then it goes to $26 for the largest. We can discuss later. I chose this size due to the overall cost on a 1st gen test board for everyone. 73, Jim McCullers WA4CWI I may not me on the call tonight. Going to a Red Sox game. As Chris and Jim will report I got did a couple white wires (yes really white!) and then got the software fixed up to use smaller MRAMs so that now works great! The board is a huge improvement !! -- 73, Burns Fisher, WB1FJ AMSAT(R) Engineering -- Flight Software

1 0

My status
by Burns Fisher (AMSAT) 20 Apr '23

20 Apr '23

I may not me on the call tonight. Going to a Red Sox game. As Chris and Jim will report I got did a couple white wires (yes really white!) and then got the software fixed up to use smaller MRAMs so that now works great! The board is a huge improvement !! -- 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*

1 0

Re: Task names
by Chris Thompson 19 Apr '23

19 Apr '23

Ok, I will take a stab at this and see if I can come up with a list for tasks and for the notifications. 73 Chris On Wed, Apr 19, 2023 at 2:55 PM Burns Fisher (AMSAT) via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > No, they are not the same. The WD has an enum value for each task that is > monitored by the watchdog (essentially all of them). The destination task > list only has the tasks that we send messages to via the message facility. > This typically allows one task or an interrupt to start up another task. > But not all tasks need it. > 73, > > Burns Fisher, WB1FJ > *AMSAT(R) Engineering -- Flight Software* > > > On Wed, Apr 19, 2023 at 2:25 PM Chris Thompson via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> Also note there is a second enum for InterTask notifications, which >> currently has this: >> >> typedef enum { >> ToNone=-1, >> ToDownlinkControl=0, >> ToCommand, >> ToRxTask, >> ToTxTask, >> ToTelemetry, >> // New message destinations go above here >> ToCAN, >> ToCoordinate, >> NumberOfDestinations >> } DestinationTask; >> >> Should this contain the same list as the WD Reports? >> >> 73 >> Chris >> >> On Wed, Apr 19, 2023 at 2:19 PM Chris Thompson via pacsat-dev < >> pacsat-dev(a)amsat.org> wrote: >> >>> This is probably a question just for Burns but I will copy to the list >>> so it is logged for posterity. >>> >>> We need to update the task names. From the architecture design I have >>> the following: >>> RxTask >>> TxTask >>> Ax25Task >>> UplinkTask >>> PbTask >>> CommandTask >>> ConsoleTask >>> TelemCollectionTask >>> >>> In the code today we define the names here, I think: >>> typedef enum { >>> CurrentTaskWD=0, >>> CANSupportWD, >>> TelemetryWD, >>> ControlWD, >>> RadioWD, >>> CommandWD, >>> IdleWD, // Note used in RT >>> ExperimentWD, >>> CoordinateWD, >>> /* Add any new tasks to watch in here. Maximum number of tasks is >>> 9. */ >>> /* The nine limit is the number of bits available in the downlink */ >>> LastWD, >>> InterruptThd = LastWD, >>> ConsoleTsk >>> }WdReporters_t; >>> >>> I have listed 8 tasks. We probably want the Experiment to be the 9th. >>> But what about idle, coordinate, Interrupt, CAN? How do we fit it into 9? >>> Or should we just assume 4 bits and have 16? >>> >>> 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/pacsat-dev@amsat.org >>> 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/pacsat-dev@amsat.org >> 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/pacsat-dev@amsat.org > 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: Task names
by Burns Fisher (AMSAT) 19 Apr '23

19 Apr '23

No, they are not the same. The WD has an enum value for each task that is monitored by the watchdog (essentially all of them). The destination task list only has the tasks that we send messages to via the message facility. This typically allows one task or an interrupt to start up another task. But not all tasks need it. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Wed, Apr 19, 2023 at 2:25 PM Chris Thompson via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Also note there is a second enum for InterTask notifications, which > currently has this: > > typedef enum { > ToNone=-1, > ToDownlinkControl=0, > ToCommand, > ToRxTask, > ToTxTask, > ToTelemetry, > // New message destinations go above here > ToCAN, > ToCoordinate, > NumberOfDestinations > } DestinationTask; > > Should this contain the same list as the WD Reports? > > 73 > Chris > > On Wed, Apr 19, 2023 at 2:19 PM Chris Thompson via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> This is probably a question just for Burns but I will copy to the list so >> it is logged for posterity. >> >> We need to update the task names. From the architecture design I have >> the following: >> RxTask >> TxTask >> Ax25Task >> UplinkTask >> PbTask >> CommandTask >> ConsoleTask >> TelemCollectionTask >> >> In the code today we define the names here, I think: >> typedef enum { >> CurrentTaskWD=0, >> CANSupportWD, >> TelemetryWD, >> ControlWD, >> RadioWD, >> CommandWD, >> IdleWD, // Note used in RT >> ExperimentWD, >> CoordinateWD, >> /* Add any new tasks to watch in here. Maximum number of tasks is 9. >> */ >> /* The nine limit is the number of bits available in the downlink */ >> LastWD, >> InterruptThd = LastWD, >> ConsoleTsk >> }WdReporters_t; >> >> I have listed 8 tasks. We probably want the Experiment to be the 9th. >> But what about idle, coordinate, Interrupt, CAN? How do we fit it into 9? >> Or should we just assume 4 bits and have 16? >> >> 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/pacsat-dev@amsat.org >> 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/pacsat-dev@amsat.org > 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: Task names
by Burns Fisher (AMSAT) 19 Apr '23

19 Apr '23

See my thoughts below: 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Wed, Apr 19, 2023 at 2:19 PM Chris Thompson via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > This is probably a question just for Burns but I will copy to the list so > it is logged for posterity. > > We need to update the task names. From the architecture design I have the > following: > RxTask > TxTask > Ax25Task > UplinkTask > PbTask > CommandTask > ConsoleTask > TelemCollectionTask > > In the code today we define the names here, I think: > typedef enum { > CurrentTaskWD=0, > CANSupportWD, > Not required. We are not using CAN in pacsat > > TelemetryWD, > Note: This task COLLECTS the telemetry every n seconds (4 in Fox and Golf I think) > ControlWD, > This may not be needed. In Fox and Golf it is the task that formats and downlinks (via Radio task) the telemetry. If the telemetry task just writes the telemetry into a file, then no one needs to format it differently. OTOH, if there are different modes etc like Golf and Fox, we might need something. RadioWD, > Is this going to be the same as Rx and Tx? Maybe not needed. > CommandWD, > This may still be needed. On Fox/Golf it is send command data to decode by the Radio task. Probably something like that still required? > IdleWD, // Note used in RT > I bet this is supposed to be "NOT" rather than "NOTE". But I'd have to check. FreeRTOS DOES have an idle task. In Fox, the idle task just whacks away at the watchdog so if there is no idle time, we reboot. On RT, we may use it to check memory, but I don't know why it does not need to pay attention to the WD. > ExperimentWD, > I'm not sure we need this. Pacsat IS a payload. CoordinateWD, > Not required. This is only for Golf where there are multiple processors. Unless we need something similar to coordinate the host and the pacsat payload. > /* Add any new tasks to watch in here. Maximum number of tasks is 9. > */ > /* The nine limit is the number of bits available in the downlink */ > LastWD, > InterruptThd = LastWD, > ConsoleTsk > }WdReporters_t; > > I have listed 8 tasks. We probably want the Experiment to be the 9th. > But what about idle, coordinate, Interrupt, CAN? How do we fit it into 9? > Or should we just assume 4 bits and have 16? > Worth a double check. THis comment (written by me no doubt) seems overly simplistic. But note that this is a bitmask, not a number. The bitmask shows which tasks have and have not kicked the watchdog. So to have 16, we need 16 bits. > > 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/pacsat-dev@amsat.org > 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: Task names
by Chris Thompson 19 Apr '23

19 Apr '23

Also note there is a second enum for InterTask notifications, which currently has this: typedef enum { ToNone=-1, ToDownlinkControl=0, ToCommand, ToRxTask, ToTxTask, ToTelemetry, // New message destinations go above here ToCAN, ToCoordinate, NumberOfDestinations } DestinationTask; Should this contain the same list as the WD Reports? 73 Chris On Wed, Apr 19, 2023 at 2:19 PM Chris Thompson via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > This is probably a question just for Burns but I will copy to the list so > it is logged for posterity. > > We need to update the task names. From the architecture design I have the > following: > RxTask > TxTask > Ax25Task > UplinkTask > PbTask > CommandTask > ConsoleTask > TelemCollectionTask > > In the code today we define the names here, I think: > typedef enum { > CurrentTaskWD=0, > CANSupportWD, > TelemetryWD, > ControlWD, > RadioWD, > CommandWD, > IdleWD, // Note used in RT > ExperimentWD, > CoordinateWD, > /* Add any new tasks to watch in here. Maximum number of tasks is 9. > */ > /* The nine limit is the number of bits available in the downlink */ > LastWD, > InterruptThd = LastWD, > ConsoleTsk > }WdReporters_t; > > I have listed 8 tasks. We probably want the Experiment to be the 9th. > But what about idle, coordinate, Interrupt, CAN? How do we fit it into 9? > Or should we just assume 4 bits and have 16? > > 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/pacsat-dev@amsat.org > 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

Task names
by Chris Thompson 19 Apr '23

19 Apr '23

This is probably a question just for Burns but I will copy to the list so it is logged for posterity. We need to update the task names. From the architecture design I have the following: RxTask TxTask Ax25Task UplinkTask PbTask CommandTask ConsoleTask TelemCollectionTask In the code today we define the names here, I think: typedef enum { CurrentTaskWD=0, CANSupportWD, TelemetryWD, ControlWD, RadioWD, CommandWD, IdleWD, // Note used in RT ExperimentWD, CoordinateWD, /* Add any new tasks to watch in here. Maximum number of tasks is 9. */ /* The nine limit is the number of bits available in the downlink */ LastWD, InterruptThd = LastWD, ConsoleTsk }WdReporters_t; I have listed 8 tasks. We probably want the Experiment to be the 9th. But what about idle, coordinate, Interrupt, CAN? How do we fit it into 9? Or should we just assume 4 bits and have 16? 73 Chris -- Chris E. Thompson chrisethompson(a)gmail.com g0kla(a)arrl.net

1 0

Main branch updated
by Chris Thompson 19 Apr '23

19 Apr '23

Burns made some changes to be compatible with Jim's new boards and I finished refactoring the PACSAT code to use the file system. That is all merged back into main now and pushed to the repository. 73 Chris -- Chris E. Thompson chrisethompson(a)gmail.com g0kla(a)arrl.net

1 0

Re: Filesystem code
by Corey Minyard 15 Apr '23

15 Apr '23

I wigged out on this. I can pick it up in Addison, if you like, or you can mail it to me. Whichever is easier for you. Address is: 7406 Wheatfield Rd, Garland, TX 75044 If I come out there, I have an appointment I need to make in Addison, what's a good day/time for you? -corey On Fri, Apr 07, 2023 at 06:21:41PM +0000, Jonathan Brandenburg via pacsat-dev wrote: > I have confirmed I have it... Now, how to best get it to Corey... I can ship > it from Addison post office, I can get it to Bill soon (if Corey is going to > see Bill at a club meeting or something), or Corey can pick it up in > Addison. > Thoughts? > Jonathan > > On 4/7/2023 11:41 AM, Burns Fisher (AMSAT) via pacsat-dev wrote: > > Jonathan, did I send you the extra Launchpad that I ended up with? In > > any case, do you want to give one to Corey? Corey, you may have to > > solder on some .1" header pins for Jim's board to have all the required > > connections. I know the headers are DNP around the outside where they > > are not used, but I'm not sure that all the inside ones are there > > either. > > > > > > > > 73, > > > > Burns Fisher, WB1FJ > > /AMSAT(R) Engineering -- Flight Software/ > > > > > > On Fri, Apr 7, 2023 at 12:30 PM Corey Minyard via pacsat-dev > > <pacsat-dev(a)amsat.org> wrote: > > > > I have the filesystem code mostly ready. I changed the configuration > > to use 256 byte block. It's available in the filesystem branch. > > > > So I will need a launchpad and a board with MRAM. My address is: > > > > 7406 Wheatfield Rd, Garland, TX 75044 > > > > Chris, you can test it if you like, too. I haven't written any tests > > for anything yet, that needs to be added. > > > > There is code to automatically mount the filesystem on startup and > > format the filesystem if it detects corruption. > > > > There are three new console commands: mount fs, unmount fs, and > > format fs. > > > > The commands are the normal POSIX commands with "red_" prefixed, > > red_open(), red_close(), read_read(), etc. > > > > I need to write a README about how this is all set up. > > > > -corey > > > > ----------------------------------------------------------- > > > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > > View archives of this mailing list at > > https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org > > 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 athttps://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org > > To unsubscribe send an email topacsat-dev-leave(a)amsat.org > > Manage all of your AMSAT-NA mailing list preferences athttps://mailman.amsat.org > > > -- > Jonathan Brandenburg, KF5IDY > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org > 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: FYI Launchpad
by Jim McCullers 15 Apr '23

15 Apr '23

I have headers that will ship with the boards, exclusive of Burns and Chris. My bad. Obviously a ‘feature’ of the newer LaunchPad boards. Jim McCullers WA4CWI I expect to get Jim's prototype board that plugs into a LaunchPad today, so I wanted to get everything ready. I did not want to disconnect all my rat's nest of jumper wires and breadboards that I was initially using to check out the pins for Jim, but luckily I have another new LaunchPad. Here is the odd thing (which I think Chris has also mentioned). While the one that I was initially using clearly had headers factory-soldered for connectors J6-J9, they are DNF for the new LaunchPad that I have. Thus I soldered in headers. (I only hope they are sufficiently straight to fit Jim's board when it arrives!). If the time comes when anyone needs to do this, I have a whole box full of headers that can easily be broken to the right length. 73, Burns Fisher, WB1FJ AMSAT(R) Engineering -- Flight Software

1 0

FYI Launchpad
by Burns Fisher (AMSAT) 15 Apr '23

15 Apr '23

I expect to get Jim's prototype board that plugs into a LaunchPad today, so I wanted to get everything ready. I did not want to disconnect all my rat's nest of jumper wires and breadboards that I was initially using to check out the pins for Jim, but luckily I have another new LaunchPad. Here is the odd thing (which I think Chris has also mentioned). While the one that I was initially using clearly had headers factory-soldered for connectors J6-J9, they are DNF for the new LaunchPad that I have. Thus I soldered in headers. (I only hope they are sufficiently straight to fit Jim's board when it arrives!). If the time comes when anyone needs to do this, I have a whole box full of headers that can easily be broken to the right length. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*

1 0

Re: Pacsat Dev Mtg 4/13/2023
by Burns Fisher (AMSAT) 13 Apr '23

13 Apr '23

Second Thursday. As usual I won't be there. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Thu, Apr 13, 2023 at 3:40 PM Bill via pacsat-dev <pacsat-dev(a)amsat.org> wrote: > Pacsat Dev Mtg 4/13/2023 > Thu, Apr 13, 2023 7:00 PM - 9:00 PM (CDT) > > Please join my meeting from your computer, tablet or smartphone. > > https://meet.goto.com/504515061 > > You can also dial in using your phone. > (For supported devices, tap a one-touch number below to join instantly.) > > United States: +1 (571) 317-3112 > - One-touch: tel:+15713173112,,504515061# > > Access Code: 504-515-061 > > Join from a video-conferencing room or system. > Dial in or type: 67.217.95.2 or inroomlink.goto.com > Meeting ID: 504 515 061 > Or dial directly: 504515061(a)67.217.95.2 or 67.217.95.2##504515061 > > > Get the app now and be ready when your first meeting starts: > https://meet.goto.com/install > > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at > https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org > 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

Pacsat Dev Mtg 4/13/2023
by Bill 13 Apr '23

13 Apr '23

Pacsat Dev Mtg 4/13/2023 Thu, Apr 13, 2023 7:00 PM - 9:00 PM (CDT) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/504515061 You can also dial in using your phone. (For supported devices, tap a one-touch number below to join instantly.) United States: +1 (571) 317-3112 - One-touch: tel:+15713173112,,504515061# Access Code: 504-515-061 Join from a video-conferencing room or system. Dial in or type: 67.217.95.2 or inroomlink.goto.com Meeting ID: 504 515 061 Or dial directly: 504515061(a)67.217.95.2 or 67.217.95.2##504515061 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0

Main sw branch updated.
by Chris Thompson 11 Apr '23

11 Apr '23

I merged the filesystem code into main. I have also merged the ax25_9600 branch into main. That was slightly more difficult because there were quite a lot of merge conflicts with the filesystem changes. Corey, you should check that I did not accidentally lose anything. The file write/read test still works, so it should be fine. Note that this still includes my fake filesystem for the PB routines. I will decommission those next and use the new file system. For now it seemed best to merge these two large changes together so that future development sits on top of them. We will continue to develop in branches so that main always compiles and works. With fairly regular updates to main to avoid branches getting too far apart. 73 Chris

1 0