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

Re: Random person (me) gets pacsat working
by Chris Thompson 27 May '23

27 May '23

I'm glad this worked. Your description looks correct to me. Now you can try to load the directory and broadcast it. 73 Chris On Fri, May 26, 2023, 15:31 Burns Fisher (AMSAT) via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > I just wanted to let you know of a configuration that works successfully > and what I did (with Chris' help) to get there. > > First, I have PacSat ground AND Direwolf installed on a PC with Win11. > Plugged into the PC is a Digirig mobile. The DRM has a Baofeng/Kenwood HT > cable connecting it to a Kenwood D72. It appears not to require setting to > full duplex, so probably a different less fancy HT would work, although it > does require two VFOs. > > Set the transmit VFO to 145935 MHz. Set the receive VFO to 435760MHz. On > the D72, I have to turn the volume up maybe 1/2 way. Probably turning the > squelch off would help too, although I did not have to. > > Be sure you have at least a dummy load on the Pacsat board tx (the same > side as the LED and the console serial connector). It was more reliable > when I put a rubber ducky on, but you can make it with just the dummy load. > > Now start up first direwolf using the command direwolf -q d -B 1200 (after > setting up the direwolf.conf file to be pointing to the correct input and > output audio devices as Chris mentioned earlier). Then start up PacSat > Ground. It should say a few things like "KISS is assumed ON" TNC IN FULL > DUPLEX. etc. > > On the "satellite console" enter "set rate 1200" and monitor on. > > On the satellite if you type "send pb status" this should cause the > satellite to transmit, the HT to receive and pass the data to direwolf, and > direwolf will decode it and send to pacsat ground. You should see "PB > Empty" appear on the PacSat ground station. On Direwolf, you might see > "Audio input level is too high". I reduced the audio level until I did not > get anything, and then went up slightly. I could not avoid that message. > > Now go to PacSat ground and hit the "DIR" key near the top. This will > send a message via direwolf and your HT to the "satellite", which will in > turn respond. PacSat Ground says something like TX: DIR REQ: HOLES etc. > From WB1FJ to VE2TCP-11. And finally OK WB1FJ (or whatever you put in for > your call). If you are not receiving a response from the satellite, PacSat > ground keeps resending every few seconds for a minute or so. > > This is not very thorough because I can't say that I understand exactly > what is going on, but I did want to record that I got all of these various > components to work and approximately how. Chris, feel free to fill in, and > thanks for the help! > > 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

Random person (me) gets pacsat working
by Burns Fisher (AMSAT) 26 May '23

26 May '23

