User Tools

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
support:sub2r_cc_revision_history [2022/08/22 20:09] – [upcoming] Igor Yefmovsupport:sub2r_cc_revision_history [2022/08/22 20:40] (current) – [2.6.0: 2022-08-22] Igor Yefmov
Line 4: Line 4:
  
 ===== upcoming ===== ===== upcoming =====
 +
 +===== 2.6.0: 2022-08-22 =====
   * general/code   * general/code
     * update to MSVC 2022     * update to MSVC 2022
Line 19: Line 21:
       * %%SysInfo%% API v.2 now reports status of peripherals - requires FX3 v60+       * %%SysInfo%% API v.2 now reports status of peripherals - requires FX3 v60+
       * access arbitrary I²C-attached module on device - requires FX3 v98+       * access arbitrary I²C-attached module on device - requires FX3 v98+
-      * MIPI SPF - requires FPGA v76++      * MIPI FPS - requires FPGA v76+
     * the connection to device is now "valid" even if the sensor is inaccessible (e.g. broken, or not initialized, or non-responsive)     * the connection to device is now "valid" even if the sensor is inaccessible (e.g. broken, or not initialized, or non-responsive)
     * API duration reporting's precision is now in ms (used to be in μs)     * API duration reporting's precision is now in ms (used to be in μs)
Line 50: Line 52:
     * bugfixes     * bugfixes
       * potential memory corruption in FPGA console       * potential memory corruption in FPGA console
-      * Sensor console script now properly ignores comments (those that being with a semicolon ";")+      * Sensor console script now properly ignores comments (those that begin with a semicolon ";")
   * Aria   * Aria
     * display true MIPI speed (FPS produced by sensor itself) - requires FPGA v76+     * display true MIPI speed (FPS produced by sensor itself) - requires FPGA v76+

This website uses cookies. By using the website, you agree with storing cookies on your computer. Also, you acknowledge that you have read and understand our Privacy Policy. If you do not agree, please leave the website.

More information