#apertus IRC Channel Logs

meeting in 90 minutes - we recently switched to summer time I hope that didnt create any confusion

welcome everyone!

\o/

_o_

I will then hand the "priviledge" from one person to the other in an orderly manner :)

se6ast1an sure

that is https://github.com/apertus-open-source-cinema/elmyra for everyone who's not familiar with it

i've refurbished the technical basis of it over the last half year

all the frontend stuff updated to latest versions (which at javascript ecosystem pace means everything is probably outdated by now already anyway :))

if there are any questions (i don't know if the format permits them anyway) let me know :)

cool, so unles there are quick questions that concludes my report

yes there is versinoning now (before there were only commit hash identified releases)

(as little changed)

yes it's out there for people to pick up

it can be used either way now

yes it's an experimental technical foundation

it works quite reliably but it's not a polished product

but probably some sanity stuff like rendering priority

I tried version 1 today and captured some screenshots: https://cloud.apertus.org/index.php/apps/gallery/s/dJEK7f56ZFfZ6py

And is there anything you think requires improvement?

mostly the stuff i mentioned

it has to be molded into an actual product i guess

right now it's a conceptual foundation

it's not geared towards some final definitive workflow

many thanks simon! anything else to add ?

great!

sure, so we've started making the presentation on axiom beta board and remote and it'll be ready by the end of this week.

i think that's it from me :)

\o/

again thank you for that :D

My report would be a sort of reduced version of last weeks. Should have some new stuff I wanna mention soon.

Wiki - Someone who knows what's going on with all aspects of AXIOM Remote should update the status on its main page as 'Nov 2018' makes things look bad. Requested 10.04.20.

we will get there soon

yes

The only other thing I've noted is:

the repo is: https://github.com/axiom-micro

note that the Power Board wiki page is still missing the PCB renders

I am not opposed to moving some axiom-micro repos to the apertus-open-source-cinema org and i think anuejn wouldn't either, your call

lets see how it shows up

lets see if we can fork/import/link it without moving it until next week, if that doesnt work out we can consider moving

I will check

anything else RexOrCine1?

great, thanks

yes

https://github.com/axiom-micro/mainboard/blob/r3/micro_rev3/micro_rev3.pdf

Finished the gateware for the connector test:

and did some preliminary tests without any connector

https://files.niemo.de/freq_tap_res_wire.png

btw the connector test gateware is also starting to show how with nmigen some nice

so if anybody working on gateware has comments / feedback regarding that aspect, we would be interested.

if nobody has any questions that would be it from me

ideally tailored to the Axiom cameras?

Bertl: most of the stuff we do regarding axiom cameras is still pretty much in flux, but sure

just let me know beforehand so I have a bit of time to prepare

and definitely not before the students have been selected

right, quick updates from me and then Bertl to wrap things up

https://developers.google.com/season-of-docs/docs/timeline

new wiki extension shows dead external links - needs cronjob set up (every week?)

and of course it also needs people to maintain the pages: remove dead links or replace with new ones

I shifted my focus from CAD design of enclosure and accessories (I consider them good enough for now - it makes no sense to design a lot of accessories at this point without getting close to shipping actual CP enclosures soon)

I hope we will be at the level of the C firmware soon, its not a huge task but still requires some attention to detail

thats it from my side

I also tried to invite Jan working on the emount protocol reverse engineering but he is probably busy, maybe next week

Actually nah, sorry. Forget it.

so, last week we did our second GSoC applicant meeting and while not everybody had something finished, we got two reports and one was especially impressive so I'm quite optimistic for the upcoming meeting there

it is mostly about basic tasks, getting code formatted, setting up a build system, writing documentation, etc

there is a separate channel, but we might consider doing them here (let's discuss that afterwards)

for now we kept the channel without logger, mainly to make it more comfortable for the applicants

fair. thanks!

yes, and it probably should be anonymous :)

on the infrastructure side, I've been working on a remote setup, which isn't complete yet, but hopefully will allow the GSoC students to test on real hardware efficiently

I'll also assemble one of the new Axiom Remotes for remote testing the coming week

on the PCB probing side there have been quite some developments and changes to make things more usable

the reason why I focused on improving the hardware is that I got some reliability issues with the previous setup and it was somewhat tricky to position

so I had the idea to use a raspberry pi zero with camera for monitoring the probe pin

this also resulted in a change of the PIC interface

there also is a nice package to program PICs from the RPi (pickle) so I completely switched to this design

the cad parts are tricky but they are basically finished except for one tiny part which I just realized we will still need

basically getting rid of all the mechanical parts connecting it now to the base

the rpi is only connected via two power wires and transmits all the data via wifi

and in the future it might also control the mechanics as well

the only remaining problem there is that the camera is mechanically oscillating in the air stream from the fan so the image is wobbling at the moment

so with BAndiT1983 basically finished with the pad extraction it should be a matter of a day or two adjusting the software side to do actual probinh

I've done some manual probes with the setup and the results are quite promising

the AVnet Ultra96-V2 'board'

overview: http://zedboard.org/product/ultra96-v2-development-board

kind of similar to the MicroZed except for the PS side MGTs for the USB 3.x

now we've considered using various NUCs and small format computers as recorders for the Axiom Beta

which in this case can be reduced to a direct LVDS connection between Axiom Beta and the Ultra96 board

very interesting board, but no built transceivers :(

but 4 PS side MGTs

so yes, it would be nice to have those on the PL side as well

this would already be an interesting recording solution

the zynq itself also has pcie, right?

do you know if / how it is broken out on the board?

yes, schematics are here: https://www.avnet.com/opasdata/d120001/medias/docus/193/Ultra96-V2%20Rev1%20Schematic.pdf

two lanes on the mini-dp

and one lane on the USB 3.1 hub

great, many thanks

nce tasks for new team members or people interested in the project looking to contribute could be

maybe more focused on documentation, cad design, creative tasks

maybe we can collectively think about that until next weeks meeting

many thanks everyone!

yes, great meeting everybody!

i'm off, thanks for the meeting also from my side!

I am wondering for students with limited budget, what would be a good starting point to even work on real hardware? Is axiom micro a good way into it?

yeah, i wonder tho whether this would be the best way for random people to test and do stuff. especially if you are rather inexperienced in some aspects

agreed :)

working on the AXIOM Remote hardware is simpler/cheaper if you are interested in contributing on that front

in addition

connected to each other over direct LVDS lnks

I just want to say that i have concerns regarding the added extra complexity

please elaborate, because I consider this approachs main advantage in its extremely low complexity :)

soldering, building hardware, software development, etc.

But maybe it can share a lot of things with the beta

no gateware reqired

Yes but you have to move the data _to_ the os

But that might be not too much work

On the other hand we have a similiar problem if we develop an fpga based plugin module (ie. for usb3)

We will see

Thats true

se6ast1an: mostly direct FPGA video work, playing with certain aspects etc pp so having sensors + fpga is a nice thing. but: explore the domain as well. Not (yet) interested in super high quality output. But nevertheless working on "real" hardware has its charme. I am not aware of too many video projects with fpgas (zynq et al) as well.

another benefit of the ultra96 in my opinion is that we can benchmark the USB3 write speeds without writing any gateware, install linux, plugin storage media, run benchmark

in contrast to the usb3 mdoule with the ftdi chip which turned out to have bandwidth issues after a lot of effort went into development

this way you can use your favorite HDMI source (computer, dvd-player, game-console) and do processing on the video data in realtime with output to a monitor

(those are zynq based, so you have a hard CPU for Linux there as well)

hope this helps ...