I just wanted to let you know of a configuration that works successfully and what I did (with Chris' help) to get there. First, I have PacSat ground AND Direwolf installed on a PC with Win11. Plugged into the PC is a Digirig mobile. The DRM has a Baofeng/Kenwood HT cable connecting it to a Kenwood D72. It appears not to require setting to full duplex, so probably a different less fancy HT would work, although it does require two VFOs. Set the transmit VFO to 145935 MHz. Set the receive VFO to 435760MHz. On the D72, I have to turn the volume up maybe 1/2 way. Probably turning the squelch off would help too, although I did not have to. Be sure you have at least a dummy load on the Pacsat board tx (the same side as the LED and the console serial connector). It was more reliable when I put a rubber ducky on, but you can make it with just the dummy load. Now start up first direwolf using the command direwolf -q d -B 1200 (after setting up the direwolf.conf file to be pointing to the correct input and output audio devices as Chris mentioned earlier). Then start up PacSat Ground. It should say a few things like "KISS is assumed ON" TNC IN FULL DUPLEX. etc. On the "satellite console" enter "set rate 1200" and monitor on. On the satellite if you type "send pb status" this should cause the satellite to transmit, the HT to receive and pass the data to direwolf, and direwolf will decode it and send to pacsat ground. You should see "PB Empty" appear on the PacSat ground station. On Direwolf, you might see "Audio input level is too high". I reduced the audio level until I did not get anything, and then went up slightly. I could not avoid that message. Now go to PacSat ground and hit the "DIR" key near the top. This will send a message via direwolf and your HT to the "satellite", which will in turn respond. PacSat Ground says something like TX: DIR REQ: HOLES etc. From WB1FJ to VE2TCP-11. And finally OK WB1FJ (or whatever you put in for your call). If you are not receiving a response from the satellite, PacSat ground keeps resending every few seconds for a minute or so. This is not very thorough because I can't say that I understand exactly what is going on, but I did want to record that I got all of these various components to work and approximately how. Chris, feel free to fill in, and thanks for the help! 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*

1 0

Special guest tonight
by Bill 25 May '23

25 May '23

I was at Dayton Hamvention last weekend and was talking with Robert Bankston, AMSAT president about the PACSAT project. I told him we had an amazing set of developers and had accomplished much in just 6 months. He said he would like to meet the team sometime. I have invited him to our meeting this evening. Hope he is able to attend. Bill, NX5R

1 0

Pacsat dev mtg 5/25/2023
by Bill 25 May '23

25 May '23

Pacsat dev mtg 5/25/2023 Thu, May 25, 2023 7:00 PM - 9:00 PM (CDT) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/354253397 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-3122 - One-touch: tel:+15713173122,,354253397# Access Code: 354-253-397 Join from a video-conferencing room or system. Dial in or type: 67.217.95.2 or inroomlink.goto.com Meeting ID: 354 253 397 Or dial directly: 354253397(a)67.217.95.2 or 67.217.95.2##354253397 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0

Re: New update to main
by Burns Fisher (AMSAT) 24 May '23

24 May '23

Nice! Thank you. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Wed, May 24, 2023 at 3:21 PM Chris Thompson via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > No, this is now setup with the expected frequencies (I think, correct me > if it is wrong). It is listening on 2m and transmitting on 70cms. You can > use either 1200 or 9600bps packet. It defaults to 1200 as I remember but > your choice is remembered in MRAM if you change it. > > The PB and Uplink are disabled initially I think. You need to enable them > with the commands: > PB open > Uplink open > > > 73 > Chris > > On Wed, May 24, 2023, 14:43 Burns Fisher (AMSAT) <wb1fj(a)fisher.cc> wrote: > >> So just to clarify, this is using 2m both up and down? >> 73, >> >> Burns Fisher, WB1FJ >> *AMSAT(R) Engineering -- Flight Software* >> >> >> On Wed, May 24, 2023 at 11:37 AM Chris Thompson via pacsat-dev < >> pacsat-dev(a)amsat.org> wrote: >> >>> I just pushed my latest code to main. This has a working version of the >>> AX25 Data Link State Machine. You can see the code in AX25Task.c. If you >>> try to upload a file it will appear to work, with the ground station saying >>> it was uploaded correctly. All of the packets are received and Ack'd by >>> PACSAT, but the Uplink state machine is not yet storing them in a file. I >>> still need to write that part. >>> >>> To trigger the ground station you need to transmit the status of the >>> uplink by typing: >>> send uplink status >>> >>> This is also using 2m as the receive frequency. Thanks to work by Jim, >>> I have set this to use GFSK with BT=0.3. BT is the shape of the bit >>> shaping filter. The filter may not be applied on receive, but setting it >>> to GFSK vs GMSK makes a big difference. It now receives well on 2m at >>> 9600bps. There is an errata from ON SEMI that says to use BT=0.3 vs BT=0.5 >>> for transmit. >>> >>> I have also implemented a mode change command. You can type these >>> commands in the console: >>> set rate 1200 >>> set rate 9600 >>> >>> These will set the radios to the specified data rate. You need to >>> restart the processor to apply it. We can probably just restart the >>> radios, but that was a quick way to implement this for testing. >>> >>> 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 >

1 0

Re: New update to main
by Burns Fisher (AMSAT) 24 May '23

24 May '23

So just to clarify, this is using 2m both up and down? 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Wed, May 24, 2023 at 11:37 AM Chris Thompson via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > I just pushed my latest code to main. This has a working version of the > AX25 Data Link State Machine. You can see the code in AX25Task.c. If you > try to upload a file it will appear to work, with the ground station saying > it was uploaded correctly. All of the packets are received and Ack'd by > PACSAT, but the Uplink state machine is not yet storing them in a file. I > still need to write that part. > > To trigger the ground station you need to transmit the status of the > uplink by typing: > send uplink status > > This is also using 2m as the receive frequency. Thanks to work by Jim, I > have set this to use GFSK with BT=0.3. BT is the shape of the bit shaping > filter. The filter may not be applied on receive, but setting it to GFSK > vs GMSK makes a big difference. It now receives well on 2m at 9600bps. > There is an errata from ON SEMI that says to use BT=0.3 vs BT=0.5 for > transmit. > > I have also implemented a mode change command. You can type these > commands in the console: > set rate 1200 > set rate 9600 > > These will set the radios to the specified data rate. You need to restart > the processor to apply it. We can probably just restart the radios, but > that was a quick way to implement this for testing. > > 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 >

2 1

Probably not there today
by Corey Minyard 24 May '23

24 May '23

I'm in San Jose this week and I have something this evening, so I will probably not be able to make the meeting today. -corey - AE5KM

1 0

New update to main
by Chris Thompson 24 May '23

24 May '23

I just pushed my latest code to main. This has a working version of the AX25 Data Link State Machine. You can see the code in AX25Task.c. If you try to upload a file it will appear to work, with the ground station saying it was uploaded correctly. All of the packets are received and Ack'd by PACSAT, but the Uplink state machine is not yet storing them in a file. I still need to write that part. To trigger the ground station you need to transmit the status of the uplink by typing: send uplink status This is also using 2m as the receive frequency. Thanks to work by Jim, I have set this to use GFSK with BT=0.3. BT is the shape of the bit shaping filter. The filter may not be applied on receive, but setting it to GFSK vs GMSK makes a big difference. It now receives well on 2m at 9600bps. There is an errata from ON SEMI that says to use BT=0.3 vs BT=0.5 for transmit. I have also implemented a mode change command. You can type these commands in the console: set rate 1200 set rate 9600 These will set the radios to the specified data rate. You need to restart the processor to apply it. We can probably just restart the radios, but that was a quick way to implement this for testing. 73 Chris -- Chris E. Thompson chrisethompson(a)gmail.com g0kla(a)arrl.net

1 0

Re: RF Components / Power Requirements
by Jonathan Brandenburg 22 May '23

22 May '23

Thank you, Bob! I could have known / should have known you're already on top of the single event upsets and the latchup aspects of the board. Thank you for confirming all the considerations already present in the layout! There are still some details to be worked out, some of which depend on the characterization of the initial boards. That makes sense. I'll call out your last point in particular: "I am sure we have a power issue as I stated earlier. I have been moving ahead to test things with the idea we will have to cut some things back when/if the design moves forward." Since PACSAT is not yet targeting a specific satellite or launch but is instead looking to build a payload that can be made available for a number of satellites and launches, there won't be a single power budget available. Instead it seems like PACSAT will have a specified power requirement (perhaps a range that can be adjusted by turn on or off features like the number of uplinks). In defining that range it might be helpful to consider the target "customer". If targeting the minimum capabilities of 1U CubeSat, I happen to know the average orbit power with fixed cells on all faces is considered 5W with a worst case orbit of 2W. How much of that would a customer be willing to allocate to this subsystem? Perhaps a fair amount if PACSAT is also their primary command and telemetry system (recognizing there will be loss in the electrical power system and other systems are equally important including the command & data handling system and the primary payload) Or, is a 3U CubeSat a more appropriate target because it will have more power with fixed cells? I don't have the answer to this question but it's good to be thinking about power as you're already doing, Jonathan On 5/20/2023 9:48 PM, Bob Stricklin via pacsat-dev wrote: > Jonathan, > > Just looking back through some PacSat-Dev emails and realized I missed > this one from you…. > > > > >> On May 5, 2023, at 11:55 AM, Jonathan Brandenburg via pacsat-dev >> <pacsat-dev(a)amsat.org> wrote: >> >> As discussed last night, I've completed some preliminary work on the >> radiation tolerant circuitry. That does bring up one question... >> >> Bob, do you already have circuitry for watchdog protection and >> current limiting in the schematic / on the board? Or does that still >> have to be shoehorned into the board? > >> Yes, There is a Hardware Watchdog in the schematic and on the PCB - >> STWD100NYWY3F > > Yes, There are several current limit ICs, MAX4495_1 on the bard. The > current limit is set by a resistor and is set at 600 mA on each chip. > Will need to be tuned to the real value needed after prototyping. > >> >> To refine the design I've prototyped, I need to know the >> anticipated/budgeted power requirements. The part I'm looking at for >> current limiting, MAX4995AAUT+T, can handle 600mA. If we derate that >> a bit (are we using 50%?) we can handle 300mA. That's quite a lot so >> I don't expect an issue with hitting max current except possibly the >> power amplifier and it's not clear to me if the power amplifier needs >> to be protected against latchup anyway. In our previous designs, we >> have a separate current limiter for each AX5043, the power amplifier, >> and the TMS570. (I think the LNAs are bundled with the AX5043 for the >> purposes of power limits and peripheral power requirements for TXCOs >> and such ). I don't think we'll need that many here but we'll >> probably need one for each voltage rail. >> >> >> Do we have answers to some of the following questions or is some of >> still being determined: >> >> 1. What power output level are we using on the AX5043? Max current at >> 16dbm TX is 48 mA plus 6.5 mA for VHF receiver or 9.5 mA for UHF receive. > > This is programable in the AX5043 and not currently fix/defined. The > AX5043 TX chip is driving a Linear Power section in the design I have > because the desire was to have 2 Watts of RF power. PA chip is > MMZ09312BT1. We have a Class E output driving a linear power Amp. >> >> 2. What LNAs are we using? Does each AX5043 have its own LNA? (I >> haven't looked for a schematic so tell me to go find it myself if >> it's in Github.) > > LNA is currently a SAV-331+ which should provide about 15 dB of gain. > The signal is then filtered and then power converted to a differential > signal and split four ways to feed the four AX5043s. > > One Receive Antenna is used which feeds the LNA. Then the signal is > filtered and converted to differential and power divided to drive the > four AX5043s. >> >> 3. What power amplifier are we using and what is the power output? (I >> still need to double-check a need for current limiter here.) > > Output power amp is MMZ09312BT1 (74 Ma) for a total power of about 2 > Watts. These are no current limits on the power amps now and they are > powered from the main voltage coming to us to get max power. >> >> 4. Do we have a characterization for the TMS570 configuration to know >> which subsystems will be active and thus have a power budget for the >> TMS570? > > No, The power budget I sent you earlier for all the chips assumes the > current posted in the data sheet for each including the TMS570. > Probably not going to save a lot of power in this device. You can save > power here by running with a slower clock which may support our needs. > This can be determined in prototype testing. The clocking for the > TMS570 and the AX5043 can be split apart to support rate sensitive > functions. > > > I am sure we have a power issue as I stated earlier. I have beed > moving ahead to test things with the idea we will have to cut some > things back when/if the design moves forward. > > Bob > >> >> Thanks a lot! >> >> Jonathan >> >> -- >> Jonathan Brandenburg, KF5IDY >> >> >> ----------------------------------------------------------- >> >> pacsat-dev mailing list -- pacsat-dev(a)amsat.org >> View archives of this mailing list at >> https://url.emailprotection.link/?buUg7YY4HZLXKo6ZKNudC8bRTBdOsBlAV5C9rq-aq… >> To unsubscribe send an email to pacsat-dev-leave(a)amsat.org >> Manage all of your AMSAT-NA mailing list preferences at >> https://url.emailprotection.link/?bO71JCUf8Kb7txAlIoAarNqcIdQhyb8VQQIN4j0Gi… > > > ----------------------------------------------------------- > > 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 -- jbrandenburg(a)amsat.org

1 0

Re: RF Components / Power Requirements
by Bob Stricklin 21 May '23

21 May '23

Jonathan, Just looking back through some PacSat-Dev emails and realized I missed this one from you…. On May 5, 2023, at 11:55 AM, Jonathan Brandenburg via pacsat-dev <pacsat-dev(a)amsat.org<mailto:pacsat-dev@amsat.org>> wrote: As discussed last night, I've completed some preliminary work on the radiation tolerant circuitry. That does bring up one question... Bob, do you already have circuitry for watchdog protection and current limiting in the schematic / on the board? Or does that still have to be shoehorned into the board? Yes, There is a Hardware Watchdog in the schematic and on the PCB - STWD100NYWY3F Yes, There are several current limit ICs, MAX4495_1 on the bard. The current limit is set by a resistor and is set at 600 mA on each chip. Will need to be tuned to the real value needed after prototyping. To refine the design I've prototyped, I need to know the anticipated/budgeted power requirements. The part I'm looking at for current limiting, MAX4995AAUT+T, can handle 600mA. If we derate that a bit (are we using 50%?) we can handle 300mA. That's quite a lot so I don't expect an issue with hitting max current except possibly the power amplifier and it's not clear to me if the power amplifier needs to be protected against latchup anyway. In our previous designs, we have a separate current limiter for each AX5043, the power amplifier, and the TMS570. (I think the LNAs are bundled with the AX5043 for the purposes of power limits and peripheral power requirements for TXCOs and such ). I don't think we'll need that many here but we'll probably need one for each voltage rail. Do we have answers to some of the following questions or is some of still being determined: 1. What power output level are we using on the AX5043? Max current at 16dbm TX is 48 mA plus 6.5 mA for VHF receiver or 9.5 mA for UHF receive. This is programable in the AX5043 and not currently fix/defined. The AX5043 TX chip is driving a Linear Power section in the design I have because the desire was to have 2 Watts of RF power. PA chip is MMZ09312BT1. We have a Class E output driving a linear power Amp. 2. What LNAs are we using? Does each AX5043 have its own LNA? (I haven't looked for a schematic so tell me to go find it myself if it's in Github.) LNA is currently a SAV-331+ which should provide about 15 dB of gain. The signal is then filtered and then power converted to a differential signal and split four ways to feed the four AX5043s. One Receive Antenna is used which feeds the LNA. Then the signal is filtered and converted to differential and power divided to drive the four AX5043s. 3. What power amplifier are we using and what is the power output? (I still need to double-check a need for current limiter here.) Output power amp is MMZ09312BT1 (74 Ma) for a total power of about 2 Watts. These are no current limits on the power amps now and they are powered from the main voltage coming to us to get max power. 4. Do we have a characterization for the TMS570 configuration to know which subsystems will be active and thus have a power budget for the TMS570? No, The power budget I sent you earlier for all the chips assumes the current posted in the data sheet for each including the TMS570. Probably not going to save a lot of power in this device. You can save power here by running with a slower clock which may support our needs. This can be determined in prototype testing. The clocking for the TMS570 and the AX5043 can be split apart to support rate sensitive functions. I am sure we have a power issue as I stated earlier. I have beed moving ahead to test things with the idea we will have to cut some things back when/if the design moves forward. Bob Thanks a lot! Jonathan -- Jonathan Brandenburg, KF5IDY ----------------------------------------------------------- pacsat-dev mailing list -- pacsat-dev(a)amsat.org<mailto:pacsat-dev@amsat.org> View archives of this mailing list at https://url.emailprotection.link/?buUg7YY4HZLXKo6ZKNudC8bRTBdOsBlAV5C9rq-aq… 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://url.emailprotection.link/?bO71JCUf8Kb7txAlIoAarNqcIdQhyb8VQQIN4j0Gi…

1 0

Re: AX25 code
by Chris Thompson 12 May '23

12 May '23

ok, thanks. I will have a look. 73 Chris On Fri, May 12, 2023 at 8:51 AM Corey Minyard via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > On Thu, May 11, 2023 at 8:01 PM Corey Minyard via pacsat-dev > <pacsat-dev(a)amsat.org> wrote: > > > > For Chris, mostly, > > > > In my AX25 code, the two queues are named read_data and write_data, > > you can search for those values. The length, position, and size are > > right after it and described in the comment above. > > > > There are also some functions named "sub_seq", "add_seq" and > > "seq_in_range" that handle the wraparound. In particular, > > seq_in_range is a little tricky. And I see that I should comment > > those better. > > Just to be clear, those are used for both sequence number handling and > for circular buffer handling. I've added some comments to document > them a little better. > > > > > And if you want, I can look at splitting up my code into a library > > that has the state machine that could be re-used. It may be some > > overkill, though, it does all the extended sequencing, XID, and such > > that we don't need. > > > > -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 > -- Chris E. Thompson chrisethompson(a)gmail.com g0kla(a)arrl.net

1 0

Re: AX25 code
by Corey Minyard 12 May '23

12 May '23

On Thu, May 11, 2023 at 8:01 PM Corey Minyard via pacsat-dev <pacsat-dev(a)amsat.org> wrote: > > For Chris, mostly, > > In my AX25 code, the two queues are named read_data and write_data, > you can search for those values. The length, position, and size are > right after it and described in the comment above. > > There are also some functions named "sub_seq", "add_seq" and > "seq_in_range" that handle the wraparound. In particular, > seq_in_range is a little tricky. And I see that I should comment > those better. Just to be clear, those are used for both sequence number handling and for circular buffer handling. I've added some comments to document them a little better. > > And if you want, I can look at splitting up my code into a library > that has the state machine that could be re-used. It may be some > overkill, though, it does all the extended sequencing, XID, and such > that we don't need. > > -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

AX25 code
by Corey Minyard 12 May '23

12 May '23

For Chris, mostly, In my AX25 code, the two queues are named read_data and write_data, you can search for those values. The length, position, and size are right after it and described in the comment above. There are also some functions named "sub_seq", "add_seq" and "seq_in_range" that handle the wraparound. In particular, seq_in_range is a little tricky. And I see that I should comment those better. And if you want, I can look at splitting up my code into a library that has the state machine that could be re-used. It may be some overkill, though, it does all the extended sequencing, XID, and such that we don't need. -corey

1 0

Re: Pacsat dev mtg 5/11/2023
by Burns Fisher (AMSAT) 11 May '23

11 May '23

Second Thursday, so I won't be there. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Thu, May 11, 2023 at 3:48 PM Bill via pacsat-dev <pacsat-dev(a)amsat.org> wrote: > > Thu, May 11, 2023 7:00 PM - 9:00 PM (CDT) > > Please join my meeting from your computer, tablet or smartphone. > > https://meet.goto.com/961241293 > > 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,,961241293# > > Access Code: 961-241-293 > > Join from a video-conferencing room or system. > Dial in or type: 67.217.95.2 or inroomlink.goto.com > Meeting ID: 961 241 293 > Or dial directly: 961241293(a)67.217.95.2 or 67.217.95.2##961241293 > > > 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 5/11/2023
by Bill 11 May '23

11 May '23

Thu, May 11, 2023 7:00 PM - 9:00 PM (CDT) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/961241293 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,,961241293# Access Code: 961-241-293 Join from a video-conferencing room or system. Dial in or type: 67.217.95.2 or inroomlink.goto.com Meeting ID: 961 241 293 Or dial directly: 961241293(a)67.217.95.2 or 67.217.95.2##961241293 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0

Building/loading PacSat software
by Burns Fisher (AMSAT) 10 May '23

10 May '23

Chris said in a previous mail that I had sent out info about how to build PacSat. Maybe I did, but I can't find it. So for Bill and any others, here is at least a quick version. Without actually DOING it again, I may miss something. We can use this thread to clarify, and I know several other people have done it. Please do speak up if I miss something. =========================== The first thing you want to do is to download and install TI's Code Composer Studio. Look at https://www.ti.com/tool/CCSTUDIO I use the Linux version 10.2.0.00009, but there are several versions newer. I tend not to update unless I need to, but feel free to try the newer one. (We should freeze the version before we start testing for flight!) When you run CCS, go to the "File" menu and select "Import" and the Git/Projects from Git. (I don't know what smart import, another choice is, so I probably did not use it). I think it will suggest a project called "PacSat" and that is what you should choose. Let it all install/download, etc, and then push the "Hammer" key to build. Hopefully this will work. Then you can plug in your LaunchPad and hit the "bug" button to download and debug. If you are not gonig to use the debugger, just hit the red square to disconnect and it will run. Remember that you have to have a serial port connected to Jim's board (the 3 pins labelled Rx, Tx, and Gnd). Use a terminal emulator to connect to this at 38400 baud. Hopefully, this all does the trick. Have I missed anything Chris, Corey, Jim? I have not done the full download in a good long time, so there are probably additional things you have to slog through. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*

1 0

Code Cleanup
by Burns Fisher (AMSAT) 10 May '23

10 May '23

Folks, I have removed references to the HET (High Efficiency Timer--essentially a co-processor in the TMS570) emulation of I2c and UART. We need extra UARTs and I2c busses in Golf, and Golf is where I initially ported the PacSat code from. This is step one of cleaning out Golf stuff. I've already removed anything that might be ITAR sensitive (and I don't think there was anything). This is just removing unnecessary stuff that need not take up space in flash. I don't think this will cause anyone any serious problems merging since most of it was in drivers, but it is currently in a branch called CleanUpHET. I'll put in a pull request to merge that with main, and if I hear no comments, will do that in a few days. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*

