Many thanks!

Great idea!

Very good idea, thought about checkbox styling for that, also because of states, but haven't thought about searching for examples.

what about checkboxes? they can be styled with css, so they look like toggle switches: https://codepen.io/mburnette/pen/LxNxNg

Install script is already in repo. One for RESTServer will follow at some point.

Moved related parts of code and started adding unit tests.

Added install_daemon.sh script.

Added Main.cpp, adjusted RESTServer code accordingly.

herbert confirmed these are the latest versions:

Did you run it with root privileges?

Error at line 79, file devmem2.c (13) [Permission denied]

2. then the camera is shipped with a bunch of random crap on it. the end result should be just the calibration files.

1. lets do it one step at a time

1. i suggest calling it factory_calibration.sh (or similar) as i intended it to do all calibrations needed before the camera get's shipped to the customer

Those are valid points indeed.

• a program is easier to find on github
• commit messages and issues are related to the one program
• we can configure a CI (like Travis/Gitlab CI) to test, build and package the program, needs a YAML file per repo (there you select one language and get the build tools)
• you can use git tags to tag releases
• it's easier to use git bisect to debug in which commit a bug was introduced

What would be the advantage compared to how we have it currently (multiple applications in one repo)?

Closed in favour of T757. If this is wrong, just reopen this task.

fine for me as well

reference and close?

merge in or move to subtask?

So close the other two tasks?

Should the control daemon replace T258 and T723?

Should the control daemon replace T258 and T723?

I think so.

Can this be closed?

I think a ubuntu docker container with the required tools installed would be simple to create (this is the current solution for the ci-builds). However, I think, that distributing xilinx tools implys some licensing and export-control related issues. The simplest way to deal with them would be to just ignore those or make the container somehow protected.

When T697 is finished

The original task is done. The mentioned binaries are linked to /user/local/bin as axiom-* by make install

Hi everybody,
I asked to steadxp if they can say to us which component they use. No answer yet but i will tell you if i have one !

https://www.xsens.com/products/mti-1-series/ for 260€ plus VAT

done

@sebastian could you please remove the URL, as it shouldnt be public ;)

This is the current push URL of the github webhook:

Wow, that's great progress you made here!

Yes! Just now i created this (https://github.com/apertus-open-source-cinema/beta-software/pull/7) pull Request. If you want to bring the work on this forwards, you could test this (https://gitlab.com/nein/beta-software/-/jobs/38788789/artifacts/download) image and report your findings. edit: bertl is already doing this.

In my opinion, no. This would just multiply number of repos, which increases difficulty of maintenance afterwards.