cancel
Showing results for 
Search instead for 
Did you mean: 
SOLVED

Problems configuring S20-CNT-INC-2/2

aFouraker
Occasional Contributor

Problems configuring S20-CNT-INC-2/2

I am attempting to configure the Encoder portion of the titled module. When I try to write the CoE objet described in the manual through the IO software I get the following error:

aFouraker_0-1663265983944.png

 

or this error:

aFouraker_0-1663267238960.png

 

To verify that the parameter exists and that the parameter was valid I first read the CoE object and then attempted to write it. This is parameter 16#0080 and subindex 3. Any help is appreciated. 

 

3 REPLIES 3
cc2go
Long-established Member

Re: Problems configuring S20-CNT-INC-2/2

Hello Alex,
example can be found in the docu of the bus coupler.
Two examples one for directly read/write CoE and the other to setup startup parameters, please see https://www.boschrexroth.com/documents/12605/25200368/R911385711_02.pdf
If you followed this, it will be great when you share, what you tried to write.

Or you use the function block for the module in the CXA_S20 lib.

aFouraker
Occasional Contributor

Re: Problems configuring S20-CNT-INC-2/2

@cc2go, yes, thank you. The manual you referenced is what I was using. In the end I was able to get the following to work. I copied the data from the read parameter SDO and moved it to the write SDO (with modifications for my applicaiton) in the IO software noting that bytes 6 and 7 should be removed. 

aFouraker_0-1663333296475.png

 

I still have the problem that the function block IL_ECAT_CoEWriteSDO does not accept the same data. I will get a screen shot of the error and provide it. 

aFouraker
Occasional Contributor

Re: Problems configuring S20-CNT-INC-2/2

The data must be entered in the way I described before but I made the mistake of setting the index on the function block to 2000 instead of 16#2000 😫. Once this was corrected then the array that was written in the IO configuration worked correctly. 

aFouraker_0-1663335383171.png

 

A utility to write these configuratoins would be very helpful, otherwise we need to read the manual and byte by byte determine what the data should be. 

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