Can you tell me, before I spend money, if this will work?
I have a MacBook Pro running 10.9.1 and a Scubapro Galileo Luna, The infrared port I use is the Sitecom USB IRDA CN-100v2.
I'm not able to communicate withe the Luna using the J-trac software. In the system preferences, under security and privacy> advanced, there is no possibility to turn on, or off any IR port.
Btw under Windows and Parallels, using the same IRDA dongle on an Imac it used to work..
The downloading is only possible with the Dt version, correct?
Please advise
Hans
MacBookPro Retina-Uwatec-IRDA
Re: MacBookPro Retina-Uwatec-IRDA
Hi Hans,
You are correct that direct downloading of dive computers is only supported in Dive Log DT or the licensed version of Dive Log Manager from our website. The free version of Dive Log Manager can import from various file formats but does not support direct device communication.
Dive Log DT and the licensed version of Dive Log Manager are designed to work with the "official" ScubaPro IRA adaptor. They will also work with other 3rd party adaptors that use the same chipset(s) as the official ScubaPro adaptors and advertise themselves to the system in the same way. In order to know if a given adaptor *might* work you need to check the USB VendorID and ProductID that the device advertises to the system. You can do this by plugging your IrDA adaptor into the Mac and selecting "About this Mac..." from the "Apple" menu and then clicking on the "More Info ..." button and then clicking on the "System Report ..." button in the window that appears. Finally, you'll select "USB" in the sidebar of the System Report window and then click on the IrDA USB device in the top right pane. The lower right pane will list the VendorID and ProductID for your device. They need to be one of:
VendorID: 0x066f
ProductID: 0x4210
or
VendorID:0x9710
ProductID:0x7780
in order for Dive Log DT/Dive Log Manager to be able to work with the device. There is no guarantee that it will work as we have not had the ability to test with all the possible devices out there, but if the above information is not the same there is no chance that it will work.
Applications sold through the Mac App Store are not allowed to depend on the need to install drivers in order to work. Therefore, Dive Log DT has the device support built right in to the application (much like J-Trac does) and can only work with devices that it knows about internally. On Windows you usually install a driver for each device that you use but many adaptor vendors do not supply device drivers for the Mac. This is another reason that Dive Log DT has the support for a select set of adaptors built in. So the fact that this adaptor works under Windows makes sense and suggests that the device is working properly. The fact that it doesn't work with J-Trac suggests that it uses a different chipset than the official ScubaPro adaptor and will therefore likely not work with Dive Log DT either. That said, you should check the Vendor and Product ID to see as Dive Log DT may support more devices than J-Trac (I don't think J-Trac has been updated in a while).
If you have any additional questions or need more information please feel free to contact us directly. I'd suggest writing to our support email address (support 'at' moremobilesoftware 'dot' com ... replacing the 'at' with @, the 'dot' with . and removing the spaces) as that might be a bit easier.
Cheers,
Greg
You are correct that direct downloading of dive computers is only supported in Dive Log DT or the licensed version of Dive Log Manager from our website. The free version of Dive Log Manager can import from various file formats but does not support direct device communication.
Dive Log DT and the licensed version of Dive Log Manager are designed to work with the "official" ScubaPro IRA adaptor. They will also work with other 3rd party adaptors that use the same chipset(s) as the official ScubaPro adaptors and advertise themselves to the system in the same way. In order to know if a given adaptor *might* work you need to check the USB VendorID and ProductID that the device advertises to the system. You can do this by plugging your IrDA adaptor into the Mac and selecting "About this Mac..." from the "Apple" menu and then clicking on the "More Info ..." button and then clicking on the "System Report ..." button in the window that appears. Finally, you'll select "USB" in the sidebar of the System Report window and then click on the IrDA USB device in the top right pane. The lower right pane will list the VendorID and ProductID for your device. They need to be one of:
VendorID: 0x066f
ProductID: 0x4210
or
VendorID:0x9710
ProductID:0x7780
in order for Dive Log DT/Dive Log Manager to be able to work with the device. There is no guarantee that it will work as we have not had the ability to test with all the possible devices out there, but if the above information is not the same there is no chance that it will work.
Applications sold through the Mac App Store are not allowed to depend on the need to install drivers in order to work. Therefore, Dive Log DT has the device support built right in to the application (much like J-Trac does) and can only work with devices that it knows about internally. On Windows you usually install a driver for each device that you use but many adaptor vendors do not supply device drivers for the Mac. This is another reason that Dive Log DT has the support for a select set of adaptors built in. So the fact that this adaptor works under Windows makes sense and suggests that the device is working properly. The fact that it doesn't work with J-Trac suggests that it uses a different chipset than the official ScubaPro adaptor and will therefore likely not work with Dive Log DT either. That said, you should check the Vendor and Product ID to see as Dive Log DT may support more devices than J-Trac (I don't think J-Trac has been updated in a while).
If you have any additional questions or need more information please feel free to contact us directly. I'd suggest writing to our support email address (support 'at' moremobilesoftware 'dot' com ... replacing the 'at' with @, the 'dot' with . and removing the spaces) as that might be a bit easier.
Cheers,
Greg