Mitsubishi RV-6SDL Robot arm Servo/Encoder usability
I am currently looking to buy a used RV-E2 with a broken CR-E116 controller.
@dm17ry Do you have any information an that controller? I found manuals for the robot, but nothing about the controllers.
Thanks,
Jonas
Please Log in or Create an account to join the conversation.
My controller has 3 identical IGBT modules (with driving electronics on board) and one was broken. I swapped one of the working modules in for the broken one and the controller would then no longer accept the modules even if I swapped them back into the original places.
There is likely some sort of diagnostic/configuration software required to service these controllers. It's all extremely proprietary and secretive.
The only thing of use from the original controller turned out to be some of the connectors, the safety relay assembly and the information extracted from the eeprom from which dmitry could then derive the motor settings to get the motors running using regular mitsubishi motor drives.
Please Log in or Create an account to join the conversation.
no, i don't... @aciera managed to read the servo drive firmware back then, it looks like a couple of MDS-DM-V3 3-axis drives on a single PCB.@dm17ry Do you have any information an that controller?
there can be some subtle differences from a normal MDS-D-V though. i played with a MDS-C1-V2-0505 with "ROBOT-D6c" firmware. it had a bunch of extra parameters. and usually the control protocol provides only the target position, but this drive also required torque limit plus feedback torque tolerance (?) (kinda dynamic collision detection i guess).
don't know anything about the NC controller inside.
Please Log in or Create an account to join the conversation.
From the pictures I found of the CR-E116 controller, the IGBT modules look very similar:My controller has 3 identical IGBT modules (with driving electronics on board) and one was broken.
i.ebayimg.com/images/g/UTIAAOSwIgRkKHWq/s-l1600.jpg
I was hoping to reuse the drives of the old controller, but it looks like the encoder feedback is integrated on the main board.
Your controller had a separate doughter board for the encoder feedback (the long one with the connectors on top left of the IGBT modules)?
From the manual it looks like they recommend an MR-H drive for additional external axis.
I will look at the robot in two weeks and report back then.
Please Log in or Create an account to join the conversation.
jst post=295500 userid=37579@dm17ry Do you have any information an that controller?
no, i don't... @aciera managed to read the servo drive firmware back then, it looks like a couple of MDS-DM-V3 3-axis drives on a single PCB.
there can be some subtle differences from a normal MDS-D-V though. i played with a MDS-C1-V2-0505 with "ROBOT-D6c" firmware. it had a bunch of extra parameters. and usually the control protocol provides only the target position, but this drive also required torque limit plus feedback torque tolerance (?) (kinda dynamic collision detection i guess).
don't know anything about the NC controller inside.
Its possible that they are doing some trickery for the robot drives compared to the normal ones. Like you guessed for collision and overload (meaning to high workpiece weight) detection, but also for features like compliance mode:
At work i program yaskawa welding robots and the goes in a lot to make the precise movements possible (e.g. compensation for the moving mass of the robot arm and tool).
Please Log in or Create an account to join the conversation.
As I recall, the encoders were connected to the main board. The daughter board you are referring to had a couple dozen capacitors on it so it must have been (at least partly) used for the power stage. Lots of processors/FPGA chips on the other side of it though. The driver boards also had processors on board. There is likely extensive serial inter-processor communication/ startup configuration going on so it its highly unlikely you would be able to reuse the drives from the controller without _very_ extensive reverse engineering.Your controller had a separate doughter board for the encoder feedback (the long one with the connectors on top left of the IGBT modules)?
Also, as you and dmitry already noted there seems to be very close integration of the drivers into the controller to achieve features like 'compliance'.
Please Log in or Create an account to join the conversation.
I have an old 6 axis robot and I plan to start it with linuxcnc.
I had already seen videos of robot control using linuxcnc on the internet and was hoping that I could do it myself.
After reading this thread and doing some tests and verifying the performance of genserkins, I was a bit skeptical.
Please guide me whether to continue with this or try another method?
I plan to use this robot for welding
Attachments:
Please Log in or Create an account to join the conversation.
- tommylight
- Away
- Moderator
- Posts: 19196
- Thank you received: 6434
Probably very old Kuka robot, so
Do you have the control box for it?
Does it have 320 written on the box or hand controller?
What motors does it use?
Does it have encoders or resolvers on the back of the motors?
When did it have the gearbox oil changed?
Does it have a spring or hydraulic counterbalance?
Edit:
Start a new topic for it, if you already did not.
Thank you.
Please Log in or Create an account to join the conversation.
My first question would be, how do you intend to create the gcode? A straight line or an arc in 3d space should be relatively easy but following a pipe joint would likely require a CAM of some sort. Also with a robot you really need to simulate the code to check for problems with singularities.
What I would recommend is this:
- take one of the available robot simulation configs and see if you can actually get what you want with that. If you cannot get it to follow the paths you need then there is really no point in going further
- If you think the software can get you where you want to go then you would need to figure out how to get the motors of the robot to run.
Please Log in or Create an account to join the conversation.
- tommylight
- Away
- Moderator
- Posts: 19196
- Thank you received: 6434
Start a new topic for the robot.
Thank you.
Please Log in or Create an account to join the conversation.