Axis not referenced

[jan.wolf]

In logger, I am getting error that my axes are not referenced.

The project is using ACOPOS table to set up the axes, which I am seeing for the first time.
In the physical view, the axes are referenced this way, same goes for gAxis_A1

Axes in Configuration View are being referenced to Axes group file, which is in Object Hierarchy

As for the AcpParTables from Configuration View, they are tied with the table in Logical View.

Since the axes are still not referenced, I am clearly missing something, is there another file that needs the axes referencing ?

[michael_w]

Hi there,

this does not mean you didn’t reference (as in use the axis anywhere properly) but that you want to start a movement without letting it know a reference position.
I recommend opening the help for the error number in the logger → B&R Online Help
Since that already contains all required info I’ll spare my words to say the same as there

[michael.bertsch]

Hello,

The wording “Axis not Referenced” in the error context means that the “IsHomed”-Bit of the Axis is not set. Your Configuration is fine, but you have to call a “MC_Home” before you command a Movement.

---

The Parameter Tables just load some ParIDs at StatUp to the ACOPOS.

The ParID 719 = 1 will Reset Encoder Errors and could interpreted as Command.
This command should not be set at every boot up, but only if a Encoder Error occured.
This command makes a write operation to the encoder memory and this can wear out the memory. It will take a thousand times but i was once told to me not set it to offten.

The ParID 347 F_Switch changes the PWM Frequency output of the ACOPOS.
This has an effect to the termal behaviour of the ACOPOS. Please consider the notes in Manual about Derating for higher Frequencies.

Greetings
Michael

[Martin.Schrott]

The error text highlighted in the original post was changed in mapp Motion V6.1.0 to

Start of movement not possible: Axis is not homed

in order to avoid ambiguity.