ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

A little confusion here; for fanuc_driver version 0.3.0 and up, just select all .kl files in the karel sub-directory. It means, that from KAREL/include sub-directory, we do not need to import any files which are in fact ending in _h.kl or _t.kl.

Correct.

Those files are only include files, similar to C/C++ .h or .hpp files.

These do not get built as stand-alone programs, only as part of other programs (ie: the files with the .kl extension).

I did not copy these _h.kl or _t.kl files, and all the files have been built successfully.

If with "copy" you mean "I did not import those into my Roboguide cell", then that would be OK.

Roboguide (ktrans really) will be able to find them. If it couldn't, you would get many errors.

Next, on the same tutorial, in section 6 Copying the Binaries, it says, Finally, the binaries need to be transferred to the controller. Since, we are on windows PC, and working inside Roboguide. We have necessary programs (compiled binaries) already available inside Roboguide, and we are using the simulated controller. Where do we have to copy the files? Or is it referring in case if we had a real-robot?

Yes, copying is only needed for a real controller, as Roboguide already copies the binaries to the virtual controller for you.

Next, I move on the next tutorial, which are in fact further configurations. I have this question, section 2 Server Tags check Tag availability and status, open the Host Comm setup screen, which I cannot locate. Please, if you can help me clarify these steps, and give suggestions on next steps.

If you go to Menu→SETUP→Host Comm you cannot find that screen?

If you can't, I'm not sure whether you are missing a particular software option on your virtual controller. I would expect all FRVC to have that screen, so I'm not sure why you cannot find it.

Please make sure your virtual controller has both option R648 (User Socket Messaging) and R636 (Socket Messaging).