lapin/LJ
1
0
Fork 0
forked from protonphoton/LJ
Code Issues Pull Requests Releases Wiki Activity

Add watchLJ to identify all LJ in network

Browse Source
This commit is contained in:
Sam 2020-10-13 01:56:26 +02:00
parent 3b0d44deb1
commit 8fbaaa7880
2 changed files with 8 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
README.md
View File

@ -7,7 +7,9 @@ LICENCE : CC BY
![LJ](https://www.teamlaser.fr/lj/images/lj2.png)
LJ is like a video projector where you fire images and forget. Lasers are dangerous : you can really fire real world objects. As content creator, it's damn easy to send frames : LJ do the heavy lifting for up to 4 lasers live actions. Think creative like games, Laser "battles", planetarium, sharing available lasers in demoparties for competition,...
LJ is like a video projector where you fire images and forget. Lasers are dangerous : you can really fire real world objects. That's why you really shouldn't forget your lasers and go drink a beer.
As content creator, it's damn easy to send frames : LJ do the heavy lifting for up to 4 lasers live actions. Think creative like games, Laser "battles", planetarium, sharing available lasers in demoparties for competition,...
LJ has 5 main components :
@ -321,7 +323,7 @@ DrawDests() will take care of all your declared drawn elements/"objects" and Des
2 compiled nannou visualisers are included, one for Linux, one for macOS. It's pretty old version but much more compatible with "old" processors/computer.
To use this visualiser as one of LJ's lasers, in LJ.conf edit one of line ip = someipaddress with the IP of the computer running the visualiser. Relaunch LJ. One visualiser per computer.
To use this visualiser as one of LJ's lasers, use configure.py to set one laser to the IP of the computer running the visualiser. Relaunch LJ. One visualiser per computer.
#
# Todo
@ -339,7 +341,7 @@ To use this visualiser as one of LJ's lasers, in LJ.conf edit one of line ip = s
#
You need to update LJ.conf to your network/etherdreams IPs and be sure to check command arguments : python3 configure.py
You need to update LJ to your network/etherdreams IPs. Be sure to check command arguments : python3 configure.py
LJ is network based and this is *critical and flickering reason #1* if not managed properly, especially if you have several lasers.
@ -379,7 +381,7 @@ For glitching experience you can change resampling strategy live with "resampler
# Colors
#
LJ is compatible with TLL and analog modulation. Each point color is an int value, wich is simply the hex color in decimal. Example : white = #fffff = 65535.
LJ is compatible with TLL and analog modulation. Each point color is an int value, wich is simply the hex color in decimal. Example : white = #fffff = 16777215
#
# Ether dream DAC
@ -445,7 +447,7 @@ python3 talk3.py -i etherdreamIP
- Check Leds : for each IRL lasers the two sets of must be green at startup and laser should display their number or the pointlist you want.
- If talk3 works but you don't see your points : click on the Grid icon in Align page. This will override your pointlist and display squares. If Grid works : recomputed points by tracers are "bad" with given values in LJ.conf.
- If talk3 works but you don't see your points : click on the Grid icon in Align page. This will override your pointlist and display squares. If Grid works : recomputed points by tracers are "bad" with given values in LJ.conf.
"Bad points" ?
@ -455,7 +457,7 @@ python3 talk3.py -i etherdreamIP
*Don't kill your scanners : becareful with kpps setting.*
The reset button copy the LJ_template.conf to LJ.conf.
#
# LJ commands reference

0
ethertools/receivebroadcast.py → ethertools/watchLJ.py
View File