Hey.

I have updated to Kide 1.1.0.0.
When programing a DuAro robot, it is no longer possible to kill and start each arm.
Also only 5 "task" (autostarts) is displayed, but the DuAro got 8.

It works fine in Kide 1.0.0.0

Kide 1.0.0.0
[img][/img]


Kide 1.1.0.0
[img][/img]

Hello,

thank you for your comment!

It seems that the robot was not identified as a DuAro. After connecting to the robot, the robot type is parsed from the AS file. For a DuAro the robot's type string must contain "WD". Can you please check your robot's type string? You'll find it on the robot / controller info page.

Hi again.

I just connected to the robot again, checked it got "wd" in the robot type string - Yes it have.

I reactivated auto backup on connection, to see if that helped - it didn't.

Kide still can't see it's a DuAro.

I have attached some files, that maybe can help you.

Hello,

thank you for your detailed information and sorry for the late reply!

I noticed that the language could not be determined correctly. At the moment I'm in vacation but I will take a deeper look when I'm back.

Hello,

I checked the connection between K-IDE and DuAro WD002N-A202 with firmware 09200023 on K-Roset and found no issue. In K-Roset the language of DuAro is set to English but I know the the DuAro in real life is set to Japanese language when you first turn it on.

In your screenshots and textfiles the language is shown as Japanese by K-IDE but the respond of the controller shows that it's configured in English language. The result of this behaviour is that K-IDE cannot understand the response of the controller.

In my simple test with K-Roset the DuAro is correctly identified. I guess something is wrong / not as K-IDE expects with the language configuration.

Hi again.

Alright.
But I tried to connect to the same robot with K-IDE 1.0.0.0, and there it identify the robot correctly.

So have there been a change on how K-IDE identify the robot between the 2 updates?

There were some changes in the language identification but not specifically for the DuAro series.

Can you send me the AS file?

Yes, backed up from K-IDE 1.1.0.0 if that makes a differnce

Thank you for the AS file!

It's strange but K-IDE is working well with your AS file. The data is correctly identified as a DuAro program.

After sending the AS file to the K-Roset robot and then disconnect and connect K-IDE can successfuly identify the robot as a DuAro.

Strange.

When I get the time, I will try some more on the DuAro, thanks for now.

Hello,

I have the same Problem with the latest KIDE 1.1.1.0

Kind regards

Dear Mr. Geyer,

welcome to the forum and thank you for the comment!

There is a bug where the task order definition is faulty initialized.

As a work-around you can edit the file "Initialisierungen.xml" in a text editor and add/replace the following lines:

  <TaskOrder>
    <TaskOrder5>5;1;2;3;4</TaskOrder5>
    <TaskOrder8>1;2;3;4;5;6;7;8</TaskOrder8>
  </TaskOrder>
 

Please close all K-IDE instances before editing!

Thanks