0:13
Hi everyone, good morning and thank you for joining us.
0:17
Today we are going to talk about CPU and OCSIO can wiring and the presentation should last around 20 minutes.
0:26
As always, if you have any questions, please add them in the question panel and we will go through them at the end. That said, let’s get started. Hello and welcome to today’s webinar.
0:40
Today we will at CPU and OCS IO CAN wiring. Let’s take a look at our agenda for today.
0:50
We are going to do a quick review of CAN port functionality.
0:54
Mainly we’re going to be talking about IO expansion.
0:59
We are going to talk about different types of connectors for CAN that are used on Hornet controllers.
1:06
We are going to talk about different types of wiring you can use for CAN with Horner Controllers and Horner IO.
1:15
We will talk about making those connections and there will be demonstrations throughout and we will finish with a Q &A session.
1:24
Let’s do a quick review of CAN.
1:27
Now what is CAN for those of you who are unfamiliar?
1:31
CAN stands for Controller Area Network and it is a specialized chip that was invented many years ago that enables robust and reliable communications now it is very popular in both industrial automation as well as automotive, some of the chips are dedicated some of the chips have this functionality included in microprocessors and microcontrollers now why do we need CAN in a world of ethernet Well, KAN is more simpler and more robust than Ethernet and requires less bandwidth, so it definitely has its place both in Automative as well as Industrial Automation and at Horner we utilise it truly.
2:19
How does Horner utilise KAN?
2:22
We primarily use KAN for two functions, easy IO expansion for all Horner systems and peer peer communications between Horner controllers and to accomplish that we invented our own protocol on Khan called CISCAN and it has been around for a while.
2:43
It is very easy to use and very robust and as a matter of fact you do not even think about the protocol you just connect up your IO and use it or Connect up your controllers and have them start exchanging data.
2:59
In addition to IO expansion and peer-to-peer communications, Horner also supports some standardized CAN protocols, including CANopen J1-939.
3:14
CANopen is an automation standard, very popular for things like servo controllers.
3:20
J1-939 is an automated standard, and we have plenty of customers that are using Horner Controllers in either their factory to test their mobile devices or even on mobile devices themselves.
3:35
Now let’s start talking about how you can make that connection with CAN on Horner Controllers.
3:42
We’re going to start with the connectors.
3:44
Horner Controllers have two different style connectors that they use for interfacing with CAN depending on the controller.
3:52
Let’s start with Open Terminals.
3:55
Open Terminals is the most flexible way of connecting CAN in that you get a terminal strip included right on the CAN port on the Horner OCS or on the IO block.
4:08
In the case of some of our IO series and in most cases it is a double plug like you see there on the screen at the upper left so you can easily make connections for CAN coming in and can going out. So that is included in a lot of our products.
4:26
Some of our newer products and some of our products that are physically smaller.
4:31
Instead of using open terminal block which takes up a little bit more space they use an RJ45 jack which not only facilitates smaller spaces but it also facilitates using category style cabling or cash pipe or cash pipe e style cabling with can and that reduces costs and reduces labor.
4:56
Now which horn or controllers use which connector?
5:00
Well you can see that the canvas and the xl prime series along with her traditional xl series they use open style connection and then the micro series as well as the OCS-IO and the new CPUs, they use the RJ-45 approach.
5:19
So that is a quick breakdown visually for which controllers use which connector.
5:24
Now let’s start talking about cabling, because not only are there two different connectors that Horner uses with CAN, there are also two different cable styles.
5:36
Let’s start with specific cable.
5:39
So this is cable developed specifically for CAN and there are some different variants but all three variants were designed for CAN. Now what does that offer you?
5:51
Well it gives you the most robust solution to take advantage of all the noise immunity that CAN offer and gives you clearly defined specifications for distance and the number of that you can put on a network and baud rate so you get a lot by using cam specific cable however not all applications need that extra capability so that is where category cable comes in this is more convenient easier to install in a lot of cases although it does have more in limitations it does not have the distance capability or the number of nodes now when we take a look at the conductors and the pin out for two different types of CAN cabling.
6:39
Let’s go through that now.
6:41
So when we are talking about CAN specific cables we are talking about five conductors.
6:47
We have a red and a black wire that can be used for power delivery when used as a pair and then black wire or the V- conductor is also used for common mode reference because these nodes can be separated by some distance and also have a blue and a white pair that is the actual calm communications pair.
7:13
Now we did not mention this before but the red and the black pair is twisted and the white and the blue pair are also twisted.
7:22
Now in addition to that you have a shield terrain which is a bare Conductor that has to be handled properly in order to achieve those noise immunity that shielded can Specific cable can offer so this is the can specific cable 5 conductors now in the case of the cash 5 or cash 5e When you are using that we can you are talking about 3 conductors We do not have the power conductor because we do not distribute power over cat 5 or cat 5e with can.
7:58
We also always use unshielded cat 5 or cat 5e so there are no shields to deal with as well.
8:06
We just have the can pair, can high and can low which is the orange pair when we are talking about category cat 5 or cat 5e wiring and then there is the reference or green white and the V minus pin so even though there are eight conductors with that cable we are only using three of them the orange pair which is two and the green white reference which is three.
8:36
Now let’s talk about some of the limitations with the two different types of cable now as we mentioned before with count specific cable there are three different variations So, depending on the variation, you get a network distance of either 100m, 300m or 500m and you have as many as 64 nodes per segment and you can also use repeaters to expand the number of nodes up to 253 and you can do power delivery up to 4A and from an EMI or FI noise protection it is the best.
9:19
Now if we look at the category 5 slash 5e cable which is always unshielded with CAN.
9:26
The network distance is limited to 33 meters which is still about 110 feet. We can do up to 8 nodes on that network.
9:36
It does not provide power to deliver as we mentioned and it is an EMI in RFI protection because the conductors are twisted so we get some benefit from that but it does not have to be top level of EMI or FY protection that we have with CAN specific cable.
9:57
Now let’s talk about termination because unlike Ethernet with CAN when you are connecting devices over CAN each physical end of the network has to be terminated with approximately 120 ohm resistor.
10:13
And we have a Horner three different methods of doing that termination. Let’s go through the three different methods now.
10:21
So if you are using open style plugs, it is probably going to be convenient for you to use a physical termination resistor.
10:30
And we include two in the box with every Horner controller that has an open style plug and those are 121 ohms.
10:39
So if you’re using open style plug that termination resistor might be the most convenient.
10:46
Now if you’re using a product that has an RJ45 jack it is not easy to get a resistor in there so we have added software termination in other words either within your program by turn on a system bus or in your system menu by going into a specific entry in the system menu.
11:07
You can turn on what we call a software termination.
11:10
That is a software switch that puts a 121 ohm resistor into the circuit at the right place on the OCS.
11:19
So that is the second method of doing termination.
11:22
And then finally, if you have a Horner product that has two J45 ports on out for can and in and out.
11:32
We now include an RJ45 Terminator plug in the box for those products.
11:38
That would be the OCSIO basis.
11:41
For instance, now we have not always done that and you can also purchase these plugs separately if you choose.
11:48
But it does come with the box now with OCSIO bases.
11:52
Now let’s talk about making those connections, because we have got two different types of connectors and two different types of cabling, so the first question we get a lot is, if I am using OCS that has an open style connector for CAN, can I use CAT5 cabling?
12:11
The answer is yes, you can certainly do that, and during this presentation we are going to go through some scenarios in which you would do that, and we are going to show you How to do it?
12:23
The other question we get is, can I use traditional CAN cabling with an RJ-45 style jack on my controller or IO drop?
12:34
And how do I do that?
12:36
And again, the answer is yes.
12:39
There are a couple of ways to do that.
12:41
And we are going to show you in today’s presentation.
12:45
Now what we are going to do for the rest of today’s topic is we are going to go through a few different installation scenarios and demonstrate on the bench how you might handle those from a wiring and connectivity standpoint.
12:59
So let’s start with our first scenario which is a simple scenario.
13:03
We have a signal control panel and we have got a micro OCS X7 which is the main controller for the machine and we’re using OCS IO inside the same control panel to expand the IO capacity of the machine and any CAN wiring we have for the system is all internal to the cabinet.
13:25
So that is our first scenario so let’s see how we handle that on the bench.
13:30
So this is our simplest scenario that we have where we have two components.
13:36
The CAN wiring never leaves enclosure and both components support RJ45 for CAN.
13:43
So we have got our X7 with this CAN port connected to our CNX OCSIO base connected to its RJ45 port.
13:54
In this case, it turns out that a three foot or one meter RJ45 patch cable works well.
14:01
And then we cannot forget about termination.
14:04
In the case of OCSIO, we have got our standard termination plug.
14:09
And in the case of the X7, we have either in logic or on the system menu, we need to turn on termination that is enabled in software.
14:19
We only do that if the x7 is on the end of the network which it is and we only terminate the CNX if it is on the end of the network which it is.
14:30
Now for our next scenario we have got a little more complex situation.
14:35
This time we have two control panels and a main control panel housing the micro OCS x7 which is controlling the machine and the second control panel, the OCS-IO, installed that is located remotely closer to where the sensors and actuators are located, providing the I-O capacity for the machine.
14:58
These two control panels are 25 meters apart, which is not too far and we do not have any significant EMI or RFI concerns with machine so we are going to use category style wiring cache 5 or cache 5e so let’s take a look at this scenario on the bench.
15:19
For this remote panel we are using cache 5 or cache 5e wiring from panel to panel and we happen to be using bulkhead connector that has RJ45 on both sides so on the outside of the panel we have RJ45 connection.
15:37
On the inside of the panel we have an RJ45 connection so we have got a standard patch cable.
15:44
This time a one footer coming from the bulkhead connector the OCSIO base and once again we have our Terminator plug to make sure this end of the network is properly terminated.
15:57
In this scenario we still have CAT5 or CAT5E coming in but this time instead of coming in through RJ45 bulkhead it is just coming straight through a traditional gland type connector to get cable entry and the three conductors for CAN are just being landed on this field terminal strip and we have got this pigtail of RJ45 patch cable that we cut off and also connected to the field terminal strip so in this case again just using traditional field terminals we need three of them, one for con high, one for con low and one for V minus in order to go with this approach for category wiring all the way through.
16:44
Now for our third scenario we have a very similar situation but this time our two control panels are separated by a greater distance and we have some concerns about extreme EMI and RFI in the application so instead of using Cattori style cabling, we are going to use traditional Khan cabling.
17:06
Now when you are using Khan style cable, it is very important to handle that shield drain properly on the Khan cable.
17:14
Now in this sort of application, the way we would typically handle that is, we would ground the shield drain of the Khan cable usually at the main control panel because that is usually where we have the best earth ground.
17:29
Now if the better earth ground was somewhere else, we would ground it on that end instead.
17:35
But either way, we would only ground it at one place only.
17:39
Now let’s go to the bench and take a look at how we make the connections.
17:43
Now we are moving into some scenarios where we are going to start using CAN wiring as an interconnection between OCS and this remote panel.
17:53
Now why might we use this traditional CAN wiring instead of CAT5 or CAT5E?
18:00
Well it could be because of distance, CAN wiring can go much further, it could be because it is a tough noise environment for EMI or FI, so in those scenarios CAN wiring is superior.
18:14
So those are a couple of reasons we might do that.
18:17
Now one of the approaches we would take would be to bring the CAN wiring in through the cable gland and then connect it to the field terminal strip and again in this case we have three connections CAN-HIGH, CAN-LOW and V- and once again we are taking the pigtail approach into the CNX base with those three conductors connected to the interposing terminal strip so this is one approach of solving that and we have got another one.
18:48
Here is the other solution we were talking about for interfacing traditional CAN wiring with RJ45 and that is this new breakout adapter or pigtail.
18:59
It allows you to take 8 pins on the RJ45 port and break them out on an 8 terminal strip numbered 1 through 8.
19:09
So that works nicely with traditional CAN wiring. Now in this case we are not running power along with CAN wiring.
19:17
We are just running CAN high which is white, CAN low which is blue and B- which is black.
19:25
Now it is feasible and we could run up to four amps of power and take advantage of that red conductor in this cable bundle here but if we did that we would not connect the red cable to this terminal strip here we would connect that red conductor to the field terminal strip or maybe even directly to the front part of the CAN IO base so this is a different approach for interfacing traditional CAN wiring with RJ45.
19:56
Now for our final scenario we are going back to a simple situation where we have a single control panel with OCS all in one controller controlling the machine and the OCS IO located on the din rail in the same enclosure handling expansion IO.
20:14
Now in this case remember the canvas feature is an open stall connector for CAN.
20:20
As we know the OCS IO features RJ45, so we need to interconnect those two inside the panel.
20:28
One easy way to solve this is to purchase a cable from Horner that has already built that interconnection and open style can port, an RJ45 style can port, and it is available in two different lengths, 3 feet or 9 feet, but you can also build this cable yourself by taking a standard RJ-45 patch cable and cutting it to length and connecting it to open terminals block that’s included in the box with your OCS.
20:58
That concludes our webinar for today.
21:01
Thank you so much for listening and the Q &A session will begin shortly.
21:19
So I’m not currently seeing any questions, at least for now.
21:26
In this case, let me jump into the schedule. I hope you can see my screen now.
21:41
So the next webinar is going to be on analog field calibration and the other one is going to be on sizing WebMI for mobile device.
21:53
And if you want to participate or are interested, please register on our website.
22:00
Since we still don’t have any questions, I believe that’s all that I have for today.
22:07
Thank you all for your time and I hope to see you in the next webinar.
22:11
Have a nice day, everyone.