The Canon RE-350 SDK is a legacy development kit designed specifically for the Canon RE-350 Video Visualizer (a specialized document camera and presentation system released in the 1990s). It is not related to modern Canon EOS DSLR or mirrorless camera SDKs (such as EDSDK or CCAPI).
An overview of how the SDK functions, its core architecture, and its integration requirements includes: Core Architecture and Environment
Vintage System Requirements: The SDK is built as a 16-bit software package natively designed to run on legacy operating systems like Windows 3.1 and Windows 95.
Physical Connectivity: It communicates with a host computer exclusively over a hardwired RS-232C serial connection via an assigned COM port.
Key Library Components: The foundation of the SDK relies on a few critical files:
re350dll.dll: The primary Dynamic Link Library providing the API layer.
CTL3DV2.DLL: A 16-bit Windows GUI support file that must be manually copied into the C:\Windows\System directory to run applications.
re350.h: The C/C++ header file containing all driver definitions and system error codes. Hardware Controls & API Functionality
The main objective of the RE-350 SDK is to bypass physical execution, mapping remote serial commands directly to the hardware components of the visualizer. Developers use the primary system function RE350_Command to execute hardware tasks programmatically:
Lighting and Optics: Toggling the built-in fluorescent upperlight arms, activating the integrated backlight panel, and triggering Auto-White Balance (AWB) routines.
Camera Head Control: Remotely adjusting the motorized zoom lens, fine-tuning the manual focus ring, and managing hardware exposure/brightness.
System Auditing: Polling data packets from the unit, such as fetching the core hardware ID name (“R1”) or querying the ROM firmware version numbers from the mainboard CPU. Protocol Logic & Handshaking
Online/Offline States: The device requires an explicit toggle using an {RS-232 Control} front panel button. When shifted “On-Line”, the physical panel locks out human interaction, granting absolute execution priority to the RS-232 serial data packets streaming from the PC.
Data Packets: Communication is strictly managed through Command Data Packets sent by the computer, which are instantly mirrored by C-Response Packets fired back by the RE-350 firmware to acknowledge successful execution.
Troubleshooting Constraints: If the provided 16-bit demo GUI fails to map commands, developers must manually audit the device’s hardware dip-switches located on the rear panel. The hardware Baud Rate and Device ID must match the software application settings exactly, and a custom null-modem serial pinout configuration is required.
If you are working on a retro-computing project or managing legacy studio equipment, Software Development Kit (SDK) – Canon Europe
Leave a Reply