WineHQ
Wine Forums

Board index » WineHQ » Wine Help




 Page 1 of 1 [ 14 posts ] 



 
Author Message
 Post Posted: Wed Mar 25, 2009 2:42 pm 
Offline
Level 1
Level 1

Joined: Fri Mar 20, 2009 3:44 pm
Posts: 7
Wine does great job for GUI on screen (PC Oscilloscope) But, can't USB connect to external hardware device that has FTDI 245AM chip in it. See device in /dev/ttyUSB0. See device in lsusb, also in lsmod. Did normal linking, ln -s /dev/ttyUSB0 ~ /.wine/dosdevices/com3. No luck. See the link with: ls -al dosdevices. Using COM3 because it's in Windows registry, for when the application comes up in Windows, it says USB Serial (COM3). This is the choice that works. Wish it would in Ubuntu. No choice comes up at all.
The application has one main .exe file. Other files are just graphics. I guess all of the I/O is in the .exe, just for Windows.
Any help?
Thanks, donde


Last edited by donde on Thu Mar 26, 2009 1:09 pm, edited 1 time in total.

Top 
 Post subject:
 Post Posted: Wed Mar 25, 2009 6:03 pm 
Offline
Level 1
Level 1

Joined: Sat Mar 14, 2009 11:59 am
Posts: 8
You might try doing a:

ln -s /dev/ttyUSB0 /dev/ttyS2

In this way, wine, acts as if a native port.

I hope to help you the answer.

Bye...


Top 
 Post subject:
 Post Posted: Wed Mar 25, 2009 7:18 pm 
Offline
Level 1
Level 1

Joined: Fri Mar 20, 2009 3:44 pm
Posts: 7
Ratax,
No that did not work. I think any link has to show up in .wine/dosdevices.

I've been at this for hours, and a medium newbie doesn't help.

thanks, donde


Top 
 Post subject:
 Post Posted: Thu Mar 26, 2009 10:38 pm 
Offline
Level 1
Level 1

Joined: Sat Mar 14, 2009 11:59 am
Posts: 8
jejeje ...

I would say I am not so novice. I had this same problem two years ago by trying to run a satellite communications program in linux for my work. After much testing and reading this was how they get it to work the software.

Anyway, I wish you luck and hope you do not have to keep looking for a lot...

Bye...


Top 
 Post subject: STILL CAN'T CONNECT
 Post Posted: Fri Mar 27, 2009 12:55 pm 
Offline
Level 1
Level 1

Joined: Fri Mar 20, 2009 3:44 pm
Posts: 7
Hey Guys and Gals !

I can't believe so many are having similar USB Serial Port problems with so little help that results in success. My device is called OPTAscope by Parallax, the maker of the famous STAMP products.They also have a very inexpensive, but great PC Oscilloscope. Of course it works in Windows. The GUI works fine with Wine, but no connect. Parallax has no intension of supporting Linux. The designer of the software has long since left the company. Parallax bought the rights from Optimum Design. They now call it Parallax Oscilloscope, but it's the same thing as the OPTAscope.

Hasn't anyone in this giant Wine community ever played with either of these scopes and got them working under Wine, preferably using Ubuntu 8.10? Or if you did and it was a lost cause, please let me know, and I'll give up and go back into the woodwork. Any pertinent comments would be appreciated.

donde




Top 
 Post subject:
 Post Posted: Fri Apr 03, 2009 2:57 pm 
Offline
Newbie
Newbie

Joined: Fri Apr 03, 2009 2:49 pm
Posts: 1
I have the a similar problem with a FTDI device (OBD II car scanner) on Ibex 8.10. Everything worked fine with WINE on Feisty Fawn.

First of all the VAGCOM software (free download if someone wants to reproduce) sort of works in that it will open the port send / receive data on the first command. However, after the first communication attempt, all subsequent operations in the program will fail (including the original working one). Closing/Reloading the program in WINE will still fail even on the first command that originally worked and the port becomes useless to WINE for any program.

HOWEVER, if you unload / reload the usbserial module (rmmod usbserial, then unplug - replug the device) you can get it back to the same "First Command Works" scenario. *Note: That reloading the ftdi doesnt solve the problem, only if you go further down the chain.

I would suspect at this point that it is not necessarily WINE that is causing this, but some regression problem in the Linux usbserial module in 8.10.


Top 
 Post subject:
 Post Posted: Tue Apr 07, 2009 12:55 pm 
Offline
Level 1
Level 1

Joined: Fri Mar 20, 2009 3:44 pm
Posts: 7
zonyl

The problem is also in 8.04.1. Don't have earlier versions up right now. Should I just download the VAGCOM software and let Wine execute it? And then put in the linking command
ln -s /dev/ttyUSB0 ~/.wine/dosdevices/com3 Bring up the oscilloscope program.

And see what happens?

Thanks...donde


Top 
 Post subject:
 Post Posted: Sun May 03, 2009 5:12 am 
