Skip to main content

Row a Concept2 on Zwift with a $10 Raspberry Pi!

Despite there being a clear appetite for rowing in Zwift, the reality is that a rowing machine is not a bicycle. A Concept2 rower will not connect to Zwift out of the box. The Zwift team occasionally hint at a future rowing mode, but it has been “coming soon” for years. I would not hold your breath.


That said, people do row in Zwift. So how are they doing it?

The key challenge is that Zwift expects to see a bicycle. To make this work, you need a way to translate data from the rower’s performance monitor, the PM5, into something Zwift recognises as a bike. This means inserting a device between the rower and the device running Zwift that can perform that translation.

There are already solutions available. Some are relatively expensive, such as the NPE CABLE, which costs around £90 in the UK. Others are technically free, like the RowedBiker app. The downside with RowedBiker is that it needs to run on an additional device separate from the one running Zwift. If you already have a compatible phone or tablet, that might be fine. If not, you will need to buy something.

A Raspberry Pi Zero W, on the other hand, costs about $10. I already had one to hand and, back in spring 2020, I suddenly found myself with a bit more time to experiment.

After a fair amount of trial and error, it eventually worked. Properly. You can download the result from GitHub, and it even comes with a tidy installer to make setup straightforward.

And now, I am off for a row. On Zwift.

Comments

  1. Awesome - super easy to download and install and I'll be darn - it just works !!!

    Thank you so much

    ReplyDelete

Post a Comment

Popular posts from this blog

Raspberry Pi A2DP Bluetooth Audio Receiver

I wanted to use a Raspberry Pi to act as a Bluetooth audio receiver or my Hi-Fi so that I could connect a phone/tablet easily to some proper speakers wirelessly. Rather than reinventing the wheel 'kmonkey' has already achieved most of what I set out to do over here ; check this out first. The only issue now is the manual intervention needed to connect up a new Bluetooth source to the output sink. I initially created a simple bash script to poll pulseaudio (every 5 seconds) and run the necessary commands as and when a new device is connected. You can see the script here and all the pertinent commands are explained over in kmonkey's blog. This is all good, but will need to be run manually using something like, # nohup ./bt_audio_attach & This is a bit rubbish and you'll be pleased to know there is a better way to get this done, UDEV! Over at the Raspbery Pi forums   there's some discussion on using UDEV scripts to auto...

Blocking Adverts from the Roku Menu

UPDATE: 18 May 2013 - A new firmware (v5) has changed the way ads are handled on the Roku such that this guide is no longer relevant.  Roku are are a pretty neat little media streaming box but one thing that I think lets them down are the trashy and mostly irrelevant adverts on the home page. Wouldn't it be great if you could get rid of these? The ads are served by the third party ad platform,  ZEDO . You can block the ads from displaying by simply blocking this domain entirely or by being more targeted and blocking the specific sub-domain serving the Roku ads. A TCPDUMP of my Roku shows that the ad images currently come from 'd7.zedo.com' (although this may change). I block them by adding a custom DNS record for this sub-domain to my home router pointing to the loopback address (127.0.0.1). There are or course many other ways you could do this, but the best way will largely depend on your own set-up and resources.

Spawning many VirtualBox machines from a single VDI

What I'm taking about here is a way to have many VirtualBox machines based upon a single hard drive image. There are many reasons why you might like to do this, but the most compelling is probably saving time by not having to install an OS over and over again, especially useful if you do anything like software testing. Our goal is a single vdi (virtual disk) file which contains a vanilla installation of our favourite OS which we can then use to conjure up a fresh new machine in a jiffy. Assuming you already have VirtualBox installed our first step is (maybe for the last time ever!) to install our OS into a new virtual machine. Now I shan't go through this as it's pretty straight forward and if you're reading this it's the sort of thing you have probably done a hundred times before. One thing of note during the initial setup is the 'Virtual Hard Disk' configuration. Be sure to allocate enough space to allow for all potential applications of the image. It wou...