A nice article about LEGO history,Robolab,LabVIEW, Control  Lab interface , RCX...

https://drive.google.com/file/d/1-AODe6NfoPuZCcgWwx3V9kYZTSpV0jyw/view?usp=drivesdk

Edited April 30, 2024Apr 30 by LH4PI

It really is, nice find!

However I believe the authors are slightly off with regard to the beginning of LEGO robotics. They write that in the late 1980's it all began with the Interface B using serial communication.

I may be wrong (and @evank as well as @alexGS and some others will know better), but I believe it was the LEGO Interface A using parallel communication on a number of computers via their built-in ports (e.g., C64) or LEGO interface cards (Apple, IBM), which started it all. Around 1986.

The Interface A directly (more or less ) listened and talked to the data bus of the computer.

Evan has composed an introduction to LEGO robotics on his website, which nicely covers the very early days: https://www.brickhacks.com/0.php

Thanks for sharing!!!

Best,
Thorsten

Edited April 30, 2024Apr 30 by Toastie

Hi Thorsten  and  (and @evank as well as @alexGS   and all that use Interface A, You are  absolutely correct , I think the article was more about the era after LOGO  .I  remember I was  in contact with  Chris Rogers ,Tufts University, Medford, MA  0215

as  B-tester for the upcoming  the Robolab  2.9  back in 2006 (when my brain still was working far better than now ) !. I should  try to reach him again   , hopefully  he can have  needed insight how to get  Interface B (CLI)  up running in 2024 !

Best Regards Lars 

Here is another  link more focus on the Interface B  from the same Tuft University group  also introduce the  separate "LEGO Engineer software "

 

https://www.ni.com/pdf/academic/us/journals/ijee_05.pdf

Edited April 30, 2024Apr 30 by LH4PI

Good morning I haven't had time to help with this debate... however I made a short video where robolab 2.9.4 controls the control lab with a motor on port B. I should have more time... but at the moment I can't... um hug to everyone.

https://drive.google.com/file/d/13S33Ql7HHK8iMMosYiPe841Y80DnVG0A/view?usp=sharing

windows XP - robolab 2.9.4  - pc with com1 port - Lego cable

this is a answer to

"Everyone 

I now also want to run interface B , rcx and nxt using robolob 2.9  on windows xp  using natively serial port . Can anybody confirm that the interface B actually works well on this platform.

Best Lars "

 

Edited April 30, 2024Apr 30 by legoROBOLAB

Thanks a llot  LegoROBOLAB!

Fantastic news , now I have  finally a platform  and  a example  that works for you but  works randomly for me , sometimes the  engine B start , sometimes  not , so it must be something with the installation I star to believe  , but I should make the exact  same example  and test out further .

 

  My setup:

I  have an a vintage Toshiba Tecra M5 with XP PRO sp3 (maybe  You have SP2 ?!, I get an error that NXT needs SP2 )  , Robolab 2.9.4c  with  a real  serial port com 1  and Lego cable  , so very similar to You  

 

Yes... sometimes there are mistakes... but I have to spend more time analyzing them. Because there are messages that say it doesn't work... and then it works... and then it doesn't work... in conclusion... I have to spend some time.

Edited April 30, 2024Apr 30 by legoROBOLAB

Hi again LegoROBOLAB!

I test again  and   I use a very simular  vi , I can get it working , but I can either change  the power level or the direction , the suddenly  the  communication  stops  , even if the  CLI indicates  that i communicate .  So You are right , it is waste of time  if  nobody knows  if the communication and Robolab actually support   it fully for the 2.9.4C version . I   have contacted Chris Rogers and wait to his response  for correct setup !.

Here is an example when it works :

https://drive.google.com/file/d/1gl_BoLF0oFSPq2MwU9KdH-D9PT4ppneH/view?usp=sharing

but when  I change  as an example the power level  from 5 (max power ) to 2 (see picture , no change  in speed , same  with  the direction , motor runs the sam direction . Then  it can suddenly stop communicate  when start the program vi again  and I have not found any  step by step procedure to follow to  get it working again . Power down and power up again can help. Running the  dacta ctrlab 1.3 in dosbox  on the same hardware  even in Linux  always work , even on windows 7 or above using usb to serial converter 

https://drive.google.com/file/d/1qP8ikgW1RdHr6lKT7XvZvx8HCeDMJicG/view?usp=sharing

---------------------------

The robolab   give  an answer as it was the RCX that was connected :

try to select CLI

https://drive.google.com/file/d/1xkgdksh3gKc9uc3FBcmF1U24jQEDm-a6/view?usp=sharing

gives this :

https://drive.google.com/file/d/1v2ebyLGzEhfZF7tb_xB0NmeEE1nIP3hp/view?usp=sharing

"Play sound only exist in RCX  so it is clear that  the software , even if should select CLI  it use  RCX  code !

--------------------------

Version i use : 

https://drive.google.com/file/d/1MwSqaxDWPfWL6tbM52geKiW0ajjEAHRG/view?usp=sharing

/Lars

Edited April 30, 2024Apr 30 by LH4PI

Lars

I have identical problems. I'll see if robolab 2.5 has the same problems... I used Windows XP SP3 and robolab version 2.9.4.c.
(I have the impression that there was an upgrade to 2.9.4. due to the use of sensors... but I'll look for that information)

 

LegoROBOLAB

 

I find this  instruction for the Robolab  2.9.4c patch  that  also list what was made and  as you can see they where  an "minor" uodate  for the CLI    and in deed when running 2.9 it was worse  problem for me 

https://drive.google.com/file/d/1ncOZ8aI6bGGT3WuUwZ_NfAcWYpM1nZ_q/view?usp=sharing

 

A very  interesting book that maybe can help is  "Engineering with LEGO Bricks and Robolab"  by Eric Wang  in consultation with Chris Rogers  , I do not have the book but it is possible to read on th vintage  forum and I find a few pages that  describe  CLI . Have  you that book ?

Edited April 30, 2024Apr 30 by LH4PI

Hello Lars

Using robolab 2.5.4. It seems to me that it works well... watch the short video... the engine is running very slowly.
I pressed the STOP key on interface B and the movement was suspended. I charged it again, and the engine continued to run slowly, as programmed... and it has never failed (so far).

https://drive.google.com/file/d/1X6YJdkGoQf5T7zpQSAVJvuy_faQqEKPb/view?usp=sharing

You can get RoboLab 2.5, here

https://legoeducacional-umcontributo.blogspot.com/search?q=robolab+

This is my blog... make a click over the image of RoboLab 2.5 ... and the archiv.org will give you a version of it.

Impressive  blog   LegoROBOLAB !! , I should study , So your impression is that  2.5.4 work more stable   for CLI then 2.9.4c  ?    As an example did you have the same proble m to  program the ppwer level in 2.9.4c ? (we  loose  NXT support but  if  CLI and RCX   work more stable   and we do not need the addition sensor from Verner  that is okay enough ) 

 

Best /Lars

Lars... you can use the sensor adapter with only LogIt sensors... Vernier sensors i think you can't... but I will see later. In this version you have the INVESTIGATOR , that wasn't i earlier versions...

Make use of 2.5.4 mixing RCX with interface B.... I will go to do the same... and then will see if 2.5.4 is the answer for your problem.

So , anybody that have the robolab 2.5.4 version handy that should work with Interface B   , please listen and help with a link .

 

Best Regards Lars  

Oh, I really wish I could help out - but no interface B here, nor Robolab 2.5.4.

Spoiler

 

And I am busy with getting an Amstrad PCW9512 "Joyce" (introduced in 1985) talking and listening to interface A using Mallard Basic-80 for CP/M ... I believe I'm really close. My initial attempt utterly failed - and that was totally me not paying very close attention to the ingenious design of the serial/parallel interface from SCA.

 

Hope that someone can help out here on your issues!

Good luck and best wishes,
Thorsten   

I have good news ! 

legoROBOLAB helped me to find a working English version of Robolab 2.5.4 that works  for my CLI  today 

 

He is the hero !

Robolab 2.5  does not work for Interface B (CLI)!

Now I can start to program .

Best Lars 

Hi!
I've been following this thread avidly since the moment I've owned a Dacta Control Lab. Recently I got my hands on a second one and I was wondering if anyone got two Control Labs working synchronised. Im currently using the official Lego software and I havent found an option in there. Also working with Visual Basic and it seems to support that, but the programming seems a bit more limited. Havent tried Robolab up until now.

Best wishes from the Netherlands, Rob

Robolab supports up to 4 control lab 

Cool, thanks!
Im interested in this Robolab version 2.5.4 as well in that case. Could you tell me where you have found it? Thanks in advance!

p\0###Do you byte, when I knock?$$$

Hi Guys new here and only got got an Interface B.
My eventual goal is to control it from an M5Go Microcontroller via an RS232 adapter using Micropython.

Currently I have it connected to a MAC via a PL2303 Usb adapter and I'm trying to communicate over python.

I think I may have activated the Serial connection but when I serial write the command 

p\0###Do you byte, when I knock?$$$

Python console returns 34

Is something wrong or am I not understanding something?
Can anyone help me?

@AJB2K3

Did you configure you serial communication correctly?

I read somewhere:

9600 baud
no flow control
no parity
no modem control lines
one stop bit
8 bit data

 

Yves

Edited October 11, 2024Oct 11 by Bliss

Ah Ok so 34 is the bytes in the string sent

Isn't the Stop LED supposed to go out when it gets received?

Here is my code and response.

Python 3.10.5 (v3.10.5:f377153967, Jun  6 2022, 12:36:10) [Clang 13.0.0 (clang-1300.0.29.30)] on darwin
Type "help", "copyright", "credits" or "license()" for more information.
import serial
ser = serial.Serial(port='/dev/cu.PL2303G-USBtoUART24110')
ser.write(b'p\0###Do you byte, when I knock?$$$')
34
ser.read(16)

However its seams to just sit there after issuing the ser.read(16)

Edited October 11, 2024Oct 11 by AJB2K3

On 10/11/2024 at 1:02 AM, Bliss said:

@AJB2K3

Did you configure you serial communication correctly?

I read somewhere:

9600 baud
no flow control
no parity
no modem control lines
one stop bit
8 bit data

 

Yves

Well, thanks for your help but it turned out to be the pins were not as expected.

My working code so far is as follows: 

Quote

 

import serial
import time
ser = serial.Serial(port='/dev/cu.PL2303G-USBtoUART24110')
ser.write(b'p\0###Do you byte, when I knock?$$$')
ser.read(16)

while True:
    ser.write(b'2')
    time.sleep(1)
    ser.read(16)
    print(ser.read(19))

 

For some reason the code function is not working.
    
    
    
    

Edited October 12, 2024Oct 12 by AJB2K3

Got a response now just need to decipher the ports

49 minutes ago, AJB2K3 said:

Got a response now just need to decipher the ports

maybe this info might help you