masspaster.blogg.se

1. #LOGITECH F710 WINDOWS 10 2016 INSTALL#
2. #LOGITECH F710 WINDOWS 10 2016 DRIVER#
3. #LOGITECH F710 WINDOWS 10 2016 SOFTWARE#
4. #LOGITECH F710 WINDOWS 10 2016 PC#

This also makes a beep to let you know it’s stopped l = right (not so intuitive I would guess ).These are mapped to keyboard inputs, as the making a direct connection with the F710 game pad is still a bit lacking (to be explained later). Here, I created a simple set of input block to control the forward/backward and left/right movement of the car. After loading, the template, you will have further features enabled in the “More Controls” section: Figure 4: Scratch2 with the “wedo_2.0_template.sb2” the extension shows up under “more blocks” This is most likely located in your “Documents\Scratch Projects” directory on for your user account. Next, you open the Scratch2 desktop application and load the “wedo_2.0_template.sb2” into Scratch. If you close it, it will disconnect from the Smart Hub.

Connection in right panel shows the status of the motors, lights, button and battery When installed and running, it looks like this: Figure 3: Screen shot of the S2Bot using the Lego WeDo 2.0 template. This enable the connection to the WeDo Smart Hub from Scratch.

#LOGITECH F710 WINDOWS 10 2016 INSTALL#

Here, you have to install under a Window 7 profile to make it work (right click on the installation executable–> Properties –> Compatibility –> Compatibility Mode: Run under Windows7)Īfter installing Scratch, you then need to install the helper application “S2Bot” from PicAxe software: S2Bot 4 Scratch . You can download the Windows 7 version from the Lego Education website.

#LOGITECH F710 WINDOWS 10 2016 PC#

You can also use the Lego WeDo 2.0 application if you like, although it’s a bit quirky on the PC (additionally, the Windows 10 version never would download for me from the Microsoft App Store…it kept saying “Problem on our side”. I chose the Scratch programming language, because I wanted to see if all of this could be done from the PC… (which it could). Mine didn’t actually have the markings “BlueGiga” Here’s what it looks like: Figure 2: BlueGiga BLED112 dongle. Perhaps other Bluetooth 4.0 dongles will work … I don’t know, I didn’t test them. I ordered one with the Lego WeDo 2.0 kit, as they recommended, so that’s what I use. It’s not quite your normal USB-Bluetooth dongle, as it doesn’t really show up normally on your system in order to connect devices the devices which have to use it know that they will look for that dongle. Anyway, only 2 degrees of freedom are required to pilot a car, so that’s good enough.Ī note on the BlueGiga BLED112 dongle: apparently, you need this special dongle to make it work. However, this only works if you’re using a tablet as the PC/BlueGiga BLED112 dongle only will handle one connection at a time. With the regular Lego WeDo 2.0 software, you can control up to 3 Smart Hubs (I think), and therefore 6 motors. The WeDo 2.0 smart hub only has 2 ports and therefore could only handle 2 motors, or a motor and a sensor, or 2 sensors.

#LOGITECH F710 WINDOWS 10 2016 SOFTWARE#

#LOGITECH F710 WINDOWS 10 2016 DRIVER#

Some improvements could be: use tank style steering (one motor for each driver wheel, and a caster wheel in the front) also a direct or gear drive would probably be better than this belt. My goal was to control the car with my Logitech F710 game pad, so my boys could find it more like their usual remote control cars. The integration was easy and used already existing software for the most part. It’s quite a short and shabby project, which a bunch of hacked together items to get it up and going. The main purpose was to build a proof-of-concept Lego WeDo 2.0 car, which could be piloted using my Windows 10 PC.