About Central_Support

Intro   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.   Step-by-step guide:   Conference Protocol Demonstrator   Please note that a web based demonstrator is available to assist developing and debug fixing for your own interface. The documentation and how tow use it can be found at this link. https://licensing.boschsecurity.com/software/html/pages/home/ https://licensing.boschsecurity.com/software/DICENTIS/ConferenceProtocol.chm   First test is to see if the port is available if not please check your IP settings.   Enter the following in your browser. https://<ipaddress>:31416/Demonstrator/ConferenceProtocolDemonstrator.html In this example the server has the IP of 169.254.212.209 (due to a test without DHCP, not recommended to use this Link Local address for your server!) If you see this page you can reach the web server.   Second example to open the Demonstrator:   As next step we will show you a simple method to test the web socket and command the DICENTIS some tasks. If this is working, then the Dicentis web socket is fine. First you have to install Weasel ADD-ONS in your browser.   Secondly you have to settle the connection with in Weasel. Please enter the following. "URL:" wss://<dcnm_server_ipaddress>:31416/dicentis/api   (in this case = wss://169.254.212.209:31416/dicentis/api  ) and open "Protocol" DICENTIS_1_0 If you did everything right it will show you "CONNECTION READY"    Next let's log in the DICENTIS.  The user name is "admin" and we have no password set "" { "messageId": 2, "operation": "Login", "parameters": {"password":"", "user":"admin" } }     You will get this response.   Now let's try to get some seats. { "messageId": 3, "operation": "GetSeats", "parameters": {} }     Oh I forgot to switch the DICENTIS on. { "messageId": 4, "operation": "GetSystemPowerMode", "parameters": {} }     Than lets switch it on now. { "messageId": 5, "operation": "SetSystemPowerMode", "parameters": { "powerMode": "poweredOn" }     With this short commands we were able to test the connection and control the DICENTIS. If you need additional information please have a look at "ConferenceProtocol.chm" under Docs which is provided within the DCNM Software. Please always use the same .chm protocol as you are running right now. If you update your system don't use the old one anymore since were are for example some changes implemented from time to time. If you use a Crestron system in between please do first a backup so that you can easily switch back if needed. You will probably have to change your programming depending on your version. Please check History before you go for a higher version. https://licensing.boschsecurity.com/software/DICENTIS/DCNM.iso   With the Debugger you can look into the program code.   Please note that every command is described in the Conference Protocol Reference!   And you can check it with the Conference Protocol Demonstrator. Please check the History before you update your system because it is steadily improving and some commands were changed.   Partner Companies which are using our open control design like for example conference protocol to build custom made control platforms are for example MIV. https://www.mvi-audiovisual.com/easyconf-and-bosch/ ... View more

