Developer Portal Community

    We are moving! We are currently migrating our community to the new Bosch Connected Industry Online Portal. The community will be available latest in the new year again, until then it will be in read-only mode. Click here for more information.

    cancel
    Showing results for 
    Search instead for 
    Did you mean: 

    Nexeed Control Plus - Furness object error

    Nexeed Control Plus - Furness object error

    TiagoMoura
    Member

    Hello everyone,

    We are trying to use the Furness peripheral object FCO75x (1.2.0.0) with the object Flow Test (1.2.0.0) with Control Plus Studio v5.4.

    Everything works fine but we get the error below when we use the Furness device in Single measurement and the test is finished. We still get the test results but the error is rised and we need to clear it before we can perform another mesurement.

    Anyone had this problem before?

    Do you know if the problem is due to some missing configuration on the device side?

    TiagoMoura_0-1674049406518.png

    Thanks in advance!

     

    3 REPLIES 3

    Düscha
    New Contributor

    hi

    a small note for the future.

    if you add picture from error, plaese open the error an create a picture with all information.

    OOID an EventNo is very important.

     

    Now to your error.

    The object and the peripheral was create with a real first software version (Beta) from Furnass.

    This error comes in two commands Leak and Flow test.

    After testing done, peripheral waiting 300ms for the state that the device is ready.

    If this state not comes, your error set.

    I think you have a new firmware on Furnesse device and this need more time.

     

    Have you contact to Furness?

    TommyF
    Member

    Hello,

     

    I think this is caused by the parameters of your measurement application. Perhaps the calculation of the result takes a little bit longer than in other applications.

    Please open a Helpdek-Ticket so we can send you a test version of the peripheral where we trigger the timeout with a longer time.

     

    Hello,

    Thanks a lot for the reply, I will describe better the error next time!

    We are using the latest version of the Furness available.

     

    The Furness device is quite new, the firmware version is: X752D11G+

    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