Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Matom

Pages: [1]
1
Software Dev / Re: Deploying camApp from Qt Creator
« on: May 21, 2018, 11:05:41 PM »
Hi BiduleOhm,

What type of hardware trigger are you thinking of? A photodiode?

We will use the camera remotely (from a different country) and therefore want to avoid as many additional part as possible. With a software trigger we can easily adjust it from home with remote desktop. In addition we want to be sure that the camera only triggers on the right type of events and events that are luminous enough for the Chronos' sensitivity.

These are the main reasons for an internal software trigger. However, I am very happy to get advice and new ideas.

2
Software Dev / Re: Deploying camApp from Qt Creator
« on: May 19, 2018, 11:06:14 PM »
Thank you for the input :) The display would be nice to turn of anyway, to avoid light leakage (we will shoot in a very dark environment). Is it possible?

And yes, I am currently trying to improve the algorithm, however it still cannot trigger on light pulses that are shorter than 50 ms.

Regarding an external led or camera as trigger, this is our plan B, but ideally everything should be internal in the Chronos.

Yes, in our research (lightning) such a trigger would be a great addition. If I manage to develop something that works, I will be happy to share ideas with you.

3
Software Dev / Re: Deploying camApp from Qt Creator
« on: May 16, 2018, 08:27:06 AM »
Dear David and the rest of Krontech,

I am sorry to keep bothering you about the SW. I am very close to my goal of making an internal trigger that stops the recording if a sudden burst of light appears. I just need a few more suggestions and maybe you can help. (Right now my trigger algorithm slows down the camApp, so it only processes something like 50 fps)

It is my understanding that the camApp runs three parallel threads. Is it possible to shut down one or two of them in order to save processing time? And how would this be done?

Is it possible to turn of the display? Either by using a specific function or by removing all the functions that make the image for the display?

Do you have other suggestions that would save me processing time? 

Maja

4
Software Dev / Re: Deploying camApp from Qt Creator
« on: May 07, 2018, 12:19:41 AM »
Dear David,

Thank you very much, it helped a lot! We now have a functioning internal trigger :D
Don't worry about the diagram. It would still be very useful, but we can manage without.

Ideally I would like to turn of the screen, video and everything. Is there an easy way to do that?

Maja

5
It worked. Thank you! Do you know what causes it or how we can avoid the issue?

6
Thank you very much! I'll try that.

7
I also had this problem occasionally. However, now I can't turn it on at all. The power button and power status indicator is on but nothing else. Tried a hard reset at least 10 times. Any suggestions?

8
Software Dev / Re: Deploying camApp from Qt Creator
« on: April 23, 2018, 04:14:10 AM »
And I  have another question.

Does anyone know what the address of trigger 1 is? I am wondering if it is part of the FPGA code?
I would like to trigger it from the software instead of with an external voltage.

Any help would be very appreciated! :)

9
Software Dev / Re: Deploying camApp from Qt Creator
« on: April 15, 2018, 11:52:46 PM »
Dear David,

Thanks for your answer. I spent the last few weeks trying to understand how the pipelines work. And I agree that the learning curve is quite steep ;) I have the live image (8 bit/per pixel version) from the OMX pipeline now. So far, I did not manage to configure the Gstreamer pipeline.

Do you have a flowchart of the software? It would be a great help to see how the pipelines are connected and how the image is transported from the sensor to the screen.

10
Software Dev / Re: Deploying camApp from Qt Creator
« on: March 27, 2018, 02:02:50 AM »
Yes, thank you :)

I am looking for the raw image sensor data. I think I found it. However, I still did not manage to open and view the image that I dumped.
I dumped the values contained in the buffer from the "VIL_ClientCbFilledBufferDone" function.
 
The goal is to do a different video processing cycle than the one currently on the camera.
Because the camera will be working autonomously I don't need the image to be displayed.

11
Software Dev / Re: Deploying camApp from Qt Creator
« on: March 26, 2018, 12:55:48 AM »
Hi David,

Thank you for the answer. After updating the software to the newest beta version the problem was solved. Not immediately though. When the exposure trigger was on the image froze, so I assumed that it was still a problem with the FPGA version. However, by unclicking the exposure trigger I can now update the software and use the camera afterwards. Thanks!

Btw, I am searching for the part of the code that holds the image (and sends it from the ccd to the screen). So far I assume that the buffer (pbuffer) in the video.cpp script holds the image. Am I on the right path? Where is the easiest place in the code to access the image?

 

12
Software Dev / Re: Deploying camApp from Qt Creator
« on: March 21, 2018, 12:57:17 AM »
When I have Qt open and deploy the app, the camera turns on but the video freezes if I click anything on the display. If I exit Qt and turn on the camera (with the new camera app moved to the /opt/camera folder) there is just a black screen, no display or anything.

13
Software Dev / Deploying camApp from Qt Creator
« on: March 20, 2018, 02:30:16 AM »
Hi, I am using Chronos 1.4 for a research project and so far I am very happy with it. I need to make some changes to the software for it to function ideally for my project.

Is anyone here able to deploy a modified version of the camApp from Qt and use the camera afterwards? If so, can we share experiences?

I have installed the Qt creator following the README guide on github. Everything seems to be working and I am not getting any error messages. So far, I have not made any significant changes to the app before deploying it (I have simply changed the spelling on the main ui, just to see if it works), but I cannot use the camera with the “new” version of the App.

I am working on Ubuntu 16.04 and the Qt creator is version 3.5.1.

Pages: [1]