servo-remote-test
Linking Fischertechnic and Lego.
With FT I use the TXT controller, with Lego I use the Maindstorms inventor hub and the Techinc hub. To make them work together I use 2 Lego remote controllers. On each remote control there are 4 servos. This controls 4 buttons, the 3 remaining buttons can be operated manually. The servos are controlled by the TXT controller. The RoboPro program on the PC is used for this purpose. The servos themselves are controlled by my DE0 module but this can also be done with an I2C module on the TXT. All hubs use the Pybricks Python software: v3.2.0b4 Pybricks Beta v2.0.0-beta.9
There are 2 Pybricks programs running simultaneously, each controlling a different type of hub.
It is now easy to send commands from the TXT to both hubs. This can be done simultaneously or separately. The big problem with Lego hubs is that they have almost no inputs. Thus, we lack the nice 8 channel digital inputs that are present with the TXT. Through my DEO module, I even have 120 digital inputs. Via the servo controlled remote I can now at least send multiple commands to the Lego modules. The large PC screen where the program can be displayed is also indispensable.
Now to send commands from the Lego hubs to the TXT are a number of possibilities. I use a lot of hall sensors. Small magnets connected to Lego parts can send commands this way quickly and easily. I can also listen in on multiple serial lines from the hubs. That data can be used by the TXT. Thus, positions of the motors can be displayed, as well as other data from the hub. The TXT can display this data on the PC screen.
Pybricks does not have a hub to hub at this time. Now, however, commands can be sent from one hub to the TXT which then forwards them to the 2nd hub.
servo-remote-test
Linking Fischertechnic and Lego.
With FT I use the TXT controller, with Lego I use the Maindstorms inventor hub and the Techinc hub. To make them work together I use 2 Lego remote controllers. On each remote control there are 4 servos. This controls 4 buttons, the 3 remaining buttons can be operated manually. The servos are controlled by the TXT controller. The RoboPro program on the PC is used for this purpose. The servos themselves are controlled by my DE0 module but this can also be done with an I2C module on the TXT. All hubs use the Pybricks Python software: v3.2.0b4 Pybricks Beta v2.0.0-beta.9
There are 2 Pybricks programs running simultaneously, each controlling a different type of hub.
It is now easy to send commands from the TXT to both hubs. This can be done simultaneously or separately. The big problem with Lego hubs is that they have almost no inputs. Thus, we lack the nice 8 channel digital inputs that are present with the TXT. Through my DEO module, I even have 120 digital inputs. Via the servo controlled remote I can now at least send multiple commands to the Lego modules. The large PC screen where the program can be displayed is also indispensable.
Now to send commands from the Lego hubs to the TXT are a number of possibilities. I use a lot of hall sensors. Small magnets connected to Lego parts can send commands this way quickly and easily. I can also listen in on multiple serial lines from the hubs. That data can be used by the TXT. Thus, positions of the motors can be displayed, as well as other data from the hub. The TXT can display this data on the PC screen.
Pybricks does not have a hub to hub at this time. Now, however, commands can be sent from one hub to the TXT which then forwards them to the 2nd hub.