Pacsat dev mtg
Thu, Mar 21, 2024 7:00 PM - 9:00 PM (CDT)
Please join my meeting from your computer, tablet or smartphone.
https://meet.goto.com/221290045
You can also dial in using your phone.
(For supported devices, tap a one-touch number below to join instantly.)
United States: +1 (646) 749-3122
- One-touch: tel:+16467493122,,221290045#
Access Code: 221-290-045
Join from a video-conferencing room or system.
Dial in or type: 67.217.95.2 or inroomlink.goto.com
Meeting ID: 221 290 045
Or dial directly: 221290045(a)67.217.95.2 or 67.217.95.2##221290045
Get the app now and be ready when your first meeting starts:
https://meet.goto.com/install
Hi Bill,
There are two ways.
Firstly, it can send telemetry bytes in a UI packet. We already do this
today and there is some telemetry that accumulates in the telemetry tab.
It has not yet been updated to reflect all 4 receivers.
Secondly, it can store telemetry in a file for later download. This will
give telemetry across the orbit or Whole Orbit Data. This has not been
implemented but the framework is in place.
73
Chris
On Thu, Mar 21, 2024, 12:10 Bill Reed <bill(a)brconnect.com> wrote:
> How can a satellite ihu send telemetry via pacsat. I would assume
> commands via the pacsat console?
>
> Bill
> On 3/21/2024 10:55 AM, Chris Thompson via pacsat-dev wrote:
>
> I have pushed version X0.2c to main. This includes the Digipeater.
>
> You can check the status of the digipeater with:
> get status
>
> You can turn it on and off from the console with:
> open digi
> shut digi
>
> You can send a ground command from the version 0.46f of pacsat ground,
> which can be downloaded here:
> https://www.g0kla.com/pacsat/
>
> The digipeater requires the via callsign to equal the callsign as setup in
> the code. To simplify that I now print the callsigns at boot into the
> console.
>
> I tested this with UISS, but would appreciate other tests.
>
> The digi is on or off for all receiver channels. We probably want to be
> able to turn it on for just one of them, so I have reserved 4 bytes in MRAM
> to hold some mode bits for each receiver channel. We can then configure a
> channel to be command only, or to optionally support broadcast, uplink or
> digi packets. The bytes are there but the rest of the code and commands
> needs to be written. Given I inserted new bytes you will need to run pre
> flight init or maybe even init new proc.
>
> With that said, I won't be able to make the meeting tonight due to a clash
> with another meeting. Send questions or comments here via email. We can
> also discuss next time.
>
> 73
> Chris
>
> --
> Chris E. Thompson
> chrisethompson(a)gmail.com
> g0kla(a)arrl.net
>
>
> -----------------------------------------------------------
>
> pacsat-dev mailing list -- pacsat-dev(a)amsat.org
> View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected]
> To unsubscribe send an email to pacsat-dev-leave(a)amsat.org
> Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
>
>
This all sounds very cool.
I will do some testing.
Bob
On Mar 21, 2024, at 10:55 AM, Chris Thompson via pacsat-dev <pacsat-dev(a)amsat.org> wrote:
I have pushed version X0.2c to main. This includes the Digipeater.
You can check the status of the digipeater with:
get status
You can turn it on and off from the console with:
open digi
shut digi
You can send a ground command from the version 0.46f of pacsat ground, which can be downloaded here:
https://www.g0kla.com/pacsat/
The digipeater requires the via callsign to equal the callsign as setup in the code. To simplify that I now print the callsigns at boot into the console.
I tested this with UISS, but would appreciate other tests.
The digi is on or off for all receiver channels. We probably want to be able to turn it on for just one of them, so I have reserved 4 bytes in MRAM to hold some mode bits for each receiver channel. We can then configure a channel to be command only, or to optionally support broadcast, uplink or digi packets. The bytes are there but the rest of the code and commands needs to be written. Given I inserted new bytes you will need to run pre flight init or maybe even init new proc.
With that said, I won't be able to make the meeting tonight due to a clash with another meeting. Send questions or comments here via email. We can also discuss next time.
73
Chris
--
Chris E. Thompson
chrisethompson(a)gmail.com<mailto:[email protected]>
g0kla(a)arrl.net<mailto:[email protected]>
-----------------------------------------------------------
pacsat-dev mailing list -- pacsat-dev(a)amsat.org
View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected]
To unsubscribe send an email to pacsat-dev-leave(a)amsat.org
Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
I have pushed version X0.2c to main. This includes the Digipeater.
You can check the status of the digipeater with:
get status
You can turn it on and off from the console with:
open digi
shut digi
You can send a ground command from the version 0.46f of pacsat ground,
which can be downloaded here:
https://www.g0kla.com/pacsat/
The digipeater requires the via callsign to equal the callsign as setup in
the code. To simplify that I now print the callsigns at boot into the
console.
I tested this with UISS, but would appreciate other tests.
The digi is on or off for all receiver channels. We probably want to be
able to turn it on for just one of them, so I have reserved 4 bytes in MRAM
to hold some mode bits for each receiver channel. We can then configure a
channel to be command only, or to optionally support broadcast, uplink or
digi packets. The bytes are there but the rest of the code and commands
needs to be written. Given I inserted new bytes you will need to run pre
flight init or maybe even init new proc.
With that said, I won't be able to make the meeting tonight due to a clash
with another meeting. Send questions or comments here via email. We can
also discuss next time.
73
Chris
--
Chris E. Thompson
chrisethompson(a)gmail.com
g0kla(a)arrl.net
This is clear and helpful.
Thanks
On Mar 14, 2024, at 8:45 PM, Chris Thompson via pacsat-dev <pacsat-dev(a)amsat.org<mailto:[email protected]>> wrote:
I pushed my latest code to main including the fix to the TX channel number.
Here is my decode of the RX devices.
RX Channel C – 145.840
0 - U405
Single Ended
35 N2HET1_9 AX5043_SEL3 U405-14 RX3 SEL Position 0
22 GIOA_7 AX5043_IRQ_RX3 U405-19 RX3_IRQ Position 0
AX5043 RX Device 3 - AX5043Dev2
RX Channel B – 145.810
1 - U305
Differential
33 N2HET1_7 AX5043_SEL2 U305-1 RX2 Select Position 1
126 GOIB_0 AX5043_IRQ_RX2 U305-19 RX2 IRQ` Position 1
AX5043 RX Device 2 - AX5043Dev1
RX Channel A – 145.780
2 - U205
Differential
24 N2HET1_3 AX5043_SEL1 U205-14 RX1_SEL Position 2 --- CONMFIRMED SIGNAL
5 GIOA_1 AX5043_IRQ_RX1 U205-19 RX1_IRQ Position 2
AX5043 RX Device 1 - AX5043Dev0
RX Channel D – 145.870
3 - U505
Differential
36 N2HET1_4 AX5042_SEL4 U505-14 RX4 SEL Position 3
14 GIOA_5 AX5043_IRQ_RX4 U505-19 RX4_IRQ Position 3
AX5043 RX Device 4 - AX5043Dev3
73
Chris
--
Chris E. Thompson
chrisethompson(a)gmail.com<mailto:[email protected]>
g0kla(a)arrl.net<mailto:[email protected]>
-----------------------------------------------------------
pacsat-dev mailing list -- pacsat-dev(a)amsat.org<mailto:[email protected]>
View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected]
To unsubscribe send an email to pacsat-dev-leave(a)amsat.org<mailto:[email protected]>
Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
I pushed my latest code to main including the fix to the TX channel number.
Here is my decode of the RX devices.
RX Channel C – 145.840
0 - U405
Single Ended
35 N2HET1_9 AX5043_SEL3 U405-14 RX3 SEL Position 0
22 GIOA_7 AX5043_IRQ_RX3 U405-19 RX3_IRQ Position 0
AX5043 RX Device 3 - AX5043Dev2
RX Channel B – 145.810
1 - U305
Differential
33 N2HET1_7 AX5043_SEL2 U305-1 RX2 Select Position 1
126 GOIB_0 AX5043_IRQ_RX2 U305-19 RX2 IRQ` Position 1
AX5043 RX Device 2 - AX5043Dev1
RX Channel A – 145.780
2 - U205
Differential
24 N2HET1_3 AX5043_SEL1 U205-14 RX1_SEL Position 2 --- CONMFIRMED
SIGNAL
5 GIOA_1 AX5043_IRQ_RX1 U205-19 RX1_IRQ Position 2
AX5043 RX Device 1 - AX5043Dev0
RX Channel D – 145.870
3 - U505
Differential
36 N2HET1_4 AX5042_SEL4 U505-14 RX4 SEL Position 3
14 GIOA_5 AX5043_IRQ_RX4 U505-19 RX4_IRQ Position 3
AX5043 RX Device 4 - AX5043Dev3
73
Chris
--
Chris E. Thompson
chrisethompson(a)gmail.com
g0kla(a)arrl.net
Attached is a short discussion document for the Digipeater.
73
Chris
On Thu, Mar 14, 2024 at 2:26 PM Bill via pacsat-dev <pacsat-dev(a)amsat.org>
wrote:
> Pacsat dev mtg 3-14-2024
> Thu, Mar 14, 2024 7:00 PM - 9:00 PM (CDT)
>
> Please join my meeting from your computer, tablet or smartphone.
>
> https://meet.goto.com/987217125
>
> You can also dial in using your phone.
> (For supported devices, tap a one-touch number below to join instantly.)
>
> United States: +1 (872) 240-3412
> - One-touch: tel:+18722403412,,987217125#
>
> Access Code: 987-217-125
>
> Join from a video-conferencing room or system.
> Dial in or type: 67.217.95.2 or inroomlink.goto.com
> Meeting ID: 987 217 125
> Or dial directly: 987217125(a)67.217.95.2 or 67.217.95.2##987217125
>
>
> 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/[email protected]
> To unsubscribe send an email to pacsat-dev-leave(a)amsat.org
> Manage all of your AMSAT-NA mailing list preferences at
> https://mailman.amsat.org
>
--
Chris E. Thompson
chrisethompson(a)gmail.com
g0kla(a)arrl.net
My other meeting is tonight so I won't be there.
73,
Burns Fisher, WB1FJ
*AMSAT(R) Engineering -- Flight Software*
On Thu, Mar 14, 2024 at 2:26 PM Bill via pacsat-dev <pacsat-dev(a)amsat.org>
wrote:
> Pacsat dev mtg 3-14-2024
> Thu, Mar 14, 2024 7:00 PM - 9:00 PM (CDT)
>
> Please join my meeting from your computer, tablet or smartphone.
>
> https://meet.goto.com/987217125
>
> You can also dial in using your phone.
> (For supported devices, tap a one-touch number below to join instantly.)
>
> United States: +1 (872) 240-3412
> - One-touch: tel:+18722403412,,987217125#
>
> Access Code: 987-217-125
>
> Join from a video-conferencing room or system.
> Dial in or type: 67.217.95.2 or inroomlink.goto.com
> Meeting ID: 987 217 125
> Or dial directly: 987217125(a)67.217.95.2 or 67.217.95.2##987217125
>
>
> 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/[email protected]
> To unsubscribe send an email to pacsat-dev-leave(a)amsat.org
> Manage all of your AMSAT-NA mailing list preferences at
> https://mailman.amsat.org
>
Pacsat dev mtg 3-14-2024
Thu, Mar 14, 2024 7:00 PM - 9:00 PM (CDT)
Please join my meeting from your computer, tablet or smartphone.
https://meet.goto.com/987217125
You can also dial in using your phone.
(For supported devices, tap a one-touch number below to join instantly.)
United States: +1 (872) 240-3412
- One-touch: tel:+18722403412,,987217125#
Access Code: 987-217-125
Join from a video-conferencing room or system.
Dial in or type: 67.217.95.2 or inroomlink.goto.com
Meeting ID: 987 217 125
Or dial directly: 987217125(a)67.217.95.2 or 67.217.95.2##987217125
Get the app now and be ready when your first meeting starts:
https://meet.goto.com/install
