I have been running Mac OS X El Capitan (10.11.4) on a MacBook Air and have been having considerable difficulty getting Isaac to recognize the Gen 3 iPro. Both USB cables do work. I have tried a number of workarounds including using different USB ports, different cables, resetting the iBike, restarting the MacBook, etc. In the end, I always have to reinstall the drivers in order for the software to recognize the iBike Pro.

This scenario reminds me of all the SCSI voodoo of the early Macs, nevertheless, I do think the problem lies with either the Isaac software and/or the iBike Gen 3 having compatibility issues with Apple's latest OS or software conflicts with PowerAgent and/or Golden Cheetah (both software packages use similar drivers).

Is anyone having software/hardware issues also? I would like to continue to use the Gen 3 iPro, as I have invested considerable money, time, and effort just getting the quirky little thing to give me dependable and reasonable power numbers (Road & TT bikes) under most circumstances, i.e used a DFPM to get a proper profile(s). I am not really interested in upgrading - unless, of course a trade-in value is offered on a new PowerPod

Any suggestions?

btw. I do have a PC desktop with the latest Windows 10 OS - I will experiment with it also. Unfortunately, I travel a lot and need the iPro to work consistently with my MacBook.

The issue is that you are using two devices (Gen III iBike and Joule, I believe) that use the same SiLabs drivers. Each time you connect your Joule to your Mac, the Joule "hijacks" the SiLabs drivers, knocking-off the iBike connection.

In order to reestablish the connection with your iBike, you need to reinstall the SiLabs drivers.

The conflict you're experiencing was corrected by SiLabs in later-generation USB/UART chips they sell and that we (and other manufacturers) now use.

So, you can continue to use the workaround you have, or upgrade to a more current Newton or PowerPod.

Thanks for your response John. As indicated in my enquiry, I did mention that it might be a conflict between software products (PowerAgent & GoldenCheetah) - and you have clarified that in a very timely fashion. Thanks again.