About WScottHicks

I think most people who've used TwinSAFE with Control Plus will admit that using a TwinSAFE IO in the TwinCAT PLC is a bit of a hassle, and requires some extra effort. I was trying to find ways to make this less painful and found I can add DigitalInput Channels to an FSOE Module and link the Safety Inputs like normal Digital Inputs.  The Safety Inputs are then usable in Control Plus without mapping Inputs in TwinSAFE.  This doesn't work for outputs, but it feels easier and less convoluted to me. It seems to work, but does anyone know of a reason why this would be a bad idea? As an example the EL1904 FSOES Safety Module could get the following addition.  (I think having the Parameter allows it to be a compatible change with existing projects.) <Parameters> <ParameterValue name="Input Linking Type" hierarchy="" refId="CFF8565D-0626-48B3-9344-87FEA4E40905" varType="STRING" textDe="Linking Type" textEn="Linking Type" initialValue="SafetyPLC" variable="FALSE" > <Values> <Value textDe="Safety PLC" textEn="Safety PLC" value="SafetyPLC"/> <Value textDe="Local (and/or Safety PLC)" textEn="Local (and/or Safety PLC)" value="Local"/> </Values> </ParameterValue> </Parameters> <Channels> <Channel name="Channel 1"> <Types> <Type name="DigitalInput" /> </Types> <Condition refLink="CFF8565D-0626-48B3-9344-87FEA4E40905" comparator="EqualTo" value="Local"/> </Channel> <Channel name="Channel 2"> <Types> <Type name="DigitalInput" /> </Types> <Condition refLink="CFF8565D-0626-48B3-9344-87FEA4E40905" comparator="EqualTo" value="Local"/> </Channel> <Channel name="Channel 3"> <Types> <Type name="DigitalInput" /> </Types> <Condition refLink="CFF8565D-0626-48B3-9344-87FEA4E40905" comparator="EqualTo" value="Local"/> </Channel> <Channel name="Channel 4"> <Types> <Type name="DigitalInput" /> </Types> <Condition refLink="CFF8565D-0626-48B3-9344-87FEA4E40905" comparator="EqualTo" value="Local"/> </Channel> </Channels> <IoLinks> <BinIoLink channelName="Channel 1" tcIoName="TxPDO^FSOE^InputChannel1"/> <BinIoLink channelName="Channel 2" tcIoName="TxPDO^FSOE^InputChannel2"/> <BinIoLink channelName="Channel 3" tcIoName="TxPDO^FSOE^InputChannel3"/> <BinIoLink channelName="Channel 4" tcIoName="TxPDO^FSOE^InputChannel4"/> </IoLinks>   ... View more

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. ... View more