OK,

If blue LED on BTLink keeps blinking then it is not pairing with your laptop's BT device.

You say Windows reports that BT device in your Ausus is configured to COM 3 and COM 4? Is that correct?

Is the BT device built-in on your laptop or are you using a USB adapter?

Is there some sort of Bluetooth software installed that you can run and set various configurations?

IS BT turned on on the laptop?

If so it may be incompatible. Can you tel me if there is some third party BT software on the laptop? I could not get the BlueSoleil BT software that came with my Bluenext USB BT adapater to work but it worked fine with XP standard driver on XP, and with Widcomm driver on Windwos 2000.

The standard Bluetooth drivers built-in to XP work OK but some third party BT software doesn't seem to.

Perhaps you can post a screen shot of the Control Panel/ System/Hardware/Device Manager showing BT Radios and COM port devices and their properties and drivers?

See screen shots from my XP system with Bluenext USB BT adapter - below.

If you are using the XP standard driver then I think the connection in Papywizard should be set as Bluetooth, If some third partry driver then it MAY need to be configured as Serial and you can enter 'COM3' or 'COM4' or whatever virtual COM port is assigned to the serial profiile of the BT device.

I'm sure we'll soon be able to find some combination of driver and settings that works.

OK,

I have re-read your original post.

It seems that your Asus EEE does not have BT device built-in and you are using a USB BT adapter.

Is it any particular identifiable brand and model?

When you adde the USB BT adapeter did you install any software that came with it? If so what was that software's name/brand?

I got Blue Soleil software with my USB Bluenext BN-01 BT adapter and it would not work with Papywizard on either Windows XP or Windows 2000.

On my XP desktop I uninstalled the Blue Soleil software then plugged in the USB BT adapter and let the system install standard XP BT drivers and then it worked OK; set a Bluetooth connection in Papywizard/Configure/Hardware then select Choose and let Papywizard find the BTLink adapter and select it.

Then in main screen of Papwizard select Hardware/Connect.

There is no need to use the BT Add Device process. If you do use this it will set up the connection to the BTLink as two virtual COM ports - COM4 and COM5.

In this case you can either remove this device and proceed as before, or leave it and proceed as before, or instead set a serial connection in Papywizard/Hardware/Configure on COM4 - at least it works this way on my XP system, then Hardware/Connect.

..................

With my old laptop running Windows 2000 (Windows 2000 lacks built-in support for BT) I used the Widcomm BT drivers that you can find here:
http://www.lm-technologies.com/ci/index … details/42

Many USB BT adapters use the same BT chipset so this driver softare may well work for yours. The Widcomm driver sets up a virtual serial port for serial profile of BT and then you choose a Serial connection in Papywizard with appropriate virtual COMX address reported by Widcomm software when configuring the virtual serial port.
..................

I would suggest you try and use the simple XP built-in BT driver if possible rather than the Widcomm driver software as Papywizard doesn't need all the features that the Widcomm software offers.

