0:01
Thank you for joining us on this webinar for migrating to the Micro CPU 250 from the RCCs.
0:08
It’s a little longer runtime than usual, we’re in about 25 minutes for the presentation, but as usual feel free to put in any questions throughout and we’ll get to them at the end.
0:16
Hello and welcome to today’s webinar.
0:20
Today we will look at migration to the Micro CPU 250 from the RCC.
0:27
Let’s take a look at our agenda for today.
0:30
We are going to start with a quick review of the CPU250 and then we are going to go through all the different RCC models.
0:40
We will talk about migration strategies from moving your application over to the RCC to the CPU250.
0:49
We will go through all the different conversion steps and there will be demonstrations throughout and we will finish with a Q &A session.
0:58
The new Micro Modular Controller are one of the micro series which previously only included Auto One Controllers and now includes Modular Controllers.
1:09
Now these Modular Controllers are loaded with capabilities, lots of connectivity options with Ethernet and USB-C for programming and micro SD, lots of built-in I.O. for the CPU 250 at least.
1:25
You can also add additional I.O. through standard OCS I.O.
1:30
blocks that you can add on the side of the unit and all the connectivity with all kinds of different protocols are supported.
1:39
There are 34 built-in I.O.
1:41
points in total, including 8 of which are flexible between digital and analogue.
1:48
Now let’s take a look at the RCC controller lineup.
1:52
These are a series of models that have been released over the years starting with the RCC 972 and moving its way through the RCC 6512 so there are currently 5 models in the lineup.
2:08
Although the RCC 2414 has already being obsolete but some of you may have an application out there that is using that particular controller so it is going to be covered in today’s presentation.
2:24
Most of the RCCs have similar features.
2:27
The microSD slots are common, at least one ethernet port and at least one serial port.
2:35
Those are all common.
2:36
DC power input.
2:38
The voltage range may vary from model to model.
2:42
They all feature recessed push buttons for starting and stopping the controller or loading a new program.
2:50
For MicroSD, they all have status indicators for run and power and some of them also have additional indicators for network activity.
3:00
And then where they really vary for the most part is in their I.O. complement.
3:06
How many digital ins and outs and how many analogue ins and outs.
3:11
They have another area where they vary is also the amount of logic resources available, how much logic space, as well as how many retentive word type registers and retentive and non-retentive bit type registers.
3:27
So for each model as we go through them you are going to see a table in the upper right hand corner that shows those differences.
3:36
So the RCC972 is the first one that we have and one thing that is unique about that particular model is the fact that the RCC972 does not have a real time clock or a battery so that was a requirement for the particular OEM that we designed it for even though we can sell it to anybody so that is something to be aware of with that particular model.
4:03
The next model we have got is the RCC1410.
4:08
Some of the big differences here, beyond the IO complement differences, are the fact that the RCC1410 has a lot of available registries as well as program space.
4:21
So it has 50 ,000% R registries, it has 32 ,000 bit type registries, half of which are retentive and it has 2MB of logic space.
4:33
But keep in mind the new CPU 250 matches that in terms of all those different parameters.
4:41
So again you will be able to see as we go through this presentation today that the CPU 250 part of its specifications were developed so that it could easily replace the RCCs moving forward from an I.O standpoint the RCC 1410 has 14-digit IN and 10-digit outputs.
5:04
It does not feature any analogue.
5:07
Now let’s take a look at the RCC 8842.
5:12
It is identical to the 1410.
5:15
The only difference is the I.O. complement.
5:18
It has 8-digit IN 8 to slot out, 4 analogue in and 2 analogue out.
5:25
Both the RCC1410 as well as the 8842 have LED indication on their terminal strips whereas any RCC model you will see that just has a green terminal strip for the IO instead of the black ones.
5:44
Those green terminal strips do not feature LED lightpipes so they do not have LED indications whereas the black terminal strips do that are used on the 8842 and the 1410. The next model is the RCC2414.
6:04
Now this one is unique this one is used in quite a few different lighting applications but is ultimately So if you have got one of these, there is a decent chance it may be used in a lighting application.
6:20
What makes the 2414 different is the fact that it has two ethernet ports instead of one.
6:28
And from a serial port standpoint, it has two ORs, 485 ports, so that is the two of the things that make it unique.
6:38
The last thing that makes it unique is it supports for USB so it has got USB for programming as well as a USB host port for a flash drive.
6:50
Now the last model we are going to talk about and it’s a very high volume product but it is primarily used for high-speed counting so if you want a remote high-speed counter this is product that most of our customers use and this is an RCC6512 which has high speed counter capability.
7:14
It has 12 high speed inputs that can be used for high speed counting, encoders, up counting and down counting and then it also has some analog built in as well so it is a very versatile product but it has a very limited number of resources from a programming standpoint because it is intended to be a core processor and due to its incredible high-speed counter capabilities and its limited CPU resources.
7:48
What are our migration strategies?
7:51
Well first of all most of the models can easily be replaced with a The CPU250 has plenty of built-in IO that can cover any RCC model that exists out there and even though most of the models have a lot of capacity for programming, in terms of programming space and register space, the CPU250 also matches that as well.
8:21
So again, that is why moving from most models to the CPU250 makes sense.
8:29
Now in a couple of cases, you may find that you want to transition to a CPU300 instead.
8:38
So in a couple of cases, if you need the two ethernet ports, or if you need the high speed counter support as well, plus or minus 10 volt analog outputs.
8:50
In these cases you might want to transition over from a 2414 or the RCC6512 to the CPU300 that we are releasing later this year.
9:05
But again even these models in a lot of situations can be replaced nicely with the CPU250.
9:13
Now let’s talk about what we have to do besides just ordering a different part number to do the migration. Let’s start by talking about physical migration.
9:25
What does that look like?
9:27
Well from a physical size standpoint the RCCs and the CPU 250 are virtually the same size so they have the same footprint on a rodent rail or in your enclosure from IO wiring and a power wiring standpoint.
9:47
If you are following the traditional approach of having a field terminal strip inside your enclosure then you are going to need to rework that wiring from the field terminal strip to the terminal strip on CPU 250 because even though a lot of the signals are the same the IO terminals are not in exactly the same location so you will have to redo that wiring now from a serial port wiring or ethernet wiring standpoint the pin outs have not changed there may be additional signals on the modular jack for instance that handles serial ports but the signals that were there before for your RCC application are still in the same location for the CPU 250.
10:40
If your communications cables or your Ethernet patch cables or your serial port cables if they are of sufficient length where you can move them from where they were the RCC to where they are with the CPU then no changes have to be made there as well.
11:00
So that is some of the physical changes. Now let’s talk about CAN.
11:05
There are some big differences with CAN.
11:08
Mainly the fact that even though the CAN wiring was not standardised across all the RCC line it was always using a terminal strip whereas with the CPU 250 it uses an RJ45 port which is a modern way of handling CAN so there are a couple ways of transitioning there.
11:32
First of all if you are using traditional CAN wiring and you would like to connect those to some wires to the CPU 250’s CAN port well you can use an RJ45 to terminal strip cable.
11:48
This is an option that you have or if all you are going to do is let’s say you have got a CAN wiring going to the field terminal strip inside the enclosure and you want to make that connection to the CPU 250 well then from a field terminal strip you can just run let’s say an Ethernet patch cable chopped off on one end and then you can three terminals the CAN HIGH, CAN LOW and the CAN GROUND to your field terminal strip to the appropriate terminal. Now what about termination?
12:29
Well with the RCC if you are using CAN then the RCC is on the end of the network then almost certainly you have got a physical resistor that is plugged in at end of the CAN network on the RCC if it is at the end of the network you do not have an easy place to put a physical resistor with the CPU 250 but the CPU 250 does have a software enabled CAN termination so simply by turning on system bus you can turn termination on so you do not have to mess with the resistor so that is another option here.
13:12
Now this particular slide here shows the pin out that you can use in those two scenarios that we went through previously.
13:21
One scenario is where you chop off that ethernet patch cable and just wire up three pins from your field terminal strip into the CPU 250.
13:33
The other scenario is use an RJ-425 to terminal strip breakout adapter like we have got shown on the screen here and then you can see the pinout that is required in that scenario.
13:49
The differences in CAN physically are more sufficient than they are in Ethernet and the serial ports.
13:58
Now let’s talk about IOMapping from a differences between the RCZs and the new CPU 250. Let’s go through the differences that do exist.
14:16
There is a feature that a lot of customers do not always take advantage of and that is there is a digital input register.
14:24
Present i bit that will turn on if you have a short circuit on one of digital inputs on one of your digital outputs that is available with every OCS model that is out there.
14:39
A lot of people do not take advantage of it but in the case of the RCCs that indication of a short circuit that comes on typically with%i16 although if you are using one of the RCC 6512 model then the for short circuit is I32 but in either case in the CPU 250 the bit is I25 so if you are using that short circuit indication bit you will have to remap that one and then another case where remapping may be required is in the case of analog outputs if you are using voltage analog outputs you may have to remap of your AQ registers as well because of the way that works with CPU 250.
15:32
Now let’s go through what you need to do in Cscape step by step when you are going through the migration from RCC to the CPU 250.
15:43
The first step as always, you want to archive your existing RCC program and then make a with a copy of that program as you make programming changes then you’re going to go to hardware configuration you’re going to change your controller model from the RCC that you are using over to the CPU 250 then you are going to go into the local IO tab and you’re going to do the configuration that is required and and most of your configuration and you will see this in the demonstration is going to be in the flexible input section and the analog output section of the CPU 250 because that is where your analog is required.
16:37
The RCC’s did not have any options for the most part with their digital inputs.
16:44
For the most part did not support high speed counting except for RCC6512 which is a high speed counter coprocessor.
16:55
All the rest of the models did not do any high speed counting at all. So there is not much configuration that will be required there.
17:04
It is all going to be on the analog side.
17:07
And then the remainder of the changes in your logic program are going be related to your analog outputs because if you are using any voltage analog outputs the voltage analog outputs are mapped in a different area with the cpu 250 as compared with the rcc so you would need to do that remapping for both a register number as well as an io names standpoint and then Finally it is just a matter of saving your program and downloading and testing.
17:43
For our demonstration let’s do a conversion of an RCC program to the CPU 250.
17:52
So we start by archiving and then copying our existing RCC program.
17:58
So let’s go ahead and copy and paste that program.
18:02
We are going to do a quick rename, whatever you want to rename it, and then that is the program we are going to open, which is the one we just created, that was a duplicate.
18:16
So before we go in and do the conversion, let’s explore what the RCC configuration currently looks like.
18:25
So we will go into Hardware Config, it is configured for an RCC 8842.
18:31
let’s go take a look at the local IO and see how that is configured.
18:38
So digital inputs everything is at default with positive logic.
18:44
Digital output everything is also at default.
18:48
Analog input it looks like we have got two 4 to 20 mini app channels and two 0 to 10 full channels with a filter constant of 3 for some digital filtering.
19:03
On the analog output side we have got a 4 to 20 milli-amp channel a 0 to 10 volt channel and we are going to 0 when the controller is stopped.
19:14
That is the configuration we want to match in our CPU 250 so now back to the hardware configuration now changing our target to the CPU 250.
19:28
Now that we have done that We can go back into local IO, we can see the picture is different, the defaults for digital inputs, nothing to change here, still positive logic defaults.
19:42
For digital inputs, nothing to change here, and now we are going to have to manually make these changes, because the analog settings do not follow through automatically, so we have to make those manually.
19:55
We are going to set our Düsseld filtering to 3 because that is what it was before on the RCC.
20:02
Our first channel is going to be analog 4 to 20 milliamps with a scaling of 32 ,000.
20:11
Our next channel is the same 4 to 20 milliamps scaling of 32 ,000.
20:18
our third channel was 0 to 10 volts again scaling of 32 000. How do we know the scaling was 32 000?
20:29
Well that is the only option that you have for the rcc’s they just by default are 0 32 000.
20:36
So now our analog input channels all match what they should.
20:41
We got our filtering, we have our signal types and we have our data range. So that is done.
20:48
Now let’s take a look at the analog output side.
20:52
We had one 4 to 20 mA channel and again 0 to 32 ,000 because that is all the RCC supports and when the controller is stopped we want to be at 0 or minimum.
21:07
Now we cannot configure the second channel here for voltage because if you want voltage you have to go down here to the 5th channel, the 5th through the 8th channel, so 0 to 10 volts, 0 to 32 ,000 and the whole state of minimum is what we want.
21:27
But we have to note that our second analog output is no longer AQ2, our second analog output is now AQ5, so we to have to make mapping changes in our program to change AQ2 to AQ5 everywhere in our program.
21:48
So we will prepare to do that now. So we are done with the hardware configuration.
21:54
Now we are going to go in and replace every instance of AQ2 in our program with AQ5.
22:01
Now if we have more than one instance, then the easiest way to do that would be to go to the edit menu and the replace option and we would do a find AQ2 and replace it with AQ5 and hit replace all.
22:18
It tells us how many have been replaced, now if we are using register based programming we are going to also do a change on our IO name, because we lost our IO name when we that change.
22:33
So we need to go over here to IONAME, right click, hit edit, find AQ2 which is the old IONAME that now needs to be AQ5.
22:45
Make that change, hit OK and hit OK again and now we can see that we have got our IONAME along with our proper analog output register.
22:57
Now if by chance we are using a short indicator which is either going to be I16 or I32 depending on our RCC model then we need to change that to I25 so we know that we have only got one instance of this here in our program so we are going to go ahead and change it from here but again if we have multiple instance we are going to have changed them all manually.
23:32
Again, we lost our IO name, so we need to go back here to the IO names area, find I16 and change it to I25.
23:44
Again, we could have done the search and replace technique.
23:48
That is also valid, but we wanted to show you the other way of doing that by changing it manually here. So now that change has been made.
23:59
The only other change we might want to make would be if in our RCC we are using a physical CAN termination resistor and in our CPU 250 we are going to use a software enabled termination resistor that is internal to the CPU. So let’s put a comment in here. Enable software.
24:24
Enable CAN termination. That is what we are going to be doing with one more quick run.
24:31
Then we are going to need to put an always on contact here.
24:36
Again we are demonstrating register base logic today and then the SR for the software enable CAN termination is sr 152.4 it does not have a default IO name so we will go ahead and name it now and there we go so that is the final change that we need to make to this particular example.
25:03
Your actual example may be slightly different but this should give you pretty much what you need to know.
25:11
Our last steps are to be to have to save the modified program and then download and test the result. That concludes our webinar for today.
25:23
Thank you so much for listening and the Q &A session will begin shortly.
25:35
Okay so we will be carrying on the CPU 250 next week with IO configuration using variables.
25:44
The registration links are up as usual so if you’d like to register for that That will be next week’s webinar.
25:51
I don’t see any questions on that, but feel free to get in touch if you do have any in the meantime. Okay, I think we can leave it there for today.
26:00
Thank you all for joining. See you next time.
