4 ms·

720p@240FPS would be little hard because of limitations on the USB controller side. because of 100Mhz and 32bit limit you have possibility of only 400Mbyteperse

720p@240FPS would be little hard because of limitations on the USB controller side. because of 100Mhz and 32bit limit you have possibility of only 400Mbytepersecnd and with few % overhead you have may be get around 200 FPS of color UYV image. if you are ok without colors then you can get to 400FPS @ 720p

DoingIsLearning 4y ago
> 720p@240FPS would be little hard because of limitations on the USB controller side. What would be the theoretical limit of the sensor itself? Could you extend the project to work as a high speed camera? Perhaps using a Firewire ip core implementation instead of USB?
- circuitvalley 4y ago
  There are only few options, 1. Use USB controller Chip that support 10Gbit or more. 2. Use 10Bit or more ethernet, Optical or copper. 3. Use PCIe 4. Use onboard storage. 5. Use HDMI or something custom and have another receiver (They are called frame grabber and everybody hate them). Right now there are not many controllers on market that can do more than 5Gbit Most useable solution is to use Ethernet , I would say optical.
- icelancer 4y ago
  Typically what cameras like the Edgertronic do are have 8-16 GB of onboard DDR3-4 RAM and write raw frames directly to memory on a trigger or a loop/trap. Then when you have X amount of frames you want, process them using ffmpeg/gstreamer using onboard hardware acceleration methods and write to an SD card / network drive / attached SSD or similar. Simply bind X GB of RAM to a memdisk and write to that path in Linux, for example. I am fine doing this and have done it using raspiraw and know the Edgertronic platform / source code very well. The problem is that sensors and MIPI lanes on commercially-available products are complete trash with even worse documentation.
icelancer 4y ago
B&W is fine by me, color not necessary. Also fine with PoE and 10GBE if required. Seems crazy that the IMX477 is capable of so much more than what people are currently drawing out of it. Any pointers on where to start? I've done raspiraw frame dumping with the RPi HQ camera but it's just going to be a non-starter given all the issues it has.

DoingIsLearning 4y ago

> 720p@240FPS would be little hard because of limitations on the USB controller side. What would be the theoretical limit of the sensor itself? Could you extend the project to work as a high speed camera? Perhaps using a Firewire ip core implementation instead of USB?

circuitvalley 4y ago
There are only few options, 1. Use USB controller Chip that support 10Gbit or more. 2. Use 10Bit or more ethernet, Optical or copper. 3. Use PCIe 4. Use onboard storage. 5. Use HDMI or something custom and have another receiver (They are called frame grabber and everybody hate them). Right now there are not many controllers on market that can do more than 5Gbit Most useable solution is to use Ethernet , I would say optical.
icelancer 4y ago
Typically what cameras like the Edgertronic do are have 8-16 GB of onboard DDR3-4 RAM and write raw frames directly to memory on a trigger or a loop/trap. Then when you have X amount of frames you want, process them using ffmpeg/gstreamer using onboard hardware acceleration methods and write to an SD card / network drive / attached SSD or similar. Simply bind X GB of RAM to a memdisk and write to that path in Linux, for example. I am fine doing this and have done it using raspiraw and know the Edgertronic platform / source code very well. The problem is that sensors and MIPI lanes on commercially-available products are complete trash with even worse documentation.

icelancer 4y ago

B&W is fine by me, color not necessary. Also fine with PoE and 10GBE if required. Seems crazy that the IMX477 is capable of so much more than what people are currently drawing out of it. Any pointers on where to start? I've done raspiraw frame dumping with the RPi HQ camera but it's just going to be a non-starter given all the issues it has.