Parallax A7eng eb500-SER Interface

[claudevh]

Parallax A7eng eb500-SER Interface

by claudevh » Thu Feb 26, 2009 7:15 pm

Hi all,

Here will be the place to exchange Tips and Tricks about the Parallax A7eng eb500-SER Interface solution ...

Last edited by claudevh on Thu Feb 26, 2009 7:22 pm, edited 1 time in total.

[claudevh]

by claudevh » Thu Feb 26, 2009 7:21 pm

Hi all,

Here some "visual explanations" about the dedicated "Cable/Connector" for Parallax ...

[mediavets]

by mediavets » Thu Feb 26, 2009 8:34 pm

Claude,

Thanks - that's a great visual description.

[claudevh]

by claudevh » Sun Mar 01, 2009 12:30 am

To all,

The pictures for the connecting the cable/connector to the BT module Parallax eb500-SER ...

[hillels]

by hillels » Tue Mar 03, 2009 1:03 am

Claude,

I received the Parallax board today and hooked your cable up to it using your diagram above in about 90 seconds. I left it dangling down from the Orion and fired up the Nokia 770. I selected the bluetooth icon and paired with the board quickly using the 0000 passkey. I started up the papywizard and it connected on the first try! The arrow icons easily moved around the head. I set the start and end positions for a tiny panorama, turned on the Digital Rebel XT, and clicked the shoot button. It immediately spun around and began collecting the panorama coverage with a visual description of each shot on the Nokia. Wow. Now I need to take it outside when the snow stops!

Thanks again Claude,

-= Hillel =-

[Gordon]

by Gordon » Tue Mar 03, 2009 1:21 am

Excellent news, and such a compact board.

Gordon

[DukeNukeIt]

by DukeNukeIt » Wed Mar 11, 2009 4:34 am

Got my board today. Placed it into a small plastic box and wired it up. Nothing... Checked my wire, fixed a few problems and now it works

Now I have to figure out the program and start shooting!

Dave

Last edited by DukeNukeIt on Sun Mar 15, 2009 6:11 am, edited 1 time in total.

[claudevh]

by claudevh » Wed Mar 11, 2009 9:11 am

Hi Dave,

Very happy for you ...!

Considering the small wiring problems you have got, do you see place for improvement into the pictures posted for the connections of the Parallax module ?

Thanks in advance for your cooperation.

[DukeNukeIt]

by DukeNukeIt » Wed Mar 11, 2009 11:42 am

Hello Claude,

If it was not for your excellent photos I never would have been able to get this thing working My short phone cord had the Green and Red wires swapped. Also the phone jack in the box had different wire colors Green ended up being VCC, Black is GND, and Yellow is TTL Logic. Basically I looked at your layout photos of the wires, remapped my wires with my trusty Fluke DMM meter, then hooked it up correctly.

I'll be double checking the camera shutter cable later tonight after work, but hopefully I'll be able to start shooting panos this weekend!

Thanks for all the great technical advice on getting this project of the ground!!!

Sincerely,
Dave

Last edited by DukeNukeIt on Wed Mar 11, 2009 11:46 am, edited 1 time in total.

[joelb]

by joelb » Sun Mar 15, 2009 2:12 am

Hello to all,
My first post here. (Hope I've posted in the proper place.) What a helpful, informative community! I'm excited to get my Skywatcher version of Merlin in operation.

Yesterday I received the Parallax A7eng eb500-SER (at last, after twice receiving incorrect parts). Today I built the cable. Thank you Claude for the excellent photos. Had no problem getting Papywizard installed on my eBay purchased Nokia N800. Thank you fma and all others for excellent documentation on that install.

I was optimistic all would work straight away, but I encountered an error.
I'm fearing that the eb500-SER may be defective.

Error is: Axis 1 can't send command.

When I turn on Skywatcher/Merlin the LED blinks briefly on the eb500-SER. I open Papywizard on the N800. I configured the Bluetooth address with the number sequence provided with the device (different from the default), entered 0000 passkey. When I connect through Menu>Hardware>Connect PW starts connection process, green LED lights and stays on steady on eb500-SER, but soon after the error mentioned above displays on Papywizard.

I've triple checked cable wiring and even though my cable wire colors differ, I'm nearly 100 percent certain they are correct and going to appropriate pins both on BT and on Skywatcher jack.

On BT: 1 = Ground, 3 & 4 = TX/RX (with resistors), and 20 = V+
On Skywathcer/Merlin: 2 = Ground, 4 = V+, 5 = TX/RX

I checked with ohm meter as well to make sure there were no shorts/opens in the cable, and that seems fine. As a further test I used the provided hand controller, and the Sywatcher/Merlin head operates fine with that in all directions.

Does anyone know if there is a way to determine if the eb500-SER is the fault? Or is there something else I am missing in the configuration? From the various posts I've read, it seems that others with the eb500-SER had no problems with it (other than minor corrections to wiring) and it worked correctly right out of the box.

Any suggestions would be greatly appreciated!

[DukeNukeIt]

by DukeNukeIt » Sun Mar 15, 2009 6:18 am

Hello Joelb,

Sounds like the problem that I had. The Blue-tooth connects, but there is no communication from the Orion/Merlin head. I would triple check the wiring for the TTL logic. Sounds like your +Vcc and Gnd are correct. You're not leaving the hand control plugged in also are you? Good luck!

On a plus for me, I've checked the trigger cable from the Orion/Merlin head and my camera fires just fine with the program!

Off to shoot panos!!!
Dave

[claudevh]

by claudevh » Sun Mar 15, 2009 11:42 am

Hi Joelb,

Could you please show a picture with :

- RJ12 side of the Skywatcher ( like on first pic)
http://www.autopano.net/forum/postgallery.php?pid=39798&filename=Cables-order.jpg
- Parallax side (like second pic)
http://www.autopano.net/forum/postgallery.php?pid=39933&filename=Parallax-A7eng-eb500-SER-3.jpg

Could you also give us more info's on your first temptative to connect ....
-Was that directly trough Nokia ?
-Do you try wit a PC/Linux/Mac ?
- in place of typing the " number sequence provided with the device", could you let Papywizard discover himselve and validate the discovered number "and after that" connect then trough Papywizard ! Please before trying that, please clear the log file and send us a copy of this log file after your trial ...

Thanks

[claudevh]

by claudevh » Sun Mar 15, 2009 11:50 am

Hi Joelb,

FYI

You are the Number "40" in the listing of the "known" Papywizard user's ...

http://www.autopano.net/wiki/action/view/Merlin-Orion-Papywizard_users_feedback

[joelb]

by joelb » Tue Mar 17, 2009 4:48 pm

Hello Dave and Claude,
Thanks for your helpful response. Still no luck. Get green LED, but Papywizard displays same "Axis 1, can't send command" error.

The first cable I used was pre-wired WITH plastic RJ-12 connectorS on both ends which I chopped in half. The wire colors were not in the same order as in Claude's excellent photos. Of course, I knew to ignore the color sequence and instead wired based on pin numbering and pin out configuration on the Eb500 BT and the Merlin input.

I saw in previous posts that the Merlin (and I presume Skywatcher brand is the same) input scheme from left to right is:

Pin 2, Ground
Pin 4, V+
Pin 5 RX/TX.

On the Eb-500 (looking straight on at 20 pins, from left to right)
Pin 20, V+ (leftmost pin, top row)
Pin 4, RX (second pin from right, top row)
Pin 3, Tx (second pin from right, bottom row)
Pin 1, Ground (first pin from right, bottom row)

Dave... thanks for the tip, but no, I did not have the handcontroller plugged in at the same time. Glad you are making progress with your Merlin.

Today as another check on my wiring I made a second cable with a spare RJ-11.

I presumed the photo showing the clear RJ-12 connector in Claude's photo is with the RJ connector latch on top. Is that correct?

Here is the photo my second cable (See two photos below). Pardon the hack wiring/soldering. I'm awaiting shipment of proper Molex pin connects.

Plugged 2nd cable into Skywatcher. Turned on Skywatcher power. Get brief blink of green Eb500 LED. Open Papywizard on Nokia N800. From menu configured Hardware to Bluetooth, clicked choose to let Papywizard 'find' BT address. Address found. Return to menu, select Hardware>Connect. PW attempts to connect, green LED on Eb500 lights steady, error message pops up: "Axis 1, can't send command"... just as with the first cable. :-(

Here is the log file showing the sequence leading to the error:

2009-03-16 21:18:45,280::MainThread::INFO::Connecting to real hardware...
2009-03-16 21:18:58,418::Dummy-5::EXCEPTION::Axis._sendCmd
Traceback (most recent call last):
File "/usr/lib/python2.5/site-packages/papywizard/hardware/axis.py", line 235, in _sendCmd
answer = self.__driver.sendCmd(cmd)
File "/usr/lib/python2.5/site-packages/papywizard/hardware/bluetoothDriver.py", line 129, in sendCmd
c = self._sock.recv(1)
File "<string>", line 5, in recv
BluetoothError: timed out
2009-03-16 21:18:58,438::Dummy-5::WARNING::Axis._sendCmd(): axis 1 can't sent command. Retrying...
2009-03-16 21:18:59,482::Dummy-5::EXCEPTION::Axis._sendCmd
Traceback (most recent call last):
File "/usr/lib/python2.5/site-packages/papywizard/hardware/axis.py", line 235, in _sendCmd
answer = self.__driver.sendCmd(cmd)
File "/usr/lib/python2.5/site-packages/papywizard/hardware/bluetoothDriver.py", line 129, in sendCmd
c = self._sock.recv(1)
File "<string>", line 5, in recv
BluetoothError: timed out
2009-03-16 21:18:59,503::Dummy-5::WARNING::Axis._sendCmd(): axis 1 can't sent command. Retrying...
2009-03-16 21:19:00,542::Dummy-5::EXCEPTION::Axis._sendCmd
Traceback (most recent call last):
File "/usr/lib/python2.5/site-packages/papywizard/hardware/axis.py", line 235, in _sendCmd
answer = self.__driver.sendCmd(cmd)
File "/usr/lib/python2.5/site-packages/papywizard/hardware/bluetoothDriver.py", line 129, in sendCmd
c = self._sock.recv(1)
File "<string>", line 5, in recv
BluetoothError: timed out
2009-03-16 21:19:00,563::Dummy-5::WARNING::Axis._sendCmd(): axis 1 can't sent command. Retrying...
2009-03-16 21:19:00,603::Dummy-5::EXCEPTION::Shooting.switchToRealHardware()
Traceback (most recent call last):
File "/usr/lib/python2.5/site-packages/papywizard/model/shooting.py", line 284, in switchToRealHardware
self.realHardware.init()
File "/usr/lib/python2.5/site-packages/papywizard/hardware/head.py", line 93, in init
self.yawAxis.init()
File "/usr/lib/python2.5/site-packages/papywizard/hardware/axis.py", line 251, in init
self._sendCmd("L")
File "/usr/lib/python2.5/site-packages/papywizard/hardware/axis.py", line 242, in _sendCmd
raise HardwareError("Axis %d can't send command" % self._num)
HardwareError: Axis 1 can't send command
2009-03-16 21:19:00,638::MainThread::ERROR::Can't connect to hardware
Axis 1 can't send command
2009-03-16 21:19:07,219::MainThread::INFO::Go to simulation mode
2009-03-16 21:19:08,227::MainThread::EXCEPTION::Axis._sendCmd
Traceback (most recent call last):
File "/usr/lib/python2.5/site-packages/papywizard/hardware/axis.py", line 235, in _sendCmd
answer = self.__driver.sendCmd(cmd)
File "/usr/lib/python2.5/site-packages/papywizard/hardware/bluetoothDriver.py", line 129, in sendCmd
c = self._sock.recv(1)
File "<string>", line 5, in recv
BluetoothError: timed out
2009-03-16 21:19:08,235::MainThread::WARNING::Axis._sendCmd(): axis 1 can't sent command. Retrying...
2009-03-16 21:19:09,243::MainThread::EXCEPTION::Axis._sendCmd
Traceback (most recent call last):
File "/usr/lib/python2.5/site-packages/papywizard/hardware/axis.py", line 235, in _sendCmd
answer = self.__driver.sendCmd(cmd)
File "/usr/lib/python2.5/site-packages/papywizard/hardware/bluetoothDriver.py", line 129, in sendCmd
c = self._sock.recv(1)
File "<string>", line 5, in recv
BluetoothError: timed out
2009-03-16 21:19:09,251::MainThread::WARNING::Axis._sendCmd(): axis 1 can't sent command. Retrying...
2009-03-16 21:19:10,266::MainThread::EXCEPTION::Axis._sendCmd
Traceback (most recent call last):
File "/usr/lib/python2.5/site-packages/papywizard/hardware/axis.py", line 235, in _sendCmd
answer = self.__driver.sendCmd(cmd)
File "/usr/lib/python2.5/site-packages/papywizard/hardware/bluetoothDriver.py", line 129, in sendCmd
c = self._sock.recv(1)
File "<string>", line 5, in recv
BluetoothError: timed out
2009-03-16 21:19:10,287::MainThread::WARNING::Axis._sendCmd(): axis 1 can't sent command. Retrying...
2009-03-16 21:19:10,322::MainThread::EXCEPTION::Shooting.switchToSimulatedHardware()
Traceback (most recent call last):
File "/usr/lib/python2.5/site-packages/papywizard/model/shooting.py", line 297, in switchToSimulatedHardware
self.realHardware.shutdown() # Test if init first
File "/usr/lib/python2.5/site-packages/papywizard/hardware/head.py", line 109, in shutdown
self.yawAxis.stop()
File "/usr/lib/python2.5/site-packages/papywizard/hardware/axis.py", line 371, in stop
self._sendCmd("L")
File "/usr/lib/python2.5/site-packages/papywizard/hardware/axis.py", line 242, in _sendCmd
raise HardwareError("Axis %d can't send command" % self._num)
HardwareError: Axis 1 can't send command[/color]


I have contacted the supplier and hope they will replace the EB500 promptly as I'm quite certain it is a problem with the BT. I'll keep you posted on progress with that.

Also, Claude, thank you for adding me to the Merlin user list... proud to be #40. I appreciate all the help I have been receiving.

Cheers,
Joel

Last edited by joelb on Tue Mar 17, 2009 4:57 pm, edited 1 time in total.

[tarnis]

by tarnis » Tue Mar 17, 2009 6:22 pm

I just stumbled across this looking for something else... says it has an RJ-11 jack on it and price wise actually looks worth it compared to the parallax board if it works?

http://www.adorama.com/ONBAETX.html

Of course once I found it, it seems like a fairly common product that I'd of thought someone else might have spotted so maybe it's no good?

[claudevh]

by claudevh » Tue Mar 17, 2009 6:33 pm

Hi Joel,

Your wiring is perfectly correct !

As you presume, I think also that the Parallax module is defective !
Tarnis has exactly the same problem and have returned to the supplier ...
But the supplier should proceed to real test because generally this is a whole batch who is defective and not a isolated one ...

Who is your supplier ?
If Tarnis read us .... Matt could you give us the name of your supplier also ?

[fma38]

by fma38 » Tue Mar 17, 2009 6:34 pm

Joel, it seems that Papywizard is unable to re-read its own output chars... The two resistors are maybe too high for this module. Could you try a 100 Ohm on the RX side only (leave 220 Ohm on TX)? You may leave the common point of the 2 resistors unconnected from the Merlin, as long as the error occurs at line 129 in the bluetoothDriver.py module. Once the error occurs at line 135, then try to reconnect the common point to the Merlin...

[claudevh]

by claudevh » Tue Mar 17, 2009 6:50 pm

Hi Matt,

I just stumbled across this looking for something else... says it has an RJ-11 jack on it and price wise actually looks worth it compared to the parallax board if it works?

http://www.adorama.com/ONBAETX.html

Of course once I found it, it seems like a fairly common product that I'd of thought someone else might have spotted so maybe it's no good?

This material isn't adapted to the Merlin/Orion, not the same wiring, not the same protocol, not the same software !

If you want try an alternative, you can go to the Ursa Minor solution !

[joelb]

by joelb » Tue Mar 17, 2009 9:08 pm

Hello Claude, Frederic, Matt...
I spoke with the supplier today, Trossen Robotics, http://www.trossenrobotics.com/parallax-embeddedblue-transceiver-appmod.aspx and the head of their Hardware Support, Andrew Alter. He and the rest of the staff at Trossen are first-rate with customer service I must say. Even though I got off to quite an unlucky start... receiving the wrong part twice, then possibly a defective Eb500, they were quick to admit their error, apologized profusely, and immediately shipped via express UPS at their expense to make it right. Today Andrew said he'd personally test the replacement Eb500 to ensure it is receiving commands/data before he ships it out express. And he will re-test the returned Eb500 and let me know what he finds. I explained to him about the Merlin community and goal with the eB500. He seemed genuinely interested and Trossen may yet prove to be an excellent supplier for this Parallax module, especially for those of us here in the States.

Frederic, I will try your 100 ohm resistor change approach tomorrow. I will report back on that, as well as how things turn out with the replacement Eb500. Fingers crossed.

Cheers,
Joel

Last edited by joelb on Tue Mar 17, 2009 9:11 pm, edited 1 time in total.

[mediavets]

by mediavets » Tue Mar 17, 2009 9:26 pm

I saw in previous posts that the Merlin (and I presume Skywatcher brand is the same)
Joel

Joel,

You don't have the GoTo version of the Skywatcher mount do you?

Does your hand controller have an LCD panel?

[mediavets]

by mediavets » Tue Mar 17, 2009 9:28 pm

Joel, it seems that Papywizard is unable to re-read its own output chars... The two resistors are maybe too high for this module. Could you try a 100 Ohm on the RX side only (leave 220 Ohm on TX)? You may leave the common point of the 2 resistors unconnected from the Merlin, as long as the error occurs at line 129 in the bluetoothDriver.py module. Once the error occurs at line 135, then try to reconnect the common point to the Merlin...

If this is the issue how come Claude had it working with 2x220 ohm resistors?

[Fletch]

by Fletch » Tue Mar 17, 2009 9:45 pm

First post I have a head on the way.

This module (from the maker of the eb500) may also be of interest. The only disadvantage I can see being the need for a voltage regulator to supply the 5v needed.

http://www.a7eng.com/products/bluetooth/productpages/eb301serialbtadapters.htm

[claudevh]

by claudevh » Tue Mar 17, 2009 11:31 pm

Hi All,

Joelb, its seems that it is a real pleasure to work with Trossenrobotics !
If they check the module before it leave, I am sure that this will work without any modifications ....

Andrew and others, this is not the first time that the story of the resistors come into consideration ... remember the problems with Emmanuel, at this moment I try to change one of the resistors of 220 Ohms with a resistor of 100 Ohms without any success, at the end that was a small change into the default configuration of the BT module (Tronisoft). So I suggest to wait till the delivery of the new Parallax module to Joelb and Tarnis before changing anything !

Andrew, your question about the value of the resistors ... this have been fixed at 220 Ohms by Frédéric since the beginning of the Papywizard story... the reason is to get a sufficient protection for the Merlin circuits in case of bad connection or accidental "high" cumuled voltage in the circuit !
You can also protect the circuit by other more sophisticated means like transistors etc ... but this will add additional complexity and costs. Fixing the same value to the two side of TTL signals simplify and eliminate the errors in the connections as you can connect RX in place of TX and vice-versa without getting problems.
Making the difference between RX and TX signals will oblige to use polarized connectors or ask an additional attention to the users for the connections ! You see what I mean ?

Fletch, welcome in the community !
About the A7eng eb301 OEM Serial Bluetooth Adapters, this is of course a excellent alternative to the eb500 SER but, as you say,this has no built-in PSU and thus need a PSU of 5V to get it operational !
I can say that I have tested this one and today I find personally the best one as it can become a real cheap alternative to the Parallax who isn't cheap and to the Ursa Minor who is "actually" very expensive.
I am busy with a prototype on basis on this eb301 who use the same chip as the eb500 SER; this prototype will be modular, actually 2 pieces ; the first one will include "entry connectors" polarized or RJ12 Plug-in, the PSU 5V, the resistors and the "exit connectors" where you can plug directly the e301 and the second one will the eb301 himselve without modification as it come from the supplier !
Maybe it will be interesting to include a plug for the remote control of the camera in replacement of the Merlin connector who has disapeared in the go-to model. Maybe we should also think to the possibility to combine with a USB connector for tethered shooting but this is another story !

If you are interrested into those tests I have summarized in a document :
http://www.autopano.fr/wiki/images-fr/e/e2/Merlin_Interface_study.pdf

[bigwade]

by bigwade » Tue Mar 17, 2009 11:52 pm

If you are interrested into those tests I have summarized in a document :
http://www.autopano.fr/wiki/images-fr/e/e2/Merlin_Interface_study.pdf

Claude, wonderfull work again !


but, I would rank the Parallax ** now (because of the problems) and the Ursa Minor ***
At least the Ursaminor is working out of the box
and there are other Ursaminor distributors if TA is not responding.
http://www.ursaminor.hu/contact_en.html
Price is/can be an issue but frustration about a not working BT module too.
It's getting spring here and there's no time to loose to get the Merlin sets working
grtz!

[mediavets]

by mediavets » Wed Mar 18, 2009 1:32 am

and there are other Ursaminor distributors if TA is not responding.
http://www.ursaminor.hu/contact_en.html

Their UK partner does not list the item on their web site.

I have emailed them to ask if they stock it; and if not, why not.