If they all use HiSilicon it can be biggest tragedy of amazing small camera company.
I posted in both E2 group and PV group, hope we'll find owners soon.
May be it is possible to make small utility to extract firmware data on place? I mean to avoid complex remote access things?
To find out all SoCs they use I need connection to cameras. Now I have only E2 (and won't buy any other).
@Vitaliy_Kiselev, to do this I need all these cameras :D
For example, if somebody shares his camera through the internet (via LAN connector and dedicated IP), I can download data from camera and get this info (for now I don't have stable way to repack fw files yet).
But I'm sure that all these cameras are almost same. The difference is in sensors. Here are all sensors for each model:
Btw about HiSilicon - this company wont be able to make SoC soon (if not already) due to US sanctions.
Do they have something else in other E2 cameras, as if they use only HiSilicon SoC chips it can be huge issue.
Thanks.
I mean all E2 variations
https://www.bhphotovideo.com/c/search?q=z-cam%20e2&filters=fct_category%3Adigital_cine_cameras_28624
E2 has Sony IMX299 sensor and HiSilicon Hi3559A V100 SoC on board.
https://www.sony-semicon.co.jp/products/common/pdf/IMX299CJK_Flyer.pdf http://www.hisilicon.com/-/media/Hisilicon/pdf/Surveillance_mobilecam/Hi3559AV100.pdf
It can be also interesting to make some table about hardware stuff used in all E2 versions using firmware data, can you do it?
In my opinion Z-Cam E2 is already a very nice camera with good firmware and support. I did not have any problems with it. But maybe I can make some little fixes for it.
For example, E2 has some delay while transmitting video via RTSP (in comparison with SSP, that works with a very tiny delay ~20-30 ms).
And, as I can see, there is a 14-bit sensor readout mode. Maybe we can use it for something...
What viable modifications do you feel would make the camera more usable?
It looks like you're new here. If you want to get involved, click one of these buttons!