#apertus IRC Channel Logs

does steingate has lot fights like hunter x?

hey, apertus dev people

CMOSIS don't mention the possibility of overclocking ANYWHERE in their datasheets, so I'm curious how it would perform at higher clocks

though 100MHz is quite insane in terms of image sensor clock

nope, we didnt do it

I'm debating on whether or not I should take the CMV2k and make something low-end, but overclocked

why not?

sure but it might behave quite differently

oh.

morning folks!

higher framerate

that's a tiny overclock

most sensors are capable of 50% and higher

no reason to not try

you won't kill the sensor if it's cooled

they designed the sensor for 600MHz, but had to release the first version with 300MHz because they couldn't reliably reach the 600MHz

680 IIRC

off for now ... bbl

se6astian, that's neat

what's the funny-looking metal table for?

the table is missing the tabletop

So to go from 936 to 1000 fps @ 4096x1080 with the CMV12k the clock boost needs to only be 41MHz

gets you 1479fps @ 4096x720

the problem is more that your calculation is flawed

I presume so, at least from the values

so we need to boost the clock 1.01683 times

er, 1.0683

you also have some limits to the exposure time, but that shouldn't be that criticial around 1000FPS

1/963rd is not that more than 1/1000th

(roughly speaking)

theoretically though, "making the sensor go" 1.06 times faster should be doable

I don't mind 936fps, but 1000 just ticks the OCD mark for me, heh

I plan on doing active TE cooling the sensor in my camera

right now I'm planning on using the MYIR Z-turn board, since it's only $119 for the 7020, and it's got 39 LVDS pairs

yes, looks like a good choice for this purpose

yeah, I really want to be able to run it full-speed

you plan to connect an SSD directly to the zynq?

or with some glue

possibly CFast cards, if it's easier

the 1.27mm connectors on the back are an unfortunate design decision when it comes to high speed interfaces

you might get away with the 600MHz interface though, if you place the pairs properly ... but I don't see that you get up to 1GHz or higher on this connector, but please let me know how it goes

the cmv2k has 16 pairs @ 480

though it'll probably just stop functioning past 10% OC

as am I :>

make a simple length-matched breakout for the sensor and whatever IO I want

inter pair length matching for the sensor is something you can safely forget about

Bertl_oO, but I like wiggly lines :(

well, if you don't care about signal quality, go ahead :)

I'm thinking of length matching it down to the package

if you're overengineering, overengineer to the max! :D

does cmosis specify theirs?

but it should be obvious, that length matching with meanders degrades the signal

every bend will cause EM

the PCBS will be dirt cheap, since there won't be any BGAs or very tight tolerances

off to bed now ...

I am off to bed