fossasystems / fossasat-1 Goto Github PK

have seen that you are using a watchdog chip (MAX6369KA), but this chip is not needed as all AtMega's have a build in watchdog which can be used too and is doing exactly the same: resetting the chip if it is not responding anymore.

Thank you for the updates to the Arduino code for FossaSat-1!

Using commit 70ef487, I get the following error. Please note that 'FOSSA-Comms' is up-to-date as of the current commit which is 1fc86e2 at the date of this post.

Thank you very much!

-Scott, K4KDR

/home/k4kdr/Arduino/libraries/FOSSA-Comms/src/FOSSA-Comms.cpp: In function 'int16_t FCP_Get_OptData_Length(char*, uint8_t*, uint8_t, const uint8_t*, const char*)':
/home/k4kdr/Arduino/libraries/FOSSA-Comms/src/FOSSA-Comms.cpp:57:5: error: 'aes128_dec_multiple' was not declared in this scope
     aes128_dec_multiple(key, encSection, encSectionLen);
     ^~~~~~~~~~~~~~~~~~~
/home/k4kdr/Arduino/libraries/FOSSA-Comms/src/FOSSA-Comms.cpp: In function 'int16_t FCP_Get_OptData(char*, uint8_t*, uint8_t, uint8_t*, const uint8_t*, const char*)':
/home/k4kdr/Arduino/libraries/FOSSA-Comms/src/FOSSA-Comms.cpp:141:5: error: 'aes128_dec_multiple' was not declared in this scope
     aes128_dec_multiple(key, encSection, encSectionLen);
     ^~~~~~~~~~~~~~~~~~~
/home/k4kdr/Arduino/libraries/FOSSA-Comms/src/FOSSA-Comms.cpp: In function 'int16_t FCP_Encode(uint8_t*, char*, uint8_t, uint8_t, uint8_t*, const uint8_t*, const char*)':
/home/k4kdr/Arduino/libraries/FOSSA-Comms/src/FOSSA-Comms.cpp:245:5: error: 'aes128_enc_multiple' was not declared in this scope
     aes128_enc_multiple(key, encSection, encSectionLen + paddingLen);
     ^~~~~~~~~~~~~~~~~~~
Multiple libraries were found for "RadioLib.h"
 Used: /home/k4kdr/Arduino/libraries/RadioLib
Multiple libraries were found for "SPI.h"
 Used: /home/k4kdr/Downloads/arduino/arduino-1.8.10/hardware/arduino/avr/libraries/SPI
Multiple libraries were found for "SoftwareSerial.h"
 Used: /home/k4kdr/Downloads/arduino/arduino-1.8.10/hardware/arduino/avr/libraries/SoftwareSerial
Multiple libraries were found for "FOSSA-Comms.h"
 Used: /home/k4kdr/Arduino/libraries/FOSSA-Comms
Multiple libraries were found for "AESLib.h"
 Used: /home/k4kdr/Arduino/libraries/AESLib
Using library RadioLib at version 1.7.0 in folder: /home/k4kdr/Arduino/libraries/RadioLib 
Using library SPI at version 1.0 in folder: /home/k4kdr/Downloads/arduino/arduino-1.8.10/hardware/arduino/avr/libraries/SPI 
Using library SoftwareSerial at version 1.0 in folder: /home/k4kdr/Downloads/arduino/arduino-1.8.10/hardware/arduino/avr/libraries/SoftwareSerial 
Using library FOSSA-Comms at version 1.0.0 in folder: /home/k4kdr/Arduino/libraries/FOSSA-Comms 
Using library AESLib at version 1.0.5 in folder: /home/k4kdr/Arduino/libraries/AESLib 
exit status 1
Error compiling for board Arduino/Genuino Uno.

The pin allocations for the simulator are;

#define RADIO_DIO0 2
#define RADIO_DIO1 3
#define RADIO_BUSY 9

When using an SX126x, do you need to connect its DIO1 pin to the pin defined as RADIO_DIO0 ?

Due to a cast from int16_t to uint8_t, only LSB of charging current is sent during RTTY system info transmission:

Also, current RTTY system info prints out letter shift symbol at the end of each hex-encoded byte. This makes transmission longer than it needs to be (although easier to decode in some cases).

Hi Dears ,

My name is Mouhamadou and I'm Telco student engineer (Final year) and cubesat/nanosat Enthousiast . I'm using the fossasystem documentation to learn and build one for my TFM.

The dimensions of the Antenna Solar Panel are missing in the gerber file. It produces an error when I try to open it in Kicad and when i try to order in Easy EDA

Regards
Mouhamadou

Sorry if this is not the right place to report a problem for http://groundstationdatabase.com/registerStation.php but I couldn't find any other place.

I am unable to register. The "Optional" Name if the institution seems to be mandatory, and I am not able to enter a valid gps location. The validation message doesn't offer any information on what it considers valid.

In the file "FOSSASAT-1/Code/FossaSat1/power_control.cpp", in the function "Power_Control_INA2256_Check()", there is Wire.beginTransmission() just before the Wire.requestFrom(). That Wire.beginTransmission() may be removed.
The timeout after the Wire.requestFrom() may be removed as well.

Explanation: Common-mistakes, number 1 and 3.

