About Central-Support

  This may occur after a FW upgrade to CPP7.3 FW 7.72.0008 or higher. Or it can occur after an ITS software is updated, but the camera remains at a FW version less than 7.72.0008. Possible causes and solution(s)   Causes Auto focus, Auto iris, and wiper functions were first released in Bosch Moving cameras in 2007 per NTCIP 1205:2001 v01.08. In September 2014 the standard was revised to NTCIP 1205 v01 AMENDMENT 1. Bosch did not implement the changes at that time. An increased amount of Department of Transportation (DOT)in various states have integrated Auto Focus and Auto Iris controls into their ITS software.   At the request of a major DOT customer, the Bosch FW was updated to meet NTCIP 1205 v01 AMENDMENT 1 in November 2020 as CPP7.3 7.72.0008. This in turn can break the functionality in other states that have not upgraded their software to NTCIP 1205 v01 AMENDMENT 1. Or, the ITS customer may upgrade their software to NTCIP 1205 v01 AMENDMENT 1, but are using a FW version less than CPP7.3 FW 7.72.0008. The new software implementation can break the functionality with the older FW.   Solution If the problem occurs after the upgrade to 7.72.0008 or higher, then please contact the software supplier and request that they update to the latest standard. The software supplier may not want to implement this globally, since some other camera manufacturers may not have updated to this standard. If this is the case, then the software supplier could possibly develop a driver for the Bosch cameras and others that use the 2014 standard. Or the cameras must be downgraded to FW to 7.70.0126. For security reasons this older FW has been revoked and is not publicly available. Contact Technical Support to request this FW via a legacy FW waiver process. If the control problems occur after the ITS software is updated to NTCIP 1205 v01 AMENDMENT 1, then the camera is probably still less than 7.72.0008. Upgrade the FW to the latest version available at the Bosch Download Store.   ... View more

  Possible causes and solution(s)   Causes MIC-7100i IP starlight or inteox does not format/record microSD/SD cards. MIC-7100i IP starlight or inteox stops recording on a full size SD card and reports the SD card in an offline state. MIC-7100i IP starlight or inteox will not format/record on a full size SD card with a capacity greater than 64 GB.     Solution Use only a full size SD card. Do not use a microSD card with an SD card adapter. If acceptable for the use case, use only a 64 GB or smaller SD card. If greater than 64 GB is required for the use case, then determine if the Serial Number (SN) of the camera is lower than 0446797*23717*011005 (January 17, 2022).         a. If the camera was made before this date, then the customer must request an RMA for an Advanced Exchange (AE).                  i. The replacement unit will have a minor HW upgrade to support full size SD cards greater than 64 GB.                  ii. Any MIC-7100i IP inteox must use CPP13 FW version 8.45.0032 or higher.                 iii. Any MIC-7100i IP starlight must use CPP7.3 FW version 7.84.0023 or higher.         b. If it was made after this date, the only requirement is to upgrade the FW.                 i.Any MIC-7100i IP inteox must use CPP13 FW version 8.45.0032 or higher.                ii. Any MIC-7100i IP starlight must use CPP7.3 FW version 7.84.0023 or higher. 4      At this time, the new FW does not support an Auto-Format. Refer to the Release Notes attached for more details.         a. The SD card must be formatted manually, regardless of whether it is new or has already been used for recordings. IMPORTANT: If any previous recordings exist, they will be erased.     SD Cards Tested by Bosch The following three Western Digital full size SD cards have been tested and are available for order from Bosch with the part numbers listed below. They have been added as accessories to the camera datasheets. SD-064G / F.01U.394.677 SD-128G / F.01U.394.678 SD-256G / F.01U.394.679 If the installer/customer wants to use an SD card of a different brand, then they must make sure that the card is equivalent to the recommended card from Bosch. The installer/customer is responsible for testing to ensure that the card is fully compatible.. The recommended test is to: Ensure that the FW has been upgraded to the fixed versions listed in the solution Step 3. Install the card on a bench test, format it, set up recording, and test it until it is full and has started to record over the video from when recording was started. ... View more

Question   Why the ‘SD card Status’ is missing in GUI of MIC IP starlight/ultra/inteox 7100i camera?   Answer   This is as per design for MIC models since the design architecture for MIC camera is different from fixed camera. On the MIC IP series, the SD card slot is internally connected via USB. Therefore, most of the SD card status information which is normally shown on the SD card status page can unfortunately not be read from the SD card. This article is also applicable to the following MIC IP series. MIC-7522-Z30xR MIC-7504-Z12xR MIC-7604-Z12xR Additionally, note that the Health monitoring of industrial SD cards with early service indications is not supported for these models. ... View more

  Causes and solution(s)   In some occasions, you can have an unwanted "rtp.p_type 97" packed in your video stream. This "rtp.p_type 97" packed can cause on some decoder Brands (for example Barco) a memory leak. This article describes the behavior of "rtp.p_type 97" for the following 2 platforms: CPP4: for example on the MIC IP starlight 7000 HD, the "rtp.p_type 97" is always active and can only be de-activated with an RCP command CPP7.3: for example on the MIC IP starlight 7000i, it can be switched on when using Video authentication, but after switch off, the camera needs a restart How to turn ON/OFF for CPP4 moving camera Payload Type 97 - RCP+ command to disable/enable the generation and transmission of those packets: RCP+ CONF_PIC_INFO   Tag Code NumDes Message SNMP Support   0x0b8e no no no   Data type Access Level Description Read t_octet access_right_minimal enables/disables the generation of pic info packets (payload type 97) Write t_octet access_right_service enables/disables the generation of pic info packets (payload type 97)  This RCP+ command was added and available since firmware version 5.80 and per the RCP+ documentation it is still applicable for CPP4 firmware version 7.10. After sending this command, the “rtp.p_type 97" packet stops Off> http://ipaddress/rcp.xml?command=0x0b8e&type=T_OCTET&direction=WRITE&payload=0x00&num=1 On> http://ipaddress/rcp.xml?command=0x0b8e&type=T_OCTET&direction=WRITE&payload=0x01&num=1 Note: As its on by default, it will also turn back on after factory reset Once it is turned off, it will also remains off after a reboot   How to turn ON/OFF for a CPP7.3 moving camera When choosing the Video Authentication option "SHA-1" , "rtp.p_type 97" will be added to the video stream But when you turn it OFF again "rtp.p_type 97" will remain ON and doesn't stop, until you have restarted the camera. "rtp.p_type 97" stream should stop when switched off Despite the fact of disabling OSD, telemetry feedback, timestamp, and watermarking, the “rtp.p_type 97” continues:   Solution A camera reboot is required when an Authentication other than Watermark is toggled ON and then OFF.   Additional information:   "rtp.p_type 97" can contains OSD information like for example: Title OSD: Sector or Shot Title Camera OSD: Digital Zoom, Iris open/close, Focus near/far OSD User defined 1 OSD User defined 2 OSD User defined 3 Time Information Hash / Signature Entry ... View more

Possible causes and solution(s) Causes When using motion/ analysis recording you will get a recording error on the Remote Portal every time the camera stops to record. If the camera records on its SD card on alarms only, Remote Portal is showing Recording Error (which is obviously not). Note: If you configure Alarm Recording with pre-alarm to RAM (no Continuous Recording), there is no continuous recording on the target (SD or VRM) which triggers the error.     Solution Try the following workarounds: You should configure Continuous Recording OR Alarm Recording with Pre-alarm Recording on SD OR You should disable the Health Status for such camera from Remote Alert Service until the issue is fixed.   ... View more