Intro   Rapid Spanning Tree Protocol (RSTP) is needed if you want to set up redundant cabling via loops. By default it is disabled and even if you update your DICENTIS Conference Software it will be again disabled and has to be activated afterwards. Also third party switches must comply with IEEE802:1D-20- 04 and support RSTP. Please also note that loops have a limited hops which are lower than 21 (devices). If you need more information regarding this please have a look in the installation manual. With the old DCNM-PS it is not possible to loop to other DCNM-PS devices.   With the DCNM-PS2 you can loop it as you please and give your system more redundancy. (22-3=19 hops / devices ) 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. The pros of the an redundant system is that the recovery time in case of an failure in the communication link is much faster and is avoiding serious operational impact. And the disadvantages is if an error occurred in the system it will not surface immediately and stay hidden. Also an intermittent loose connection is an challenge to the RSTP protocol and can bring it down in the worst case. As the old Spanning Tree Protocol (802.1d) is slow and is untuned taking 30-45 seconds from blocking to forwarding the new RSTP protocol (802.1w) supports recovery time around 100ms to 200 mill seconds and around 6 seconds if the root bridge fails.   The Root Bridge is the center of the network and all units find the best way to connect to the Root Bridge and then block all redundant links which are not the best way. It is divined by the Root Bridge Priority. OMNEO has changed the default value for RSTP timers. Timer Default Value Value used in OMNEO HelloTime 2s 9s MaxAge 20 22 ForwardDelay 15s 30s One reason is that the boot time of an OMNEO device is about 15s and not BPDU for 3* Hello Time.   There is also an maximum of 22 devices counted with 1 from the root bridge. Each time packets are passing through a network device, for example server, switch, DCNM-PS2 or DCNM-MMD2, it will add delay and is counted as one hop. The max latency is 10ms which leads with an calculated bit error rate to 22 hops which is the limit of RSTP. If you use more devices it will still work until the loop and redundancy breaks and only 22 units will pass through.  This leads in a typical DICENTIS installation to an max of 19-17 discussion units in one loop.   Step-by-step guide:   RSTP enabling Type in the search column (Windows + S key ) "advanced system settings" than click on "Advanced" and on "Environment Variables".   Create a system environment variable named DCNM_RSTP_ENABLED and set the value to 1 to enable RSTP, and 0 to disable RSTP. Restart the DICENTIS services.   Additional way to find this settings… (not needed it's just a another way how to do it)   Additional you can open the file explorer (Windows + E Key) and do a right mouse click on "This PC". After that select Properties and open Advanced system settings.   Click on "Advanced" and on "Environment Variables"   Now change the "Variable value" from 0 to 1 to activate the RSTP   Restart services of the DICENTIS. ... View more

Possible causes and solution(s)   Cause:   During upgrading the DICENTIS Conference system to 3.60, TLS1.0 securoty encryption will be disabled and replaced with the new TLS1.2. Since the first generation of Multimedia Device (MMD) do not support TLS1.2 instead of MMD2 version, it will not be possible anymore to show an logo or participant images on old harware MMDs. Please check the Release Notes for problems. https://licensing.boschsecurity.com/software/DICENTIS/RLN_DCNM_en.pdf   Solution:   If you have such old MMD units you need to switch back to the old TLS1.0 encryption manually to get them working again. (MMD2 are not involved) Quick steps: Open a command prompt in Administrator mode. Run \Tools\TLS_MMD\EnableTLS1.0.bat from the DICENTIS Software. Powercycle the server. Note: This directory in our Software also contains the opposite to activate TLS1.2.   Procedure: Go to the homepage and download the newest software. https://licensing.boschsecurity.com/software/html/load.htm?1000 Direct link: https://licensing.boschsecurity.com/software/DICENTIS/DCNM.iso     Open DCNM.iso file from 3.60 or newer.  (I have renamed the DCNM.is file to DCNM_3.61 so that I know which version it is)   Run \Tools\TLS_MMD\EnableTLS1.0.bat from the DICENTIS Software DCNM.iso file ... View more

This article provides instructions for exporting and saving the program from an FPA-1000 to be imported into a replacement FPA-1000 panel. This information may be needed when replacing an FPA-1000 fire panel with another with intentions to use the same panel program.   Step-by-step guide   1)  Connect to the panel over the site network or by using a crossover Ethernet cable. Log into the panel as normal to access the FPA-1000 Online Start Page (see figure 1). Figure 1 Download a copy of the existing panel 2) Select Download configuration. 3)  The panel program is downloaded in an XML file format which may appear as programmer’s data (see figure 2). Figure 2 Downloaded panel program as XML file 4)  Select File >Save Page As… to save a copy of the current configuration. Be sure to save the file using the default option; [Web Page, Complete (*.xml)] (see figure3).  Figure 3  Save the downloaded panel program 5) Upload the FPA-1000 configuration to the new panel. a.  Log into the panel as normal to access the FPA-1000 Online Start Page as described in step 1. b.  Select Upload configuration (PC -> FPA-1000). Browse to the location of the saved file and press Upload (see figure 4). Figure 4 Upload configuration to the panel 5)  The new panel is now ready for testing. ... View more

In some rare cases the log file from the Dicentis Server become too big and it should be cleared to reduce the size from time to time. (Normally only after many years) 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, it is most likely that a error occurred within the DICENTIS system and produce a lot of logging data each minute. In the next steps we will show you how to clear the logging. For more details please have a look in our Release Notes as well in the Configuration Manual. https://licensing.boschsecurity.com/software/DICENTIS/RLN_DCNM_en.pdf https://resources-boschsecurity-cdn.azureedge.net/public/documents/SWM_Configuration_Manual_enUS_72057607375843211.pdf https://commerce.boschsecurity.com/nlexp/en/System-server/p/F.01U.404.927/   Step-by-step guide:   Clear the logging Open the logging program of the DICENTIS server. C:\Program Files\Bosch\DICENTIS\Bosch.TestUtils.LogViewer.exe   First Dump the logging to a text file to archive the old one next click on Clear Logging Database. You can find the archived LogDump under this path. C:\ProgramData\Bosch\DICENTIS   ... View more