Known issues

The faults in PAROL6's firmware and software that are known and not yet fixed, and what to do until they are. The pages that describe each part say the same where it matters; this page collects them in one place. Which versions work together is in Versions and compatibility.

Control board firmware

Seen in: release 1.

	What happens	What to do	More
KI-1	Enforces the joint limits of the earlier robot model, which differ from those in these pages; a target between the two is accepted.	Keep to the limits in the Joint limits table.	Joint limits

Control board test firmware

Seen in: release 1.

	What happens	What to do	More
KI-8	Enables all six drivers when it boots and turns every motor slowly, without a command, with no limits and no homing, until the power is switched off; no command stops them.	Run it with the arm free to move or the motors unmounted, never on a robot folded against its stops.	The test firmware
KI-9	Most command names the parser knows (#STATUS, #STEP1 to #STEP6, #FLASH, #CAN) are answered with Unknown command: only #IO, #LIMIT, #STOP and #start do something.	Use the four commands that work; CAN has its own test program.	Test firmware commands

Commander software

Seen in: main branch, 2025-09-23.

	What happens	What to do	More
KI-2	Enforces the joint limits of the earlier robot model, and computes with its dimensions (a5 = 176.35 mm, the pneumatic gripper's a6 = 62.8 mm), so its Cartesian positions are off by up to about 0.65 mm.	Keep to the limits in the Joint limits table; teach the poses that need accuracy on the robot.	Kinematics
KI-3	Output(2,HIGH) and Output(2,LOW) are refused by a bug in the program check (Invalid Output() command), and the program stops.	Use output 1 in commander programs, or switch output 2 from the Python API.	RBTscript, I/O
KI-4	SpeedJoint(), Input() and Home() pass the program check but have no action: the program stops on that line until you press Stop.	Leave them out of programs; home with the Home button before you start a program.	RBTscript, SpeedJoint and SpeedCart
KI-5	SpeedCart(), Get_data and Timeouts are in the command menu but fail the program check: a program that contains one is refused.	Leave them out of programs.	RBTscript, SpeedJoint and SpeedCart
KI-6	A move's profile written in quotes ("trap") or as func=trap is ignored without a message, and the move gets the default profile.	Write the bare word, trap or poly, as the last argument.	RBTscript
KI-7	The Cartesian rotation jog buttons do nothing in the world frame (WRF).	Rotate in the tool frame (TRF), the default.	The GUI

Python API (parol6)

Seen in: 0.9.1.

	What happens	What to do	More
KI-10	Enforces the joint limits of the earlier robot model, and computes with its dimensions (a5 = 176.35 mm), so its Cartesian positions are off by up to about 0.65 mm from the model these pages use; its tool offsets put the TCP up to about 14 mm from the model's.	Keep to the limits in the Joint limits table; teach the poses that need accuracy on the robot.	Kinematics
KI-11	The tool frame (TRF) and the flange frame have Y and Z the other way from the commander's and these pages': the frame is turned 180° about X, so its Z points back into the wrist. A TRF move or jog along +Z, or a TCP offset with a positive z, goes towards the robot instead of out of the tool, and +Y goes the other way.	In the Python API, use negative z for out of the tool: move_l([0, 0, -20, 0, 0, 0], frame="TRF", rel=True), set_tcp_offset(0, 0, -120). Jog slowly in the TRF before you run a TRF move written for the commander.	Reference frames

Something that is not here

Check By symptom first. If it is still not explained, Report a problem says what to include so it can be reproduced. A fixed issue stays on this page, under "Fixed", with the version that fixes it.

Comments

---

Found a mistake on this page? Edit it on GitHub · Report it · Get help · This page as Markdown · llms.txt · The whole manual as PDF