Gunners TekZone

Hello and Yes. They are blocking commands. But you got me curious, so I started paging through the Reference Guide again (the list of "primitives" are alphabetical) and found a couple that reference parallel processes. The one you are probably interested in is launch This test will run both the sound and lamp at the same time for 5 seconds to test launch [tto "SoundC setleft onfor 50] launch [tto "LampB setleft onfor 50] Despite owning 10 of these little yellow bricks (enough for short yellow brick road to the wizard of LEGO) I really haven't done anything with them (I really didn't like the blocky method, and get bogged down in all the alternatives, of which I can never seem to find the right firmware for an example I am interested in). Anyhow, I digress... I believe the RCX can follow both internal and remote commands at same time. I know the IR remote control (and tower) can start/stop programs and directly control outputs. They can also communicate between themselves via IR (but not sure if that requires alternate firmware or not).

Sure... Glad to share... I have looked, but haven't found any others programs for the Control Lab on the internet. Hard to believe, but then Google search parameters are just not up to the task :D I don't have it properly documented... In fact I actually didn't know commenting could even be done, until I found some PDFs of a set of four Control Lab manuals to learn the language from. I had printed them all out... Then, finally, I just found an original set on Bricklink that is currently in transit. Yay! The Control Lab Train Program: https://www.dropbox.com/scl/fi/qooeyf5k2sg5ubvwr6bnf/dual-train-run-and-auto-park.WCL?rlkey=l7hwikysb4cithgrqjueqbuaq&amp;dl=1 to train tto "LampB setright on tto "MotorD setright onfor 20 tto "SoundC setright onfor 20 forever [ ; Run 9v CN forward tto "MotorH setright setpower CN_Auto_Speed on ; Wait for button if Touch4 [ tto "MotorH off tto "LampF on wait 10 tto "SoundC setleft on tto "MotorH setleft on ; backup until trigger light sensor waituntil [light8 < 70] tto "MotorH off tto "LampF off tto "SoundC off tto "MotorD setleft onfor 20 tto "SoundC setright onfor 20 tto "MotorG setright setpower 8 onfor 1 ; Run 12v steam train waituntil [Touch4] tto "MotorG setleft setpower 5 on tto "LampF on wait 10 tto "SoundC setleft on tto "MotorG setleft setpower 8 onfor 1 waituntil [light7 < 70] wait 5 tto "MotorG setright setpower 5 onfor 1 tto "SoundC setleft off tto "LampF off wait 50 tto "SoundC off tto "MotorD setright onfor 20 tto "SoundC setright onfor 20 ]] end to CN_park tto "MotorD setright onfor 1.5 tto "MotorH off tto "LampF on tto "SoundC setleft on tto "MotorH setleft on waituntil [light8 < 70] tto "MotorH off tto "LampF off tto "SoundC off end to steam_park tto "MotorD setleft onfor 1.5 tto "LampF on tto "SoundC setleft on tto "MotorG setleft setpower 8 on waituntil [light7 < 70] wait 5 tto "MotorG setright setpower 5 onfor 1 tto "SoundC setleft off tto "LampF off end

@Bliss Working great so far!! Thanks! Now to improve my Python coding so I can make good use of this. Currently I am just using three push buttons on one device to manually control a switch and drive a 9v train (powered on another device) around my test track. Next intent is to duplicate my semi-autonomous program, currently on ControlLab (running TC LOGO) in Python.

Working good now. Nice! I will experiment a bit more with my dual interface setup, and let you know if I run into anything else.

Well... it keeps crashing and blurring out the screen. I think it is trying to use the same COM2 port for both devices. Also... Trying to remember to use numbers for outputs... But just not liking it Ahhh... It does the same thing if I use the dropdown menu to choose the different ports as well. Even without a script. Crashes as soon as I press the Sart Lego button for the 2nd device.

Not quite yet... The only setup I can run multiple Interface-B's on is my pokey slow Win7 QBOX 2060, so I currently have one setup there and the other on my Win10 laptop. Actually the QBOX it is not that bad, but is setup in a lousy location for working on, in any comfort. I am trying to make some layout adjustments, now that I have your tools to make use of my multiple devices (and still awaiting my 3rd anyhow).

