Radiation detector send to trigger lights
-
like this?
-
I think an arduino of some kind is needed to get an 'electronic' signal into it and then convert it into a digital format.
Thoughts?
-
If I'm not mistaken, a Geiger counter also produces sound so maybe is has some sort of a headphone output or you can make one. and use the sound to activate things.
@Skulpture, there is even an Geiger counter arduino shield. Than you only have to take the input of that shield an use this line:
Serial.print(1,DEC);
Serial.println(Sensor data);Than connect arduino to isadora using serial. And with the Serial in watcher you can use the info to manipulate other stuff by using this line:
"1"
serValue : integer = 4 digitsYou can change the 1 for other data you want to send.
@dbini, osc and arduino is a bit mor difficult. But also possible and easer for longer distances. Together with some smart people on and off this forum I made a simple way for osc between isadora and arduino but it can also be used the other way around in this post.
-
Thank you all for your input so far. I will know more tomorrow what the unit is I may have to work with and what the output is. I'll reply with that info then.
-
@joejdrums: Ok folks more info. This is for a student project and I just received more crucial info. They will already have converted the geiger readings into a data file through a piece of software. I don't know what file types Izzy reads. I'm guessing they would need to put the data into a data table actor of sorts? That Izzy can read continuously/or once per trigger? Is that possible?
The "data table" actor would then need to send to Izzy to manipulate light parameters in whatever meaningful way is both possible and/or the student chooses.
Make sense? Thanks again in advance.
-
@joejdrums
Do you mean data array? If I'm not mistaken that actor can only read data in a format made by a data array (= numbers with a space in between and a character return at the end of every data line, I think)
What you need to know is: if the software also sends real time data or it only saves it in a file.
If it only saves it as a text file maybe you can read that text file with a javascript actor and use java to read whatever information is in that file. Best would be Json data.
Every time the Javascript acter is triggered it reads the file again. So if the data change in the text file you should have a "nearly live" connection (is that correct @DusX ?). -
@gertjanb: It sounds like a data array actor then. I do not know, but thanks for pointing me in the right direction. As I'm understanding it currently the software the student is using will save it as a file, not sending in real time but that would be even cooler.
If a file then that into javascript actor. confused about json data. are you saying to somehow turn a .text file into json data and then into javascript actor?
Also, lets just say the software that was converting the geiger send could send real time. Would that be back to the OSC solution that first came in?
-
@joejdrums
I'm not an expert on Json data (DusX is) but from what I know, you can save Json data in a text file and read it with the javascript actor.
I think there are other ways of importing Json but i never had the need of using it before.OSC would only be possible if the other software can send osc. And if it is an industrial software i doubt it will have an osc function.
-
@gertjanb: so the javascript actor inserted in place of the OSC Listener in the patch shown above?
-
@joejdrums
Your javascript will have an array it sends out, so you will have multiple outputs. These outputs can be a value or text.
If its a value you can swap it for the osc listener in the patch above. (you probably won't be needing the limit scale value because you can do that in your javascript.)
-
@gertjanb: Looks like the software the student is using does send OSC information. Real time looks possible if desired.
-
Update. The workflow is as follows. Homemade Gieger meter is sending analog signal through a digital converter into a computer running LabView. LabView can run NI OSC library in it so we should be able to get a live send from LabView into Izzy!
Questions- How to pull in the OSC message via the network into the OSC Listener? Izzy will more than likely be running on one machine and LabView will be sending on another. I recall an actor called OSC Receiver but cannot find it? How does Izzy "receive" the send from LabView's OSC output?
-
@gertjanb said:
Every time the Javascript acter is triggered it reads the file again
The reading of external files can be done 2 ways. Using the Read() and Include() functions.
Include must be the first line of your code, and will simply include the text in the file passed to it as additional Javascript. (parsed inline with your code after).
Read can put the text content of a file into a variable. This one can be used on command.
If using Include(), the command is run on Initialization of the javascript actor (this can be triggered via a User Actor on/off if within an user actor)
Read() can be called as part of a function. I wouldn't suggest calling it constantly (this will be a slowdown to the system), rather use a trigger input to call the function containing Read() when required.
Either of these can help you with reading JSON, but I would recommend Read() for getting data, and Include() for code Libraries (CSV parsing libs, XML parsing libs etc..)
-
@dusx: Thanks! That will be very helpful if we deal with files. Trying to understand how to have OSC listener "hear" the network send from LabView in real time?
-
open the communication menu --> stream setup --> and click on auto-detect input. The source machine has to send to the IP address of the receiving computer.
Best Michel
-
@jetjaguar said:
@dusx: Thanks! That will be very helpful if we deal with files. Trying to understand how to have OSC listener "hear" the network send from LabView in real time?
You basically need to know the IP address and the port number it is sending to.
It's a little hard to explain how this work over text/written words.
-
also> check the OSC port number in Preferences. it needs to be the same as the one being used by your interface application to send the OSC. i think i remember correctly that the default is 1234. if you change it in Izzy, you need to restart Izzy for it to take effect. and> OSC coming into Izzy needs to start with a forward slash.
-
A tutorial I did for TouchOSC and Isadora. The methods are the same, just pretend Touch OSC is instead LabView (....kinda)
-
Excellent! Will play with all of this over next week or so, great community of support for Izzy.
-
@dusx- Could you explain this more? It is looking more like a live OSC send will not work with the hardware we have available. When you say Read () and Include (). What are you putting that into, a text file? what actor are you using to get the info into Isadora? Javascript actor? Thanks.