Screenshots below show my XP (with SP3) setup with USB BT adapter (Bluenext Bn-01 - http://www.bluenext.co.uk/bluetooth-ada … ongle.html) using standard XP built-in BT drivers having used the Add Device process (which is not necessary, use Hardware/Bluetooth if you haven't done the Add device thing) . With Papywizard 1.5.5-1 I can connect to Merlin with Papywizard/Configure/Hardware configured either as Bluetooth or as Serial on COM4.

Last edited by mediavets (2008-12-30 12:45:03)

So do you have it working yet?

If not and you are using a USB BT adapter my suggestions are:

1. Check - via Control Panel/Add-remove programs - if you have third party BT software installed and if you do uninstall it.
2. Power down the PC and remove USB BT adapter if currently plugged in, then power up again and when XP has loaded plug in the USB BT adapter.
3. XP should detect it and install default XP BT drivers.
4. Then run Papywizard and use Configure/Hardware to select Bluetooth setting for the connection and use Choose button to let it search for the BTLink on the Merlin (I'm assuming this is powered up at this point - blue LED blinking).
5. If it sees the BTLink (you named it 'merlin' I believe) then choose that - it may prompt at some point for a pass key - that will be '1234' unless you changed the default when programming the baud rate on the BTLink adapter.
6. Close Configure.
7. In main Papywizard screen select Hardware/Connect and see if it will connect to the Merlin.

If you run into problems at any stage of this process take screenshots and post here.

Last edited by mediavets (2008-12-31 00:53:58)

did you try it with the handcontroller connected too?

I have a very strange effect here:

with a short cable between Merlins connector plug and my BT it behaves as you describe unless I start with the handcontroller connected - then it works

with a long cable between Merlins connector plug and my BT everything works - without the handcontroller

irpano wrote:

Hi andrew,
Sorry I cant get the screen dump to work on the Asus computer so I answer in text.

To answer the questions you posed;

"have re-read your original post.
It seems that your Asus EEE does not have BT device built-in and you are using a USB BT adapter"
-- correct I have a bluetooth USB  plugged into the port and I did not install the software that came with it.(Bluesoleil)
     The device is working correctly as I can use it to communicate with my Tungsten Palm

---- I have reinstall Papywizard and made sure my computer reflects what your screen dumps display
        Set ups like this  Configure>Bluetooth> choose ---- Connection to Merlin @ 00:12:6f:02:21:60 OK

       Then in papywizard  Hardware > connect
      After a few seconds the blue light on tronisoft stops blinking and glows solid

Then an error message - "CANT CONNECT TO HARDWARE - Axis cant send command"
This in without the autoconnect box checked.  If i check the autoconnect box The blue light glows fully but the Please wait window stays on constantly and the only way to stop it is to CTRL-ALT DEL the pc

At least I now get the two BT devices reacting to one another

OK - the error message suggests very much that the baud rate is not set correctly on the BTLink RS232-BT adapter.

Please go through the programming process again and send me a screenshot.

I also want to see a screen shot of how your BT device look in Control Panel/Hardware/Device Manager

To get a screenshot use Shift-PrintScreen which places screenshot on the clipboard then paste into an image editor and save.

Or get hold of a screenshot program such as Ultrasnap:
http://www.mediachance.com/ultrasnap/index.html

You should have a BT icon in the bottom right of Windows XP screen.
Right click on it and Open Bluetooth settings and then post screen shots from each of the tabs of the window - mine are shown below.

IF your Bluetooth COM port settings look like mine then Configure/Hardware in Papywizard to a serial connection on COM4 as shown in my last screenshot and then try again to connect - it it fails then post screenshots of the error message and also post the output from the log file (use the CODE tag and post log file output between the tags).

Last edited by mediavets (2008-12-31 09:51:13)

Hi IRPANO,

For your information, hereafter an exemple of the Log you should get when connection with BT goes 100 % OK 

2008-12-31 12:34:14,651::MainThread::DEBUG::Papywizard.l10n(): default locale=fr_BE
2008-12-31 12:34:14,651::MainThread::DEBUG::Papywizard.l10n(): LANGUAGE=None
2008-12-31 12:34:14,651::MainThread::DEBUG::Papywizard.l10n(): langs=['fr_BE', 'en_US', 'fr_FR', 'pl_PL', 'de_DE']
2008-12-31 12:34:14,651::MainThread::DEBUG::Papywizard.l10n(): localeDir=C:\Program Files\Papywizard\share\locale
2008-12-31 12:34:14,664::MainThread::INFO::Starting Papywizard...
2008-12-31 12:34:14,664::MainThread::INFO::Loading default presets
2008-12-31 12:34:14,677::MainThread::DEBUG::Preset.__init__(): loading name='4@0 + Z + N'
2008-12-31 12:34:14,677::MainThread::DEBUG::Preset.__init__(): loading name='3@-15 + Z'
2008-12-31 12:34:14,677::MainThread::DEBUG::Preset.__init__(): loading name='6@30 + 6@-15 + N'
2008-12-31 12:34:14,677::MainThread::DEBUG::Preset.__init__(): loading name='3 + 6 + 12 + 6 + 3 (28mm)'
2008-12-31 12:34:14,677::MainThread::DEBUG::Preset.__init__(): loading name='10 mm 40D ( N + 2 rows + Z )'
2008-12-31 12:34:14,678::MainThread::DEBUG::Preset.__init__(): loading name='10 mm 40D ( N + 3 rows )'
2008-12-31 12:34:14,678::MainThread::INFO::Loading user presets
2008-12-31 12:34:14,680::MainThread::WARNING::No user presets found
2008-12-31 12:34:14,680::MainThread::DEBUG::Spy.__init__(): yaw=0.0, pitch=0.0
2008-12-31 12:34:15,145::MainThread::DEBUG::ConfigManager.__init__(): versions: dist=['1', '4', '0'], user=['1', '4', '0']
2008-12-31 12:34:15,145::MainThread::DEBUG::ConfigManager.__init__(): user config. is up-to-date
2008-12-31 12:34:15,150::Spy::INFO::Starting Spy...
2008-12-31 12:34:15,150::Publisher::INFO::Starting Publisher...
2008-12-31 12:34:17,374::MainThread::TRACE::MainController.__onConfigButtonClicked()
2008-12-31 12:34:17,551::MainThread::DEBUG::ConfigController.__onCancelButtonClicked(): orientation=portrait
2008-12-31 12:34:17,552::MainThread::TRACE::ConfigController.__onLensTypeComboboxChanged()
2008-12-31 12:34:17,552::MainThread::DEBUG::ConfigController.__onLensTypeComboboxChanged(): lens type set to 'rectilinear'
2008-12-31 12:34:17,552::MainThread::TRACE::ConfigController.__onDriverComboboxChanged()
2008-12-31 12:34:21,680::MainThread::TRACE::ConfigController.__onBluetoothChooseButtonClicked()
2008-12-31 12:34:21,683::MainThread::INFO::Scanning available bluetooth devices...
2008-12-31 12:34:28,210::MainThread::INFO::Bluetooth available devices: [('00:06:66:00:19:7B', 'FireFly-197B'), ('00:12:6F:02:21:4D', 'MERLIN')]
2008-12-31 12:34:33,316::MainThread::TRACE::BluetoothChooserController.__onOkButtonClicked()
2008-12-31 12:34:33,323::MainThread::DEBUG::ConfigController.__onChooseBluetoothButtonClicked(): address=00:12:6F:02:21:4D, name=MERLIN
2008-12-31 12:34:35,799::MainThread::TRACE::ConfigController.__onOkButtonClicked()
2008-12-31 12:34:35,801::MainThread::INFO::Configuration saved
2008-12-31 12:34:41,647::MainThread::DEBUG::MainController.__onHardwareConnectMenuitemToggled(True)
2008-12-31 12:34:41,648::MainThread::INFO::Connecting to real hardware...
2008-12-31 12:34:41,655::Dummy-5::TRACE::Shooting.switchToRealHardware()
2008-12-31 12:34:41,665::Dummy-5::DEBUG::Head.init(): initializing driver...
2008-12-31 12:34:41,667::Dummy-5::DEBUG::BluetoothDriver.init(): trying to connect to 00:12:6F:02:21:4D...
2008-12-31 12:34:43,904::Dummy-5::DEBUG::BluetoothDriver.init(): successfully connected to 00:12:6F:02:21:4D
2008-12-31 12:34:43,904::Dummy-5::DEBUG::Head.init(): driver initialized
2008-12-31 12:34:43,904::Dummy-5::DEBUG::Head.init(): waiting for bluetooth connection...
2008-12-31 12:34:51,904::Dummy-5::DEBUG::Head.init(): initializing axis...
2008-12-31 12:34:52,233::Dummy-5::DEBUG::Axis.init(): full circle count=0xe62d3
2008-12-31 12:34:52,276::Dummy-5::DEBUG::Axis.init(): sidereal rate=0x6f9
2008-12-31 12:34:52,403::Dummy-5::DEBUG::Axis.init(): full circle count=0xe62d3
2008-12-31 12:34:52,457::Dummy-5::DEBUG::Axis.init(): sidereal rate=0x6f9
2008-12-31 12:34:52,459::Dummy-5::DEBUG::Head.init(): axis initialized
2008-12-31 12:34:52,459::Dummy-5::DEBUG::Shooting.switchToRealHardware(): realHardware initialized
2008-12-31 12:34:52,459::Dummy-5::DEBUG::MainController.__switchToRealHardwareCallback(): flag=True
2008-12-31 12:34:52,470::MainThread::INFO::Now connected to real hardware
2008-12-31 12:34:52,546::Spy::TRACE::MainController.__refreshPos()
2008-12-31 12:34:57,907::MainThread::TRACE::MainController.__onHelpViewLogMenuitemActivate()
2008-12-31 12:35:04,809::MainThread::TRACE::LoggerController.__onSaveButtonClicked()

I have seen that you have installed the last development version (1.5.5.1)...
I suggest to "deinstall" it properly and that you install the last stable version :

http://www.gbiloba.org/download/papywiz … nstall.exe

Then try to get the "Log File" and send it to the forum...

For your info, if you get the Blue light "ON" continuously on the BT , this mean that the connection is "effectively" established between the PC and the Tronisoft Bluetooth and that the problem isn't not a BT problem !!!
But...this not mean that the connection is well made with the Merlin head !!! If the Baud Rate is not set to 9600 (and this is mandatory for establish the dialog with the Merlin head) the Merlin head will not "understand" the instructions send by PAPYWIZARD !

Ok ?

Sorry for the problems...

Happy new year

irpano,

This is what my BTLink adapter configuration - from working setup - looks like:

Last edited by mediavets (2008-12-31 15:14:46)

claudevh wrote:

Hi Andrew,

Mediavets  wrote:

Do you think it possible that the connections to the two resistors within the shrink wrap on the special cable could be faulty or been damaged during module assembly? Or are these connections stablised within the shrink wrap?

Andrew, I am a "perfectionist" so each cable is tested individually and completelly after assembly and before dispatching certainly when they have to travel so far  !!!
The connections are "reinforced" with "individual" shrink wrap and protected with another "common" shrink wrap.

Happy New Year and a lot of satisfactions for 2009 ...

Hi Claude,

Yes, I'm sure you made the cable carefully and correctly - I was just wondering whether it was feasible for a heavy-handed user (perhaps more used to wrestling with crocodiles and boxing kangaroos ) to pull a cable tie so tightly around that part of the cable when assembling that they could damage it?

But as you point out the BT connection is made - blue LED no longer blinking - irpano's problem is something else, my feeling is that it is most likley to be either the programming of the BTLink or some issue with the Merlin head itself.

BTW is the cable shipping now with the Tronisoft kit? They don't mention a cable on the Web page.

My best wishes to you for 2009. And many thanks for creating the interface kit.

Last edited by mediavets (2008-12-31 16:59:56)

OK fellas I can now send files (I hope ) that might clear up a few points.

I have had the head working with the hand controller and all was ok.
I assembled all of the componects (Carefully) and plugged them in (Softly) Then went through the procedures as described.
I notice paul has mentioned that a long cable performs differently that a short one. I'm not suggesting that its the cable, The module, the head  or anything else that is at fault. I accept that I may be a blockhead but
I believe I have tried everthing you have suggested SO FAR.
As a last resort I tried the head again without the BTLink modfule. ---- The bloody thing reported a communication error (Lights on the handpiece flashing:
So off the head goes to the supplier for repairs.
in the meantime here is the screen dumps of the setup to make sure I have got it right.

irpano wrote:

It appears that I cant upload a pdf directly - so here are the URL's to the screen dumps.http://dnirman.jalbum.net/Temp/Papy%20mess%201.pdf
http://dnirman.jalbum.net/Temp/Papy%20mess%202.pdf

1. After programming the adapter did you use Get adapter info to read back the current config to check that programming had succeeded?

2. If you Remove the BT device afyter the right-click on BT icon in system tray there is no need to Add it again. My setup works fine without any device listed there if setting in Papywizard is for Bluetooth rather than Serial.

But if I want to use the Serial setting via BT virtual serial port then I can proceed as follows....

3. If after removing the device I then choose Add a Bluetooth device it opens a wizard.

4. The wizard discovers and offers Merlin as a device to add, when I select that I get a dialogue about pass keys. Select the second option (use passkey found in documentation) and enter '1234' which is passkey programmed into BTLink.

5. It then connects and exchanges passkeys and reports COM ports assigned, in my case COM4 and COM 5 (this never changes on my system).

6. If I then right-click the BT icon in system tray and select Open Bluetooth settings then  I see what is shown in screenshots 1-4 below. You can see that in my case Serial port (SPP) 'Dev B' is on COM4.

7. Then I run Papywizard (in tis case 1.5.5-1) and Configure/Hardware as Serial connection on COM4 as shown in screenshot 5. I do not check the Auto-connect check box. Click OK to save configuration.

8. Returning to main Papywizard screen I choose Hardware/Connect.. and the Please wait is shown until it connects to real hardware.

9. That's it Papywizard can now control the Merlin head. This is what the log looks like:

2009-01-01 03:11:18,592::MainThread::DEBUG::Papywizard.l10n(): default locale=en_GB
2009-01-01 03:11:18,592::MainThread::DEBUG::Papywizard.l10n(): LANGUAGE=None
2009-01-01 03:11:18,592::MainThread::DEBUG::Papywizard.l10n(): langs=['en_GB', 'en_US', 'fr_FR', 'pl_PL', 'de_DE', 'es_ES', 'nl_NL', 'it_IT']
2009-01-01 03:11:18,592::MainThread::DEBUG::Papywizard.l10n(): localeDir=C:\Program Files\Papywizard\share\locale
2009-01-01 03:11:18,608::MainThread::INFO::Starting Papywizard...
2009-01-01 03:11:18,608::MainThread::INFO::Loading default presets
2009-01-01 03:11:18,625::MainThread::DEBUG::Preset.__init__(): loading name='4@0 + Z + N'
2009-01-01 03:11:18,640::MainThread::DEBUG::Preset.__init__(): loading name='3@-15 + Z'
2009-01-01 03:11:18,640::MainThread::DEBUG::Preset.__init__(): loading name='6@30 + 6@-15 + N'
2009-01-01 03:11:18,640::MainThread::DEBUG::Preset.__init__(): loading name='4@30 + 4@-30'
2009-01-01 03:11:18,640::MainThread::DEBUG::Preset.__init__(): loading name='3 + 6 + 12 + 6 + 3 (28mm)'
2009-01-01 03:11:18,640::MainThread::INFO::Loading user presets
2009-01-01 03:11:18,671::MainThread::DEBUG::Preset.__init__(): loading name='mosaic 180x90 100mm'
2009-01-01 03:11:18,687::MainThread::DEBUG::Spy.__init__(): yaw=0.0, pitch=0.0
2009-01-01 03:11:18,875::MainThread::DEBUG::ConfigManager.__init__(): versions: dist=['1', '5', '5'], user=['1', '5', '5']
2009-01-01 03:11:18,875::MainThread::DEBUG::ConfigManager.__init__(): user config. is up-to-date
2009-01-01 03:11:18,875::MainThread::TRACE::MainController.__onNoteBookSwitchedPage()
2009-01-01 03:11:18,875::MainThread::DEBUG::MainController.__onNoteBookSwitchedPage(): shooting mode set to 'preset'
2009-01-01 03:11:18,890::Spy::INFO::Starting Spy...
2009-01-01 03:11:18,890::Publisher::INFO::Starting Publisher...
2009-01-01 03:11:23,890::MainThread::INFO::Connecting to real hardware...
2009-01-01 03:11:25,858::MainThread::INFO::Now connected to real hardware

FWIW I've never run my Merlin head using internal AA batteries, I have either used a 12V DC 500ma mains adapter or an external Skywatcher Power Tank 12V DC lead-acid battery pack (http://www.pulsar-optical.co.uk/prod/Sk … upply.html). Not that I can see that it should make any difference; most users run with internal AA rechargable NiMH batteries I believe.

Last edited by mediavets (2009-01-01 04:37:59)

Paul wrote:

irpano wrote:

The bloody thing reported a communication error (Lights on the handpiece flashing:
So off the head goes to the supplier for repairs.

So my Merlin does since two days (lights flashing, handcontroller not working) but Merlin works with Papywizard when BT and handcontroller are connected. My first Merlin did it from beginning and Tommy exchanged it.

I hope Tommy from TelescopeAustria will find a solution to get the handcontroller working again, so that we don't need to send the Merlin for repair (is there a way to reset the Merlin?).

Paul,

This is interesting - it seems to be happening relatively frequently just now. Perhaps a batch production problem with Merlin?

Did your first unit also work with Papywizard if both BT interface and handcontroller were connected?

I understand from your post that in the beginning your second Merlin head would work with Papywizard with needing also to connect the hand controller? Is that correct?

Now for last few days you have needed to also connect the hand controller to get it to work with Papywizard?

I have absolutely no knowledge of electronics but perhaps your observations and experiences will suggest the likely nature of the fault to someone who does have a knowledge of electronics and some understanding of the circuitry of the Merlin internals.

I wonder how many faults/failures of this kind Teleskop-Austria has seen? They were very quick to offer to replace your first Merlin so maybe this is a common fault?

I have forgotten - do you now use a Tronisoft-based TT-BT interface or are you using a different set of components to create the TTL-BT interface?

Happy New Year.

Last edited by mediavets (2009-01-01 12:37:34)

Paul,

It is puzzling as to why it should work with the long cable without also having the HC also connected, but only when the HC is also connected with the short cable.

Can you suggest any possible reason for this?

I think you also reported that when HC alone is connected the HC flashes LEDs to suggest a comms. problem and does not work? Is that correct?

Do you feel/think that there is a problem/fault  just with the HC, or with the HC AND with the electronics in the head itself?