The IP camera address is always the key if you would like to monitor or remote viewing it. Like any network device, the camera is assigned an IP address when it is connected to the router with Internet access and powered on.
Here we will introduce 3 ways to find the network camera IP address quickly and easily.
AUTODOME 7000 HD, MIC 7000i, and MIC 9000i
Why is the minimum FW version 6.52.0003 for these models?
In November 2018 an internal hardware (HW) change was made to these models that requires this new minimum FW version. The new HW version isn't backwards compatible with older FW versions.
If the unit has been upgraded to a higher version, how do I get the 6.52.0003 FW?
This FW version was only released for these three models, so it isn't available on the Bosch Download Store. At this time, please contact Technical Support to obtain this FW. It will be available on the individual Product catalog pages by March 11, 2019 (or sooner).
RTSP and multicast streaming
There are different ways for a client to receive a multicast stream:
the client can connect to the camera and request a multicast stream. In this case you would see a connection in the dashboard.
If not checked, it requires at least one connected client to have the camera provide the stream into the multicast group. Clients who just joined would receive no stream if there is no client connected.
the client can join an existing multicast stream without connecting to the camera. It must know the multicast group. You would not see this client on the dashboard.
The streaming flag tells the camera if it should feed its stream into this multicast group, regardless of a connected client. This is an option if there are many, many clients possibly connecting to the same camera/stream.
There is no difference in data amount if streaming is checked or not as long as there is at least one multicast client connected to this multicast group.
Below you find a way how to pass a special connection string to request a multicast stream via RTSP from a BOSCH IP camera or IP encoder.
MIC IP starlight 7000i (MIC-7502-Z30x), MIC IP fusion 9000i (MIC-9502-Z30xxx)
MIC IP starlight 7100i (MIC-7522-Z30xx), MIC IP Ultra 7100i (MIC-7504-Z12xx)
AUTODOME IP starlight 7000i (NDP-7512-Z30xx)
Complaints received about video performance in terms of sharpness, focus, and color.
AUTODOME IP starlight 7000i, MIC IP starlight 7100i.
Complaints received about focus failure,
MIC IP starlight 7000i, MIC IP fusion 9000i .
Complaints received about NTCIP control of Autofocus, Autoiris, and MIC wiper.
MIC IP 7000i, MIC-9000i: Focus failures caused by an unexpected range of tolerances in a small percentage of lenses.
AUTODOME IP starlight 7000i: Incorrect default settings, camera block performance, and compatibility issue between the optical characteristics of the bubble and the camera block.
MIC IP starlight 7100i : Sharpness and color performance were not aligned with the previous model.
Autofocus and Autoiris functions were released in 2007, but the NTCIP standard was changed in 2014. These functions were not used in the ITS market until recently.
NTCIP Wiper Operation
This operation was never implemented and no complaints were received until June, 2020.
FW release 7.72.0008
Contained camera block FW for video improvements for the MIC IP starlight 7100i and the AUTODOME IP starlight 7000i .
Contained the NTCIP Autofocus, Autoiris, and MIC wiper control implementation for all of the models.
FW release 7.80.0128.
Contains new camera block FW with additional video improvements for the AUTODOME IP starlight 7000i and still contains the camera block FW for the MIC IP starlight 7100i.
Contains new camera block FW with focus improvements for the MIC IP starlight 7000i and MIC IP fusion 9000i.
All of camera block FW updates require an additional step for the FW upgrade process, which is described in the documents attached.
The MIC IP starlight 7000i and MIC IP fusion 9000i focus improvements are only applicable to a specific S/N range, so there is a separate FW upgrade for these models.
he Project Assistant offers two ways of importing existing project data:
Option 1) Importing a .bpassist file, which was exported from the app at some point and which contains all information and data ever created/entered inside the app for that specific project. Simply select the "Project Assistant" mode >> click "continue" >> and press "import".
Option 2) Importing from a tab-separated text file. This option may be useful, if you have existing project data, e.g. in an Excel spreadsheet, which you want to transfer into the Project Assistant for further use.
This article deals with option 2 and explains the steps potentially needed before you can refer to the steps explained in the following Youtube video ("Import from file").
What you should know when you request a password reset for the Bosch IP camera?
If you forgot the service level password for you Bosch IP camera and you want to reset its password, the Central Support Team can help you.
Before requesting a password reset for your IP camera, please note that you need to provide some important information to the Central Support Team to get help from them.
This article contains detailed examples for the absolute position functions of the various IP models of the Autodome & MIC cameras.
The support model series are: • Current Models: AUTODOME IP 4000/5000, AUTODOME IP 4000i/5000i, VG5 IP 7000, MIC IP 7000 & MIC IP 7000i, MIC IP 9000i • EOL models: VG5 700, VG5-800, JR HD
NOTES: 1. These commands will NOT work with either the Analog cameras with the serial interface.
2. The HD cameras do not support the OSRD absolute position commands. The HD models operate using the BICOM protocol over IP.
Which CPP corresponds to certain cameras and encoders?
The capability of a Bosch IP camera or encoder is driven by two forces: One is the hardware capability, defined by the Common Product Platform (CPP) itself and the combined components of the product. The other is the firmware that drives this hardware. The firmware is developed on a common code basis and derived from there for the active platforms, making the feature sets of various platforms fairly similar within a certain firmware version.
This article gives an overview of CPPs that correspond to certain types of cameras and encoders. Here you can search by the CTN of the camera and find out the CPP of it. Thus, you will know which firmware you should use for upgrading your device.
A possible situation can occur when you have, for example, one DIP 3000 with BVMS 8.0 and CPP7.3 cameras. The cameras are not working because the firmware is old.
The problem that might arise could be:
Configuration Client will display a message like: "unknown platform"
Gaps in recordings or not recording at all
VCA settings cannot be changed
Logs warning: "2020-11-22 04:49:29.339;cameraId=10.13.22.98\0\1;Sender;Error;This device has an abnormal high storage consumption. To protect other recordings, storage allocation is reduced. But this may result in recording gaps for this device"
Some devices that demand 60W or less are not powered by the NPD-9501A Midspan
Possible causes and solution(s)
Some devices that demand 60W or less are not powered by the NPD-9501A Midspan
The Midspan was released before the standards on mega poe were crystallized into accepted definitions at the IEEE standardization body. This device specifically targets to support power application to Bosch products that could not be served by lower capacity power source equipment.
Using power devices that are not listed for this product in the datasheet migth result in power failure.
NPD-9501 Midspan will not work with UHO-PoE-10 Housing
For products demanding 60W or less advise to use NPD-6001B Midspan.
To achieve a broader compatibility with switches and Midspans, for example the NPD-9501 Midspan and Cisco PoE+ switches (like C2960X, C3560CX and C9200).
The UHO-POE-10 Outdoor housing received a product enhancement.
How to identify if UHO-PoE-10 is the new variant?
The new batch contains products which contain SN starting with 404023113800040670
POE module is Blue, previous was Black!
Web Browsers: o Google Chrome o Microsoft Internet Explorer 11 or higher o Microsoft Edge (Chromium based) o Mozilla Firefox
When using browsers where Mpeg ActiveX is required → VCA, clock & date and recording dot point may not work.
For a complete browser functionality, Mpeg ActiveX 6.34 or newer is needed and it is supported only by Internet Explorer (IE). This is the only browser that allows the VA configuration option (for e.g.).
If you would like to avoid using IE and you want to configure VA, it is recommended to use Configuration Manager.
According to the Release Letter, Configuration Manager is used for configuration and licensing of the various products. It includes Video SDK 6.3 and latest plug-ins for VCA configuration.
You can Download it from here.
If you use Firefox, the issue below might arise. In this situation, IE browser/ CM is recommended to be used in order to access the missing elements.
Firefox does not allow ActiveX elements . Therefore, some features are missing inside the webpage.
Note: VCA related check boxes is fixed in 7.80 for Microsoft Edge. (7.80.0128 Release Letter)
In certain situations of the support process for a particular product, the customer number and the material/ serial/ commercial type number of your Bosch device may be required.
But where can you find them?
The purpose of this article is to help you find this information in different ways.
Extra licenses can be purchased for additional features of your devices as your business grows.
After adding cameras to the system, you may need to use additional features of them, like microphone use, Serial Protocol Software License, Camera Trainer license for Intelligent Video Analytics, NTCIP license for moving cameras and so on.
Depending on the camera model, you can have additional features by installing the optional lice nses.
Follow the instructions below and find out how you can activate a license on your camera.