View allAll Photos Tagged servo
…Is the name of the electric drive attachment, designed to attach to the (shared) chassis of the Baldessa, Baldamatic, and Super Baldamatic (the model illustrated here).
Reading the fine print it seems that each film advance takes more than two seconds; but still, a powered winder (with 19 feet of remote extension cable!) seems like an improbable accessory for a sort of mid-tier camera type.
Controller with DE0-nano soc module. This controller works together with the TXT controller of Fischertechnik via an I2C connection. The TXT is connected to the PC. With this own controller a lot of extensions are possible. Also the processing speed of the different serial modules is much higher. There are 5 spi lines available. Each serial line has 24 digital inputs. Outputs are according to the module and are motors, servo's, stepping motors, power outputs. The spi lines work with a clock of 2MHz so all inputs and outputs are processed in 14 usec. With the 5 spi lines up to 120 inputs are read. A real time overview is shown by an LCD display of 4x20 characters. Via the rotary encoder button 4 different pages can be selected. A second rotary encoder button selects the spi channel. There are 6 additional keys available. At the top is an IR receiver. A remote control is available with 40 keys.
To be able to follow the operation of the FPGA 17 outputs are made for the logic analyser and 4 for the picoscope. This way it is possible to bring out any internal signal within the FPGA for the measurements.
There are 4 analog inputs with a range of 10V. There are also 4 pot meters available for an analog setting. These have a resolution of 12 bits and are read out every 140 usec. These values are also available for the TXT Controller via the I2C connection. 2 BNC connectors are available for a digital clock up to 50 MHz. These can be made as input or output.
On the right side there is a connection for 2 circuits with neopixel leds each up to 256 leds. A separate 5V power connection is provided for this purpose.
Nederlands:
Controller met DE0-nano soc module. Deze controller werkt samen met de TXT Controller van Fischertechnik via een I2C verbinding. De TXT is verbonden met de PC. Met deze eigen controller zijn enorm veel uitbreidingen mogelijk. Ook de verwerking snelheid van de verschillende serieel modules ligt veel hoger. Er zijn 5 spi lijnen beschikbaar. Iedere serieel lijn beschik over 24 digitale ingangen. Uitgangen zijn volgens de module en zijn motoren, servo's, stappen motoren, vermogen uitgangen. De spi lijnen werken met een clock van 2MHz waardoor alle in en uitgangen in 14 usec verwerkt worden. Met de 5 spi lijnen worden tot 120 ingangen gelezen. Een realtime overzicht wordt weergegeven door een LCD display van 4x20 tekens. Via de rotary encoder knop kunnen 4 verschillende pagina's gekozen worden. Een 2de rotary knop selecteer het spi kanaal. Er zijn 6 extra toetsen beschikbaar. Bovenaan zit een IR ontvanger. Een afstands bediening is beschikbaar met 40 toetsen.
Om de werking van de FPGA te kunnen volgen zijn 17 uitgangen voor de logic analyser gemaakt en 4 voor de picoscope. Op deze manier is het mogelijk om gelijk welk intern signaal binnen de FPGA naar buiten te brengen voor de metingen.
Er zijn 4 analoge ingangen met een bereik van 10V voorzien. Er zijn ook 4 pot meters beschikbaar voor een analoge instelling. Deze hebben een resolutie van 12 bits en worden om de 140 usec uitgelezen. Deze waarden zijn ook voor de TXT Controller via de I2C verbinding beschikbaar. 2 BNC connectoren zijn beschikbaar voor een digitale clock tot 50 MHz. Deze kunnen zowel als ingang of uitgang gemaakt worden.
Aan de rechter zijn is er een aansluiting voorzien voor 2 kringen met neopixel leds elk tot 256 leds. Een afzonderlijke 5V power connectie is hiervoor voorzien.
Cut the wires at the potentiometer, then heat their pads and remove them. Remove the solder from the middle pad with solder wick. Apply flux, then heat the left pad and push a resistor into it. Heat the right pad and push a resistor into it. Apply flux and solder the two resistors to the middle pad.
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.
Connect the servo to your microcontroller (here an Arduino) and tell it to move to position 0 (i.e., a pulse width of 1500µs). The gears should start spinning, unless it was previously at 0.
This series of images will guide you through modifying an HS-311 servo to give continuous rotation in either direction, with a degree of speed control.
The modification is non-reversible, but these servos are cheap as chips so this shouldn't be a big worry.
Now superglue the tab in place. Use lots of superglue! This is the second non-reversible step. If you accidentally move the tab a bit, you should still be able to fix it. If not, don't panic, you can fix it in software later.
Using tweezers, move the potentiometer tab until the gears completely stop moving. Be as accurate as possible, though you can compensate for it not being dead centre in software later.
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.