Messages

76

OpenLase Discussion / Re: Level nearly completed ...

« on: November 24, 2015, 08:48:39 PM »

rompath         $HOME/skappy/.xmame/roms

This is incorrect. (it is pointing to /home/skappy/skappy/.xmame/roms) It should be:

Code: [Select]

rompath                 $HOME/.xmame/roms


skappy@skappy-portable:~/.xmame/roms$ ls
034602-01.c8   035143-02.j2   035145-04e.ef2  readme.html
035127-02.np3  035144-04e.h2  asteroid.zip

You need to rename these files to match what xmame is looking for when it tries to run the asteroid game. That is what these lines correspond to:

Code: [Select]

035145.02    NOT FOUND
035144.02    NOT FOUND
035143.02    NOT FOUND
035127.02    NOT FOUND


77

OpenLase Discussion / Re: Level nearly completed ...

« on: November 23, 2015, 11:11:24 PM »

Did you modify the following line in your xmamerc file to specify where your rom folder is?:

Code: [Select]

rompath                 $HOME/.xmame/roms
Is your xmamerc file located in one of the locations it was searched for at? I.e.:

Code: [Select]

info: trying to parse: /usr/local/share/xmame/xmamerc
info: trying to parse: /home/skappy/.xmame/xmamerc
info: trying to parse: /usr/local/share/xmame/xmame-x11rc
info: trying to parse: /home/skappy/.xmame/xmame-x11rc
info: trying to parse: /usr/local/share/xmame/rc/asteroidrc
info: trying to parse: /home/skappy/.xmame/rc/asteroidrc

Finally in your rom directory (or a subdirectory), do these files exist?:

Code: [Select]

035145.02    NOT FOUND
035144.02    NOT FOUND
035143.02    NOT FOUND
035127.02    NOT FOUND

What does the rompath directory point to and what is inside of this directory? (use ls -l)

78

OpenLase Discussion / Re: Level nearly completed ...

« on: November 19, 2015, 11:49:34 PM »

Some warnings are expected. As long as there were no errors you are ok. Looks like it finished compiling successfully

79

OpenLase Discussion / Re: Level nearly completed ...

« on: November 17, 2015, 10:09:00 PM »

If you receive messages concerning missing header files, it indicates you do not have the appropriate developer packages installed on your computer which contain these headers.

When you encounter errors of this type, you will need to identify and install the package which provides these headers. This page describes how to do this:
https://kobablog.wordpress.com/2011/05/17/how-to-find-and-install-the-missing-file-in-ubuntu/

In your case you need to install the following packages (note that packages ending with -dev indicates they include headers generally):

Code: [Select]

sudo apt-get install zlib1g-dev x11proto-video-dev


You should remove the two headers you added to the project folder.

80

OpenLase Discussion / Re: Level nearly completed ...

« on: November 15, 2015, 11:53:25 PM »

Glad you got it working. To compile jv4779's code you should do the following:

To build

Code: [Select]

cd ~/Desktop
mkdir mame
cd mame
git clone https://github.com/jv4779/openlase-mame.git
cd openlase-mame/xmame-0.106

If you have not installed the libopenlase.so library, you will need to specify where it is located:

Code: [Select]

export LD_LIBRARY_PATH=/home/<openlase directory>/build/libol:$LD_LIBRARY_PATH

In the Makefile within the of xmame-0.106 directory make the following changes:

Code: [Select]

Change this line to point to where openlase source is:
OL_DIR = /home/nelsonjm/laser_projector/openlase_macpod/openlase

Change this line:
#CFLAGS = -O2 -mtune=i686 -fomit-frame-pointer -fstrength-reduce -ffast-math
To this:
CFLAGS += -O2 -mtune=i686 -fomit-frame-pointer -fstrength-reduce -ffast-math

Comment out this line (assuming you are running a 64-bit os):
MY_CPU = i386
And uncomment this line:
MY_CPU = em64t

If you want to use a joystick, uncomment this line:
JOY_STANDARD = 1


If you want sounds, uncomment htis line:
SOUND_ALSA = 1

Build it:

Code: [Select]

make

To run:
If you have not installed the libopenlase.so library, you will need to specify where it is located:

Code: [Select]

export LD_LIBRARY_PATH=/home/<openlase directory>/build/libol:$LD_LIBRARY_PATH


Code: [Select]

Copy or link xmamerc that is in ~/Desktop/mame/openlase-mame/ into $HOME/.xmame directory

Update rompath in $HOME/.xmame/xmamerc to point to where your roms are

Start up openlase (ie jackctl, etc)

cd ~/Desktop/mame/openlase-mame/xmame-0.106
padsp ./xmame.x11 asteroid


81

OpenLase Discussion / Re: Level nearly completed ...

« on: November 09, 2015, 09:32:19 PM »

