There could happen some occurrence were you should return your Dicentis wired license.
Reasons can be for example a hardware error, Windows software problems or an Windows upgrade of the Dicentis server etc…
After upgrading to DICENTIS Conference system 3.60, TLS1.0 is disabled for security reasons, and TLS1.2 is enabled. Since the Multimedia device does not support TLS1.2, it does not show logo and participant images anymore.
When upgrading from a previous DICENTIS version that supports DANTE (V2.20 – V3.00) to the latest version 3.10, the following problem will occur; The DICENTIS system is not visible anymore in the Audinate’s DANTE controller software, where it was visible before the upgrade.
In order to change the layout, the StyleSheet needs to be changed. Default it is located in C:\ProgramData\Bosch\DICENTIS\VotingResult.xslt, this file can be opened in any text editor, Notepad++ is recommended as it is very versatile.
The new INT-TXO Integrus Transmitter integrates the Integrus system in the DICENTIS via OMNEO. Old Radiators and Receivers stay the same and existing equipment can be used in the DICENTIS now with the new INT-TXO transmitter. It is usable from software version 4.20 onward and is made for DICENTIS only usage at the moment. But it will be open up in future for the usage of 3rd party devices which than are planned to be managed with the Dante Controller software. Please visit our product page for more information.
When using a fixed IP addresses in a multi-subnet Dicentis system, certain settings need to be made for the system to function well. If the settings are not made correctly, the system can stop functioning & disconnect from the server.
Trouble mixing and matching older & newer Dicentis cable assemblies, cables and connectors. The problem is usually that the cables and connectors do not fit together correctly or it's very hard to put them together.
Possible causes and solution(s)
The Dicentis does not need any additional encryption to be set via the OMNEO Firmware Upload Tool. (OFUT)
If you have set this by accident it could lead to that you can not see or update your units with the OFUT any more.
stop the Firmware Upload Tool
delete the following file C:\Program Files\Bosch\OMNEO\Firmware Upload Tool\FirmwareUploadHIConfig.ini
start the Firmware Upload Tool
Encrypted devices did not show up and you can not update them anymore. Do not set a password for default!
Open and delete this file C:\Program Files\Bosch\OMNEO\Firmware Upload Tool\FirmwareUploadHIConfig.ini
Open the OFUT and units will appear again.
The DetectDevices script was developed to give a fast feedback on connection problems or any other failure within the DICENTIS wired system. It will simulate a device and give out an advanced log file which can be used to track sporadic or normal connection problems. The technical support will provide this tool to get a deeper look into some issues if needed.
To send or receive a multicast Dante stream for example from different languages it will require some DCNM-LDANTE licenses but if you only need it for import and export audio signals the DCNM-LSYS includes already one channel (floor).
The Conference protocol is a platform-independent protocol which is based on Web-Socket technology to enable scalability of the DICENTIS system and it connects with the DICENTIS web server.
This is a small introduction to test if the web socket is basically working and if the connection is right.
If RSTP is not enabled in an looped system packets will loop infinitely exhausting all available bandwidth and could cause an overflow of MAC address tables.
In the end it will result in a broadcast storm and breakdown of the entire network.
In some cases the log file from the Dicentis Server become too big and it has to be cleared to reduce the size from time to time. The normal size is between 10MB and 50MB depending on the operation time but it should normally not grow over 100MB. If it does exceed, is most likely a fatal error within the DICENTIS system which produce a lot of logging each minute.
It could be possible that the driver of the Network Card (3rd party Server) to become intermittent and the log file to grow to 300MB. In the next steps we will show you how to clear the logging.
The DICENTIS cannot handle more than one enabled NIC at the same time and this could lead that it choose the wrong NIC and interrupts the system.
This will be specially important if you use your own Server. To solve this problem it is necessary to precisely define the DICENTIS NIC.
These next few steps will show you how to do that.
The DICENTIS Server has a own log file system which is working in the back ground and is called LogDump.
If something went wrong during the operation it will be reported in there. In many times this is a good tool for error analysis as well as fault detection and will often requested by the Technical Support for pre-analysis.
In the next Step-by-step guide it will be shown how to extract the LogDump file form DICENTIS Conference System.
If you are facing unknown problems with your DICENTIS wired system and you need advice from the technical support they will ask for a lot of different information.
For that reason this little program was created to make the extraction of all needed log files, system settings and other data more easily.