Important Cookie Information

This website uses absolutely necessary cookies. If you consent to the use of convenience cookies, please click “Yes, I agree.” By clicking on “Privacy Settings.” you can change this setting at any time and withdraw your given consent. Icon down see more You can find detailled information in our Privacy Policy Icon forward-right
Icon up see less

Bosch Building Technologies

    cancel
    Showing results for 
    Search instead for 
    Did you mean: 

    How to troubleshoot BVMS SDK Scriplet or issues in BVMS System using BVMS SDK functionality

    Related Products:
    BVMS SDK, BVMS 

     

    Overview:

    Analyzing BVMS systems with SDK components is a challenging task,
    because the functionality and the runtime behavior of those systems are harder to determine
    than for a BVMS systems without SDK functionality.
    In order to troubleshoot BVMS systems with SDK components support needs the following information and logging.

     

    Please prove the following information to support.

    1. Detailed description of the expected behavior of the SDK functionality.

    2. Detailed description of the actual behavior of the SDK functionality.

    3.SDK Components

    • What type is the standalone SDK application (based on ClientSDK, ServerSDK, or CameoSDK) and on which machine is it running?
    • Are there additionally client scripts, server scripts or workstation startup scripts?

    4.SDK Interactions

    • Do SDK components interact with remote Operator Clients?
    • Do SDK components interact with the Operator Client UI?
    • Do SDK components control devices?
    • How often are client scripts triggered?
    • How often are scripts triggered by BVMS event?

    5.Environment

    • Which shared resources are accessed by SDK actions? (Dome cameras, AMG, Operator Client UI)
    • Do SDK components interact with an unreliable environment? (Unstable network, offline devices, offline PCs, etc.)
    • Do SDK components properly handle offline situations? (offline devices, configuration changes, etc.) 

     

    Please provide the Scriplet and/or Log files

    The optimal approach is to provide both the scriplet and logging.

     

    Version history
    Revision #:
    2 of 2
    Last update:
    ‎04-01-2019 12:33 PM
    Updated by:
     
    Labels (2)
    Contributors
    Icon--AD-black-48x48Icon--address-consumer-data-black-48x48Icon--appointment-black-48x48Icon--back-left-black-48x48Icon--calendar-black-48x48Icon--center-alignedIcon--Checkbox-checkIcon--clock-black-48x48Icon--close-black-48x48Icon--compare-black-48x48Icon--confirmation-black-48x48Icon--dealer-details-black-48x48Icon--delete-black-48x48Icon--delivery-black-48x48Icon--down-black-48x48Icon--download-black-48x48Ic-OverlayAlertIcon--externallink-black-48x48Icon-Filledforward-right_adjustedIcon--grid-view-black-48x48IC_gd_Check-Circle170821_Icons_Community170823_Bosch_Icons170823_Bosch_Icons170821_Icons_CommunityIC-logout170821_Icons_Community170825_Bosch_Icons170821_Icons_CommunityIC-shopping-cart2170821_Icons_CommunityIC-upIC_UserIcon--imageIcon--info-i-black-48x48Icon--left-alignedIcon--Less-minimize-black-48x48Icon-FilledIcon--List-Check-grennIcon--List-Check-blackIcon--List-Cross-blackIcon--list-view-mobile-black-48x48Icon--list-view-black-48x48Icon--More-Maximize-black-48x48Icon--my-product-black-48x48Icon--newsletter-black-48x48Icon--payment-black-48x48Icon--print-black-48x48Icon--promotion-black-48x48Icon--registration-black-48x48Icon--Reset-black-48x48Icon--right-alignedshare-circle1Icon--share-black-48x48Icon--shopping-bag-black-48x48Icon-shopping-cartIcon--start-play-black-48x48Icon--store-locator-black-48x48Ic-OverlayAlertIcon--summary-black-48x48tumblrIcon-FilledvineIc-OverlayAlertwhishlist