joeylamb / opentx

Automatically exported from code.google.com/p/opentx
0 stars 0 forks source link

Companion9X (Mac) connectivity to Taranis #198

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Which board (stock / gruvin9x / sky9x / Taranis) are you using? Taranis

What is your openTx FW version? x9d-v1.1.02

What is your openTx EEPROM version? 215

I'm using Companion9X Version 1.51 (revision 2321), Oct 31 2013

What steps will reproduce the problem?
1. Plug the usb connector between my iMac (Mavericks) and the Taranis
2. Wait for "Hard Disks" to mount on Mac desktop - will take about a minute <= 
the problem
3. On ejecting the disks, they immediately are remounted. <= the 2nd problem

Additional information:  The provided driver suggestion of AVRDUDE wouldn't 
allow a connection.

Finally I loaded and linked to: /opt/local/bin/dfu-util where I now operate 
with the above problems
The actual load was: dfu-util-0.7.mpkg

A 2nd problem I'm having may be related.  I'm unable to save the file that I'm 
working on using "Save As."  The error displayed is "Error Writing File xxxxxx: 
Unknown format."  I am able to write the EEPROM to the transmitter, saving an 
"Eprom Backup" successfully.  I use this backup as the start for my continued 
work in Companion9X.

Original issue reported on code.google.com by MonteFri...@gmail.com on 17 Dec 2013 at 5:10

GoogleCodeExporter commented 8 years ago
I really think that you have selected a wrong firmware family in ccompanion9x 
preferences. it should be "opentx for taranis"
The only part of the issue that is a real issue is the 2nd problem
as it happens not only to you and is an already open issue..

Original comment by romolo.m...@gmail.com on 18 Dec 2013 at 7:17

GoogleCodeExporter commented 8 years ago
Thanks for the quick answer Romolo.  But, I do have "opentx for FrSky Taranis" 
selected and have had since I started.  So, I'm still confused.

Do you have any other ideas?

Original comment by MonteFri...@gmail.com on 18 Dec 2013 at 3:08

GoogleCodeExporter commented 8 years ago
Hi, re the second problem.. when doing a save as you need to add '.eepe' to the 
file name.  If it's a new file the Companion software does this automatically 
from the save command.

Original comment by gprince...@gmail.com on 29 Dec 2013 at 2:45

GoogleCodeExporter commented 8 years ago
Also, I've found that on a Mac, if you eject the volumes using Disk Utility, 
you have just enough time to remove the USB cable before they remount and you 
don't get the error message.

Original comment by gprince...@gmail.com on 30 Dec 2013 at 4:17

GoogleCodeExporter commented 8 years ago
Thanks for the "add .eepe suffix" suggestion.  It works, although still appears 
to the mac as a PC file.  This is easy to correct so I'm off and running with 
this issue.

Still would like to know why Mavericks takes so long to mount the disk images 
the first time.

Original comment by MonteFri...@gmail.com on 3 Jan 2014 at 4:43

GoogleCodeExporter commented 8 years ago
My drives mount in < 5sec on Mavericks. 
The only real problem is why they remount upon ejection, so I'm setting this as 
a duplicate of the existing relevant issue.

Original comment by bernet.a...@gmail.com on 4 Jan 2014 at 6:45

GoogleCodeExporter commented 8 years ago
I wish you wouldn't close this issue as the Mac I'm using is a brand new iMac 
with the latest Mavericks loaded.  It is obviously 100% repeatable and the fact 
that a few others, or one, don't see the problem isn't necessarily indicative 
of "no problem."  There are only the normal printer drivers and companion9X 
loaded.  I'd be more than happy to work with the programmers if that would 
help.  I'm an experienced Mac user so might be able to offer help, if needed.

Original comment by MonteFri...@gmail.com on 5 Jan 2014 at 12:06

GoogleCodeExporter commented 8 years ago
I had the problem of the Taranis drives re-mounting. The issue seemed to be a 
Mac problem. When I upgraded to Yosemite it went way. 
The other issue .eepe extension works but its weird.
PS If you upgrade to Yosemite you will need more RAM. 4GB is only enough to 
boot and no more.
Thanks for the help:)

Original comment by dave.bi...@gmail.com on 26 Feb 2015 at 11:36