From e60ccb8965bbc1a460bf85bfc87b885cf1260151 Mon Sep 17 00:00:00 2001 From: Patrick Roth Date: Fri, 4 Oct 2019 10:17:42 +0200 Subject: Initial commit import from github --- ChangeLog | 46 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 46 insertions(+) create mode 100644 ChangeLog (limited to 'ChangeLog') diff --git a/ChangeLog b/ChangeLog new file mode 100644 index 0000000..f1ec48c --- /dev/null +++ b/ChangeLog @@ -0,0 +1,46 @@ +------------------------------------------------------------------------------- +- ChangeLog O-3000 Host Driver +------------------------------------------------------------------------------- + +Version 2.0.2 + 2018-04-11-PR + * Function handle_transfer() rewritten: + The image frame synchronization was a bit hacky. Image frames were passed only to the + overlaying application after the next image frame has been received. But when receiving a single + snapshot, there won't follow an image. This causes a delay of one image until the application + receives it. Now the function passes images to the application after a image is + received completely without checking the preamble of the following image. + * Bug race condition at o3000_init() function: + Accessing the session table for getting next free session and allocation session structure + must be atomic. + * New function o3000_get_num_cam() added: + This function returns the number of connected O-3000 cameras to the system. + * New loglevel O3000_LOG_VERBOSE added: + This loglevel will set the libusb to debugging mode and is very useful for debugging purposes. + +Version 2.0.1 + 2015-08-11 -PR + * Bugfix in function handle_transfer(): A negative byte offset was calculated when the resolution + has changed during wrap-around. A SEGFAULT occured. + * Fields added to image header and image header version update to 4: + - data rate in bytes/seconds + - frames per seconds + - field-of-view added used by lense distortion algorithm + * Short USB bulk transfers are supported now by the driver. Therefore the resolution + doesn't have to be a multiple of 512 bytes anymore and binning is done correctly. + There are following restrictions about image resolution settings: + - Window size must start with an even pixel coordinate (see examples below) + - Minimum image resolution is 640x480. + - Binning is allowed at full-screen only (1280x960) + E. g. valid window: X = 110 to 1111, Y = 32 to 917 + E. g. invalid window: X = 111 to 1111, Y = 33 to 917 --> coordinate 111 and 33 are odd numbers + + 2016-03-01 + * Calling convention added for Win32 and Win64. + +Version 2.0.0 - 2015-02-16 + * PR: Multi camera sessions capability. The host can scan the number of cameras and establish a connection to + each of them. Sending a XML message to the camera uses the synchronous API with OS dependet timeout handling. + +Version 1.0.0 - 2015-02-16 + * PB: Inititial version -- cgit v1.2.1