search

RobertK66 / obc_1769_core

Implements hardware abstractions and Layer2(3) modules for usage of the OBC hardware in cubesat projects
GNU General Public License v3.0
1 stars 1 forks source link

Only utf-8 should be printed to debug uart for radtest #40

Closed kodsurf closed 1 year ago

kodsurf commented 1 year ago

All characters that are sent over debug uart has to be utf-8 (ascii)

Non ascii charachet received by rasbery pi would trigger "try, except" failed to read com port error image

Log file from raspberry pi shows this error catched by python try except image

kodsurf commented 1 year ago

image

I checked the latest "developer" branch code merged by Robert.

All output is indeed utf-8 now.

We will reflash the OBC again tommorow (17.08) and try to see if error fixed.

P.S - Looks like pure_print_debug() without non ascii event id bytes was actually neccessary to be written :)

kodsurf commented 1 year ago

@RobertK66 can you please confirm with your updates regarding sensor output code that there will be no utf-8 symbols ?

Otherwise we would have to change python code to proccess binary data. Which is much more complicated then changing it on OBC side...

RobertK66 commented 1 year ago

Yes I did this when merging the code with your pure_print_debug() I found. The Magic is done in line 127-147 of L7_climb_app.c

We now have the rtst_eventoutput(event_t event) function where we can translate events to pure ASCII strings output for the radtest

RobertK66 commented 1 year ago

I also remember now how we did the analyses after the tests last time:

Each line with some useful values (e.g. the Sensor Line) is now formatted as ';' separated string. This together with the header (output with rtst_init() ) can be used to be simply loaded into an Excel where the values then can be analyzed -> into diagrams or whatever.

So I plan to use this format also for the 'results' (Counters,bit error counters ) of the memory tests. The first field is the 'type of record' text.

kodsurf commented 1 year ago

Here are the log photo from test carried out by Abbas today, with latest develop branch code

image

@RobertK66 Please verify that debug uart works as intended for the test.

RobertK66 commented 1 year ago

I can't verify that ;-). I never saw the screen you show here. I only got log files from Andi after the test, and I analysed my memory stuff with Excel then.

Do you have text files where you can read all the sensor values written afterwards? Are the values feasable (temp, voltage, current)? Ah, I see now. Its already in 'Excel Tab form. So the values look good to me.

RobertK66 commented 1 year ago

I think this is okay already with current developer branch.