1 0

Re: PACSAT Operating Instructions
by Chris Thompson 10 May '23

10 May '23

Hi Burns, Yes. I just haven't had time to do that. The startup routine would have to be changed to detect if it is vhf or uhf and then pass the right value as appropriate. Then we could remove my override. 73 Chris On Wed, May 10, 2023, 15:13 Burns Fisher (AMSAT) via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Chris et al, > > Does it make sense to put the values that we want in the MRAM status > section right now? In that way we don't have two different places that are > setting the values differently, and it is relatively easy to change using > the existing "change" commands. > > 73, > > Burns Fisher, WB1FJ > *AMSAT(R) Engineering -- Flight Software* > > > On Wed, May 10, 2023 at 3:09 PM Chris Thompson via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> Hi Corey >> >> Glad to see things are working. >> >> I agree the frequencies are a little screwy. The TX defaults to 435750 >> based on some original Golf code I think. We can set that to default to >> whatever we want. The receiver defaults to 145835 but I have a bit of >> code that overrides it in the startup of the receiver. That hard codes the >> receiver to UHF and 436800. Initially that was because the boards I had >> only worked on 70cms. Now it is because the receive config does not work >> that well on 2m. You can go into deviceSupport/src/ax5043-ax25.c and >> comment out these two two lines in start_ax25_rx(): >> freq = 436800000; // Use for testing >> band_vhf = BAND_UHF; >> >> Then it will work as expected and receive (sort of) on 2m. >> >> 73 >> Chris >> >> On Wed, May 10, 2023 at 2:42 PM Corey Minyard via pacsat-dev < >> pacsat-dev(a)amsat.org> wrote: >> >>> It could be the serial port, that makes some sense, I guess. >>> >>> I installed a jumper feeding 3.3v on J4 pin 1, and the MRAM still >>> works, but the 5043s still don't. >>> >>> I think I found it. R10 and R11 are not populated. One of them says >>> 330 ohms, one says zero. What needs to be put here? I think I have >>> some SM resistors, but probably 0603, and these look smaller. >>> >>> -corey >>> >>> > Ok, I got both mails. One thing I notice is that there is some >>> backflow of >>> > power from the serial line which lights the LED (dimly) even if the >>> > LaunchPad is unpowered. Could that be the reason for the 2.7V? I have >>> > those jumpers installed on both halves of the board, but I'm surprised >>> the >>> > MRAM works at all if you don't have it installed (maybe that 2.7V is >>> > enough---and I don't see how that relates to the 5043). >>> >>> On Tue, May 9, 2023 at 9:41 AM Corey Minyard <minyard(a)acm.org> wrote: >>> > >>> > I send this from my acm.org account and realised it's not going to get >>> > to the pacsat mailing list. So here it is again. >>> > >>> > On Tue, May 9, 2023 at 9:39 AM Corey Minyard <minyard(a)acm.org> wrote: >>> > > >>> > > On Tue, May 09, 2023 at 09:28:06AM -0400, Burns Fisher (AMSAT) wrote: >>> > > > Ok, glad the MRAM is working. Any chance that you don't have the >>> two >>> > > > jumpers on the LaunchPad required to power the 5043s? These would >>> be a >>> > > > pair on the right (components up, USB down, I think) just below >>> the bottom >>> > > > set of pins. >>> > > >>> > > Yes, the two jumpers labeled +5V and +3V3 right by J1 are both >>> installed. >>> > > I'm getting 3.3V on J1 pin 1 and 5V on J1 pin 2. >>> > > >>> > > There are unpopulated jumpers on the LaunchPad by J4 (J6 on the >>> > > Laumchpad) that have the same labels. I'm getting 2.7V on J4 pin 1, >>> > > which is strange. That's what powers the MRAMs and the temperature >>> > > sensor. >>> > > >>> > > Should I put a jumper on 3V3 by J4? I'm getting 3.3V on the other >>> side >>> > > of the jumper. I'm wondering if the power is somehow coming through >>> the >>> > > 5043s and getting to the MRAMs, but I don't see how that could >>> happen. >>> > > >>> > > > >>> > > > BTW, I don't even try to push Jim's board all the way on. It is >>> tight as >>> > > > it is and I want to be able to get it back off (relatively) >>> easily. But >>> > > > regardess, the tops of the pins are all level, even though the >>> newly >>> > > > soldered pins have a plastic holder at the bottom and the original >>> pins do >>> > > > not. >>> > > >>> > > Yeah, strange. I didn't notice until I tried to put the board on. >>> My >>> > > board now looks terrible, but it seems to be making good contact now. >>> > > >>> > > I looked at close-up pictures on TI's web site, and the pins I had >>> look >>> > > the same as the ones in the picture. >>> > > >>> > > -corey >>> > > >>> > > > >>> > > > 73, >>> > > > >>> > > > Burns Fisher, WB1FJ >>> > > > *AMSAT(R) Engineering -- Flight Software* >>> > > > >>> > > > >>> > > > On Mon, May 8, 2023 at 11:52 PM Corey Minyard via pacsat-dev < >>> > > > pacsat-dev(a)amsat.org> wrote: >>> > > > >>> > > > > Burns sent me the info on that. I ran J5 pin 12 to a via on the >>> > > > > bottom right of U1. After doing that wiring change, all but one >>> MRAM >>> > > > > appears to be working. It looks like R5 got removed somehow, I >>> may >>> > > > > have done that removing the wire. I just installed a bridge >>> there, >>> > > > > since it's a zero-ohm resistor, and the mram seems to be working >>> now. >>> > > > > >>> > > > > The temperature sensor on the daughter board seems to be working. >>> > > > > >>> > > > > I don't think the 5043's are working. I'm not getting anything >>> on >>> > > > > transmit, and I eventually get: >>> > > > > >>> > > > > Pacsat>send pb status >>> > > > > ## SELF TEST: pb_test_status >>> > > > > TX QUEUE FULL: Could not add UI frame to Packet Queue >>> > > > > PB Empty. >>> > > > > ## PASSED SELF TEST: pb_test_status >>> > > > > >>> > > > > after running that a few times. At startup, I'm getting: >>> > > > > >>> > > > > ERROR: In start_rx, axradio_init returned: 5 >>> > > > > ERROR: In start_tx, axradio_init_70cm returned: 5Initializing PB >>> Task >>> > > > > ERROR: Failed in init PB Status Timer >>> > > > > >>> > > > > -corey >>> > > > > >>> > > > > On Mon, May 8, 2023 at 9:51 PM Jim McCullers via pacsat-dev >>> > > > > <pacsat-dev(a)amsat.org> wrote: >>> > > > > > >>> > > > > > Chris, >>> > > > > > >>> > > > > > Please take a look at the email I sent out earlier. >>> > > > > > There is the possibility of a wiring error on the board with >>> my white >>> > > > > wire correction. >>> > > > > > >>> > > > > > As for the connectors being longer, I never noticed that and >>> these >>> > > > > should be the same connectors I sent Burns and Chris. >>> > > > > > Burns say the MRAM is working after the wiring change and the >>> AX5043s >>> > > > > are working for Chris and Burns so not certain there. >>> > > > > > >>> > > > > > Attached is the revised schematic. I'll have the Kicad files >>> on github >>> > > > > hopefully tomorrow. Have a couple of issues to deal with. >>> > > > > > >>> > > > > > Jim McCullers >>> > > > > > WA4CWI >>> > > > > > >>> > > > > > >>> > > > > > >>> > > > > > I sent this earlier, but just to Chris. >>> > > > > > >>> > > > > > I got my board today and soldered on the connectors. Looking >>> at the >>> > > > > board now, I see that the connectors that came with the >>> launchpad are >>> > > > > around 1cm longer than the ones Jim supplied. I can't get the >>> mram or >>> > > > > ax5043s to be detected. I don't think it's making good contact >>> on the >>> > > > > connectors, for obvious reasons. Do I need to trim the old >>> connector, or >>> > > > > did I do something wrong? >>> > > > > > >>> > > > > > I clipped the pins, and still no help. The power light by the >>> serial >>> > > > > connector works, and the serial port works. But the mrams and >>> the ax5043's >>> > > > > are not there. >>> > > > > > >>> > > > > > I can't find the schematics in the git repository. >>> PacSatDocs, I >>> > > > > assume. I guess I need to start debugging to figure out what is >>> wrong. >>> > > > > > >>> > > > > > -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 >>> > > > > >>> >>> ----------------------------------------------------------- >>> >>> 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 >

