#apertus IRC Channel Logs

hi

good day

who is here?

hi

great

yea!

I am trying to run visulizer in windows.. but last 2 days have been bit depressing.. above is the progress so far..

yea.. :D I know its not a good or of much use, since BAandiT1983 had added docker.. but still.. thought it might help some one..in future

I was about to ask why this was necessary yes :)

I don;t know, to be honest.. before it was useful , because there was no docker container..

but since i have started it, will finish it by tommrrow, maybe someday it might be of use..

btw whats the state with the finished tasks, keyboard for example?

it was crashing, but it is not related to the keyboard at first

yes, the known heap/stack problem we are facing currently I assume

Shohei: would you like to report next?

I’m afraid I don’t have finished tasks this week, but reviewing the designs of PCB holding brackets and Front plate. It’s very exciting for me :)

That's all from my side. Thank you:)

for reference: I created two mechanical parts (adaptions) for the AXIOM Beta compact enclosure

BAndiT1983: would you like to report/share?

please :)

besides that was guiding the students, creating some prototypes, that would be it

yep

xc32 is already installed there?

yes

haven't found any restrictions there with unattended install and free license, many such containers already exist, but that's also why i want to move to free toolchain like ARM GCC

UART works, USB is slowly progressing, as i'm a bit limited with time currently, wanted to test also SPI soon, as i have fitting display here, would like to test one with parallel interface, but maybe later

ok, thanks!

next week ;)

right :)

CAD design progress as shared above

*assemble

thats it from my side, Bertl the closer?

well, I've been chasing ghosts and fighting windmills for the last few days trying to identify problems on the remote beta and hardware we got from felix

note that there were definitely some problems on each and every changed aspect but I haven't found and fixed everything yet

unfortunately my righ to reflow the sockets broke yesterday, so I'm currently fixing that (light-bulb ala malcolm-in-the-middle style :)

that's it from my side for this week, hopefully more positive news next week

anyone else who wants to report progress/share/etc.?

excellent satacker[m]!

coding guidelines are for C++, Bertl would kill me if i try to teach you that

https://www.kernel.org/doc/html/v4.10/process/coding-style.html

ok then MEETING CONCLUDED!

Thanks :)

Thank you

good evening!

what changes do i need to make in "Remote_Firmware_Visualizer' repo in order to run it locally on my system(windows 10) ,also i can not enable hyper-v vartualisation in my PC as i enabled virtualization through BIOS my PC ran into problem,even i tried to reset my PC but at last i had to disable virtualization mode to bring my PC back in normal mode ,working properly.

sounds like you need a new computer or a better operating system

visualiser should be buildable with some adjustments, mostly regarding SDL2 on windows, you need to download it and unpack, then probably point to it in cmake script

mingw? std::thread is pretty standard and should also work under windows with MSVC++

http://www.cplusplus.com/forum/general/267237/

what is unistd.h used for?

would certainly help

yeah, some changes were rather workarounds, as we needed quick solutions at some points

eppisai: by the way, you can comment unistd.h out, as it is just belonging to some prototype code, which got pulled into the dev branch

markusengsner: this one looks interesting -> https://www.sourcetrail.com/

but that's the first step one needs to do, check what affects the build, jumping to another compiler won't help as you need to understand the basics of the module first

*approached

am already on it ;) am trying to connect with vscode to the appimage server

*select from VSCode

but usually i prefer clang to gcc, as it has pretty nice analysis built in

;)#

you have also to add Bootloader as source folder, was also done as workaround, as our BL hasn't been developed further yet

but in the future it should be some sort of BIOS, which controls the hardware and e.g. firmware will ask it to draw to display

https://github.com/apertus-open-source-cinema/AXIOM-Remote/blob/37c4abbc94b6f437ef396919e093d907cd2ce4f7/AXIOM_Remote_Firmware_Visualizer/Main.cpp#L115

what about the line?

like i said before, this line was added for the prototype, which would use serial port/socket ot communicate to the programmer script or to some mock service written in python, which would simulate the service on the camera

there is not much a problem with docker, but with unclear possibility to install the compiler there, either the install file will be in the container and installed on first startup, in text mode to show the license agreement to the user, just need to check how to persist the data, otherwise it will install at every startup