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: 

    Fault during parameter access (two parameter access calls) after updating Nexeed Axis past 1.2.16.0

    Fault during parameter access (two parameter access calls) after updating Nexeed Axis past 1.2.16.0

    WScottHicks
    Established Member

    I have a station in OES 4.11b, that after updating  Nexeed Axis from version 1.2.16.0 (to 1.2.17.0 or 1.2.18.0) I receive an error shortly after station startup from the Axis Base object. (A467FE50-013E-11E1-8619-000423132FC8)

    Event number: 6

    System text: Fault during parameter access (two parameter access calls)

    Additional text: _101A710 (IndraDrive MPC20 FS__EcRx.WriteParam

    The station has a number of Indradrives, all of them are

    HCS01.1E-W0013-A-02-A-CC-EC-ET-S4-NN-FW

    FWA-INDRV*-MPC-20V24-D5-1-SRV-NN

    All of the drives that have MSK motors connected give the above error.  None of the drives that have third-party motors connected give this error.

    Once the error occurs, I can't clear it.  The only way to get the station running is to downgrade the Axis Object version.  Going back to version 1.2.16 of Nexeed Axis causes all of the errors to go away.  I haven't done much troubleshooting apart from loading different versions of the Axis and Axis Base to see which versions cause the error message.

    1 REPLY 1

    WScottHicks
    Established Member

    @Bianca, Thanks for reaching out with offers of assistance.

    I had a few minutes of line time, and figured out some additional information.  The MSK vs third-party motor difference isn't valid, it's a quirk related to the order in which the axis are activated by the station.  The real issue seems to be with the POWERON command of the Axis Object.  Modifying the code to use ParImm.Activate instead of the POWERON command, makes the problem go away.  I created a simple project at my desk using a single axis and I'm able to reproduce the issue.

    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