| |
Hello All,
A small update
The "Fixes CLI vis in Pilot mode" dated 7-17-2002 to be applied to 2.5.2
is incorrect. It must be applied to Robolab 2.5.1. That is the error I
received when I tried to apply to Robolab 2.5.2. Tufts hopefully will
upgrade their Web page.
This means if you install Service Pack 1 to Robolab 2.5.1 you get the
CLI patch mentioned in the previous paragraph.
As I said below applying Service Pack 1 to Robolab 2.5.1 gives you
Robolab 2.5.2.
Also the Robolab Reference Guide has been upgraded to 1.1. It contains
information on creating sensor files and some corrections in the text. A
great document! It explains EVERY icon in ALL levels of Robolab. Good
job to the people that did it!
Good luck,
Bill Blackmer
PS Does anybody read the Robolab stuff here??
-----Original Message-----
From: Bill Blackmer [mailto:bill@bbccd.org]
Sent: Friday, August 16, 2002 11:39 PM
To: 'Miles Gentry'; 'lugnet.robotics.rcx.robolab@lugnet.com';
'lugnet.dacta@lugnet.com'
Subject: FW: updating Robolab 2.5 - Some testing
Hello Miles and all,
Here is what worked for me on the upgrade process:
Number 1.) Robolab 2.5 basic release
Number 2.) The CD-ROM 2.5.1 from Pitsco overlaying the 2.5 release
Number 3.) Service Pack 1 applied. My version is now 2.5.2
The SP.1 text note that is installed as part of Service Pack 1 says,
" You have successfully installed ROBOLAB Service Pack 1.0.
Your RL 2.5.1 program should now be updated to 2.5.2."
This means to me that SP1 must be applied to version 2.5.1.
As I said this is what worked for me. Maybe you can apply SP1 to the
base release of 2.5. I do not know.
About 15% of the VIs in the directories have new dates which means
changes.
They are in vision, music, RCX communications areas.
Some of these VI are large and will take some time to review. They work
fine I just want to know what is in them.
The file structure has some new directories and some of the older
directories are empty.
ALL of my current VIs work fine. I have not tried any of the new changes
in SP1. Currently my confidence is high.
All my VIs that talk directly to Labview 6i or Production Labview look
OK.
The "Fixes CLI vis in Pilot mode" dated 7-17-2002 to be applied to 2.5.2
have not been installed by me. Service Pack 1 has some fixes in CLI
area. I am not sure they are the same as the patch. More on that later.
I guess I have many changes to make to my presentation notes for
NWBRICKcon.
Email if you have other questions,
Bill Blackmer
-----Original Message-----
From: Bill Blackmer [mailto:bill@bbccd.org]
Sent: Friday, August 16, 2002 5:10 PM
To: 'Miles Gentry'; 'lugnet.robotics.rcx.robolab@lugnet.com';
'lugnet.dacta@lugnet.com'
Subject: RE: updating Robolab 2.5
Hello Miles,
After all the help you have been to me in the past I am happy to help
you.
About two months ago I received a CD-ROM from Pitsco with the label
2.5.1 on it. The instructions were very simple "Overlay everything in
the current Robolab directory with what is on this CD-ROM" I did and
everything worked fine and Robolab system said 2.5.1.
In order to get this CD-ROM for 2.5.1 I called Deanna Newell at Pitsco.
She was on vacation and they transferred me to some very friendly tech
support people. To make a long story short, I pointed out all the
patches that need to be applied to 2.5 and they freely sent me 2.5.1.
Good people there.
I have applied all the beta patches mentioned with dates before
7-5-2002. They do install and fix problems in my environment:
1.) My early container problems disappeared;
2.) My vision and camera problems largely disappeared with the vision
patch;
(Some vision issues remain with certain cameras. My solution has been do
not use the ones that require more work)
3.) The generic sensor patch works with the one third-party sensor I
own. (Most third-party sensors that act like light sensors work fine I
believe)
4.) The Robo server patch works.
The "Fixes CLI vis in Pilot mode" dated 7-17-2002 I have not installed
because it says 2.5.2 not 2.5.1!!
I understand the Service Pack 1 dated 8-14-2002 is 2.5.2. I have not
confirmed this. I will download it in the next hour and let you know
tomorrow if you are interested.
The one other issue is I use XP with NTFS file system. I only log on as
an administrator user only and I have no problems.
I do not know what version Pitsco is shipping now.
Lastly, I giving two presenations at NWBrickCon on Advanced Robolab and
basic Robolab, it would nice to meet you.
http://www.sealug.org/nwbrickcon.html
Let me know if you need other information.
Bill Blackmer
-----Original Message-----
From: news-gateway@lugnet.com [mailto:news-gateway@lugnet.com] On Behalf
Of Miles Gentry
Sent: Friday, August 16, 2002 3:58 PM
To: lugnet.robotics.rcx.robolab@lugnet.com; lugnet.dacta@lugnet.com
Subject: updating Robolab 2.5
Need your help understanding why and how to update Robolab 2.5.
Tufts offers Service Pack 1 for Robolab version 2.5.1 at
http://www.ceeo.tufts.edu/robolabatceeo/Resources/Service_Pack/default.a
sp .
What should owners of version 2.5 do ?
Does 2.5 need the updates in Service Pack 1 ?
How do owners of version 2.5 update it to 2.5.1 ?
What does 2.5.1 update beyond 2.5 ?
Does Lego currently ship 2.5.1 ?
Do the Beta Patches at
http://www.ceeo.tufts.edu/robolabatceeo/Resources/downloads/default.asp
applicable to version 2.5.0 update it to 2.5.1 ?
Lego's Robolab page http://www.lego.com/dacta/robolab/default.htm does
not
mention version 2.5.1 or even version 2.5 even though Pitsco ships 2.5.
How
do owners of Robolab 2.5 normally update to the current version ?
Thanks in advance for your help.
|
|
1 Message in This Thread:
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
