What should be the specs for the output waveform of the inverter to work with Bosch MIC IP cameras? Should the inverter produce a sine/sinusoidal wave, a square wave or other?
This must be pure sine converter. Square wave has another power factor. The power factor of a load on a modified sine wave inverter is generally lower than that of a pure sine wave inverter. This is because a modified sine wave inverter produces a waveform that is not a perfect sine wave, and the load may not be able to fully utilize the power being supplied to it. Additionally, some loads, such as certain types of motors, may be damaged by a modified sine wave inverter.
It is important to ensure that the load and inverter are compatible to ensure optimal performance and prevent damage.
You can try to use: the Moxa PoE injector INJ-24A 60w 24vdc or similar offerings from Antaira Technologies or Micro Semi. An alternative to PoE injectors that run off 12/24vdc are 12/24vdc to AC inverters manufactured by https://absopulse.com/ or power stream https://www.powerstream.com/inv.htm
To power both 7100i with Illuminator as well as MIC-9000i thermal models, you can try to use the Planet IPOE-171-95W IPOE-171-95W - 802.3bt Ultra PoE Injector - PLANET Technology
The Midspan needs to be set to legacy mode and will run on 12VDC. The datasheet and the user manual of the Planet IPOE-171-95W midspan mention both a "Standard mode" and a "Legacy and Force mode" for PoE of the midspan.
... View more
This article describes how to move one or multiple cameras from one company (account) to another one in Bosch Remote Portal.
In Bosch Configuration Manager there is a feature in "Connectivity" tab to re-register a camera to another account in Remote Portal. However it was discovered that the implemented procedure is not safe in presence of errors (such as transient network issues), and might end up in the camera being permanently disconnected: the installer would need to drive on-site to register the camera once again.
Therefore please use the re-register feature in Configuration Manager only if you want to re-register the camera to the same account (e.g. to change the camera name in Remote Portal).
In Bosch Remote Portal there is now the feature implemented to change the cameras' company (account) without these effects.
Note: There might be some remaining manual work after the moving of cameras in the first step of implementation, however this can be done from remote, no travel on-site is needed for this clean-up.
To move the camera(s) to another company requires an Administrator user role in Remote Portal.
The Administator needs to be a user in both companies, the source and the target company.
The camera(s) need(s) to be online in the source company!
There must not be any activity ongoing for this camera(s) (e.g. no firmware update, no company change ongoing) before the camera(s) can be moved.
The Video Relay might change when moving the camera(s) to another company; therefore a different domain or IP address might need to be unblocked in the customer's firewall. Used domains see Troubleshooting Camera Connectivity & Bosch Remote Portal > Chapter 2
Offline cameras cannot be moved. The cameras need to be online in the source company to become moved to another company!
No groups can be moved to another company, but only cameras.
Only cameras of one group should be moved to the target company at one time
After the change has been completed, the cameras should be moved to the related group in the target company before moving cameras of the next group
All services activated for the camera and licenses assigned to the camera get deactivated and unassigned during the change!
Note down the license numbers assigned to the cameras to be moved in the source company.
Note down the services which are activated for the cameras to be moved in the source company.
Note down the users which are added to the cameras to be moved in the source company.
Connectivity to linked applications such as Cloud VMS get lost for the cameras during and after the change.
Note: There might be some remaining manual work after the moving of cameras in th first step of implementation, however this can be done from remote, no travel on-site is needed for this clean-up.
In Bosch Remote Portal logon as Administrator
In Systems tab select the list view
Select the camera(s) to be moved to another company
Click the "Change Company" icon
A dialog shows the number of cameras where the company can be changed
Select the target company
Click the Move button and wait until the change has been completed (depending on the amount of cameras this may take several minutes)
In the target company, move the cameras to the related group
Licenses and services
in the source company, copy the license numbers wich are now un-assigned after the change and delete the licenses in the source company
in the target company add the license numbers in the Service Licenses tab
in the target company activate the services which were activated before the change in the source company
in the target company add the users (customers) to the Remote Connect service like in the source company.
Cleanup in linked applications (e.g. Alarm Management)
Add the moved camera(s) to Alarm Management once again
Add the moved cameras to the related service(s) in Alarm Management and delete the cameras from the source company from the service(s) accordingly
Delete the cameras from the source company in Alarm Management's Devices tab Note: the moved cameras are now treated as new devices in Alarm Management.
... View more
Can I use hash tag # as special character in BVMS or camera’s password?
Hash Tag "#" is one of the few special characters, which is accepted by the camera, but it cannot be accepted on BVMS side (in order to connect to the camera) — due to the limitations of communication specifics some BVMS components are using. And as a result, communication might not work properly and "No connection" warning message in Operator Client image pane and black screen might occur:
⚠️ In BVMS Configuration Client, there's a very clear indication giving a warning, that this character should not be used:
But it still allows saving it.
If you'd be connecting cameras which had already password configured with this character (like "#") you can still add it to the system and change the password afterwards (as also clearly indicated in the prompt message). If it wouldn't be possible to save it, it wouldn't be possible to add such camera to BVMS at all.
You need to differentiate the two different types of passwords used in BVMS:
Camera password used to connect the camera with BVMS (where "#" is not allowed on BVMS side)
BVMS user passwords used to log in to the Configuration Client or Operator Client — here there are no such additional limitations, so "#" is allowed and different rules apply.
... View more
What to do if BVMS Operator Client cameo is white and the camera can’t be displayed (device failed)?
This may be caused by the NVIDIA graphic card driver that might not be compatible.
GPU decoding is supported on specific NVIDIA GPU’s:
− In general, the following NVIDIA Series: Quattro, RTX and T series are supported
− Specific NVIDIA Graphic card drivers need to be used to avoid issues. Therefore, depending on the BVMS version you have, please check the latest BVMS release notes.
GPU or CPU decoding? Which cameras benefit from which method in the Operator Client?
Below are the download links for compatible drivers for NVIDIA:
These 2 are compatible for BVMS 11.1.1:
470 version: https://www.nvidia.com/download/driverResults.aspx/185532/en-us/
510 version: https://www.nvidia.com/download/driverResults.aspx/186766/en-us/
Information found in BVMS Release Letter (page 10)
This is compatible for BVMS 12.0.1:
525 version: https://www.nvidia.com/Download/driverResults.aspx/199657/en-us/
Information found in BVMS Release Letter (page 12)
Along with installing the drives, if the issue persists, try also to disable the integrated GPU from BIOS.
... View more
Why is the BVMS SMA validity displayed as expired in the License Manager, the SMA being still valid?
For example, according to the Remote Portal Assurance PRO is valid until 05.09.2025:
While on the local software, the License Manager it is showing to be expired on 08.11.2022:
This mismatch of the SMA expiration date could occur due to the license being initially activated on an HW ID on an older version of BVMS. Afterwards the BVMS was upgraded to a higher version and the license was activated on the fingerprint. Therefore, the SMA has not been extended in Remote Portal after the upgrade of BVMS.
For the SMA expiration date to be displayed correctly, please download again the activation files from Remote Portal, remove the licenses from the server, upload the newly downloaded activation files to the server and check if the issue persists.
To remove the licenses from the server:
Stop the services Sentinel RMS License Manager and BVMS Central Server.
Locate the file C:\ProgramData\Bosch\VMS\LicFiles\lservrc and delete it.
Restart the Sentinel RMS License Manager and BVMS Central Server services.
Load the activation files in Config Client
... View more