AJB2K3

A little bit of progress on my IDE. Thanks to @Bliss for his work with his RCX lib

We don't have a W.H.Smiths anymore and never seen it in lidl I do have the double poly

I have to go to extreme lengths to find the technic mag as non of the shops in my town sell it. What's the release date on these?

Thats the other reason that I didn't put much thought into the Interface B's checksum, it just doesn't really serve any purpose once you understand the byte stream. Writes don't need a checksum so its (in my uneducated eyes) not important.

One of the top requests I had for my project was a install that configured everything with no hunting and cross platform, the other was that it had to be beginner friendly hence why the m running blockly on python so that users can start with blocks and see how the code links. I had to make an install script for Linux based systems after the security change to them requiring the use of VM’s As to checksums, that’s not implemented as I don’t understand them at present

Sometimes the OS overrides the bit rate and tries to run at 9600 or the USB adapters only run at 9600. I've also notice that USB3* ports also don't like running slower.

https://www.hackster.io/AJB2K3/lego-dacta-interface-b-part-3-starting-again-42100a My Hackster page has has a few guides on the interface B. I work in Python using py serial which bypasses all the web serial problems and is completely OS independent. I also have a Work in progress version of Blockly I am building just for lego devices.

Very WIP and don't know yet, still early.

Wow, Sweet. Now there a start to a technic set we haven't seen for decades.

Ok, I forgot to import time. Once I imported time. the byte codes started working.

Glad it wasn't just me. Thanks. I have mentioned you and your project in my book.

Eww, its not even a nice model

From what I understand, the tag is just a list of notes like a midi steam. If that's the case then in theory you could add customised sounds using compatible smart tags. What is unknown is if the instructions are in the implanted RFID chip. If its in a chip, is it a normal common band RFID chip. I wonder how many will be brought then parted out for the smart brick.

@Bliss I'm not sure if its just me or your code but when I run from legorcx import RCX r=RCX("COM1") r.mot(r.A).pow(6) r.mot(r.A).on() print(r.LastCmdSerStr) I get the output byte string b'\x55\xff\x00\x10\xef\x10\xef' but If I try this string in a serial write import serial #ser.write(b'\x55\xff\x00\x10\xef\x10\xef') Nothing happens.

In manual 1 where its explaining the screen. No the rotation wont work as the scout doesn't support active sensors.

Reading through the manual for the Robotics Discovery set, I see a reference to a "Scout Booster Set" but I can't find any detail on what this is. can anyone provide some information.

Indeed created a table from 00 to FF and realised you can work out the sums and complimentary bytes by just moving around the chart

Yes my checksum and complimentary bit calculations are wrong, I used 256 for 0xFF when it should have been 255! EDIT: Yes, once I use the correct number, it works. Here is the normal (1st and 3rd) and flipped (2nd and 4th) ser.write(b'\x55\xFF\x00\x59\xA6\x01\xFE\x5A\xA5') ser.write(b'\x55\xFF\x00\x51\xAE\x01\xFE\x52\xAD') ser.write(b'\x55\xFF\x00\x59\xA6\x02\xFD\x5B\xA4') ser.write(b'\x55\xFF\x00\x51\xAE\x02\xFD\x53\xAC')

Thanks bud.

Opps, thanks for giving it a look.

I have the initial beep beep running and flipping but struggle to math the other sounds. Is this the correct sound 2 (down sweep) ser.write(b'\x55\xFF\x00\x59\xA6\x02\xFD\x5B\x03')

Hi Now I'm poking at bits I just need to check the maths. In my example I said x59 which make the complimentary bit xA6 But I just check and the play sound is actually x51 making the complimentary bit xAF. Im a correct in reading that the sound value is x00 to x05 ?

Thanks, I’ll have a play when back at the computer. I don’t do c++ I’m a python user as I can’t handle c!

Oh is that why MrAligator has two bytes listed on his listing? one being the command and the other being the complimentary byte?

Thank you for your patience. The next question is on the complimentary bytes. how are these known, I’m confused over the issue of working them out dispute having read the docs. so the special bit on the end after the checksum needs to be “flipped” it a command is repeated on and then off so like in the case off remote control where the control button is held down or “button bashed” to make it continue to drive in one direction. sorry I have a brain ache from all this braining and need to keep repeating to get things to stick