mappMotion using P3 meet error -1067378796 (Power on failed)

Ask Questions
1

I can not power on the motor on cockpit, I think the configuration is OK.
Please help me check that , thanks!

image
image1555×844 121 KB

image
image1784×856 43.8 KB

image
image1091×545 34.4 KB

image
image829×775 120 KB

2

Hello Shenyang

Have you linked your axis encoder to the option board you inserted in the drive?

screenshotAS_P3config
screenshotAS_P3config650×314 17.9 KB

This is not clear from the screenshots.
In order to analyze this properly we’d need at least a network command trace or a motion drive log.

3

Desktop.zip (46.8 KB)

image
image1086×720 89.9 KB

Hello Jan,

This is the nct/drive log and Encoder config, it seems the motor parameter does not configured.
But the motor parameter should load automatically I think.

4

I see these are old motors without a 2.0.0 upgrade
Can you try and copy the content of the motor files to the motorsynchronous_any hw file? Maybe this will help.

5

In addition to the comment of Jan. Please note that in MappMotion the motor configuration some of the parameter have a changed precision/exponent.

Can you try and copy the content of the motor files to the motorsynchronous_any hw file

1 Like
6

Hello Jan,

We tried this:

  1. Manually write the motor parameters into the parameter table A34R0_2200.apt.
  2. Add Config_3.axisfeature (Feature_AcpParTable) in mappmotion.
  3. Call A34R0_2200.apt in Feature_AcpParTable.
  4. Call Feature_AcpParTable in the channel characteristics of the servo.

We use these steps and now it works well.
Thanks!