LH4PI

Impressive info , well done

Robolab supports up to 4 control lab

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

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

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

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 ?

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

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

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

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

A nice article about LEGO history,Robolab,LabVIEW, Control Lab interface , RCX... https://drive.google.com/file/d/1-AODe6NfoPuZCcgWwx3V9kYZTSpV0jyw/view?usp=drivesdk

Hi Brian When you mention that you tried CLI (Control Lab Interface ) using Robolab in earlier days but didn't get it to work , do you remember if you get any communication at all or not , my knowledge so far is that it sometimes it work (initate the correct outport port (at least A,B and C ) and keep going to do so but dependent of the history of what I do it van stop to work , it can also be that the Robolab 2.9.4c installation is not set up correctly .!? By the way did you test RCX with Robolab , better experience with that hardware ? Best Regards Lars

Hi Thorsten Okay now You have the sam setup as me,also Download the same ( I suppose you also update to 2.9 4C) Since I have the Interface B ( as well as rcx an nxt ) I like to try Robolab of course I have tried to communicate using usb to serial dongle on my windows 7 pro 64 machine but the communication work not stable ( but using dosbox on the same hardware ad well on my vintage Toshiba Tecra M5 and dacta ctrlab 1.3 work perfectly) So it something with Robolab But if I remember correctly you do not have a Interface B , do You can not test ?! Best Lars HiThorsten No , I have not testet rcx yet with robolab but should try to get time for that tomorrow. I am initially more interested to get cli to work if possible . I have tested little more and its clear that the implementation of cli (control lab interface) is buggy and I try to understand what commands works and what is wrong ( it looks like the cli commands use the rcx commands instead sometimes . The update to 2.9 4c was needed to get at least a basic start of working communication. More to come Best /Lars

Hi Thorsten Okay now You have the sam setup as me,also Download the same ( I suppose you also update to 2.9 4C) Since I have the Interface B ( as well as rcx an nxt ) I like to try Robolab of course I have tried to communicate using usb to serial dongle on my windows 7 pro 64 machine but the communication work not stable ( but using dosbox on the same hardware ad well on my vintage Toshiba Tecra M5 and dacta ctrlab 1.3 work perfectly) So it something with Robolab But if I remember correctly you do not have a Interface B , do You can not test ?! Best Lars

Hi again Please , that must be somebody in this forum that use or have experience using the Robolab that I can share information to get Lego running Best Regards Lars

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

I find a solution , I bought a vintage Toshiba Tecra M5 that have a standard 9 pin serial port (as well as SD, PCCARD, USB, CD/DVD, Video ou and a 80 GB SATA harddrive and 2G RAM) , I successfully install Lubuntu 18.04 LTS and Dosbox for linux and get it working using the Dacta Dos program and the serial port ! https://drive.google.com/file/d/1qP8ikgW1RdHr6lKT7XvZvx8HCeDMJicG/view?usp=sharing https://drive.google.com/file/d/1ksEbxfCaHvN_ZMdJo2E9ZHQbzpGiAcLO/view?usp=drive_link

I find a solution , I bought a vintage Toshiba Tecra M5 that have a standard 89 pin serial port (as well as SD, PCCARD, USB, CD/DVD, Video ou and a 80 GB SATA harddrive and 2G RAM) , I successfully install Lubuntu 18.04 LTS and Dosbox for linux and get it working using the Dacta Dos program and the serial port !

Thanks Thorsten I also use Hterm ! I testet the software , but it is free only for two first week and not as good for the same price as my suggestion in my opinum . I have bought a faulty interface B from USA and hope to be able to fix it , I let You know . Best Lars

Hi All Anybody that have info or link about a good free rs-232 monitor/analyzer that can " sniff'/ listen to the traffic between a wIN 7/10/11 64 bit computer and a RS 232 device and save that to file ? Best Regards Lars

Test of uploading a picture from my Google drive https://drive.google.com/file/d/1kpDcydF3zalG7CGQnTBvIEHQe4pUOlR-/view?usp=drive_link

Bricklab.exe actually have been made by Swedish programmer , I have talked to him but it is clear that it is not running win 3.11 but win 95 and up !. you find the program here http://www.blockcad.net/dacta/, the interface B The sniffer program I have found that actually support win 11 64 bit is https://www.electronic.us/products/serial-port-monitor/ Best Regards Lars

Almost correct Point 4 differs Bricklab.exe is a windows test program for interfacec B and it works in windows 11 but no use for me. Ctrlab exe is the original Dacta full funktion DOS program with labview like interface that I can run i DOSbox-X but not yet errorfree communication . I have started to use a sniff terminal program , let see if that help

Hi Thorsten It is no problem to run the dos Dacta LEGO control lab program ver 1.3 itself using DOSbox-X The present problem are related to set up the communication to the Interface B . I have tried to get DOSbox-x working using ATEN usb to serial adapter at com1 . That serial adapter works with Windows 7 and windows 11 using windows bricklab.exe application for the interface B . The strange thing when I run the serial emulation (using directserial realport: com1) I only get communication working for a short time (at least it indicate that it sense the right port and speed I believe) , a few seconds and then the dos program loose the communication (Can't find the control box message is displayed ) I have to play around how to config and set up virtual serial1 port using the DOSbox-x configuration Tool. It may be that dos program is sensitive for how it share the port with windows in the background and now have incorrect handshaking that is not what it expect or something in that direction . I have to investigate using a terminal and usb oscilloscope or/and play around with the settings I belive Best/Lars

Thorsten , I already run the original control lab for interface B in Dos , it works perfectly on my old OB 600C so why not try win 11 and DOSbox-X using DOS 5.0 ?!