ROS LinuxCNC Link

@rodw the image processing part I have down. I go back to the olden days of industrial television. When we wanted to use a computer to process video we had to wait for fast enough ones to be invented.

I was wondering about how to hook external inputs such as offsets into his robot control idea.

You would want to use ros for this. It already has a support for real sense cameras and more so all you need is to figure out what you want to use it with.

As for the robot code, you should build a parser and use something like UR Script as a base so it can work with offline programmers. Using Gcode or straight C isnt a good solution. It's just going ass backwards up a tree.

There is btw an undocumented python api for hal streams. So you can stream hal data to rt components from python programs. Which was a nice find.

Hi,

Today i started coding the teach in primitives in the treewidget.
The basic 3d primitives like point, line, arc and spline are ready.
The program line is autogenerated and can be edited by user in the text display window.
For info, the program is producing random value's when running in demo mode.

@Roiki,

C isnt a good solution.
Why is hal written in c? Maybe try to write hal or a kernel module in Python.
Python is for me the most unlogical language ever written.

Using Gcode isnt a good solution
If the program can deal with Gcode you don't have to worry about "how can my robot execute a cadcam processed file?"

@Bari,

You see in the program there is a function loaded in this program line. The function is called "include vision offset component".
This function is active during this executed program line.

The way of creating a function inside this program is new. A function is like calling something like "gripper open".

You see further on the screen a function builder appear's in the treewidget.
Here you can add offset's or whatever logic you want. This function builder is an ultimate control feature.
These created functions have .so extension are direct added to the /rtlib and are added to the "Add function" content combobox.

To use a live vision system, we have to switch the controller to operate in live mode. Normally it would operate in stream mode.
A other option is to process the data of the vision system, and then execute it. Then the machine can stay in stream mode.

It's just going ass backwards up a tree. :laugh:


@Arciera,
I looked into the dmitrys nyx-branch. It is quite close to master branche to my surprise.
It can be used, no problem.

I looked into the dmitrys nyx-branch. It is quite close to master branche to my surprise.
It can be used, no problem.

Thanks for looking into it. There has actually been talk of including the driver into master but it hasn't happened yet.
If you can include that in your system then I'll be more than happy to test your application.

How do you think your system will be installed? Built from source or an ISO image?

I mean as a language for the movements that control the robot like gcode, which is an interpreted scripting language. You want something similar and not just direct C code or something. You always want to validate your instructions.

Also gcode is so different for what a robot needs that you´ll need to modify it beyond the rs274 that its no longer really gcode. Most robot controllers can also parse up to 5 axis gcode programs inside their own parsers. But the language has the functionality that robots need.

@Roiki

Actually I'm not aware that there is support for industry style robot programming even in ROS. Last time I had a look at it one had to use c++ or python script to send the commands. But maybe this has changed.

[edit]
In any case I'm not really fussy about the programming language. If I can program my robot using points from a teach-in function in JOINT, XYZABC and TOOL coordinates and can create components that use external IO, subroutines and IF/THEN statements AND have smooth movements using proper kinematics then I'm a pretty happy camper.
Certainly I will want to simulate that code before I run it on the actual hardware. Simulation is pretty much a must with robots.
To be sure, having an industry style language that's compatible with third party software like roboDK using Postprocessors would be VERY useful but surely we can't really expect Grotius to single handedly roll out a product like that in a few weeks.