direct import form dive computer

[Alessandro Volpi]

Dear Willem,

I am pretty sure that the MCS7780 (the standard UWATEC IR adapter) is a FIR
device.

lsusb lists the device as : Bus 001 Device 008: ID 9710:7780 MosChip
Semiconductor MCS7780 4Mbps Fast IrDA Adapter

The content of file /proc/sys/net/irda/max_baud_rate is "16000000" . A 16 M
baud rate cannot be reached by anything else than a FIR device.

The WXP Virtual machine also lists the MCS7780 as a FIR device.

Moreover the IR interface works perfectly with the FAST Galileo and does
not work with the slower SmartTec.

What I am saying in this message is referred to the Ubuntu trusty system,
since I am not able to get a working IR interface in Ubuntu xenial and
Fedora 24.

More details about the irda issue can be found in a  post of mine in the
subsurface mailing list on Febrary 18th  2017. Linus Torvalds has replied
to my post on  February 19 and I have understood he is not very optimistic
about the chance of being able to work with the UWATEC IR with linux in the
future ...

Very best regards.

Alessandro


On Mon, Mar 13, 2017 at 10:52 AM, Willem Ferguson <
willemferguson at zoology.up.ac.za> wrote:

> From phone. Alessandro,  you need to know whether the Smartek does only
> serial infrared (SIR) or fast infrared (FIR). Then you need to understand
> whether your Linux driver does any or both of these speeds. Maybe it is a
> speed issue? If I remember correctly, the Linux driver I use allows speed
> selection. The Galileo also has a menu setting to choose between slow and
> fast infrared. Does the Smartek have anything similar?
> Kind regards, Willem.
>
> On 13 Mar 2017 12:15, "Jef Driesen" <jef at libdivecomputer.org> wrote:
>
> On 2017-03-12 18:52, Alessandro Volpi wrote:
>
>> I apologize for not having actually loaded the
>> subdirectory galileo_trimix_import on my Dropbox folder. The Galileo data
>> download was executed on a laptop computer. The Ubuntu trusty system is
>> not
>> set up so that it automatically starts the Dropbox sync operation, as
>> usual
>> for laptops, which may not be always connected to Internet. I just forgot
>> to manually start the Dropbox sync, after having created the mentioned
>> directory. If you open my Dropbox folder right now you are going to find
>> it
>> as expected.
>>
>> In the same folder you will also find the subdirectory Smarttec_import ,
>> with the log file.
>>
>
> No problem. I have them now.
>
>
> I have not hitherto considered the chance of installing the Windows version
>> of subsurface on the WXP VM .  I thought it might have been be a good
>> suggestion, just in order to try to get the memory dump. It is  a bit
>> funny, since I have begun to look for linux dive log software mainly in
>> order to get rid of the WXP virtual machine ...
>>
>> I have also tried this possible solution. Subsurface seems to be
>> flawlessly
>> installed, but it does not work. As I try to launch it I only get an error
>> pop-up saying : "The procedure entry-point qsort_s could not be located in
>> the dynamic link library msvcrt.dll" .  This is not surprising since, in
>> the subsurface web site, WXP is not mentioned in the list of the
>> subsurface
>> supported Microsoft operating systems.
>>
>
> That's probably a subsurface issue on Windows XP. As a workaround, you can
> download the memory dump using libdivecomputer's command-line tool. You can
> get it here:
>
> http://libdivecomputer.org/builds/stable/windows/dctool.exe
>
> Execute with these options:
>
> dctool.exe -v -l smart.log -f smart dump -o smart.bin
>
>
> What I would like to confirm with this test is very simple: Since you are
> able to download your smarttec with smarttrak, we know that IrDA is working
> fine on this system. That allows us to check whether the problem is
> located. If downloading with libdivecomputer works on this system, then the
> failure on linux is an IrDA related issue, if it fails then it's in
> libdivecomputer.
>
>
> As far as the reasons for not being able to connect the SmartTec to the
>> linux ( Ubuntu trusty ) IR interface, I think it may be related to the
>> fact
>> that, even with the SmartTrak program running on the WXP VM, the SmartTec
>> takes much more time than the Galileo for the download, in spite of the
>> fact that the amount of data sent by the former is much smaller than that
>> sent by the latter. This means that the transmission data rate of the
>> SmartTec is much lower.
>>
>
> For the smarttec, we don't even get a chance to download any data. The
> IrDA device was discovered successfully, but connecting to the device
> failed:
>
> INFO: Discover: address=f0e03201, name=Aladin Smart Tec, charset=00,
> hints=8000
> INFO: Connect: address=f0e03201, lsap=1
> ERROR: Connection reset by peer (104) [in irda.c:369
> (dc_irda_connect_lsap)]
> ERROR: Failed to connect the device. [in uwatec_smart.c:188
> (uwatec_smart_device_open)]
>
> This might indeed indicate a problem with the IrDA.
>
>
> Jef
> _______________________________________________
> subsurface mailing list
> subsurface at subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.subsurface-divelog.org/pipermail/subsurface/attachments/20170313/355c0484/attachment-0001.html>