Skip to main content

Dream Chip Camera Set Up and Test

Setting up DreamChip cameras (SSM-500 example)

 

Cables to camera

The camera ships with a special cable that connects the Hirose connector on the camera with 

    • a) 12V Power (Broadcast 4-pin XLR) - Attach this to a 12V power supply
    • b) serial RS485 communications (3 Pin female mini XLR) - Attach this to a USR-TCP232-306 Ethernet-Serial converter on T+(A) = orange (mini XLR pin 1), T-(B) = black (mini XLR pin 2) and GND = brown (mini XLR pin 3)

image-1647512462854.png

 

 

 

Ethernet-Serial converter

Follow instructions for the Ethernet-Serial converter to get it onto your network. When done, make sure to provide it this Serial setup for operation with the DreamChip camera:

image-1647512470167.png

Baud Rate: 115200

Data Size: 8 bit

Parity: None

Stop Bits: 1

Local Port Number 5000

Work Mode: TCP Server

 

Bug on USR-TCP232-306: It looks like the red TX and green RX LEDs on top of the unit is labeled wrong: On one or more of the units we have tested, it's clear that RX will blink green as we send out content on the serial bus and TX blinks red as we receive content. It feels more intuitive that the TX LED should blink in that case (and vice versa).

 

The "Link" LED will light up when the device has a network connection. It may not turn of if you pull the plug though - apparently it won't detect such a disconnect.

 

Test connection

Open a terminal and use "nc" (netcat) or telnet to connect to the converter on port 5000. Using "nc" will send LF as line ending. The camera (SSM-500) has proved to respond correctly to both "LR" and "CRLF" line endings. When connected, you won't receive any greeting, but type in "100 identify" and press enter and you should see the camera answer back. Will look like this:

 

kasper@Kaspers-MBP-2 ~ % nc 192.168.10.48 5000

100 identify

 

id: caterham_hs 1 0 0 ATOM one SSM500

OK

 

Here, we're connecting to converter on IP 192.168.10.48. The blue tekst is the command to the camera, the red is the cameras response back to us. This response shows that the camera has ID = 1 (bold). If multiple cameras were on the serial bus, you would see more cameras respond and announce their ID.

 

Notice: The converter will accept multiple connections over IP, but the responses from the camera(s) will be returned to all clients regardless of whether they were the sender of a command. The DreamChip cameras is NOT designed to work with multiple masters, so make sure that only one connected client over IP is talking to the camera - any other clients should only listen to the conversation (if that is even useful for them). If you desire a multi master workflow with DreamChip, you should use a SKAARHOJ Blue Pill with the DreamChip device core which will provide a multi master interface with the BPDC protocol.

 

Back to top