Startseite › Forums › English › BT747 Installation

Cannot connect to device. Linux, Holux gpsport 245

Bild von lockywolf
Mo, 05/16/2011 - 21:18 – lockywolf

I have the latest software version, the device is recognized by the kernel(and works with gpsd).

 

The user is in dialout group.

But when i try to use BT747, (run, type /dev/ttyUSB0, connect) - connection fails and the following lines are printed in console:

 

gnu.io.NoSuchPortException
    at gnu.io.CommPortIdentifier.getPortIdentifier(CommPortIdentifier.java:218)
    at gps.connection.GPSRxTxPort.openPort(Unknown Source)
    at gps.connection.GPSrxtx.myOpenPort(Unknown Source)
    at gps.connection.GPSrxtx.setUSBAndOpen(Unknown Source)
    at bt747.model.Controller.setUsb(Unknown Source)
    at bt747.j2se_view.BT747Main.access$300(Unknown Source)
    at bt747.j2se_view.BT747Main$7.actionPerformed(Unknown Source)
    at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
    at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
    at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
    at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
    at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
    at java.awt.Component.processMouseEvent(Unknown Source)
    at javax.swing.JComponent.processMouseEvent(Unknown Source)
    at java.awt.Component.processEvent(Unknown Source)
    at java.awt.Container.processEvent(Unknown Source)
    at java.awt.Component.dispatchEventImpl(Unknown Source)
    at java.awt.Container.dispatchEventImpl(Unknown Source)
    at java.awt.Component.dispatchEvent(Unknown Source)
    at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
    at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
    at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
    at java.awt.Container.dispatchEventImpl(Unknown Source)
    at java.awt.Window.dispatchEventImpl(Unknown Source)
    at java.awt.Component.dispatchEvent(Unknown Source)
    at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
    at java.awt.EventQueue.access$000(Unknown Source)
    at java.awt.EventQueue$1.run(Unknown Source)
    at java.awt.EventQueue$1.run(Unknown Source)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown Source)
    at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown Source)
    at java.awt.EventQueue$2.run(Unknown Source)
    at java.awt.EventQueue$2.run(Unknown Source)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown Source)
    at java.awt.EventQueue.dispatchEvent(Unknown Source)
    at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
    at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
    at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
    at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
    at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
    at java.awt.EventDispatchThread.run(Unknown Source)
136862 -
Listing known ports:

‹ net.sourceforge.jnlp.LaunchException: Fatal: Application Error: Unknown Main-Class. Could not determine the main class for this Cannot connect iBlue 747A ›
Mo, 05/16/2011 - 21:30 – mdeweerd
Bild von mdeweerd

Hi The known ports list is

Hi

The known ports list is apparently empty.

'gpsd' and 'BT747' are not very compatible as 'gpsd' occupies the port.

Still, I would expect BT747 to 'see' the port.  If the device is connected, that should happen.

If you activate the debug function, the port name gets printed in the info window.

Mi, 05/18/2011 - 07:51 – lockywolf
Bild von lockywolf

Well, i turned on the debug -

Well, i turned on the debug - and the error output is slightli changed.

http://pastebin.com/YnJqiRX3

 

And if I type USB instead of /dev/ttyUSB0, i receive the following:

http://pastebin.com/LeRdpYLf

Mi, 05/18/2011 - 08:19 – mdeweerd
Bild von mdeweerd

Ok, what I suggest to do next

Ok, what I suggest to do next is the following:

Without the device connected:

In a terminal:

ls -r /dev  > ref1

With the device connected:

ls -r /dev > ref2

Find the difference(s) between ref1 and ref2 => that is your portname.

Enter that port name as the port.

Connect.

 

Report back here - I'll see what I can do to set that port as a known port.

 

[An alternative to the terminal is to open an explorer and check visually]

Mi, 05/18/2011 - 21:41 – lockywolf
Bild von lockywolf

The problem magically

The problem magically disappeared. I really don't understand, but now the program sees the tracker.

I still cannot download tracks, but I suspect, it's my fault.

Mi, 05/18/2011 - 22:06 – mdeweerd
Bild von mdeweerd

Make sure that you set the

Make sure that you set the right speed too (could be 38400 as with quite a few holux devices).

Sa, 05/12/2012 - 19:44 – Shura (nicht überprüft)

Please help, I have the same

Please help, I have the same issue:

http://pastebin.com/Ci7raJyU