-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running on a mac #11
Comments
You need libusb. Can you try after |
1 similar comment
You need libusb. Can you try after |
Thanks John, installed libusb (and brew!) and that gets me to the same point as the raspberry pi, looks like I've had the same install issue, will try the install script for both and see how I get on: sudo python /Users/James/antifier/antifier.py --debug |
I've updated the install script and removed scipy:) |
Thanks John, Saw that you had done so and so retried a fresh install. But still getting the following (weirdly the file that says is missing is in the folder: Assuming fixed resistance return value from trainer Thanks again for your continued help. |
Are you executing the script with sudo whilst in the script directory?
On Tue, 7 Nov 2017, 22:27 JamesBudge, ***@***.***> wrote:
Thanks John,
Saw that you had done so and so retried a fresh install. But still getting
the following (weirdly the file that says is missing is in the folder:
Assuming fixed resistance return value from trainer
get ant stick
Trying to write to 4104 dongle
USB READ ERROR [Errno 60] Operation timed out
<< ['a4016f20ea']
Using Suunto dongle
get trainer
0x1932
Found variable resistance return value from trainer
Exception in thread Thread-2:
Traceback (most recent call last):
File
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py",
line 810, in __bootstrap_inner
self.run()
File
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py",
line 763, in run
self.__target(*self.__args, **self.__kwargs)
File "/Users/James/antifier/antifier.py", line 500, in run
pc_dict = trainer.parse_factors(power_curve)#get power curve dictionary
File "/Users/James/antifier/trainer.py", line 116, in parse_factors
temp = open(filename,'r').read().split('\n')
IOError: [Errno 2] No such file or directory:
'power_calc_factors_fortius.txt'
Thanks again for your continued help.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AfAO_Yle_kvjH2Lbl3Z4XfVpjeNjnM0uks5s0NlOgaJpZM4QVWlh>
.
--
John Taylor
MA VetMB MRCVS
Director
Mansion Hill Veterinary Practice
133 Main Road,
Middleton Cheney
01295 712110
www.mansionhillvets.co.uk
|
Oh that was very silly of me, no I wasn't. Have done so now and it runs but couldn't pick up a signal when in zwift. ran with debug and now getting the follow: Any ideas what I'm doing wrong now? Thank again, James |
realise part of the problem (connecting to zwift) may be that my two ant+ dongles are not the same version one is 1008 one 1004. The 1004 version is not recognised by antifier on either my mac or my raspberry pi (understandable as you state that its only built for 1008 and 1009). However zwift recognised the 1004 ant+ stick but doesn't pick up the signal from the 1008 broadcasting from antifier on the raspberry pi (which isn't having the above err no 60 issue) Will get one or two newer ant+ sticks and see if I can at least get it working with my raspberry pi! |
Could you post the debug log with the 1008 stick? We could get the 1004
working if you fancy giving it a go
On Wed, 8 Nov 2017 18:08 JamesBudge, ***@***.***> wrote:
realise part of the problem (connecting to zwift) may be that my two ant+
dongles are not the same version one is 1008 one 1004. The 1004 version is
not recognised by antifier on either my mac or my raspberry pi
(understandable as you state that its only built for 1008 and 1009).
However zwift recognised the 1004 ant+ stick but doesn't pick up the
signal from the 1008 broadcasting from antifier on the raspberry pi (which
isn't having the above err no 60 issue)
Will get one or two newer ant+ sticks and see if I can at least get it
working with my raspberry pi!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AfAO_VxDZLoCCDNqWyTD_6DHUFCkhJAjks5s0e4qgaJpZM4QVWlh>
.
--
John Taylor
MA VetMB MRCVS
Director
Mansion Hill Veterinary Practice
133 Main Road,
Middleton Cheney
01295 712110
www.mansionhillvets.co.uk
|
Hello John, Thanks for your message. Here is the debug script using the 1008. for some reason it wouldn't let me use the out.log on the mac so have just copied the debug output from the terminal, hope thats ok! Happy to try and get the 1004 working too if they will speak to each other! Jamess-MacBook-Pro:~ James$ cd /users/james/antifier/ |
Thanks James- we now have the libusb backend working :) can you ensure the ANT+ dongle is installed as a libusb device? It seems libusb is having problems reading and writing to it. If you've used the dongle on the mac with another application a kernel device may be blocking it. Try If this doesn't work we can try writing to the dongle via the serial kernel extension rather than through libusb |
Hi James- I've added 1004 dongles into the device scan. This only applies to Windows/Mac. Can you redownload the ant.py script and try again? (once we've got libusb working) |
Hello John, Thanks you for both your above messages. I tried your recommend: But get back: When I go into this directory there is no SiLabsUSBDriver.kext. Sorry these are probably rather incompetent questions my limit in coding is the occasional line in R for work! |
I'm going to try to load OSX in VirtualBox and replicate! |
Thanks John! |
Hi
I get to the same error as above:
I have Adidas miCoach ANT+ USB dongle (don't have a 2nd ANT+ receiver yet).
|
Using python 2.7, any version of libusb should work but 1 is recommended |
I have connected Fortius with blue T1942 head unit but there is also problem with loading tacx firmware:
How .exe file should work on macOS or linux? Info about connected T1942 head unit:
|
Sorry guys not having a Mac or knowing much about them I can't help. Can I suggest a Raspberry Pi or even a Pi Zero as a low cost alternative until someone sorts Macs out? |
I managed to run antifier on macOS but need to test it. Line 61 in 6e9d26d
I have the same error on macOS. |
Hello John,
Tried to run it on my Mac, but running up against an issue.
Getting the following error message in the debug:
get ant stick
No backend available
No backend- check libusb
No backend available
No backend- check libusb
ANT Stick not found
any thoughts?
checked in system information and the ant stick is listed there. No instances of zwift or garmin etc running.
Thanks,
James
The text was updated successfully, but these errors were encountered: