Pomoco not opening

Hexy Questions, Problems and Suggestions
#1

When i open pomoco it closes.I have looked everywhere but cant find a answer.I know my servos are initiated because servo comm works.What do i do?

EDIT:I got the GUI to open but it does nothing. I think it might be a driver problem. Any ideas?

#2

Hello Camero,

if the GUI is displayed, but Hexy does not move the connection to it couldn’t established. ( If you start PoMoCo in some terminal window you will get an error message, too. )
You use Windows? Please check if the device/driver are initialized correct if you plug in Hexy. Which COM-Port will be used? I did not give you more details because I use Linux.

Regards Yggdrasil

#3

it says “Arduino Leanardo” For the driver. Should it be this? When I look at my devices it says “servotor32”. My Hexy is connected on COM3.

#4

help?

#5

Are you double-clicking the file or running from the command line? What OS are you using? If you’re double-clicking, that invariably doesn’t work… try running in a Terminal or Cmd window.

Without connecting the robot, you should still get the GUI, and should see this in the command line window:

Attempting to connect to Servotor
Trying Windows Method
Connection to Servotor failed. No robot movement will occur.
initilizing servos
servos initalizied
Killing all servos

If you can’t start it from the command line without connecting the robot first, then respond and we can go from there.

#6

Hey guys,

  I'm having the same issue with my Hexy bot. Were you able to figure out what the issue was? Any insight would be greatly appreciated.

Thank you.

     Joe Tobia
#7

I had the same issue you need to install PySerial [more than likely].

Depending on your system[windows 32 or 64 bit or MAc/Linux], pull the file from the page below
arcbotics.com/products/hexy/start/

Basically, when that prompt disappears without staying on screen, you are missing libraries PoCoMo is calling. PySerial and or other files imports. So what happens is the program errors out although the command prompt does not show the error. If you right click PoCoMo and select edit with IDLE, you can go to ‘run’ the file 'run module" to see specific errors which should help with troubleshooting. Also, be sure the batteries are hooked up to the servo and not the logic port.

#8

I have a similar issue and cannot start PoMoCo.py. I’ve ran the PoMoCo.py from the command line and get this error:

…file path…, line 32
print “Preforming move:”,moveName

SytaxError: invalid syntax

This is a type of error I’ve seen when I forgot to put a “” or ; in C#. I’m not familar with Python though. I haven’t modified the code.

When I right click and edit from IDLE -> then Run > Run Module, I get a popup box stating “System Error”, Invalid Syntax. The IDLE then highlights the quotes after the move: in the print line (line 32).

I’m running Win8.
I’ve installed python and pyserial (did this 2x, per another post).

Any help would be fantastic. Thanks!

#9

If I comment out the print “preforming move:” line, the closing bracket on the second to the last line will error. Commenting out that, I get the following error:
Traceback (most recent call last):
File “C:\Python33\Scripts\PoMoCo-1.0\PoMoCo.py”, line 9, in
import servotorComm
File “PoMoCo\servotorComm.py”, line 66
print “sent ‘%s’ to COM%d”%(str(toSend).strip(’\r’),self.serNum+1)
^
SyntaxError: invalid syntax

I’ve ensured c:\Python33 is within my path environment variables line.

#10

Then after commenting out all prints in the servotorComm.py, I get the following error:
Traceback (most recent call last):
File “C:\Python33\Scripts\PoMoCo-1.0\PoMoCo.py”, line 9, in
import servotorComm
File “PoMoCo\servotorComm.py”, line 74
def connect(self):
^
IndentationError: expected an indented block

Which, does this set of code simply determine which COM ports to connect to?

#11

Hi Mitch,

I think you explained the error right here:
“I’ve ensured c:\Python33 is within my path environment variables line.”

PoMoCo is designed for Python 2.7. It is incompatible for Python 3.x. Try uninstalling python 3 and using python 2.7 instead

#12

Turns out, I had installed Python 3.3, not seeing the line in the instructions to use 2.7.3 (I’m actually using 2.7.4 and it appears to be working now - looks like I’m onto not enough power to the servos, but I’m not using the right batteries). Phew.