#apertus IRC Channel Logs

off to bed now ... have a good one everyone!

good day

MEETING TIME!

well, we probably can save the time then ...

I will publish the gsoc article then now

nice

a bit, was not that present lately because of my regular job

we had a problem with rotated data there, which was resulting in complains from the PCB fab

final obstacle was the drill layer, but after some experiments with decimal settings it finally worked

panels have been sent to pcb fabs already for quotes

don't have a preview right now, otherwise i would show some nice images of 2d lines ;)

that would be it

now I feel motivated to give a brief insight into the pcb prober as well

https://github.com/apertus-open-source-cinema/pcb-prober/blob/master/calibration/testpattern_v2_150x150.pdf

with the attached microscope camera I then ran an automated optical center detection of around 4000 points and did each measurement 4 times

the results were visualized by Bertl

https://github.com/apertus-open-source-cinema/pcb-prober/blob/master/calibration/result%20visualization%2002.svg

github is crashing there, maybe too big, have to download

are the peaks just some random errors?

possibly because the tension on them is too high or too low

usually the belt tension is not that important, at least not to the extent people always think and propagate

I also tweaked the belt tension but what I meant was the pressure on the wheels

anyway, we figured we wanna try probing now and see where we actually end up

the probing routine has been added today, there are some things still to be tweaked or improved

for the smaller chip pads we will see what the best approach is

shotgun approach

the idea is that the measurement will tell us if we hit immediately

the problem is that the movement between centering camera and moving the needle there will also produce an error

but potentiall smaller error

yeah, I am curious if the measurement will show that

I mean if it will allow us to identify the neighbour pad

but the GND plane is grounded yes

resistance of the trace?

Bertl: can you elaborate

basically we do a resistive as well as capacitive measurement

regarding 'hitting the wrong pad', if we are that far off, we have a bigger problem

chances are, if we miss a pad, we a right on the edge of the pad

(a sufficiently small circular motion that is :)

and I'm somewhat confident that we can tell the difference there

for sure a more stable construction would work better, we just started with the ender 2 because it was available and cheap

not too expensive

so for now, let's see how well this one does ...

so much for the prober

guess so ...

and I did a SIMD (NEON) implementation for the line conversion

still if we run the cmv_snap over ssh, we get about 1.6-1.8 seconds

did you also benchmark writing to micro sd card ?

iss SSH mandatory or can we use (R)UDP?

I also updated the storage system at the hub, added two disk drives there and we are currently spreading the data over the drives

two boards actually no?

correct

could you test this script with it:

until line 21

*second

yes

disable hdmi

regarding UDP or whatever can be used, can't we just check wit socat if it will work? just as a proof of concept -> https://knplabs.com/en/blog/share-files-on-the-local-network-with-socat

turn hdmi back on

the problem I see here is that there is no sync

good idea, added

(because caching and then sync is a baad idea too :)

and update the script then please

great

anuejn is currently occupied with a lot of other things

Hey guys! I can share something...

tx!.. so I tested my driver with the latest kernel in-tree (had some help from vup there), and it seems to work nicely

only I realized as soon as the driver is bound with the devicetree and probes...it automatically does some jtag stuff (queries status)

reloading the driver works fine then

but i think it would be better if we turn jtag on from within the driver...

Bertl: yep... have a look at this patch.. looks good?

other than this... i have yet to add some kernel documentation, update the newer devm version of some functions, and some other clean up stuff... I guess it will be somewhat ready for mainline then...!

we can make this a more generic command rather than just for jtag as you mentioned...

anyway... i guess thats it from me now..

Bertl: yeah yeah.. we can have a switch inside that function basically that does different stuff based on the argument..

ok, anyone else here otherwise we can conclude this weeks meeting

many thanks everyone!