Ask Your Question

Mathias Lüdtke's profile - activity

2019-09-12 11:37:09 -0500 commented answer How do I do the PDO mapping in EDS/DCF files?

This EDS does not seem to be complete. Or the manufacturer does not support PDOs and CANopen 402.

2019-09-12 09:07:21 -0500 commented answer How do I do the PDO mapping in EDS/DCF files?

I cannot access your EDS via codeshare. Please consider uploading it to Github Gist or alike.

2019-09-12 09:02:53 -0500 edited answer How do I do the PDO mapping in EDS/DCF files?

Moreover, I’m willing to write a tutorial on ROS Wiki of this package based in my experience since there is none. T

2019-09-11 10:24:16 -0500 edited answer How do I do the PDO mapping in EDS/DCF files?

Moreover, I’m willing to write a tutorial on ROS Wiki of this package based in my experience since there is none. T

2019-09-11 10:20:18 -0500 answered a question How do I do the PDO mapping in EDS/DCF files?

Moreover, I’m willing to write a tutorial on ROS Wiki of this package based in my experience since there is none. T

2019-09-11 10:20:18 -0500 received badge  Rapid Responder (source)
2019-09-11 09:48:17 -0500 commented answer Schunk lwa4p random stops with ros_canopen

Normally, a SYNC interval of 10ms work perfectly fine with LWA4, but you might need to increase the TX queue length (htt

2019-09-11 09:45:36 -0500 edited answer Schunk lwa4p random stops with ros_canopen

EMCY: 83#128621D633D81848 This is error code 8612 (see /diagnostics as well). Unfortunately, Schunk does not list t

2019-09-05 10:52:08 -0500 answered a question Schunk lwa4p random stops with ros_canopen

EMCY: 83#128621D633D81848 This is error code 8612 (see /diagnostics as well). Unfortunately, Schunk does not list t

2019-09-02 11:59:06 -0500 received badge  Nice Answer (source)
2019-09-02 09:39:09 -0500 commented question ros_canopen interpolated position mode, time period?

Which sync master plugin are you using? How often do you get the warning?

2019-09-02 09:38:54 -0500 answered a question ros_canopen interpolated position mode, time period?

First of all, [ WARN] RPDO timeout and 60C2 are not related. The warnings gets printed if the driver does not receive

2019-09-02 06:36:52 -0500 answered a question Can I just use socketcan_bridge and socketcan_interface ROS packages to communicate with motor controllers using ROS?

Can I just use socketcan_bridge and socketcan_interface ROS packages, basically the CAN layer, to communicate with mo

2019-08-22 19:01:54 -0500 received badge  Nice Answer (source)
2019-08-20 02:56:51 -0500 answered a question ros_canopen Profile position + Interpolated position modes

So the question is, what is the workaround here? :) You can specify mixed modes I suppose, that two arm_joint_c

2019-08-20 02:56:51 -0500 received badge  Rapid Responder (source)
2019-08-19 15:01:39 -0500 received badge  Enlightened (source)
2019-08-17 05:06:53 -0500 received badge  Nice Answer (source)
2019-08-15 16:47:31 -0500 edited answer ros_canopen vel_from_device: (obj606C) issue

Unfortunately, if i put vel_from_device: "(obj3A04)2pi/60" then i get the error: It looks like 3A04 is a struct/rec

2019-08-15 16:47:10 -0500 edited answer ros_canopen vel_from_device: (obj606C) issue

Unfortunately, if i put vel_from_device: "(obj3A04)2pi/60" then i get the error: It look like that 3A04 is a struct

2019-08-15 16:46:57 -0500 edited answer ros_canopen vel_from_device: (obj606C) issue

Unfortunately, if i put vel_from_device: "(obj3A04)2pi/60" then i get the error: It look like that 3A04 is a struct

2019-08-15 16:43:11 -0500 commented answer ros_canopen vel_from_device: (obj606C) issue

Yep, you're right, I was somehow mistaken.

2019-08-15 10:55:42 -0500 answered a question ros_canopen vel_from_device: (obj606C) issue

Unfortunately, if i put vel_from_device: "(obj3A04)2pi/60" then i get the error: It look like that 3A04 is a struct

2019-08-15 10:55:42 -0500 received badge  Rapid Responder (source)
2019-07-23 09:22:29 -0500 commented answer command igus-dryve with canopen_motor_node

