-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't reproduce Example 2 bringup_examples on Windows #20
Comments
If that's all you have done (ie: you haven't called any services yet, as the example explains), then I believe this would be what you'd see. There just isn't an active EGM session yet on the virtual controller, so the driver doesn't get any feedback from it. Hence the warning. |
Thanks for your explanation, I've followed all the subsequent steps. When I get to step 5 in example 2, there seem to be 5 lines to be pasted into the terminal -- which evidently didn't work as individual commands. When I tried concatenating them together: |
just stating this is never sufficient. |
This was the error in #3 (comment) :
|
I think the curly brackets are missing in the example. Should it be: |
In a Bash session, the command line shown in the example readme does work. You're likely using If you can't use a regular dictionary (ie: using whitespace) then perhaps an in-line one could work, but you'd have to add commas.
No, there are no missing curly-braces. YAML doesn't need them. An in-line dictionary definition would need them, but you'd still need to add the commas. |
The comma separated inline dictionary worked for me on Windows. The controllers seem to time out after about a minute of being inactive, with this After I have published the message in step 6, am I supposed to see the robot move in RobotStudio? |
please see #16.
yes, albeit potentially very slowly, but that'd depend on how you've configured things (like EGM). |
As it seems you got things to work, I'm going to close this issue. I'll open a new one to track the tasks around adding more documentation for Windows. |
Tracking in #21. |
Thanks a lot for your help! |
Hi,
This isn't an issue, but I'm not being able to start a successful EGM session.
I've set up a virtual controller and system with the
623-1 Multitasking
,689-1 EGM
options, and used the StateMachine Add-in when I installed the robot controller system.In
Controller -> Configuration -> Communication -> Transmission Protocol
I made sure thatROB_1
had typeUDPUC
and hadRemote Address
andRemote Port Number
which were the same asUCDevice
. Please see the image below:When I run
roslaunch abb_robot_bringup_examples ex2_rws_and_egm_6axis_robot.launch robot_ip:=127.0.0.1
I get this in the terminal:
Click to expand
Have I set up everything correctly? Or have I missed out somewhere?
The text was updated successfully, but these errors were encountered: