FAQ ARM/Linux Cameras

The temperature of the CPU will be higher than its surrounding temperature. The maximal CPU core temperature is specified at 100°C but VC advises to keep temperature below 80-90°C. The core temperature can be read by software with the script vc-get-temperature.sh (available on all VC Z cameras in /usr/bin).

If a proper temperature transfer is created between the CPU and the casing, the CPU core temperature should not differ more than 10 to 15°C from the temperature of the casing. This brings the casing temperature at 80-15=65°C. Considering that the casing will be warmer than its surroundings, we end up at about 50°C. Should the casing be black, or have a big surface, the temperature difference will be smaller.

To change the IP address of a Z series camera edit the file /root/vcsetip.scr and modify the parameter ipaddr:

ipaddr 192.168.3.15
netmask 255.255.255.0
gatewayip 192.168.3.254
serverip 192.168.3.35
dnsip 192.168.3.254
dnsip2 192.168.3.254
addip setenv bootargs ${bootargs}
"ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}:${ethd
ev}:off:${dnsip}:${dnsip2} "

Other network parameters like subnet mask, gateway and DNS addresses can also be modified here. Do not modify the last line of the script.

Save the modifications and run the script vcsetip.sh with

bash vcsetip.sh

to apply the changes. Reboot the camera.

To activate the DHCP client, run the script /root/vcsetdhcp.sh with

bash vcsetdhcp.sh

Reboot the camera.

After reboot the camera gets an IP address from your DHCP server. If not DHCP server is present, after a timeout it falls back to the standard IP address 192.168.3.15.

Follow these steps to recover the camera:

1. connect the camera to the same network as your Windows PC
2. power up the camera
3. wait about 2-3 seconds
4. run the attached batch script nano_fix_ip_windows.bat (doubleclick nano_fix_ip_windows.bat)

After execution the camera should be reachable under its standard IP-address 192.168.3.15.

This process may require several attempts to work.

Vary the time in step 3 if a try is not successful.

Download-Link: vc_z_fix_ip.zip

• create a script file named “user_init.sh” in the folder /etc/vcinit/
• write in it your program calls
• the script user_init.sh has to be executable. This can be done with the command “chmod +x user_init.sh”
• the script /etc/vcinit/vcinit.sh calls the script user_init.sh at startup if it is available.

An example file can be found attached. Pay attention to the path for the programs to be executed.

Download-Link: user_init.zip

For VC Lib Q / Halcon users: at the time the user_init script is executed the Halcon environment variables are not set yet, which leads to errors while attempting to start the program. To prevent this, the environment variables have to be set in the user_script too. See the attached example.

Download-Link: user_init_vclibq.zip

The serial device on the VC Z Series cameras is

/dev/ttyPS0

The serial device can be used using the standard Linux method.

Ex-factory the RS232 interface is used by the serial shell. To be able to use the RS232 interface from one’s program it is necessary to disable this shell first.

This will disable the service at boot time:

#systemctl mask serial-getty@ttyPS0.service
Created symlink from /etc/systemd/system/serial-getty@ttyPS0.service to /dev/null.

This will reenable the service at boot time:

#systemctl unmask serial-getty@ttyPS0.service
Removed symlink /etc/systemd/system/serial-getty@ttyPS0.service.

This will start the service at run time (ONLY when unmasked see above!):

#systemctl start serial-getty@ttyPS0.service

This will stop the service at run time:

#systemctl stop serial-getty@ttyPS0.service

The attached program shows to to read/write from/to the RS232 interface. It is designed as an example only, for it to actually run successfully the TX and RX pins on the VCSBC nano Z board have to be connected together.

Download-Link: rs232.zip

The i2c interface is "standard Linux" programming, information is available here:
https://www.kernel.org/doc/Documentation/i2c/dev-interface

It is necessary to know the device name. On the VC Z cameras it is:

/dev/i2c-0

Any i2c address can be used except 0x68, which is used by VC for the real time clock.

There is also a debian package for testing the i2c interface easily from the command line (i2c-tools, documentation here: https://manpages.debian.org/buster/i2c-tools/index.html). It is installed be default on VC Z cameras. Simple use examples:

Detecting all devices on i2c bus 0 (zero):

i2cdetect –r 0

Writing 0xff to device with address 0x44 to register address 0x11:

i2cset –y 0 0x44 0x11 0xff

To update your VC Z Camera, ensure your camera has an internet connection and execute the script /root/up.sh with

bash up.sh

The script will download and install the latest VCLinux Kernel, as well as the latest Debian packages from VC (libraries and tools).

If you cannot connect your camera to the internet, please send a request for an offline update package to our support: suppormlt@v_pk0ision-componenffts.cud+om.

The demo program linked below shows how to read the serial number was well as the product number and FPGA version. 

Download link: ver.zip

To create an image of your camera and optionally duplicate it on other cameras, follow the instructions in our online manual:
https://www.vision-components.com/fileadmin/external/documentation/software/image/camera_image.html

Each hardware documentation contains a description of the corresponding camera’s GPIO pins and numbers.

The attached program shows how to read and write from and to the GPIOs.

Download-Link: gpioTest.zip