|
|
| |
Dear Claude,
I tried to send a direct e-mail to you but it was returned. I am working on my
next art making robot and Erik’s Plotter vi’s are just what I need to adapt to
my software. I will be using a balancing mobile as the plotter.
May you send me the vi library for Erik’s Plotter to my e-mail? tom@tomlohre.com
It would be just the thing to keep me focused on my problems.
http://www.convict.lu/Jeunes/ultimate_stuff/Erik_s_xy_plotter/E_xy_plotter.htm
|
|
| |
In lugnet.robotics.rcx.robolab, Tom Lohre wrote:
> In lugnet.robotics.rcx.robolab, Tom Lohre wrote:
> > I am working on recreating Vision Center vi in RoboLab 4.9.
>
> I found the link to CEEO's VIsion Tutorial.
> http://www.ceeo.tufts.edu/robolabatceeo/College/tutorials/image_cli/
> This is the go to place to study the Vision Center.
> I was able to adapt GPS8.vi in the GPS_Camera8.llb part of:
> http://www.convict.lu/Jeunes/Robo_Soccer/Robo_Soccer2.htm
> from Claude Baumann of the Convict School in Luxembourg to perform the Vision
> Center process.
I completely missed your question. Sorry about that. But I see that you found
help. Great!
|
|
| |
I am working on recreating Vision Center vi in RoboLab 4.9.
Currently my Vision Center vi: Threshold, MorphOpen, MorphClose,
MorphProperOpen, MorphProperClose, MorphThin and Invert causes a clear outline
in the build window.
When I try to recreate it in RoboLab, I have trouble figuring out if, it is
truly binary. When I get to the point of inserting the Morph.vi's the resulting
image blacks out. Sometimes it is there but faintly. Below are both vi’s
although I do not know the extension of the Vision Center Command. Ultimately, I
will address the outline in the image and have the Lego motors draw it in
pencil. The outline created in Vision Center Build Window needs to be my working
image. At this point, it can only be exported out of Vision Center Build by
right clicking on the image. Therefore, I must recreate Vision Center in
RoboLab.
My work: http://tomlohre.com/lego.htm
vi's used:
Vision Sensor: http://tomlohre.com/labview/11.0912
RoboLab vi: http://tomlohre.com/labview/091202W.vi
|
|
| |
In lugnet.robotics.rcx.robolab, Mark Friedman wrote:
> No language war intended, but for now I'd rather use Robolab.
I don't know for certain but I would be a bit surprised if Robolab works with
the Spybot bricks. There would have to have been a new release with
modifications specifically made to support the Spybot. Searching these
newsgroups suggests that support for the Spybot was never added to Robolab.
http://news.lugnet.com/robotics/?n=23159
NQC, on the other hand, includes full support for programming the Spybot and API
functions designed specifically to take advantage of all the capabilities
specific to the Spybot brick.
> That said, if I change my mind I'd appreciate some tips on using MacNQC with
> Spybotics.
I'm not sure if MacNQC was updated with all the Spybot support but I think it
was. The BricxCC help files or the latest NQC Guide PDF file are probably your
best bet for learning what API functions can be used with the Spybot and how to
control its motors and sensors. BricxCC includes several small programs for the
Spybot written in NQC. BricxCC also supports programming the Spybot in LASM and
MindScript if you want to try something other than NQC.
> One of my biggest questions is whether I need to download
> firmware from the SDK to the Spybotics controller.
The Spybot firmware is onboard the brick permanently and it cannot be replaced.
There is no need (or ability) to download a firmware to the Spybot bricks.
John Hansen
|
|
|
