Search the Community
Showing results for tags 'communication'.
Found 3 results
I have read all sorts of complaints about Robot Inventor and by inference Spike Prime. Some are valid (eg poor documentation)... some are less so (eg colour scheme). One thing seems clear is that the hardware is well thought out (yes there are issues with cables). Now in robotics three elements stand out as being super important: being able to use multiple motors (motors are basic building blocks), multiple sensors plus having the computational brain (and software) to hold it all together. Unfortunately Lego only provide 6 ports on each hub and have 2 versions of software both of which initially appear limiting. Whereas wireless Inter-hub communication could be very helpful enabling models to use multiple hubs and access both software platforms this is not something that Lego have explicitly provided at the moment. There is however a very simple and seemingly reliable work around available immediately that could help in cases where high speed comms and high data volumes are less important. This is to use optical communication. The idea which I have tested is to use the distance sensor to signal light flashes to the colour sensor. The number of flashes in a fixed time frame thus delivers information from Transmitter to Receiver. As expected using downloaded compiled code speeds the process up though not massively. This process could be 2 way, could enable daisy chaining of hubs and could be expanded to longer instructions (again high speed not being a limitation). On the downside the process sacrifices at least one port on each of a pair of hubs (if the requirement is for one way communication between the pair). The sensors need to be carefully and firmly positioned for reliability although there is no other requirement for any connection between them. In this context a model containing the one hub could “launch” the second. As SP and RI software can be easily swapped on any hub the user has the choice of using SP/SP or SP/RI or RI/RI platforms. Unfortunately size limitations prevent me from uploading images of the set up and demo code at the moment.
Lego doesn't support a message protocol that is interchangeable between the NXT and EV3 brick. To overcome that problem, I have written a small program in C# to make the translation between the two different bricks. It works fine, but you always need a PC in between. At our blog (see https://siouxnetontr...pc-application/), I have written an article with a completely different solution, namely a 'motor communication protocol'. Enjoy. /Hans
In this MOC I put the dome of the second Cantina set to good use (the first being the Outhouse). The Empire has established large bases on Tatooine. To keep them in contact small communication posts were set up. This is an example of one such posts made to fit into Mos Eisley. Several antennas to keep in touch with troops all over the planet and to listen for rebel messages. Complete with a space communication array. I am still working on my own Cantina though. No telling when it will be finished. MOS_Communication-post-03 by L-space, on Flickr MOS_Communication-post-06 by L-space, on Flickr MOS_Communication-post-01 by L-space, on Flickr The entire album is on filckr