The controllers seem to work, but they just forward message, so it is hard to make them fail. It looks like your unit s

2019-07-23 08:47:12 -0500 commented answer command igus-dryve with canopen_motor_node

I was referring to https://github.com/ipa320/schunk_robots/blob/indigo_dev/schunk_lwa4p/config/arm_driver.yaml#L7. Accor

2019-07-19 09:08:32 -0500 edited answer command igus-dryve with canopen_motor_node

How do I actually move/command the motor? You have to publish to the command topic of the lifter_joint_position_co

2019-07-19 09:08:01 -0500 answered a question command igus-dryve with canopen_motor_node

How do I actually move/command the motor? You have to publish to the command topic of the lifter_joint_position_co

2019-07-12 16:15:37 -0500 commented answer Emergency error of Schunk PG70

Not all errors get signaled via EMCY. In addtion, ros_canopen resets 0x1003 ("errors") on init and recover.

2019-07-12 16:09:08 -0500 edited answer Emergency error of Schunk PG70

From diagnostics: key: "errors" value: "2350#df" 23xx errors are related to the current ("Current, device output side

2019-07-12 16:08:28 -0500 edited answer Emergency error of Schunk PG70

key: "errors" value: "2350#df" 23xx errors are related to the current ("Current, device output side"). This protect

2019-07-12 16:07:24 -0500 edited answer Emergency error of Schunk PG70

key: "errors" value: "2350#df" 23xx errors are related to the current ("Current, device output side"). This protect

2019-07-12 16:06:46 -0500 edited answer Emergency error of Schunk PG70

key: "errors" value: "2350#df" 23xx errors are related to the current ("Current, device output side"). This protect

2019-07-12 16:06:28 -0500 edited answer Emergency error of Schunk PG70

key: "errors" value: "2350#df" 23xx errors are related to the current ("Current, device output side"). This protect

2019-07-12 16:00:19 -0500 edited answer Emergency error of Schunk PG70

key: "errors" value: "2350#df" 23xx errors are related to the current ("Current, device output side"). This protect

2019-07-12 10:52:49 -0500 received badge  Nice Answer (source)
2019-07-11 07:19:57 -0500 answered a question Emergency error of Schunk PG70

key: "errors" value: "2350#df" 23xx errors are related with the current ("Current, device output side"). This protects

2019-07-11 07:19:57 -0500 received badge  Rapid Responder (source)
2019-07-10 06:53:33 -0500 answered a question motor oscillates after diff_drive_controller configuration

There is no PID controller in between, canopen_motor_node just forwards the target commands. BUT: the joint limits inte

2019-07-09 12:23:22 -0500 commented question motor oscillates after diff_drive_controller configuration

Do you specify any joint velocity limits in your URDF (or a separate yaml)?

2019-06-21 10:15:10 -0500 answered a question Schunk LWA4P initialization problem with ros_canopen

EMCY: 8A#2232257400000000 EMCY: 85#223225740000803F EMCY: 86#2232257400001C42 If I am not mistaken, this is an under-

2019-06-21 10:07:26 -0500 answered a question ros_canopen homing simultaneously or one-by-one?

Do the motors execute the homing simultaneously or one-by-one? One-by-one (canopen_motor_node, as-is). If one-b

2019-06-21 10:07:26 -0500 received badge  Rapid Responder (source)
2019-05-03 17:53:02 -0500 commented answer Send data thanks to PDO protocol

please don't post new, unrelated questions as a comment in a 3 years old question, which was already resolved.

2019-04-30 12:06:54 -0500 commented answer Schunk_lwa4p initialization error with ros_canopen

I guess the same(?)

2019-04-30 12:04:49 -0500 received badge  Critic (source)
2019-04-01 08:31:49 -0500 commented question rosservice call /arm/driver/init issue

Did you see https://answers.ros.org/question/289428/schunk_lwa4d-problem-initialising-with-ros_canopen/? Did you try th

2019-04-01 08:28:40 -0500 commented question rosservice call /arm/driver/init issue

Did you see https://answers.ros.org/question/289428/schunk_lwa4d-problem-initialising-with-ros_canopen/?

2019-03-02 20:24:45 -0500 received badge  Nice Answer (source)
2019-02-18 13:21:53 -0500 commented answer ROS_CANOpen NMT (+jerk during PP-PV mode switch)

I believe what this does is put the drive into the pre-operational NMT state during mode switching to prevent unwante