Offline
Level 1
Level 1

Joined: Sun May 03, 2009 4:15 am
Posts: 8
Location: UK
I have a similar problem with a real serial port with ubuntu 9.04, so I suspect it's not a FTDI problem - besides the USB>serial translation itself is done in the host system not in wine.

Connecting to another computer I have no problems sending data back and forth via gtkterm or cutecom in any linux distro.

I've tried several serial port readers in wine and they all suffer the same problem. They send data fine but can't reliably receive it. As you say, the very first receive seems fine but then characters get lost from the begining of a line, then it gets progressively worse :(

I have 3 programs that are windows only and use the serial port so I would dearly love to be able to junk my windows partition!


Top 
 Post subject:
 Post Posted: Mon May 04, 2009 9:45 am 
Offline
Newbie
Newbie

Joined: Mon May 04, 2009 9:29 am
Posts: 1
I have been pursuing this for 2 days, and your post might help. Amazing you posted so recently.
I was just about to post in the forums, and I had just emailed an apparent successful user in the appdb.
I may just need help with pointing to my ports, as you have been showing above.
I have a USB astronomy imager, SBIG st-2000xcm, works in XP.
When done installing app and app driver finder from SBIG (Ccdops) all installs but when plugging in the camera nothing happens.

I came to winehq here because someone says it is platinum running in wine on Ubuntu.
I started out with my main system and PCLinuxOS 2009 and the exact symptoms.

Maybe I am very close, could one of you tell me how to point my WINE entity to my USB port? Now I know you are talking usb/rs232, but maybe the other guy can point me in right direction. Here is my lsusb: I am only lightly familiar with linux code details, but no longer a noob.
$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 004: ID 0d97:0001 Santa Barbara Instrument Group SBIG Astronomy Camera (without firmware)
Bus 002 Device 003: ID 046d:c512 Logitech, Inc. LX-700 Cordless Desktop Receiver
Bus 002 Device 002: ID 124b:4d01 Nyko (Honey Bee) Airflo EX Joystick
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Maybe a kernel thing? I haven't tried an older kernel yet on my pclos. I installed the latest Ubuntu to pursue this.

I also have plenty of boxes to play with.


P.S. I have orig STAMP, and always wanted a PC scope to replace my bulky Tektronix, how is it?


Top 
 Post subject: I've got it working
 Post Posted: Fri Oct 09, 2009 11:28 pm 
Offline
Newbie
Newbie

Joined: Fri Oct 09, 2009 8:47 pm
Posts: 1
:D
I have the Parallax USB Oscilloscope working in Debian Lenny/Linux 2.6.26-2-686,
WINE version: wine-1.0.1-174-gc4039bd
:D

I didn't have to do any compiling or anything like that, I'm simply using the version
of WINE that comes from the Debian repository with apt-get. I think it'll probably
work on Ubuntu too.

Ratax's suggestion is part of the solution. I think someone owes him an apology.
Some entries have to be added to the registry as well.

Sometimes the program is very slow if you start it with the scope plugged in.
Starting the program before plugging in seems to fix this problem.

I've posted a thorough how to on my blog.
http://jethomson.wordpress.com/2009/10/ ... e-in-wine/


Top 
 Post subject:
 Post Posted: Sat Oct 10, 2009 5:12 am 
Offline
Newbie
Newbie

Joined: Sat Oct 10, 2009 5:10 am
Posts: 1
Try to add or remove hardware option in your control panel.


Top 
 Post Posted: Sat Oct 10, 2009 6:59 am 
 
yardleydobon wrote:
Quote:
I've posted a thorough how to on my blog.
http://jethomson.wordpress.com/2009/10/ ... e-in-wine/


Please update the Applications Database as well.

James McKenzie


Top 
 Post subject:
 Post Posted: Sun Oct 11, 2009 5:46 am 
Offline
Level 1
Level 1

Joined: Sat May 31, 2008 5:07 am
Posts: 9
It didnt work in my case. The problem is one of my programs requires CTS/DSR lines to be set in HIGH state, if they are in low it just refuses to read the data on the port. AFAIK this is the requirement of the com-port specs.


Top 
 Post subject: All OK Here Now
 Post Posted: Sun Oct 11, 2009 5:37 pm 
Offline
Level 1
Level 1

Joined: Sun May 03, 2009 4:15 am
Posts: 8
Location: UK
Just want to say that with wine 1.1.28 I have no problems either with real serial ports or USB ones. Mind you all of my programs only need Tx & Rx.

One problem that was leading me astray was that one of the bits of hardware had a crap faked Tx -ve which used a diode. This had a dry joint and the high resistance meant that it took several pulses to build up sufficient voltage :(


Top 
Display posts from previous:  Sort by  
 
 Page 1 of 1 [ 14 posts ] 




Board index » WineHQ » Wine Help


Who is online

Users browsing this forum: No registered users and 4 guests

 
 

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to: