#apertus IRC Channel Logs

you're very welcome!

Hi BAndiT1983

Hi Y_G, do you have a minute?

did BAndiT1983 already chat with you about the wiki documentation of the control daemon CLI examples?

Yes ,I have went through these ,He asked me to extend these with the functionalities added during the task

What I wanted to propose is adding more examples of commands that are already possible now and do not rely on extending the code

in particular chaning image sensor registers

is that something you could dig into?

yes

so examples how to read and set some example registers would be very handy

Yes ,I have gone through it

then picking out a few key image sensor parameters and providing examples how to get set them with the control daemon CLI would be great

and some explanation what the return values mean exactly and how to interpret them

is that something you could work on?

great

as you need to provide register index and value

if we have a function for adc_range it will automatically know which register to set.

my focus was on config_register

there are two ways how to do the same thing

like changing analog gain

and set the image sensor register directly

and how to do it

Ok will have a look on what registers look important and will update them accordingly.

sure

Test

hi Y_G

second thing about index and value for registers, everything is there

also setters and getters for registers are there also for quite a while, but i had no time to check it, as we had connection problems to HDMI, afterwards my job took some time and will still take a lot of time in the next weeks

There is a functionality that requires to capture information about all pac1720 ,The output is as follows : "https://pastebin.com/FDjZNZw8"

pastebin is not longer there

https://pastebin.com/MNSUb2EL

this is exactly the opposite what the daemon communication should do

I have individual functions for getting each row too . But to get the overview of all the sensors would help the user

i don't see a necessity to do the formatting on the daemon side

have you wrote down the processes and goals, so i can analyse the steps you want to take?

and what was decided?

ok, but then i don'T understand why you want to create info output in the daemon

so oyu would have like a method for 5V_NORTH, 5V_NORTH_AMP or so

It was majorly a test to check I2CAdapter ,to see if it was working properly.Which I suppose does work properly now

another thing, please avoid placing long methods in if/else, you can grab the variables which are different and set values, afterwards call the method using it

also smbus.cpp of course

word of caution, looks like you've renamed smbus.c to smbus.cpp, first thing is naming, according to C++ it should be SMBus.cpp

-probable +possible

Hello BAndiT1983 ,

hi Dev_

Have tried going through articles ,all of them suggested to use smbus commands instead of simple read/write

was the reason named, why they were deprecated?

https://www.kernel.org/doc/html/latest/driver-api/i2c.html

BAndiT1983: I have changed the sharing settings of document . Can u able to check it now

will check your allocator tomorrow or while weekend, but have seen quite some problems

yes , I saw your comment about IAllocator on trello ,

so, have to leave for today, work awaits tomorrow

we would be having different implementation for Allocate(), Deallocate() methods for different cases and we can extend the IAllocators methods easily

working on your comments on Gdoc document now ..