sebleedelisle
commented
3 years ago Hey Friso,
Thanks for letting me know about this. My suggestion is :
1 : Let me fix the code so it doesn't throw an error when the laser number is out of range 2 : You can set up the 3 lasers within the app... every time you run it from now on the 3 will be set up. 3 : Choose the relevant etherdream from the dropdown menu in the laser settings (it no longer relies on IP address so will always find the DAC based on its MAC address)
When you restart the app, the etherdream allocation should be remembered by the system. But for now you will have to click the "Refresh controller list" button as it doesn't always find the ether dreams during the start up process. (I will fix this in a later release so that the dac list will be updated automatically as they are discovered).
Hope this helps!
Seb
On Mon, 21 Jun 2021 at 14:15, Friso Modderman @.***> wrote:
Hi Seb, I am working with Gijs on his project.
In the project we use the sendRawPoints on the 3 lasers we have. this method uses the lasernumber as value. Because the lasers cannot programatically be set now with the new version, we can never make sure they are set. Currently I get a vector out of range in the update loop. As the update loop starts running directly after boot and directly tries to send points to a laser that does not exist yet. If we revert the option to programatically set the lasers (with dac (IP) setup) it is again possible to setup the laser setup at application startup. I think this can work the same way as the add laser button in the gui does.
What are your thoughts about this? Greetings Friso
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/sebleedelisle/ofxLaser/issues/25, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAA3CEVAMFZGVV3WH4NKPNTTT43P3ANCNFSM47BR7KKA .
adminfriso
Hi Seb, I am working with Gijs on his project.
In the project we use the sendRawPoints on the 3 lasers we have. this method uses the lasernumber as value. Because the lasers cannot programatically be set now with the new version, we can never make sure they are set. Currently I get a vector out of range in the update loop. As the update loop starts running directly after boot and directly tries to send points to a laser that does not exist yet. If we revert the option to programatically set the lasers (with dac (IP) setup) it is again possible to setup the laser setup at application startup. I think this can work the same way as the add laser button in the gui does.
What are your thoughts about this? Greetings Friso