<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:webfeeds="http://webfeeds.org/rss/1.0">
    <channel>
        <title><![CDATA[Automation Community - ctrlX DRIVE]]></title>
        <description><![CDATA[Drives and motors]]></description>
        <link>https://community.boschrexroth.com</link>
        <generator>Bettermode RSS Generator</generator>
        <lastBuildDate>Fri, 08 May 2026 14:14:53 GMT</lastBuildDate>
        <atom:link href="/rss/kype8OUOzpkc/posts" rel="self" type="application/rss+xml"/>
        <pubDate>Fri, 08 May 2026 14:14:53 GMT</pubDate>
        <copyright><![CDATA[2026 Automation Community]]></copyright>
        <language><![CDATA[en-US]]></language>
        <ttl>60</ttl>
        <webfeeds:icon></webfeeds:icon>
        <webfeeds:related layout="card" target="browser"/>
        <item>
            <title><![CDATA[DC Bus coupling XCS <-> XCS]]></title>
            <description><![CDATA[I want to connect the DC-bus of two axes. Of course, this is not a problem. The obvious choice would be to use an XCS as the supply and an XMS as the second drive connected to the DC bus.
However, to ...]]></description>
            <link>https://community.boschrexroth.com/ctrlx-drive-5thklqt9/post/dc-bus-coupling-xcs---xcs-ySmhxXtXld6gU5j</link>
            <guid isPermaLink="true">https://community.boschrexroth.com/ctrlx-drive-5thklqt9/post/dc-bus-coupling-xcs---xcs-ySmhxXtXld6gU5j</guid>
            <dc:creator><![CDATA[Pinball_NL]]></dc:creator>
            <pubDate>Fri, 08 May 2026 13:24:48 GMT</pubDate>
            <content:encoded><![CDATA[<p>I want to connect the DC-bus of two axes.  Of course, this is not a problem. The obvious choice would be to use an XCS as the supply and an XMS as the second drive connected to the DC bus. <br>However, to keep the bill of materials small, I am now opting for two XCS*-W0010 Amp drives. One XCS will be connected to the mains, and the second XCS will receive its supply via the DC bus of the first XCS. So in total two XCS drives.</p><p>Now it comes down to the parameter settings. I can't really set in the drive firmware that I'm only using the second Drive as an inverter. I assume that the drive will simply go into 'ready' (bb/Ab) mode once the DC bus has reached the desired voltage level. <br>I see no showstopper and will proceed with this. However, a checkbox in the drive would have been desirable. As far as I know, this was provided for in the IndraDrive. <br><br>Since we're on the forum, a question: <br>Can I connect the DC-bus of XCS to XCS, provided the power requirements are sufficient?</p><p>As before in Indradrive : </p><figure data-align="center" data-size="best-fit" data-id="44V8BQ2Z5PJhXzSfAVZ80" data-version="v2" data-type="image"><img data-id="44V8BQ2Z5PJhXzSfAVZ80" src="https://tribe-eu.imgix.net/44V8BQ2Z5PJhXzSfAVZ80?auto=compress,format"></figure>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[XCS2-H]]></title>
            <description><![CDATA[Hello,

1 . I'd like to know how long the drive will last at 2 times the rated current.

 2. 200% torque output can be maintained for how long, not protected by the thermal model.]]></description>
            <link>https://community.boschrexroth.com/ctrlx-drive-5thklqt9/post/xcs2-h-MtiuGQx2v6HVsPH</link>
            <guid isPermaLink="true">https://community.boschrexroth.com/ctrlx-drive-5thklqt9/post/xcs2-h-MtiuGQx2v6HVsPH</guid>
            <dc:creator><![CDATA[JHU1XI1]]></dc:creator>
            <pubDate>Wed, 06 May 2026 08:32:24 GMT</pubDate>
            <content:encoded><![CDATA[<p>Hello,</p><p><strong>1 </strong>.    I'd like to know how long the drive will last at 2 times the rated current.</p><ol start="2"><li><p>   200% torque output can be maintained for how long, not protected by the thermal model.</p></li></ol>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[EX drive option not recognized by 3rd party EtherCAT master]]></title>
            <description><![CDATA[I am testing an EX drive option with a Trio Motion controller that is configured with ESI files for ctrlX Drives. So far, I am successfully able to get standard and compact XCS drives to work with the...]]></description>
            <link>https://community.boschrexroth.com/ctrlx-drive-5thklqt9/post/ex-drive-option-not-recognized-by-3rd-party-ethercat-master-8CDO8rv0w5FDKEB</link>
            <guid isPermaLink="true">https://community.boschrexroth.com/ctrlx-drive-5thklqt9/post/ex-drive-option-not-recognized-by-3rd-party-ethercat-master-8CDO8rv0w5FDKEB</guid>
            <dc:creator><![CDATA[StephenO]]></dc:creator>
            <pubDate>Mon, 04 May 2026 14:48:30 GMT</pubDate>
            <content:encoded><![CDATA[<p>I am testing an EX drive option with a Trio Motion controller that is configured with ESI files for ctrlX Drives. So far, I am successfully able to get standard and compact XCS drives to work with the controller. However, when I connect an EX drive to the controller, sometimes I am unable to get the controller to recognize there is any devices on the EtherCAT network at all. Instead, I get an error that no devices are detected on the network.</p><p>I suspect that the EX drive in standalone mode is not responding to the Trio's initial packets to scan the EtherCAT network.</p><p>I captured wireshark captures from a Trio connected to an XCS2-F with success. I have attached them for reference.</p><figure data-align="center" data-size="best-fit" data-id="KPMoaIi4q6kjASlngotbX" data-version="v2" data-type="image"><img data-id="KPMoaIi4q6kjASlngotbX" src="https://tribe-eu.imgix.net/KPMoaIi4q6kjASlngotbX?auto=compress,format"></figure><p>I tried to capture when the TRio connected to the EX drive, but there is only a single packet from the Trio (BWR command) with no response that I see from the Drive. I'm not sure if there is a specific sequence the EX drive expects to switch to 'parallel' mode that is causing this to not work reliably. Can I get some guidance on the expected way to startup the drive?</p><p>EX drive is using FWA-V-0610, with ESI files dated from 2025-11</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Trio MC EtherCAT master to XCS2 CtrlX Drive]]></title>
            <description><![CDATA[Customer has been using Trio MC EtherCAT master with Indradrive in the past.
Now they are switching to CtrlX Drive.

So far, they are able to adjust the EtherCAT master EC_EXTEND file to include the ...]]></description>
            <link>https://community.boschrexroth.com/ctrlx-drive-5thklqt9/post/trio-mc-ethercat-master-to-xcs2-ctrlx-drive-DulsKjgYNcc3NdO</link>
            <guid isPermaLink="true">https://community.boschrexroth.com/ctrlx-drive-5thklqt9/post/trio-mc-ethercat-master-to-xcs2-ctrlx-drive-DulsKjgYNcc3NdO</guid>
            <dc:creator><![CDATA[StephenO]]></dc:creator>
            <pubDate>Thu, 30 Apr 2026 14:43:43 GMT</pubDate>
            <content:encoded><![CDATA[<p>Customer has been using Trio MC EtherCAT master with Indradrive in the past.<br>Now they are switching to CtrlX Drive. </p><p>So far, they are able to adjust the EtherCAT master EC_EXTEND file to include the CtrlX Drive using the Import ESI file tool in the Trio software. But, they still cannot get the EtherCAT bus to startup automatically and are looking for the solution.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CtrlX Sense Standard encoder error, signals disturbed]]></title>
            <description><![CDATA[Hello,

A client has installed an MS2N10-D1BFN-MMVK0-NN with CtrlX Sense Standard using the RG2-007ABB-NN-006 cable and a CtrlX Drive with firmware 06v08. When the equipment is power on, the error E2074...]]></description>
            <link>https://community.boschrexroth.com/ctrlx-drive-5thklqt9/post/ctrlx-sense-standard-encoder-error-signals-disturbed-DWjxtQLs7Ly0QsU</link>
            <guid isPermaLink="true">https://community.boschrexroth.com/ctrlx-drive-5thklqt9/post/ctrlx-sense-standard-encoder-error-signals-disturbed-DWjxtQLs7Ly0QsU</guid>
            <category><![CDATA[ENCODER]]></category>
            <dc:creator><![CDATA[Curzar08]]></dc:creator>
            <pubDate>Thu, 30 Apr 2026 09:06:22 GMT</pubDate>
            <content:encoded><![CDATA[<p>Hello,</p><p>A client has installed an MS2N10-D1BFN-MMVK0-NN with CtrlX Sense Standard using the RG2-007ABB-NN-006 cable and a CtrlX Drive with firmware 06v08. When the equipment is power on, the error E2074 Signals disturbed appears and it does not go to OM but it does read the motor data.</p><p>I don't have another cable to check if the problem is the cable itself. The strange thing is that it does read the encoder's memory, but then the encoder error appears.</p><figure data-align="center" data-size="best-fit" data-id="6uZLXq3HdCAhV6XaIxeRh" data-version="v2" data-type="image"><img data-id="6uZLXq3HdCAhV6XaIxeRh" src="https://tribe-eu.imgix.net/6uZLXq3HdCAhV6XaIxeRh?auto=compress,format"></figure><p>What could I check to determine the problem?</p><p>Could it be a firmware issue? The device is new.</p><p>Thanks.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Error C8214 during safety configuration in a XMV system]]></title>
            <description><![CDATA[Hello team,

I tried to configure the SafeMotion in a ctrlX DRIVE XMS with connector M8 with safety digital I/O integrated in the own drive. The customer wants activate the "E-Stop" and "STO" options ...]]></description>
            <link>https://community.boschrexroth.com/ctrlx-drive-5thklqt9/post/error-c8214-during-safety-configuration-in-a-xmv-system-4A6j9bER5kFdgQS</link>
            <guid isPermaLink="true">https://community.boschrexroth.com/ctrlx-drive-5thklqt9/post/error-c8214-during-safety-configuration-in-a-xmv-system-4A6j9bER5kFdgQS</guid>
            <dc:creator><![CDATA[Aitor-92]]></dc:creator>
            <pubDate>Mon, 27 Apr 2026 13:27:30 GMT</pubDate>
            <content:encoded><![CDATA[<p>Hello team,</p><p>I tried to configure the SafeMotion in a ctrlX DRIVE XMS with connector M8 with safety digital I/O integrated in the own drive. The customer wants activate the "E-Stop" and "STO" options via digital inputs with external dinamization.</p><p>The problem is that is not possible exit to the CM. Appear error C8214 an in reference details "invalid scaling type".</p><attachment data-id="udob919nJRXnq9LJnDiwb" data-type="attachment"></attachment><p> </p><attachment data-id="kBeVxALZArLK3Jgqhc374" data-type="attachment"></attachment><p>I configured the parameters P-0-3222.0.1 and P-0-3242.1.2 according top the scaling type but the error persist. What else can be checked?</p><attachment data-id="Mcy7qCRZ86wYeqSyjqwrU" data-type="attachment"></attachment><p> Thanks in advance</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ON-OFF cycles XVR]]></title>
            <description><![CDATA[What are the maximum on-off cycles for the XVR?]]></description>
            <link>https://community.boschrexroth.com/ctrlx-drive-5thklqt9/post/on-off-cycles-xvr-NIwUiFwkQ6xcURC</link>
            <guid isPermaLink="true">https://community.boschrexroth.com/ctrlx-drive-5thklqt9/post/on-off-cycles-xvr-NIwUiFwkQ6xcURC</guid>
            <category><![CDATA[CTRLXDRIVE]]></category>
            <dc:creator><![CDATA[Rechi]]></dc:creator>
            <pubDate>Fri, 24 Apr 2026 13:47:02 GMT</pubDate>
            <content:encoded><![CDATA[<p>What are the maximum on-off cycles for the XVR?</p><figure data-align="center" data-size="best-fit" data-id="MKBZIBxI66Uh022TVixLv" data-version="v2" data-type="image"><img data-id="MKBZIBxI66Uh022TVixLv" src="https://tribe-eu.imgix.net/MKBZIBxI66Uh022TVixLv?auto=compress,format"></figure>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Encoder validation error with MS2M04 motor]]></title>
            <description><![CDATA[One of customer is having an issue with C3700 encoder validation procedure. MS2M04 motor connected to XCS2-W0035FRN-01NETT0NNNN-S0612NNNNNN0NN with AXS6V12 firmware keep failing with C3703 error while...]]></description>
            <link>https://community.boschrexroth.com/ctrlx-drive-5thklqt9/post/encoder-validation-error-with-ms2m04-motor-Qr0HSdZ0Bs9hvNM</link>
            <guid isPermaLink="true">https://community.boschrexroth.com/ctrlx-drive-5thklqt9/post/encoder-validation-error-with-ms2m04-motor-Qr0HSdZ0Bs9hvNM</guid>
            <dc:creator><![CDATA[Young_1]]></dc:creator>
            <pubDate>Wed, 22 Apr 2026 19:04:22 GMT</pubDate>
            <content:encoded><![CDATA[<p>One of customer is having an issue with C3700 encoder validation procedure. MS2M04 motor connected to XCS2-W0035FRN-01NETT0NNNN-S0612NNNNNN0NN with AXS6V12 firmware keep failing with<strong> C3703</strong> error while executing C3700 command.  The motor seems to be operating without a problem during normal operation and showing correct velocity and position value.   The customer is following a startup procedure he found in web and have question why this error is triggering.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[XCS_F & Twincat3 (Beckhoff)]]></title>
            <description><![CDATA[Hello,

I am doing some test with a ctrlX DRIVE compact (XCS_F) with Twincat3. Firmware 06V10.

When testing the EtherCAT CoE, it works OK.

But, using EtherCAT SoE, after adding the axis as slave, there is...]]></description>
            <link>https://community.boschrexroth.com/ctrlx-drive-5thklqt9/post/xcs-f-twincat3-beckhoff-v7WQaKwnsqPSDQd</link>
            <guid isPermaLink="true">https://community.boschrexroth.com/ctrlx-drive-5thklqt9/post/xcs-f-twincat3-beckhoff-v7WQaKwnsqPSDQd</guid>
            <dc:creator><![CDATA[hgd]]></dc:creator>
            <pubDate>Wed, 22 Apr 2026 14:16:01 GMT</pubDate>
            <content:encoded><![CDATA[<p>Hello,</p><p>I am doing some test with a ctrlX DRIVE compact (XCS_F) with Twincat3. Firmware 06V10.</p><p>When testing the EtherCAT CoE, it works OK.</p><p>But, using EtherCAT SoE, after adding the axis as slave, there is no way to add it in the NC of the Twincat. </p><p>Last device datasheet are used: 2026-03-01</p><p>Any idea?</p><p></p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DriveLink Consumer connection]]></title>
            <description><![CDATA[DriveLINK basic FWS-XD1-APP-AXC_BAS_NNNN-NN-V-0104-NN shows an issue with not retaining the producer topology index ctrlX DRIVELink consumer connection. After power cycle, new address set in the ...]]></description>
            <link>https://community.boschrexroth.com/ctrlx-drive-5thklqt9/post/drivelink-consumer-connection-a9QioZPNeOrv5Ig</link>
            <guid isPermaLink="true">https://community.boschrexroth.com/ctrlx-drive-5thklqt9/post/drivelink-consumer-connection-a9QioZPNeOrv5Ig</guid>
            <category><![CDATA[ctrlX DRIVELink]]></category>
            <dc:creator><![CDATA[Young_1]]></dc:creator>
            <pubDate>Tue, 21 Apr 2026 16:13:05 GMT</pubDate>
            <content:encoded><![CDATA[<p>DriveLINK basic FWS-XD1-APP-AXC_BAS_NNNN-NN-V-0104-NN shows an issue with not retaining the producer topology index ctrlX DRIVELink consumer connection.  After power cycle, new address set in the producer topology index revert back to the original setting.</p><p>Attached is all the parameters from the customer machine and screen shot of DriveLink configuration space.</p><p>Please let me know if you any further information or clarification of this issue.</p>]]></content:encoded>
        </item>
    </channel>
</rss>