2 1

Re: Newest PACSAT daughter board
by Burns Fisher (AMSAT) 10 May '23

10 May '23

Just to clarify, only ONE white-wire needs to be changed. The one connecting to R4 is ok. The one connecting to R5 needs to be moved to a via along the edge of the board (it probably needs a longer wire unless you find a different way to make the connection to that trace). 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Mon, May 8, 2023 at 10:42 PM Jim McCullers via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Burns has informed me I reversed my own directions and MRAM fix may not be > correct. > > Please review the attached images and if the board you received looks like > the ‘Before’ image break out the soldering iron and swap them. > > The correct wiring is the ‘After’ image. > > > > I write directions much better than I follow them, even my own. > > > > Burns reports with the changes the AX5043 are ranging correctly and the > MRAM works. > > > > Jim McCullers > > WA4CWI > > ----------------------------------------------------------- > > 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: PACSAT Operating Instructions
by Jim McCullers 10 May '23

10 May '23

Corey, Sorry but list has been offline. Populate with 330 ohm or almost anything. Zero may work and that's on my future test list. It's like the zero ohm resistors that we found out were not needed on the MRAMs to as load separation between the chips. Kicad protested that something had to be there and at that time on the MRAMs we did not know and still do not know on the 5043s. Not much literature on putting two on the same SPI bus. I ran out of 330s and forgot to populate when the shipment came in. Jim McCullers WA4CWI It could be the serial port, that makes some sense, I guess. I installed a jumper feeding 3.3v on J4 pin 1, and the MRAM still works, but the 5043s still don't. I think I found it. R10 and R11 are not populated. One of them says 330 ohms, one says zero. What needs to be put here? I think I have some SM resistors, but probably 0603, and these look smaller. -corey > Ok, I got both mails. One thing I notice is that there is some > backflow of power from the serial line which lights the LED (dimly) > even if the LaunchPad is unpowered. Could that be the reason for the > 2.7V? I have those jumpers installed on both halves of the board, but > I'm surprised the MRAM works at all if you don't have it installed > (maybe that 2.7V is enough---and I don't see how that relates to the 5043). On Tue, May 9, 2023 at 9:41 AM Corey Minyard <minyard(a)acm.org> wrote: > > I send this from my acm.org account and realised it's not going to get > to the pacsat mailing list. So here it is again. > > On Tue, May 9, 2023 at 9:39 AM Corey Minyard <minyard(a)acm.org> wrote: > > > > On Tue, May 09, 2023 at 09:28:06AM -0400, Burns Fisher (AMSAT) wrote: > > > Ok, glad the MRAM is working. Any chance that you don't have the > > > two jumpers on the LaunchPad required to power the 5043s? These > > > would be a pair on the right (components up, USB down, I think) > > > just below the bottom set of pins. > > > > Yes, the two jumpers labeled +5V and +3V3 right by J1 are both installed. > > I'm getting 3.3V on J1 pin 1 and 5V on J1 pin 2. > > > > There are unpopulated jumpers on the LaunchPad by J4 (J6 on the > > Laumchpad) that have the same labels. I'm getting 2.7V on J4 pin 1, > > which is strange. That's what powers the MRAMs and the temperature > > sensor. > > > > Should I put a jumper on 3V3 by J4? I'm getting 3.3V on the other > > side of the jumper. I'm wondering if the power is somehow coming > > through the 5043s and getting to the MRAMs, but I don't see how that could happen. > > > > > > > > BTW, I don't even try to push Jim's board all the way on. It is tight as > > > it is and I want to be able to get it back off (relatively) easily. But > > > regardess, the tops of the pins are all level, even though the > > > newly soldered pins have a plastic holder at the bottom and the > > > original pins do not. > > > > Yeah, strange. I didn't notice until I tried to put the board on. > > My board now looks terrible, but it seems to be making good contact now. > > > > I looked at close-up pictures on TI's web site, and the pins I had > > look the same as the ones in the picture. > > > > -corey > > > > > > > > 73, > > > > > > Burns Fisher, WB1FJ > > > *AMSAT(R) Engineering -- Flight Software* > > > > > > > > > On Mon, May 8, 2023 at 11:52 PM Corey Minyard via pacsat-dev < > > > pacsat-dev(a)amsat.org> wrote: > > > > > > > Burns sent me the info on that. I ran J5 pin 12 to a via on the > > > > bottom right of U1. After doing that wiring change, all but one > > > > MRAM appears to be working. It looks like R5 got removed > > > > somehow, I may have done that removing the wire. I just > > > > installed a bridge there, since it's a zero-ohm resistor, and the mram seems to be working now. > > > > > > > > The temperature sensor on the daughter board seems to be working. > > > > > > > > I don't think the 5043's are working. I'm not getting anything > > > > on transmit, and I eventually get: > > > > > > > > Pacsat>send pb status > > > > ## SELF TEST: pb_test_status > > > > TX QUEUE FULL: Could not add UI frame to Packet Queue PB Empty. > > > > ## PASSED SELF TEST: pb_test_status > > > > > > > > after running that a few times. At startup, I'm getting: > > > > > > > > ERROR: In start_rx, axradio_init returned: 5 > > > > ERROR: In start_tx, axradio_init_70cm returned: 5Initializing PB > > > > Task > > > > ERROR: Failed in init PB Status Timer > > > > > > > > -corey > > > > > > > > On Mon, May 8, 2023 at 9:51 PM Jim McCullers via pacsat-dev > > > > <pacsat-dev(a)amsat.org> wrote: > > > > > > > > > > Chris, > > > > > > > > > > Please take a look at the email I sent out earlier. > > > > > There is the possibility of a wiring error on the board with > > > > > my white > > > > wire correction. > > > > > > > > > > As for the connectors being longer, I never noticed that and > > > > > these > > > > should be the same connectors I sent Burns and Chris. > > > > > Burns say the MRAM is working after the wiring change and the > > > > > AX5043s > > > > are working for Chris and Burns so not certain there. > > > > > > > > > > Attached is the revised schematic. I'll have the Kicad files > > > > > on github > > > > hopefully tomorrow. Have a couple of issues to deal with. > > > > > > > > > > Jim McCullers > > > > > WA4CWI > > > > > > > > > > > > > > > > > > > > I sent this earlier, but just to Chris. > > > > > > > > > > I got my board today and soldered on the connectors. Looking > > > > > at the > > > > board now, I see that the connectors that came with the > > > > launchpad are around 1cm longer than the ones Jim supplied. I > > > > can't get the mram or ax5043s to be detected. I don't think > > > > it's making good contact on the connectors, for obvious reasons. > > > > Do I need to trim the old connector, or did I do something wrong? > > > > > > > > > > I clipped the pins, and still no help. The power light by the > > > > > serial > > > > connector works, and the serial port works. But the mrams and > > > > the ax5043's are not there. > > > > > > > > > > I can't find the schematics in the git repository. > > > > > PacSatDocs, I > > > > assume. I guess I need to start debugging to figure out what is wrong. > > > > > > > > > > -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 > > > > ----------------------------------------------------------- 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: PACSAT Operating Instructions
by Burns Fisher (AMSAT) 10 May '23

10 May '23

Chris et al, Does it make sense to put the values that we want in the MRAM status section right now? In that way we don't have two different places that are setting the values differently, and it is relatively easy to change using the existing "change" commands. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Wed, May 10, 2023 at 3:09 PM Chris Thompson via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Hi Corey > > Glad to see things are working. > > I agree the frequencies are a little screwy. The TX defaults to 435750 > based on some original Golf code I think. We can set that to default to > whatever we want. The receiver defaults to 145835 but I have a bit of > code that overrides it in the startup of the receiver. That hard codes the > receiver to UHF and 436800. Initially that was because the boards I had > only worked on 70cms. Now it is because the receive config does not work > that well on 2m. You can go into deviceSupport/src/ax5043-ax25.c and > comment out these two two lines in start_ax25_rx(): > freq = 436800000; // Use for testing > band_vhf = BAND_UHF; > > Then it will work as expected and receive (sort of) on 2m. > > 73 > Chris > > On Wed, May 10, 2023 at 2:42 PM Corey Minyard via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> It could be the serial port, that makes some sense, I guess. >> >> I installed a jumper feeding 3.3v on J4 pin 1, and the MRAM still >> works, but the 5043s still don't. >> >> I think I found it. R10 and R11 are not populated. One of them says >> 330 ohms, one says zero. What needs to be put here? I think I have >> some SM resistors, but probably 0603, and these look smaller. >> >> -corey >> >> > Ok, I got both mails. One thing I notice is that there is some >> backflow of >> > power from the serial line which lights the LED (dimly) even if the >> > LaunchPad is unpowered. Could that be the reason for the 2.7V? I have >> > those jumpers installed on both halves of the board, but I'm surprised >> the >> > MRAM works at all if you don't have it installed (maybe that 2.7V is >> > enough---and I don't see how that relates to the 5043). >> >> On Tue, May 9, 2023 at 9:41 AM Corey Minyard <minyard(a)acm.org> wrote: >> > >> > I send this from my acm.org account and realised it's not going to get >> > to the pacsat mailing list. So here it is again. >> > >> > On Tue, May 9, 2023 at 9:39 AM Corey Minyard <minyard(a)acm.org> wrote: >> > > >> > > On Tue, May 09, 2023 at 09:28:06AM -0400, Burns Fisher (AMSAT) wrote: >> > > > Ok, glad the MRAM is working. Any chance that you don't have the >> two >> > > > jumpers on the LaunchPad required to power the 5043s? These would >> be a >> > > > pair on the right (components up, USB down, I think) just below the >> bottom >> > > > set of pins. >> > > >> > > Yes, the two jumpers labeled +5V and +3V3 right by J1 are both >> installed. >> > > I'm getting 3.3V on J1 pin 1 and 5V on J1 pin 2. >> > > >> > > There are unpopulated jumpers on the LaunchPad by J4 (J6 on the >> > > Laumchpad) that have the same labels. I'm getting 2.7V on J4 pin 1, >> > > which is strange. That's what powers the MRAMs and the temperature >> > > sensor. >> > > >> > > Should I put a jumper on 3V3 by J4? I'm getting 3.3V on the other >> side >> > > of the jumper. I'm wondering if the power is somehow coming through >> the >> > > 5043s and getting to the MRAMs, but I don't see how that could happen. >> > > >> > > > >> > > > BTW, I don't even try to push Jim's board all the way on. It is >> tight as >> > > > it is and I want to be able to get it back off (relatively) >> easily. But >> > > > regardess, the tops of the pins are all level, even though the newly >> > > > soldered pins have a plastic holder at the bottom and the original >> pins do >> > > > not. >> > > >> > > Yeah, strange. I didn't notice until I tried to put the board on. My >> > > board now looks terrible, but it seems to be making good contact now. >> > > >> > > I looked at close-up pictures on TI's web site, and the pins I had >> look >> > > the same as the ones in the picture. >> > > >> > > -corey >> > > >> > > > >> > > > 73, >> > > > >> > > > Burns Fisher, WB1FJ >> > > > *AMSAT(R) Engineering -- Flight Software* >> > > > >> > > > >> > > > On Mon, May 8, 2023 at 11:52 PM Corey Minyard via pacsat-dev < >> > > > pacsat-dev(a)amsat.org> wrote: >> > > > >> > > > > Burns sent me the info on that. I ran J5 pin 12 to a via on the >> > > > > bottom right of U1. After doing that wiring change, all but one >> MRAM >> > > > > appears to be working. It looks like R5 got removed somehow, I >> may >> > > > > have done that removing the wire. I just installed a bridge >> there, >> > > > > since it's a zero-ohm resistor, and the mram seems to be working >> now. >> > > > > >> > > > > The temperature sensor on the daughter board seems to be working. >> > > > > >> > > > > I don't think the 5043's are working. I'm not getting anything on >> > > > > transmit, and I eventually get: >> > > > > >> > > > > Pacsat>send pb status >> > > > > ## SELF TEST: pb_test_status >> > > > > TX QUEUE FULL: Could not add UI frame to Packet Queue >> > > > > PB Empty. >> > > > > ## PASSED SELF TEST: pb_test_status >> > > > > >> > > > > after running that a few times. At startup, I'm getting: >> > > > > >> > > > > ERROR: In start_rx, axradio_init returned: 5 >> > > > > ERROR: In start_tx, axradio_init_70cm returned: 5Initializing PB >> Task >> > > > > ERROR: Failed in init PB Status Timer >> > > > > >> > > > > -corey >> > > > > >> > > > > On Mon, May 8, 2023 at 9:51 PM Jim McCullers via pacsat-dev >> > > > > <pacsat-dev(a)amsat.org> wrote: >> > > > > > >> > > > > > Chris, >> > > > > > >> > > > > > Please take a look at the email I sent out earlier. >> > > > > > There is the possibility of a wiring error on the board with my >> white >> > > > > wire correction. >> > > > > > >> > > > > > As for the connectors being longer, I never noticed that and >> these >> > > > > should be the same connectors I sent Burns and Chris. >> > > > > > Burns say the MRAM is working after the wiring change and the >> AX5043s >> > > > > are working for Chris and Burns so not certain there. >> > > > > > >> > > > > > Attached is the revised schematic. I'll have the Kicad files >> on github >> > > > > hopefully tomorrow. Have a couple of issues to deal with. >> > > > > > >> > > > > > Jim McCullers >> > > > > > WA4CWI >> > > > > > >> > > > > > >> > > > > > >> > > > > > I sent this earlier, but just to Chris. >> > > > > > >> > > > > > I got my board today and soldered on the connectors. Looking >> at the >> > > > > board now, I see that the connectors that came with the launchpad >> are >> > > > > around 1cm longer than the ones Jim supplied. I can't get the >> mram or >> > > > > ax5043s to be detected. I don't think it's making good contact >> on the >> > > > > connectors, for obvious reasons. Do I need to trim the old >> connector, or >> > > > > did I do something wrong? >> > > > > > >> > > > > > I clipped the pins, and still no help. The power light by the >> serial >> > > > > connector works, and the serial port works. But the mrams and >> the ax5043's >> > > > > are not there. >> > > > > > >> > > > > > I can't find the schematics in the git repository. PacSatDocs, >> I >> > > > > assume. I guess I need to start debugging to figure out what is >> wrong. >> > > > > > >> > > > > > -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 >> > > > > >> >> ----------------------------------------------------------- >> >> 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: PACSAT Operating Instructions
by Chris Thompson 10 May '23

10 May '23

Hi Corey Glad to see things are working. I agree the frequencies are a little screwy. The TX defaults to 435750 based on some original Golf code I think. We can set that to default to whatever we want. The receiver defaults to 145835 but I have a bit of code that overrides it in the startup of the receiver. That hard codes the receiver to UHF and 436800. Initially that was because the boards I had only worked on 70cms. Now it is because the receive config does not work that well on 2m. You can go into deviceSupport/src/ax5043-ax25.c and comment out these two two lines in start_ax25_rx(): freq = 436800000; // Use for testing band_vhf = BAND_UHF; Then it will work as expected and receive (sort of) on 2m. 73 Chris On Wed, May 10, 2023 at 2:42 PM Corey Minyard via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > It could be the serial port, that makes some sense, I guess. > > I installed a jumper feeding 3.3v on J4 pin 1, and the MRAM still > works, but the 5043s still don't. > > I think I found it. R10 and R11 are not populated. One of them says > 330 ohms, one says zero. What needs to be put here? I think I have > some SM resistors, but probably 0603, and these look smaller. > > -corey > > > Ok, I got both mails. One thing I notice is that there is some backflow > of > > power from the serial line which lights the LED (dimly) even if the > > LaunchPad is unpowered. Could that be the reason for the 2.7V? I have > > those jumpers installed on both halves of the board, but I'm surprised > the > > MRAM works at all if you don't have it installed (maybe that 2.7V is > > enough---and I don't see how that relates to the 5043). > > On Tue, May 9, 2023 at 9:41 AM Corey Minyard <minyard(a)acm.org> wrote: > > > > I send this from my acm.org account and realised it's not going to get > > to the pacsat mailing list. So here it is again. > > > > On Tue, May 9, 2023 at 9:39 AM Corey Minyard <minyard(a)acm.org> wrote: > > > > > > On Tue, May 09, 2023 at 09:28:06AM -0400, Burns Fisher (AMSAT) wrote: > > > > Ok, glad the MRAM is working. Any chance that you don't have the two > > > > jumpers on the LaunchPad required to power the 5043s? These would > be a > > > > pair on the right (components up, USB down, I think) just below the > bottom > > > > set of pins. > > > > > > Yes, the two jumpers labeled +5V and +3V3 right by J1 are both > installed. > > > I'm getting 3.3V on J1 pin 1 and 5V on J1 pin 2. > > > > > > There are unpopulated jumpers on the LaunchPad by J4 (J6 on the > > > Laumchpad) that have the same labels. I'm getting 2.7V on J4 pin 1, > > > which is strange. That's what powers the MRAMs and the temperature > > > sensor. > > > > > > Should I put a jumper on 3V3 by J4? I'm getting 3.3V on the other side > > > of the jumper. I'm wondering if the power is somehow coming through > the > > > 5043s and getting to the MRAMs, but I don't see how that could happen. > > > > > > > > > > > BTW, I don't even try to push Jim's board all the way on. It is > tight as > > > > it is and I want to be able to get it back off (relatively) easily. > But > > > > regardess, the tops of the pins are all level, even though the newly > > > > soldered pins have a plastic holder at the bottom and the original > pins do > > > > not. > > > > > > Yeah, strange. I didn't notice until I tried to put the board on. My > > > board now looks terrible, but it seems to be making good contact now. > > > > > > I looked at close-up pictures on TI's web site, and the pins I had look > > > the same as the ones in the picture. > > > > > > -corey > > > > > > > > > > > 73, > > > > > > > > Burns Fisher, WB1FJ > > > > *AMSAT(R) Engineering -- Flight Software* > > > > > > > > > > > > On Mon, May 8, 2023 at 11:52 PM Corey Minyard via pacsat-dev < > > > > pacsat-dev(a)amsat.org> wrote: > > > > > > > > > Burns sent me the info on that. I ran J5 pin 12 to a via on the > > > > > bottom right of U1. After doing that wiring change, all but one > MRAM > > > > > appears to be working. It looks like R5 got removed somehow, I may > > > > > have done that removing the wire. I just installed a bridge there, > > > > > since it's a zero-ohm resistor, and the mram seems to be working > now. > > > > > > > > > > The temperature sensor on the daughter board seems to be working. > > > > > > > > > > I don't think the 5043's are working. I'm not getting anything on > > > > > transmit, and I eventually get: > > > > > > > > > > Pacsat>send pb status > > > > > ## SELF TEST: pb_test_status > > > > > TX QUEUE FULL: Could not add UI frame to Packet Queue > > > > > PB Empty. > > > > > ## PASSED SELF TEST: pb_test_status > > > > > > > > > > after running that a few times. At startup, I'm getting: > > > > > > > > > > ERROR: In start_rx, axradio_init returned: 5 > > > > > ERROR: In start_tx, axradio_init_70cm returned: 5Initializing PB > Task > > > > > ERROR: Failed in init PB Status Timer > > > > > > > > > > -corey > > > > > > > > > > On Mon, May 8, 2023 at 9:51 PM Jim McCullers via pacsat-dev > > > > > <pacsat-dev(a)amsat.org> wrote: > > > > > > > > > > > > Chris, > > > > > > > > > > > > Please take a look at the email I sent out earlier. > > > > > > There is the possibility of a wiring error on the board with my > white > > > > > wire correction. > > > > > > > > > > > > As for the connectors being longer, I never noticed that and > these > > > > > should be the same connectors I sent Burns and Chris. > > > > > > Burns say the MRAM is working after the wiring change and the > AX5043s > > > > > are working for Chris and Burns so not certain there. > > > > > > > > > > > > Attached is the revised schematic. I'll have the Kicad files on > github > > > > > hopefully tomorrow. Have a couple of issues to deal with. > > > > > > > > > > > > Jim McCullers > > > > > > WA4CWI > > > > > > > > > > > > > > > > > > > > > > > > I sent this earlier, but just to Chris. > > > > > > > > > > > > I got my board today and soldered on the connectors. Looking at > the > > > > > board now, I see that the connectors that came with the launchpad > are > > > > > around 1cm longer than the ones Jim supplied. I can't get the > mram or > > > > > ax5043s to be detected. I don't think it's making good contact on > the > > > > > connectors, for obvious reasons. Do I need to trim the old > connector, or > > > > > did I do something wrong? > > > > > > > > > > > > I clipped the pins, and still no help. The power light by the > serial > > > > > connector works, and the serial port works. But the mrams and the > ax5043's > > > > > are not there. > > > > > > > > > > > > I can't find the schematics in the git repository. PacSatDocs, I > > > > > assume. I guess I need to start debugging to figure out what is > wrong. > > > > > > > > > > > > -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 > > > > > > > ----------------------------------------------------------- > > 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: PACSAT Operating Instructions
by Chris Thompson 10 May '23

10 May '23

DireWolf uses a config file. A template is supplied with the installation. It looks very complicated but you only have to change a very small amount. If you are using DireWolf in KISS mode you do not even need to set your callsign or Full Duplex. The ground station will do that when it connects to DireWolf. You do need to set the speed to 1200 or 9600, but I do that from the command line. I run DireWolf like this: direwolf -q d -B 9600 The -q d stops it printing APRS. The -B is the speed and can also be 1200. That means the only things you must set in the config file are the sound card and how to key the radio. When you run direwolf for the first time it prints out all the sound cards it can see and gives each a number. Note which numbers you want to use for Receive/Transmit. Then open the config file and edit the section labeled FIRST AUDIO DEVICE. Set the line ADEVICE to have the two sound card numbers after it. I have: ADEVICE 0 3 Which means sound card 0 for receive and soundcard 3 for transmit. You might be able to key the radio with VOX for testing. But I recommend keying it with a serial line. I use a DigiRig sound card that comes with a built in serial line setup to key the radio. But I have also used a serial line and a single transistor to key the radio. One advantage of the DigiRig is that he sells cables ready made for many radios. If you want to transmit outside of the shack then go into config.h in the PACSAT code and put in your own callsign. Also remember that it is transmitting and receiving 9600 bps packet on 70cms. This is currently hard coded but we should add a command to switch modes no doubt. If you want to change this then modify deviceSupport/ax5043-access.c - ax5043StartTx()/ax5043StartRx() to pass RATE_1200 vs RATE_9600 and update deviceSupport/ax5043-ax25.c - start_ax25_rx() - where the band is overridden to 70cms for receive. 2m will work for 1200bps but is very deaf for 70cms. Jim has solved this but the code fixes still need to be applied. 73 Chris On Mon, May 8, 2023 at 8:17 PM Burns Fisher (AMSAT) via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Ok, thanks. I saw a video about hooking up DireWolf to a BaoFeng radio, > and I have exactly that radio. I'm not sure about the PTT though. I could > also use my Kenwood D72--it does APRS, so it may even have a builtin TNC > for other purposes. > > 73, > > Burns Fisher, WB1FJ > *AMSAT(R) Engineering -- Flight Software* > > > On Mon, May 8, 2023 at 8:15 PM Chris Thompson via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> Yes, DireWolf to a sound card and then to a radio. You could test >> receive with an sdr as long as you can get the audio into DireWolf. >> >> I can provide details on DireWolf setup tomorrow. >> >> 73 >> Chris >> >> On Mon, May 8, 2023, 17:06 Burns Fisher (AMSAT) <wb1fj(a)fisher.cc> wrote: >> >>> I assume you need to connect DireWolf through a sound card to a radio >>> too. Or am I not following somthing? Your software does not do SDR like >>> FoxTelem, right? >>> 73, >>> >>> Burns Fisher, WB1FJ >>> *AMSAT(R) Engineering -- Flight Software* >>> >>> >>> On Mon, May 8, 2023 at 1:41 PM Chris Thompson via pacsat-dev < >>> pacsat-dev(a)amsat.org> wrote: >>> >>>> If you have received a PACSAT Booster Board from Jim, then here are >>>> some instructions for testing/using it. >>>> >>>> >>>> First make sure you have followed Burns instructions to install the IDE >>>> and flash the launchpad. You know this has worked when you have the >>>> console up and can type commands. When it tells you to type a command in >>>> these instructions, it means on the PACSAT Console. You can type help to >>>> show a list of commands. >>>> >>>> >>>> >>>> I suggest installing DireWolf on the same or another computer. You >>>> need to set it up to operate in full duplex at 9600bps. Initially you can >>>> use DireWolf to see you are receiving packets. Then you need to connect >>>> the ground station software by telling Pac Sat Ground that the TNC is >>>> connected to TCP port 8001, using the File > Settings screen. >>>> >>>> >>>> >>>> In the console type: >>>> >>>> *send pb status * >>>> >>>> >>>> >>>> This will transmit a packet and it should say PB Empty in DireWolf. >>>> >>>> >>>> >>>> Then type: >>>> >>>> *ls * >>>> >>>> >>>> >>>> This should show there are no files on the sat. If this does not work >>>> then type: >>>> >>>> *unmount fs* >>>> >>>> *format fs* >>>> >>>> *mount fs * >>>> >>>> >>>> >>>> In the console type: >>>> >>>> *make psf* >>>> >>>> >>>> This will create a set of test files >>>> >>>> >>>> >>>> Type: >>>> >>>> *ls * >>>> >>>> >>>> >>>> To list them. We now need to set the time before we load them into the >>>> directory. We dont have a real time clock so it needs to be set manually. >>>> >>>> >>>> >>>> Look up the current Unix time on the web. I use >>>> https://www.unixtimestamp.com/ >>>> >>>> Type: >>>> >>>> *set unix time <value> * >>>> >>>> >>>> >>>> Then you can type: >>>> >>>> *load dir * >>>> >>>> >>>> >>>> This will load the files into the directory and set their upload time. >>>> In the future PACSAT will load the directory at boot. Probably once we >>>> have a real time clock in place. >>>> >>>> Type : >>>> >>>> *list dir * >>>> >>>> >>>> >>>> This will list all the files in the directory. Now when you reset the >>>> satellite the files will still be in the file system with the correct >>>> upload time, but the directory will be empty. You can type: >>>> >>>> *load dir * >>>> >>>> >>>> >>>> Without having to set the Unix Time, and it will load the files and >>>> remember their upload time. >>>> >>>> >>>> >>>> In the Pacsat ground station you can press the DIR button if the PB is >>>> available, i.e. you are not already on the PB. If it thinks you are on the >>>> PB then you can type this on the console: >>>> >>>> *send pb status * >>>> >>>> >>>> >>>> If you press the DIR button it should request the directory and >>>> download all the headers. If you interrupt the download then subsequent >>>> requests will ask for the holes in the directory. >>>> >>>> >>>> >>>> You can press the FILE button to download a file . Either type the >>>> file number you want in the box or click on the file in the directory to >>>> populate the box. You can also give a file a download priority by pressing >>>> numbers 1-9. See the manual for Details. >>>> >>>> >>>> >>>> Feel free to ask any questions. >>>> >>>> >>>> 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 >> > > ----------------------------------------------------------- > > 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

2 4

Re: Newest PACSAT daughter board
by Bob Stricklin 10 May '23

10 May '23

I received the board. I have soldered on the connectors and made the little wiring change you indicated Jim. It all looks very nice. I have not done any testing yet but will try to do some soon. Thanks for all your efforts. Bob On May 8, 2023, at 9:42 PM, Jim McCullers via pacsat-dev <pacsat-dev(a)amsat.org<mailto:pacsat-dev@amsat.org>> wrote: Burns has informed me I reversed my own directions and MRAM fix may not be correct. Please review the attached images and if the board you received looks like the ‘Before’ image break out the soldering iron and swap them. The correct wiring is the ‘After’ image. I write directions much better than I follow them, even my own. Burns reports with the changes the AX5043 are ranging correctly and the MRAM works. Jim McCullers WA4CWI <After.jpeg><Before.jpeg> ----------------------------------------------------------- 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: PACSAT Operating Instructions
by Burns Fisher (AMSAT) 10 May '23

10 May '23

Ok, glad the MRAM is working. Any chance that you don't have the two jumpers on the LaunchPad required to power the 5043s? These would be a pair on the right (components up, USB down, I think) just below the bottom set of pins. BTW, I don't even try to push Jim's board all the way on. It is tight as it is and I want to be able to get it back off (relatively) easily. But regardess, the tops of the pins are all level, even though the newly soldered pins have a plastic holder at the bottom and the original pins do not. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Mon, May 8, 2023 at 11:52 PM Corey Minyard via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Burns sent me the info on that. I ran J5 pin 12 to a via on the > bottom right of U1. After doing that wiring change, all but one MRAM > appears to be working. It looks like R5 got removed somehow, I may > have done that removing the wire. I just installed a bridge there, > since it's a zero-ohm resistor, and the mram seems to be working now. > > The temperature sensor on the daughter board seems to be working. > > I don't think the 5043's are working. I'm not getting anything on > transmit, and I eventually get: > > Pacsat>send pb status > ## SELF TEST: pb_test_status > TX QUEUE FULL: Could not add UI frame to Packet Queue > PB Empty. > ## PASSED SELF TEST: pb_test_status > > after running that a few times. At startup, I'm getting: > > ERROR: In start_rx, axradio_init returned: 5 > ERROR: In start_tx, axradio_init_70cm returned: 5Initializing PB Task > ERROR: Failed in init PB Status Timer > > -corey > > On Mon, May 8, 2023 at 9:51 PM Jim McCullers via pacsat-dev > <pacsat-dev(a)amsat.org> wrote: > > > > Chris, > > > > Please take a look at the email I sent out earlier. > > There is the possibility of a wiring error on the board with my white > wire correction. > > > > As for the connectors being longer, I never noticed that and these > should be the same connectors I sent Burns and Chris. > > Burns say the MRAM is working after the wiring change and the AX5043s > are working for Chris and Burns so not certain there. > > > > Attached is the revised schematic. I'll have the Kicad files on github > hopefully tomorrow. Have a couple of issues to deal with. > > > > Jim McCullers > > WA4CWI > > > > > > > > I sent this earlier, but just to Chris. > > > > I got my board today and soldered on the connectors. Looking at the > board now, I see that the connectors that came with the launchpad are > around 1cm longer than the ones Jim supplied. I can't get the mram or > ax5043s to be detected. I don't think it's making good contact on the > connectors, for obvious reasons. Do I need to trim the old connector, or > did I do something wrong? > > > > I clipped the pins, and still no help. The power light by the serial > connector works, and the serial port works. But the mrams and the ax5043's > are not there. > > > > I can't find the schematics in the git repository. PacSatDocs, I > assume. I guess I need to start debugging to figure out what is wrong. > > > > -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 >

2 6