# Connecting to ABB NextMove E100 PLC **URL:** \ **Category:** General Discussion\ **Tags:** ignition79, ignition80\ **Created:** [May 7, 2020, 5:25pm UTC](https://forum.inductiveautomation.com/t/connecting-to-abb-nextmove-e100-plc/34537 "2020-05-07T17:25:42Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![cole.wittrock](https://avatars.discourse-cdn.com/v4/letter/c/54ee81/32.png) [@cole.wittrock](https://forum.inductiveautomation.com/u/cole.wittrock)\ **Post date:** [May 7, 2020, 5:25pm UTC](https://forum.inductiveautomation.com/t/connecting-to-abb-nextmove-e100-plc/34537/1 "2020-05-07T17:25:43Z")
I have been trying to set up an ABB communication with ignition to be able to control a set of servos from an ignition UI. I can’t seem to find the correct documentation or forum that explains the issues I’m having. I’m not sure what communication protocol the ABB PLC-s utilize, therefore I don’t know whether to use the modbus TCP protocol or the siemens 1200 or 1500 protocol. If anyone could point me in the right direction of at least where I could find the information I need then I would very much appreciate it. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [May 7, 2020, 5:49pm UTC](https://forum.inductiveautomation.com/t/connecting-to-abb-nextmove-e100-plc/34537/3 "2020-05-07T17:49:20Z")
[The manual](https://library.e.abb.com/public/f5a577de7cb345869658c50b97ff78f6/LT0231A09EN.pdf?x-sign=uXV6S1PEjEBGefpIStOUdzuhDfzZJu7Ec7oXshnVqBYJ8r4IMnhXb3uXuc+OLg1O) doesn’t paint a very hopeful picture. This thing definitely doesn’t talk Modbus or S7 protocol. It looks like it does CANopen. I’m not sure if even Kepware has a driver that will work with this. ---
**Author:** ![cole.wittrock](https://avatars.discourse-cdn.com/v4/letter/c/54ee81/32.png) [@cole.wittrock](https://forum.inductiveautomation.com/u/cole.wittrock)\ **Post date:** [May 7, 2020, 6:18pm UTC](https://forum.inductiveautomation.com/t/connecting-to-abb-nextmove-e100-plc/34537/4 "2020-05-07T18:18:01Z")
Kepware has what’s called “ABB Totalflow Drive” but I’m not sure if that would apply to my use case here or not. I tried setting up the Etherenet connection for the ABB controller but couldn’t get it to work properly, I have it connected via USB currently and it seems like ABB’s own software is the only thing able to detect it. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [May 7, 2020, 6:22pm UTC](https://forum.inductiveautomation.com/t/connecting-to-abb-nextmove-e100-plc/34537/5 "2020-05-07T18:22:52Z")
ABB Totalflow is an entirely different device for a different purpose than these, I wouldn’t expect their Totalflow driver to work. ---
**Author:** ![cole.wittrock](https://avatars.discourse-cdn.com/v4/letter/c/54ee81/32.png) [@cole.wittrock](https://forum.inductiveautomation.com/u/cole.wittrock)\ **Post date:** [May 7, 2020, 7:09pm UTC](https://forum.inductiveautomation.com/t/connecting-to-abb-nextmove-e100-plc/34537/6 "2020-05-07T19:09:20Z")
so how does CANopen work exactly? ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [May 7, 2020, 9:43pm UTC](https://forum.inductiveautomation.com/t/connecting-to-abb-nextmove-e100-plc/34537/7 "2020-05-07T21:43:29Z")
You can start your trip down the CAN rabbit hole here: > **[CANopen](https://en.wikipedia.org/wiki/CANopen)** > > CANopen is a communication protocol and device profile specification for embedded systems used in automation. In terms of the OSI model, CANopen implements the layers above and including the network layer. The CANopen standard consists of an addressing scheme, several small communication protocols and an application layer defined by a device profile. The communication protocols have support for network management, device monitoring and communication between nodes, including a simple transport la... You may also find this useful, if you are inclined towards the details: > **[SocketCAN](https://en.wikipedia.org/wiki/SocketCAN)** > > SocketCAN is a set of open source CAN drivers and a networking stack contributed by Volkswagen Research to the Linux kernel. Formerly known as Low Level CAN Framework (LLCF). > Traditional CAN drivers for Linux are based on the model of character devices. Typically they only allow sending to and receiving from the CAN controller. Conventional implementations of this class of device driver only allow a single process to access the device, which means that all other processes are blocked in the mean...