Forum Replies Created

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • Bryce Ashey
    Participant
    Post count: 4
    in reply to: TF Fail #5187

    Log submitted via the tech support link – thank you again for guidance – even without being able to use it yet Niryo has taught me quite a bit. I’m really enjoying it.

    Cheers,
    bryce

    Bryce Ashey
    Participant
    Post count: 4
    in reply to: TF Fail #5154

    Hey Edouard,
    Thank you for responding – I did use the image – even refreshed it from the site to make sure. Is there anything that I could have screwed up from the start (physically) that would just prevent the services from starting? The plugs on my board differ from those in the video (one black [20 pin I think] versus several white) and the board came assembled in the packaging – not sure if that helps at all.

    Here’s the full log – please let me know if there’s anything I missed (I just did a ctrl-a/ctrl-c from the studio ROS log):

    Connected to 192.168.201.46
    sync
    chevron_left

    NIRYO ONE STUDIO LOGS

    [ ERROR ] [2019-05-13 15:45:06] Robot Connection – [object Event]
    [ INFO ] [2019-05-13 15:45:06] Robot Connection – Connection to robot is now closed
    [ ERROR ] [2019-05-13 15:45:27] Robot Connection – [object Event]
    [ INFO ] [2019-05-13 15:45:27] Robot Connection – Connection to robot is now closed
    [ ERROR ] [2019-05-13 15:45:56] Robot Connection – [object Event]
    [ INFO ] [2019-05-13 15:45:56] Robot Connection – Connection to robot is now closed
    [ SUCCESS ] [2019-05-13 15:45:56] Robot Connection – Successfully connected to ws://192.168.201.46:9090
    ROBOT LOGS (ROS)

    [2019-05-13 15:45:57] TF fail
    [2019-05-13 15:45:57] TF fail
    [2019-05-13 15:45:57] TF fail
    [2019-05-13 15:45:58] TF fail
    [2019-05-13 15:45:58] TF fail
    [2019-05-13 15:45:58] TF fail
    [2019-05-13 15:45:58] TF fail
    [2019-05-13 15:45:58] TF fail
    [2019-05-13 15:45:58] “shoulder_link” passed to lookupTransform argument source_frame does not exist.
    [2019-05-13 15:45:58] “arm_link” passed to lookupTransform argument source_frame does not exist.
    [2019-05-13 15:45:58] “elbow_link” passed to lookupTransform argument source_frame does not exist.
    [2019-05-13 15:45:58] “forearm_link” passed to lookupTransform argument source_frame does not exist.
    [2019-05-13 15:45:58] “wrist_link” passed to lookupTransform argument source_frame does not exist.
    [2019-05-13 15:45:58] Could not find a connection between ‘base_link’ and ‘hand_link’ because they are not part of the same tree.Tf has two or more unconnected trees.
    [2019-05-13 15:45:59] TF fail
    [2019-05-13 15:45:59] TF fail
    [2019-05-13 15:45:59] TF fail
    [2019-05-13 15:45:59] TF fail
    [2019-05-13 15:45:59] TF fail
    [2019-05-13 15:46:00] TF fail
    [2019-05-13 15:46:00] TF fail
    [2019-05-13 15:46:00] TF fail
    [2019-05-13 15:46:00] TF fail
    [2019-05-13 15:46:00] TF fail
    [2019-05-13 15:46:01] TF fail
    [2019-05-13 15:46:01] TF fail
    MOTOR DEBUG OPTIONS

    Not connected to Niryo One.

    Learning mode
    Joints (rad)
    0.000
    0.000
    0.000
    0.000
    0.000
    0.000
    save
    Position (m)
    x : 0.000
    y : 0.000
    z : 0.000
    Rotation (rad)
    x : 0.000
    y : 0.000
    z : 0.000
    Arm max. speed

    %
    mode_edit
    No tool selected

    Bryce Ashey
    Participant
    Post count: 4
    in reply to: TF Fail #5150

    Further up in the logs I also get:

    [2019-05-12 17:48:55] TF fail
    [2019-05-12 17:48:55] TF fail
    [2019-05-12 17:48:55] Niryo ROS control LED service is not up!
    [2019-05-12 17:48:55] Could not call /niryo_one/set_dxl_leds service
    [2019-05-12 17:48:55] Activate learning mode
    [2019-05-12 17:48:55] TF fail
    [2019-05-12 17:48:55] TF fail

Viewing 3 posts - 1 through 3 (of 3 total)