Hah! I can relate. Started off with LEGO, then a VIC-20 (but never mixed them at the time... Just wasn't aware that was a thing. So sad... What I could a learned, had there been LEGO Education resources at the time and in my area). Subbed to your channel, and will build that yellow arm one day, when I can figure it out (apparently there are no official plans). Been thinking about finding some old laptop for DOS use (no space or $$$ for a proper vintage PC to replace what I had to give up over 20 years ago due to a major move). But will see if I can figure out an emulator and try our your program And that explains why your example worked on COM1 (where my USB adapter is set for) when I forgot to change it from 14 in the script Is it just me, or is there no way to adjust the window size (with the internals dynamically fitting)? Even on my Win 10 1600x1200 screen (my largest) the whole box is too tall, and way too big to use on my Win7 PC with its wee low-res 1370x768 screen. Otherwise, it is a very nice program... And working great!! Thank You!

Oh... Python based Interface-B programming... Nice! I have been messing around with this for past few weeks... But even after fixing version changes to things like print() I just couldn't make it do anything... Soooo frustrating. https://www.shamlian.net/projects/dacta/index.html Nice to have something in current development to work on instead!

Looking real good!... Easy to see at a glance what is happening. Happy New Year! (4 hours to go here)

Ahhh, Nice to find out why it confused me so... Successfully running your app on my laptop the first time, but forgetting to plug in my USB-COM adapter after that ). But at least that is what got me to make my initial post about your program. I have been scouring the web for alternative to Control Lab, but so many had missing links, missing articles, software, etc. Your was the only "current" one that also stated a hopeful programmability to it... so I wanted to try it! After thinking about it... I think having a Connect/Disconnect button (keep as is or amalgamate the current Start Lego/Stop Lego buttons into one with GREEN indication) that resets everything when disconnected, is good. Then adding a dedicated STOP button (that turns all RED when connected, dims out when pressed?) that acts like a emergency software stop that retains all settings. Basically a similar idea as the Control Lab. Of course resetting everything on App start.

Might as well... When not testing, I tend to run multiple instances anyway, so I can see and control both on same screen... Not that there is much benefit, as my initial attempt to test signaling from one Interface to the other met the obvious inability to make the "signal" meaningful without logic... when using your program alone... But at least a button/sensor on one interface (on your app) can start a process on the 2nd interface (on ControlLab). Altogether, that was just messing around. Really looking forward to your other project. As I have my RCX setup connected to same PC, and like the simplicity of the Control Lab programming interface over most of the RXC programming options)... I find myself wishing your project could control/program both RXC and Interface-B (just an attempt to plant a thought worm as they do seem so compatible... just one static and the other portable).

Works great now, Thanks. Harder to find quibbles... But I'll keep trying The slider positions remain after a start/stop action (Just the visual, the actual settings reset to full) And for another aesthetic/beneficial suggestion... Perhaps make the Stop Lego button turn red when the interface is running? Again not critical with only 2 choices, and if an output is activated the nicely coloured arrows do show as connected. And on the note of device choices... In the next week or two, I should have a 3rd Interface-B delivered (and hopefully not requiring repairs). So if you want to expand to three (or more), I can help test that as well.

Good day, Unfortunately neither download ran on my Win7... Same "Not compatible" error as posted prior. On Win 10 the direct .exe ghosted. While the folder version opened, it looks and operates the same as the last one I tested. Might I recommend inserting development version numbers or something (perhaps on the GUI for the development timeframe?) to help us keep track one which one works or not. Oops... sorry... neither seems to run on my Win 10 PC either, I apparently forgot to delete the prior folder from yesterday's final test The Date/Time stamp on the exe (in the folder) is 2024-12-30 10:45 AM

Ok, the only issues/ideas I have ran into so far are: - The Set Power slider adjustments still transfers settings across the two Interfaces. - And there needs to be some visible indication that an Output Port is active... I think simply highlighting the Arrow button that is active would be sufficient. - Perhaps a option to set one of the Yellow Inputs when a temperature sensor is used, so as to display the appropriate temp value in C or F (may need a "+/- calibration adjustment" option as is on Control Lab).

You are welcome... I do enjoy testing stuff I want to use And YES!! Now this looks and runs as expected. Both download methods run, and on both PC/Windows versions. No more errors when I try to change COM ports when already running. Less trying to count my fingers (Lets see... 1=A, B=2... ) when figuring out the correct Out Port to click on (Yes, the battle is real ) I will play around with the app in more detail later... must eat... nom nom... Thanks again for your efforts in developing this, for all us enthusiasts!!

