Can someone give me some tips and/or pointers to the relevant information on how to create a simple project for an AC140.61-2 module installed in an ACOPOS 8V10xx drive?
Basically, I would like to
create a new project on a CF card which would enable my AC140 module boot properly (have the RUN LED lit up in steady green color)
establish communication to the AC140 device via Ethernet (IF6) and have some tests done with the host ACOPOS 8V10xx drive
I have some quite a few projects with ACOPOS 8V1xxx drives and X20CP1382 or similar CPUs (SG4). So I know my way around AS 3.0.90 and 4.x…
However, I have not even manage to complete the part 1 above. When I use a CF (128MB) card with my simple project in the AC140 module.
it does not transition to RUN mode (the RUN LED changes colors from red to orange and very occasionally to green). So, there is no communication with the module at all,
neither over the Ethernet (IF6) nor RS232 (IF1). Well, I never had experience with AC140 series or any device of the SG3 platform, so I must be doing something wrong.
Please help me find out what that is.
My questions are as follows:
a) I’m using AS 3.0.90.18. What is the highest possible version of the AR that I can use?
(the AS suggests me to use a 4 or 5 different versions from I3.07 to H3.10)
b) I do not need to use PLC Open, so is it OK to use the ACP10MAN motion module?
If so, what would be the proper version range for this? (the lowest one I have installed is V2.28.2)
c) The module has a CNC capability, but I don’t need it in my simple test. So, is it OK to use the V1.28.1)
d) Are there any special considerations/steps about regarding creating projects for SG3 PLCs (compared to SG4)?
Well, even if you don’t have answers to some of these questions, ANY suggestions or pieces of information would be extremely helpful and much appreciated!
unfortunately I don’t know much about motion, so I’ve never worked with AC140.
But: AC140 is Intel-based, and therefore a SG4 system.
The LED sequence for me sounds like a endless reboot for whatever reason. Maybe you could try to force a service / diag boot to check the logger via serial connection, if AC140 has a mode switch (can’t remember that, sorry). Or, unplug the CF card after the failed boot sequence, extract the logger module using Runtime Utility Center, and open it with Automation Studio - if no logger module exists means, that the boot is already interrupted on a very early phase - then I would recommend trying first to install AR only without any motion library to check if the boot behavior changes.
I believe based on my memory AC140 should be considered an SG4 module due to i believe it had an x86 processor and CF support. SG3 used memory cards (think PCMCIA cards that were just storage). (I thought I recall it just being an under clocked processor from a PP100/200 to lower the heat). CF was 99.9% SG4 because it used a PATA/IDE interface built into the chipset of the x86 based processor.
You might need to go even older, try AS 2.7. I recall them being used in some esoteric applications in the late 2000s, but not after 2010 time frame. The AS 3.x series started rolling out late 2009 so I’d try the 2.7. Which I know might require virtual machines and Windows XP.
Depending on the amount of RAM on the AC140, you might have to use NCActions instead of PLC Open. I recalling doing projects on PP35s with CAN motion and we had to use NC Actions, as the library for PLCopen required too much memory. You still need to pull in ncGlobal and couple other ACP10 or nc libraries.
Thank you both for very quick and helpful replies. It’s really good to confirm that AC140 belongs to the SG4 platform.
Regarding the other details, I will experiment and post my progress here.
i have used it in the past, but its very long time ago…
i do not remember to have had memory constrains with this. But i would not bet for it.
The Hardware is Supported in AS3.0.90 and it should be possible to use it there.
About the Version of the ACP10 i would recomment to stay on the highest 2.x Version. As i think the 3.10 was one of the first 3.x Versions and up there CAN is no longer supported for Motion-Communication.
Sorry for the delayed reply. After long hours and many trial error cycles, I have managed to solve the issue!
Due to the very limited amount of RAM on the AC140.61-2 product (16 MB), one must squeeze the project as much as possible.
I had to use AR I3.07 (the earlier is the better, I think), ACP10 2.28.2 and remove un-essential things like ACP0NC and SDM.
BTW, the improved version AC140.61-3 has 32 MB of RAM instead of 16. As far as I know, that is the only difference.
Does anyone here know otherwise? Please correct me, if you can.
