I get the Error -1067352607 and dont know what to do

Ask Questions
,
1

Hello there,
I’m relatively new to programming SPS modules so please forgive me if this solution is to obvious.

I got two systems: the ETAL310.1C05-1 and the ETAL410.1033-1. The first one is running without an issue, so I wanted to set up the second one. Since the ACOPOS-Micro in the second system, has no CPU, I connected it via PowerLink with the CPU from the first system (4PPC70.0573-20B). So far so easy.

After setting up the ACOPOS with two axes, getting all the settings ready and writing a little test-program, no matter what i try, I get this error and I don’t know how to solve it.
Im currently running AS: 4.12.6, AR: J4.93 and MM: 5.28.3

Is there any specific setting i have to change ? Do i have to use an other AR version ?
SDM says its not even plugged in but i obviously have.

I hope you guys can help me out.
Regards, Moritz
grafik

2

Hello,

i work a lot with B&R Motion but, as far as i remember i never had this error.
The AS-Help “Casue and remedy” section talks about rebuilding the Project and about Versions.

image
image987×390 10.3 KB

Can you check that you have the Library McAcpAx in your Project and assigned to the plc (Software Configuration)

image
image612×168 17.2 KB

In this Guide there are all Steps for a generall Commissioning descriped. The base for this Guide was the ETAL410.1033-1.

Guide Motion Comissioning for beginners

I think based on your Odernumber you have the Resolver Option on your Motors .R0
The ETAL was also available with .B1 Encoder Option so for all who are using B1:
In this Thread there is the B1 Encoder Option descriped.

8LVAxx.B1 EIB Encoder ParID 719 → 1

Greetings
Michael

1 Like
3

Thank you really much for your answer! I found the mistake, there were incorrect settings in the PKL and 80VD100.. Configurations for Controlled and Managing Node.

Now the system is running.

Since you also used the ETAL410.1033-1 in your motion guide, can you tell me, if you used it in your single and multi axis guides? In specific, if i want to run both motors simultaneously, can i use MpAxisBasic two times and give each one an axis and a AxisParameters reference, or do i have to use axis groups and MappRobotics, even though the axis are in no correlation to each other?

1 Like
4

You can use two instances of MpAxisBasic and AxisParameters references to have two independent axes.

1 Like
5

Hello,
I may add that also in a situation were you use an AxesGroup for GroupCommands its often usefull to have a MpAxisBasic instance for each axis, to allow single Axis commands for service purpose in the application.

So i would typicaly say that it is most common to have a MpAxisBasic Instance per Axis.

Greetings
Michael

2 Likes