Sorry, you need to enable JavaScript to visit this website.

Python-1300 on SVDK (PicoZed Carrier Card)

Unsolved
6 posts / 0 new
prenav-franz's picture
prenav-franz
Junior(0)
Python-1300 on SVDK (PicoZed Carrier Card)

I was able to successfully capture video data utilizing the shipped video board (Aptina AR0134 1.2MP Camera Module) using Sphinx GEV Viewer.

To take it a step further I'd like to replace the Aptina AR0134 with a pin compatible module, the ON Semi PYTHON-1300. After checking pinout compatibility I plugged in the camera module. The documentation for the module states it's both MicroZed Embedded Vision Carrier Card and Smart Vison compatible (although indications are it's primarily a MicroZed EVCC module)

However, when I attempt to capture video from it using the same configuration as the Aptina AR0134 no video is captured. Within the Sphinx tool when toggling on "Grab" an error message states "[ERROR] - GEVGetImage() [STATUS_TIMEOUT]"

Strangely the Width and Height default = 1. I've manually changed them without resolution.

The console window displays the following:
[INFO] - Open stream channel.
[INFO] - Stream channel IP: 169.254.126.27
[INFO] - Stream channel port: 50164
[INFO] - Log mode: Detailed Log Info off
[INFO] - Log mode: Detailed Log Warning off
[INFO] - Log mode: Detailed Log Error off
[INFO] - Display corrupt frames: Yes
[INFO] - Allocate ring buffer for images.
[INFO] - Allocate index buffer for images.
[INFO] - Width: 1
[INFO] - Height: 1
[INFO] - PixelFormat: 0x01080001
[INFO] - PayloadSize: 64
[INFO] - PacketSize: 1364
[INFO] - PacketDelay: 500
[INFO] - Message Channel Device 2 -> stream channel start of transfer
[INFO] - Start acquisition time: 06:20:21
[INFO] - Message Channel Device 2 -> stream channel end of transfer
[INFO] - Free index buffer for images.
[INFO] - Free ring buffer for images.
[INFO] - Frames: 0, Errors: 0 Lost: 0.00 %
[INFO] - Packets: 0, Errors: 0 Lost: 0.00 %
[INFO] - 0.0 fps
[INFO] - Stop acquisition time: 06:20:22
[ERROR] - GEVGetImage() [STATUS_TIMEOUT]

As a comparison, this is what a successful transfer looks like in the console using the AR1034 (and, yes, there seems to be packet/drop issues in the "working" format:

INFO] - Open stream channel.
[INFO] - Stream channel IP: 169.254.126.27
[INFO] - Stream channel port: 58348
[INFO] - Log mode: Detailed Log Info off
[INFO] - Log mode: Detailed Log Warning off
[INFO] - Log mode: Detailed Log Error off
[INFO] - Display corrupt frames: Yes
[INFO] - Allocate ring buffer for images.
[INFO] - Allocate index buffer for images.
[INFO] - Width: 1280
[INFO] - Height: 960
[INFO] - PixelFormat: 0x01080001
[INFO] - PayloadSize: 1228800
[INFO] - PacketSize: 1364
[INFO] - PacketDelay: 500
[INFO] - Message Channel Device 2 -> stream channel start of transfer
[INFO] - Start acquisition time: 06:15:40
[ERROR] - ReadRegister[0x00000A00] Status: C008
[WARNING] - CCP lost.
[INFO] - CCP reconnection.
[INFO] - Free index buffer for images.
[INFO] - Free ring buffer for images.
[INFO] - Frames: 613, Errors: 0 Lost: 0.00 %
[INFO] - Packets: 552313, Errors: 305992 Lost: 55.40 %
[INFO] - 50.0 fps
[INFO] - Stop acquisition time: 06:15:52

AlbertaBeef's picture
AlbertaBeef
Moderator(5)
Need to change the design :)

Franz,
The PYTHON-1300-C camera module does not have the same interface (serial LVDS + SPI) as the Aptina AR0134 camera module (parallel + I2C).  You need to modify the GigEVision design to accomplish this.
You will need to replace the hardware design and the software application.
Although there is no reference design available for what you are asking, there is a user that was successful in getting the PYTHON-1300-C camera module working on the SVDK (ie. they created a new design).
   http://zedboard.org/content/porting-python-1300-ref-design-svdk-artifact...
 
Regards,
 
Mario.

prenav-franz's picture
prenav-franz
Junior(0)
Mario,

Mario,

Wonderful reference. Thank you!

Franz.

rjpeyser's picture
rjpeyser
Junior(0)
picozed smart vision sphinx gev viewer 30 min timebomb

I recently purchased a picozed based smart vision development system from Sensor to Image via Avnet. It did not exactly jump to life out of the box, and no UART output was forethcoming, but after twenty minutes of screwing around I was able to get the Sphinx viewer to take a picture. Ten minutes later a message appeared indicating my 30 minute trial period had expired! Excuse me?

Subsequently, I've examined the code and find that yes indeed there is a bit set by Sphinx that keeps the hardware from streaming after the "trial" period has expired.

Can anyone clue me in to what is going on here? I am hoping I'm just being stupid and have overlooked something I was supposed to do (like registering, which I did).  Anybody?

Or shall I just return this piece of BS to Avnet?

AlbertaBeef's picture
AlbertaBeef
Moderator(5)
Sensor To Image GigEVision design

 

The reference designs for the SVDK are created by Sensor To Image, a german company specializing in machine vision connectivity.

Sensor To Image provides IP cores.  They also provide reference designs to allow customers to evaluate their cores before purchasing the IP cores.  The "30 minute timebomb" is occuring in the IP core inside the hardware design.  This is a very common practise from third party IP providers.

Please note that the price of the SVDK does not include the price of the Sensor To Image IP cores.  If you want to purchase the Sensor To Image IP cores, please contact Sensor To Image.

Regards,

Mario.

rjpeyser's picture
rjpeyser
Junior(0)
Perhaps you should clearly

Perhaps you should clearly state in your marketing literature that without purchasing additional licenses, this board will become useless after 30 minutes.
Shall I call my Avnet rep and see if he was aware of this?