This section:

  // try to read
  Wire.beginTransmission(INA_ADDR);
  Wire.requestFrom((uint8_t)INA_ADDR, (uint8_t)2);
  uint32_t start = millis();
  while(!Wire.available()) {
    if(millis() - start >= INA_TIMEOUT) {
      // timed out
      return(false);
    }
  }

can be reduced to:

  // try to read
  Wire.requestFrom((uint8_t)INA_ADDR, (uint8_t)2);

If you want to check if the data was received, then you can do this:

  // try to read
  Wire.requestFrom((uint8_t)INA_ADDR, (uint8_t)2);
  if(Wire.available() != 2) {
    return(false);
  }

or this:

  // try to read
  if(Wire.requestFrom((uint8_t)INA_ADDR, (uint8_t)2) != 2)
    return(false);

Hi
I want to ask if Fossate-1 is still working now?

hi all
Is there any S Band transmetere in maeket that can add to this pico sat?
i searched but only s band transmetere for cube sat is avalable (size pc104 )

PDFs aren't even usable with manufacturers. That would require the gerber files.

But even then, the hardware is not currently open source without the original Altium/Kicad/Eagle/etc. files that can be modified or improved upon by outside individuals.

Hello,

I'm currently researching transceivers for nano/pico-satellites. Looking at your design for FOSSASat-1's beacon, the BOM and schematic say that the transceiver is a "SX1278T", with a SX1262/68 footprint. Based on your flight hardware pictures this seems to be some sort of PCB breakout board using the Semtech SX1278. However, searching the internet I haven't found anything with the specific model name "SX1278T".

What model exactly did you use for this project?

I've been struggling to get an Adafruit RFM96 module to work with your code. One issue appears to be with the sync word 0X0F0F. Since RadioLib's RFM9x support is based on the SX127x, when you dropped support for the SX127x (issue 10), that also dropped support for the RFM9x family. May I suggest you update the documentation on Github and in your Communications Guide to reflect this fact.

Using commit a5fddca, the following error appears on VERIFY:

/home/k4kdr/Arduino/libraries/FOSSA-Comms/src/FOSSA-Comms.h:5:10: fatal error: AESLib.h: No such file or directory
 #include <AESLib.h>

... after installing AESLib, (manually from https://github.com/DavyLandman/AESLib), the code will VERIFY & UPLOAD without error.

You may wish to add library "AESLib" to the list of required libraries if that is correct.

Thank you!

-Scott, K4KDR

The current SX126x sync word (0x0F0F) does not match with any sync word supported by SX127x. Apparently, when using 0x1424 as the sync word, the SX127x will match as long as the 4 MSb are 0x1 or the 4 LSb are 0x2 - though some combinations are more reliable than the others, for example 0x11 - 0x1F match every time.

I want to ask how to interact with the satellite.

Hi, I could not find reference that the SPV1040 can be used directly as a CC CV LiON battery charger. Although in the circuit, you have directly connected it to the battery. Should we not hook up SPV1040 with a CC CV LiOn charger IC?

Another point is that R1 and R2 would make the output be 3.7V which is not the max voltage the battery can be charged upto. Is it a conscious decision or am I missing something?

Referring this :

Hi @Bambofy, did you know that KiteLib supports RTTY directly? You don't have to implement it yourself ;)

All you have to do to change from LoRaLib to KiteLib is to replace the included file

#include <KiteLib.h>

and the constructor

SX1278 lora = new Module(cs, dio0, dio1);

Because KiteLib is built on top of LoRaLib, nothing in the API changes, so those two things are literally the only two lines of code you have to change.

After that, you can use the RTTY just as easily as Arduino Serial port:

RTTYClient rtty(&lora);

rtty.begin(freq, shift, baudRate, dataBits, stopBits);
rtty.println("Hello World!");

Hi Dears ,

My name is Mouhamadou and I'm Telco student engineer (Final year) and cubesat/nanosat Enthousiast . I'm using the fossasystem documentation to learn and build one for my TFM.

The dimensions of the Antenna Solar Panel are missing in the gerber file. It produces an error when I try to open it in Kicad and when i try to order in Easy EDA

Regards
Mouhamadou

Question or possible issue ref. the command:

r - send message to be retransmitted

When a simple string is transmitted, the Simulator reply is initially as expected:

00:03:38.314 -> Got repeated message:
00:03:38.366 -> hello

... but when you send additional messages, the reply can include extra characters:

00:05:05.545 -> Got repeated message:
00:05:05.579 -> hello again⸮⸮⸮&�

... and the really strange reply comes when a short message is sent AFTER a longer message:

00:07:20.852 -> Got repeated message:
00:07:20.852 -> 123456789_123456789_12345ds⸮⸮⸮

00:08:01.194 -> Got repeated message:
00:08:01.229 -> hi there9_12345�

... perhaps is something in either the GroundStation code or the Simulator code not clearing out a buffer between re-transmitted messages? Also, in certain circumstances, the re-transmission from the simulator dumps dozens or hundreds of characters - I assume an overflow condition of some kind?

Of course this is not a big deal and I only bring it to your attention in case the spacecraft code behaves like the simulator code in this regard. NOT a priority, obviously; just wanted to share my observation as we anxiously await the launch.

Great to see so many people registered on the Ground Station site now!

-Scott, K4KDR