Thanks. Unfortunately, I am still getting the same results. The direct LegoDemoB.exe - On Win10 64bit it does a ghost routine AKA nothing happens at all (compatibility adjustments didn't make a difference) and, yes, I made sure my USB-Serial adapter is plugged in (missing that in the beginning for me was the culprit). - On Win7 32bit it gave same error I mentioned before... Not sure how compatability down from there would matter. The full download of LegoDemoB folder will run on both computer/windows versions... But it is NOT the colourised, adjusted, version you posted an image of. I ran this path : C:\...\LegoDemoB\bin\Release\net8.0-windows\publish\win-x86\LegoDemoB.exe Showing screen of my LEGO Win7 32bit PC (as that is my main target for most of the vintage LEGO programs I run). But short of not seeing any error or result on the Win10 64bit PC, the results are the same. Somewhere, somehow, we ran into a disconnect with the app testing and ran into version/download troubleshooting :D We will figure this out I am sure. But I need to take a break and go watch some Netflix or something to get my mind off this for a bit. And thanks for your effort and patience with my apparent trouble getting your latest app to test.

(No content avail)

That might have been just a False Positive due the fact that it is an .exe My AV didn't complain. Sorry, when setting up the screenshot it was on the wrong post... I meant the prior link (as was in the quote) where you had added colour and alphanumeric labeling.

(No content avail)

OK, either I am due a nap ;) Or perhaps going cuckoo?? Not sure why I can't seem to get the correct app running all of a sudden. On my Win10 64bit Laptop (now with USB-Serial and one Interface connected), that executable just does it's ghost routine... Nada happens. On my QBOX LEGO PC - Win7 32bit, it just gives some hard to catch error.

Honestly... I don't know... Hah... I used to follow on your recommended path. Then thought I was finding and choosing the correct .exe once you just sent the zip link without the path... But I can get easily lost when unable to clearly focus. Unfortunately that is often my normal state :D But then I also started downloading them directly onto my LEGO PC, where the interfaces are normally plugged into... But which is much slower to extract (so more waiting, which causes my mind to wander) and then deleting the old folder so I don't get them mixed up. That might not be going as planned, hahhah. I'll try again on my main laptop... No interface currently hooked up here, but then once I know I have the correct one I can sneakernet it over. Hmm... Mine (from your last posted link) doesn't look like your image. Is this the correct path? C:\Users\Gunner\Downloads\LegoDemoB\bin\Release\net8.0-windows\publish\win-x86\LegoDemoB.exe

Wow... so quick with the updates :D I was still just testing the last... It now starts a connection on 1st try. As for the switching COM while running, there is still an error popup, but I think that might be "normal"?? And I also think I misread it and assumed a crash, when actually clicking on Quit, meant quit. My bad.

I totally agree!! I refuse to use blocky, or whatever it is called, style programming with Mindstorms (the real reason I never got started with it when it first came out) or the same GUI with PyBricks (but I like Python). I am NOT a programmer (more a copy paste/manipulate script kiddy type... hehe)... But have been teaching myself new programming languages as much as able. BUT... I am also visually oriented, get really confused when a control is oriented vertically for a device laid out horizontally, colour is better than monochrome and mixed labeling is just painful for me to react too quickly... Of course, I am mostly housebound due ME/CFS and have 4 cats and LEGO, literally, all over the place... So my sanity might be in question... Ha! Looking forward to that... I started my self-taught entry into computers with BASIC waaaayyy back on the VIC-20

It says... Stopped Opening Serial Port on COM2... Serial Port on COM2 Opened. Sending Initialization Message on COM2... Running on COM2 (But the STOP light on the interface is still lit) Stopped This only happens on any 1st attempt to Start Lego at initial start of application. Once past that 1st attempt, connection works as expected for both devices. Also, any attempt to change port while already running will crash app... similar to what happened when attempting to run 2nd device a few posts back.

@Bliss Hah, I just realized that I can run multiple instances of the program... Nice!... And no apparent conflicts between them. So short of cross device program-ability in the future, what is the reasoning of dual (or more) device control in a single instance? Honestly, if Windows DACTA Control Lab had the ability for running multiple instances, then that would be near perfection in my mind. Yes, somewhat limited programming, due the older TC LOGO language, but by far better than anything else I have tried so far, particularly with the WYSIWYG GUI side it also incorporates.