Error C14 (Multi-turn encoder error)

Hi there,

I’m encountering a C14 Multi-turn encoder error. Bear in mind that I’ve tried the solution suggested here, point number 5. Please find below the output in the terminal after running clear_pvl_err.

This program is only used to clear multi-turn encoder errors

Please input the xArm ip address[192.168.1.194]: 192.168.1.218
Ip: 192.168.1.218
main-socket connect 192.168.1.218 success
is_old_protocol: False
version_number: 1.2.2
[set_state], xArm is not ready to move
Connect success!

state(200)=[1, 300]
state(A03)=[1, 0]
state(A04)=[1, 1]
state(01C)=[1, 0]
clear muti-turn, ret=[1]
state(01C)=[1, 0]
Please Enter to exit

I’ve also noticed that our xarm 7 came in a slightly different ‘setup’ as the manuals. The default side of the arm is on the same side as the plugs. As per attached image.

Please advise.

Hi, did you restart the controller after clear the error?
If you could run the xArm without error, you could press the Zore Position to let the the TCP move to the default position.
We move xArm 7 to the position in the image for packaging.

Thanks

Hi Daniel,

Yes I restarted the controller by pressing the power button and holding it for 3 to 5 seconds, before pressing it to turn it on again. I’ve also tried to restart by turning off the main power.

I’m unable to control xArm using xArm studio. I’ve tried switching from Simulation Robot to Real Robot but was prompted with a pop with the error code C14 Multi-turn encoder error.

Got it, how about try this one and then restart the controller and the xArm Studio:https://drive.google.com/open?id=1hjAk8_47Ha2jj5SYI67UJGfNOP1arXxG

Thanks

Hey Daniel,

I ran the script you just sent and it worked, it cleared the error. But may have caused some other problems with the orientation of the robot arm.

Here is the output in the terminal after running the script.

This program is only used to clear multi-turn encoder errors

Please input the xArm ip address[192.168.1.194]: 192.168.1.218
Ip: 192.168.1.218
main-socket connect 192.168.1.218 success
is_old_protocol: False
version_number: 1.2.2
[set_state], xArm is not ready to move
Connect success!

[1] state(200)=[1, 300]
[1] state(A03)=[1, 0]
[1] state(A04)=[1, 1]
[1] state(01C)=[1, 0]
[1] clear muti-turn, ret=[1]
[1] state(01C)=[1, 0]
==================================================
[2] state(200)=[1, 300]
[2] state(A03)=[1, 0]
[2] state(A04)=[1, 1]
[2] state(01C)=[1, 0]
[2] clear muti-turn, ret=[1]
[2] state(01C)=[1, 0]
==================================================
[3] state(200)=[1, 300]
[3] state(A03)=[1, 0]
[3] state(A04)=[1, 1]
[3] state(01C)=[1, 0]
[3] clear muti-turn, ret=[1]
[3] state(01C)=[1, 0]
==================================================
[4] state(200)=[1, 4853]
[4] state(A03)=[1, 4724]
[4] state(A04)=[1, 4726]
[4] state(01C)=[1, 4700]
[4] clear muti-turn, ret=[1]
[4] state(01C)=[1, 4380]
==================================================
[5] state(200)=[1, 300]
[5] state(A03)=[1, 0]
[5] state(A04)=[1, 1]
[5] state(01C)=[1, 0]
[5] clear muti-turn, ret=[1]
[5] state(01C)=[1, 0]
==================================================
[6] state(200)=[1, 230]
[6] state(A03)=[1, 0]
[6] state(A04)=[1, 1]
[6] state(01C)=[1, 0]
[6] clear muti-turn, ret=[1]
[6] state(01C)=[1, 0]
==================================================
[7] state(200)=[1, 200]
[7] state(A03)=[1, 0]
[7] state(A04)=[1, 1]
[7] state(01C)=[1, 0]
[7] clear muti-turn, ret=[1]
[7] state(01C)=[1, 0]
==================================================
Please Enter to exit

Hi
(1)Please download this tool:https://drive.google.com/open?id=1T81nrlT2P2Jw7hRD3PQowYXAj8oiHyfk
and make sure that the xArm is the same post
(2)then input: D13I4, and then power off and power on the xArm by press EMS(emergency Stop button)
(3)then try to control by xArm, and to check if this issue is solved.
If you could shoot a video about your operation will be better, just incase that the trouble shooting is not work.

Thanks

Hi Daniel,

A few question.

  1. What do you mean by making sure that the xArm is in the same post?
  2. I’m running the tool and this is the output in the terminal, with characters that I can’t make sense of. As attached below.

Please advise.

Hey Daniel,

I’m running the tool in Visual Studio Code that has proper encoding, I’m able to see the characters now. As below.
Can you guide me through the steps?

choose 2
and then input the last 3 numbers of the controller’s IP address, for example controller’s IP is 192.168.1.234, then input 234 is OK.
What do you mean by making sure that the xArm is in the same post?
Sorry for making it confuse, I mean you make sure that the xArm now is on the same position in the image you sent to me, like that
image

Gotcha. I managed to figure out. Right now the terminal is stuck at this screen, and it’s taking a while. Is it normal?

[tcp proc] arm socket thread start
Tcp Control connection successful
[gc_proc ] gcode thread start
[terminal] terminal thread start

Yes, did you send D13I4?

Okay I just did. Now I see this.

[gc_proc ] ok: 
[gc_proc ] ok:
[gc_proc ] set id_num = 4 zero, ret = 0

Do I restart the arm?

yes, resrat

Hi Daniel,

Thanks for your help so far.

We’ve managed to control the xArm using xArm studio. Slight problem here, I think our zero position for the robot is not correct. Please refer to attached photo for reference.

How can we fix this?

Hi,
(1) Please press the Zero Position button on xArm Studio to let all the joints are on 0°.
(2) Adjust Joint-4 on xArm Studio live control panel to let the TCP plane parallel to the mounting plane(the plane of desk)


(3) Calibrate again: run the python tool, input 2 and then input ip and then D13I4 and restart the xArm robot by EMS
(4) Check if the problem solved.

Thanks

Hi Daniel,

Yes. We estimated the joint 4 angle and used the python tool to reset the zero position.

Thank you!

Great

Hi @Daniel I have the same calibration issue with the same xarm7 robot.
where can I get the python tool?

thanks,