skappy@skappy-portable:~/Bureau/MacPod/openlase/examples$ python tweet.py test
  File "tweet.py", line 42
    def __init__(self):
      ^
IndentationError: expected an indented block


Can you please help me to understand the meaning of this error message...

Python uses spacing at the start of the line to determine when code blocks start and end. It seems line 42 is improperly indented. Spaces are not considered the same as tabs. You will need to update the indentation of this line so the program can run.

https://docs.python.org/2/reference/lexical_analysis.html#indentation

May I ask you if I can try a another argument than 'test' in

python tweet.py test

Thank you very much and sorry once again 

I can use whatever argument I want and it behaves the same.

If it is still installed, you should uninstall python-twitter:
pip uninstall python-twitter

82

OpenLase Discussion / Re: Level nearly completed ...

« on: November 08, 2015, 09:58:49 PM »

1.17.1 is correct.

The fact that it accepted the api = twitter.Twitter(...) line indicates you are using tweet vs tweet-python.. I'm not sure why this isn't working for you with the information provided.

Did you modify the python program?

83

OpenLase Discussion / Re: Level nearly completed ...

« on: November 07, 2015, 05:30:18 PM »

What version of the tweet api do you have installed?

84

OpenLase Discussion / Re: Level nearly completed ...

« on: November 07, 2015, 01:15:49 PM »

Sounds like it is using the python-twitter api vs the twitter api. You should uninstall the python-twitter api.

85

OpenLase Discussion / Re: Level nearly completed ...

« on: November 06, 2015, 09:48:42 PM »

I have made the bare minimum changes needed to get this running again:

https://github.com/macpod/openlase/blob/master/examples/tweet.py

In order to use this you will need to make a Twitter app:
https://apps.twitter.com/app/new

Once you create this app you will need to modify the source to include your designated API Key and API Secret.

Since tweet.py was first written by marcan it seems twitter.com has exposed a streaming api. This should be used if a new version of tweet.py were to be made.

86

OpenLase Discussion / Re: Level nearly completed ...

« on: November 06, 2015, 01:30:17 AM »

Lets start on question 1. Please read through this fully because there are multiple problems here:

a. 'sudo easy_install python-twitter'
This is not actually the twitter library used by openlase, instead this one is just called "twitter"

I would suggest using pip vs easy_install to install packages:
sudo pip install twitter

b. 'python tweet.py'
This is not the correct usage. You need to specify a twitter search term. This is why you are getting this error:
Traceback (most recent call last):
  File "tweet.py", line 114, in <module>
    search = sys.argv[1]
IndexError: list index out of range

Try running it as:
python tweet.py test

Since you say you want to learn more about programming check out these tutorials which talk more about parsing command line arguments:
http://www.cyberciti.biz/faq/python-command-line-arguments-argv-example/

c. Twitter no longer supports their v1 REST API so even if you did import the right modules and provide the proper command line arguments it would not work. I'll take a look at what is needed to update this tomorrow.

Down the rabbit hole!

87

OpenLase Discussion / Re: Level nearly completed ...

« on: October 30, 2015, 10:40:45 PM »

Hi Fabrice,

Glad you got your projector working to your liking.


1. This question is very difficult to answer without output to identify the problem you are encountering.

2. jv4779 modified xmame to support OpenLase. By default Xmame does not support OpenLase. You are going to have to compile jv4779's code.

A fair warning: I did this a while ago and even with proper 30kpps galvos, it was quite choppy and probably overly-complicated for a galvo system. I don't know or have access to many ROMs, but if you do experiment, do so with very simple games like asteroids.

88

LaserShark Support / Re: Lasershark on Win 10 - 64bit: "Error finding USB device"

« on: October 19, 2015, 12:36:26 AM »

After working on this problem today I have found that libusbK must be installed for the "LaserShark (Composite Parent)". This was not necessary in the past. I have updated the instructions to reflect this.

Once libusbk is installed in place of usbccgp everything should work as-is.

While I was debugging this I decided that it would be easy enough to support selection of which LaserShark can be controlled. You can list LaserShark units via the -l option and specify the LaserShark you want to connect to via the -s option (the serial number is used to identify the LaserSharks).

These changes have been checked into git and new binaries for Windows 32bit and 64bit architectures have been uploaded to my website (see the windows usage page)

89

LaserShark Support / Re: Lasershark board tuning

« on: October 15, 2015, 11:43:48 PM »

The program should be self-documenting when run.

I suspect if you are fabricating the board for yourself that you will have trouble. It is a two layer board but there are quite a few vias and some are under parts.

The Fluke 289 should be ok for this.

90

LaserShark Support / Re: Firmware update problem

« on: October 15, 2015, 11:32:15 PM »

Yea, for Windows you may have to re-install the drivers if you update the firmware. Glad you got figured it out.