Hi Bullshark,
Thanks for the tips, but I guess I did not make myself clear. Please
see inline below.
> >However, the MA-620 does not work *at all* with SmartTrak and my
> >SmartCom. (No connection is establshed, but SmartTrak does seem to
> >know that an IRDA device is present.)
When it can't find an IrDA device, it reports just that. When it finds
a IrDA device but then can't connect to a Smart DC, it reports a
different error, the error I am getting now.
> That statement contradicts itself. Why/what does Smartrak seem to know?
>
> >Any tips for me?
>
> Put the Smart device *very* close to the Irda device.
> McAffee AV is a known show-stopper. You won't connect if it's loaded.
I don't have McAffee and I put the device within a millimeter of the
SmartCom (as well as slightly further away).
> >I am running Windows 2000 and I am using the MA-620 drivers from the
> >Uwatec CD.
>
> Why on earth would you use Uwatec supplied driver? Throw it away immediately.
> Go to the Mirror, look at yourself scornfully, and ask "What was I thinking"?
The MA-620 is the device that Uwatec itself re-sells for the
communicating with the Smart DCs. I used the Mobile Action-branded
MA-620 driver on the Uwatec SmartTrak CD for W2K.
The MA-620 is listed as a "known good" IrDA device on the Uwatec
website. http://www.uwatec.com/english/SCIDL.htm) The Uwatec install
disk actually contains the Mobile Action MA-620 driver installation
program.
> Did you install the MA-620 software as it came from the MAKER?
Yes.
> Does the device show up in the Win2K device list and is it free of problems?
Yes.
> I don't know the MA-620. I'm not sure it's agood choice. They specialize in Cell phone connectivity.
> Their software download page doesn't even offer drivers.
Well, they *offer* drivers but they are failing to download at the
moment (http://www.mobileaction.com.tw/English/dls-ir-USA.htm)
Mark
> I use a BAFO BF-120 http://www.bafo.com/bafo/productslists.asp?foproduct_id=844
> On XP or Win2K, I need no drivers. I just plug it in and the system automagically recognizes it.
[quoted text clipped - 4 lines]
>
> bullshark
bullshark - 28 Oct 2004 03:06 GMT
>When it can't find an IrDA device, it reports just that. When it finds
>a IrDA device but then can't connect to a Smart DC, it reports a
>different error, the error I am getting now.
I have Smart DCs and I still don 't know your error.
Smart trak pretty much behaves the same way for me all the time
when it fails to connect.
The IrDa adapter is the one looking for IrDa devices, not smarttrak.
At least it does if it's worth a crap (more later).
>> Put the Smart device *very* close to the Irda device.
>I don't have McAffee and I put the device within a millimeter of the
>SmartCom (as well as slightly further away).
That's probably close enough. (c: 20-100 works for me.
>The MA-620 is the device that Uwatec itself re-sells for the
>communicating with the Smart DCs. I used the Mobile Action-branded
>MA-620 driver on the Uwatec SmartTrak CD for W2K.
I would re-iterate my prior remark, but your experience with Uwatec is probably not
sufficient. It's typical bone-head swiss-made bullshit. You see, IrDA is a very specific
protocol. If a device says IrDA, then it works. I don't know what qualifies a device
listed on their page, but know it hasn't changed in over a year even though they
have specific knowledge of many other devices that do work. The "swiss-made" part
is that they make half-assed client, and then make their web page sound like IrDA is
flaky....not so.
>The MA-620 is listed as a "known good" IrDA device on the Uwatec
>website. http://www.uwatec.com/english/SCIDL.htm) The Uwatec install
>disk actually contains the Mobile Action MA-620 driver installation
>program.
That really floors me. A) "Known good" - it obviously isn't. B) Uwatec
says "flawless" and is evidently a reseller. C) My device required no drivers.
Just plug it in and it works. It adds a little icon to the tray that lets you do
stuff, and disappears when you unplug it. It's totally seamless.
>Well, they *offer* drivers but they are failing to download at the
>moment (http://www.mobileaction.com.tw/English/dls-ir-USA.htm)
I didn't find that page for some reason. Anyway, good luck. We've covered the
basics, except for a few more things
1) If you have a Palm, you should be able to initiate a file transfer. I don't know
how yours works, but all I have to do is bring mine near and I can beam files
to my PC or vice versa. I can also hotsync by IR
2) Do you know that your USB port works? Do you have another device to try?
(I take it that you used your Irda adapter and cable on someone elses machine
so you know they work ok)
3) make sure the Smart DC is on.
safe diving,
bullshark
Floyd - 28 Oct 2004 17:08 GMT
bullshark <bullshark@gmail.com> wrote
<snip/>
...
> I didn't find that page for some reason. Anyway, good luck. We've covered the
> basics, except for a few more things
>
> 1) If you have a Palm, you should be able to initiate a file transfer. I don't know
> how yours works, but all I have to do is bring mine near and I can beam files
> to my PC or vice versa. I can also hotsync by IR
I have no Palm, but it works with my cell phone.
> 2) Do you know that your USB port works? Do you have another device to try?
> (I take it that you used your Irda adapter and cable on someone elses machine
> so you know they work ok)
Yes, it works with my USB drives, mice, card readers, etc. It even
works with the MA-620 when connecting with a cell phone.
> 3) make sure the Smart DC is on.
Check.
Thanks for your continued assistance,
Mark
> safe diving,
>
> bullshark
bdurrett - 29 Oct 2004 12:28 GMT
Floyd,
I don't know if this applies to you but....
FWIW, when I set up an IrDA port on my PC, there were 2 different types
of IrDA "modes" or formats that I could chose from. One wiorked with my
laptop, one didn't. I have forgotten which was which, having gone the
way of WiFi but this might be what is eating your lunch and why it works
with the Cell Phone but not the Dive Computer and has to do with the
buffering of the data as it is passed. Might be worth checking out in
the "Device Properties" of the Control Panel (or whatever passes for
such - on SuSE Linux it was the "Hardware Configuration")
To me, it almost sounds as if you have some difficulties at a lower
level than the IrDA, COM port translation perhaps. Take a look that the
Dice Comp is not expecting some esoteric COM config like 7-bit even
parity or some such nonsense.
I am a telecomm Network person by degree and trade so lots of these
things look like potential protocol issues to me.... :D
Bret
--
bdurrett - Colorado Transplant
Bret Durrett
Frankfurt am Main, Germany
:wave
"Diving - The closest thing to outer space - and it won't cost you $20
million!"
Floyd - 30 Oct 2004 22:59 GMT
Thanks for the tip, Bret.
The only parameter I can modify is "Maximum Connection Speed" and I
have tried all selectable speeds with no luck.
Mark/Floyd
> Floyd,
>
[quoted text clipped - 29 lines]
> "Diving - The closest thing to outer space - and it won't cost you $20
> million!"