cybuch

On 3/10/2017 at 10:32 AM, jackstone said:

For those interested, we've done a minor update over the V2 DMX Driver, it adds a new feature that many people may find useful: RGB Dimmer auto-rename.

Are you tired of renaming all the child dimmers of your RGB dimmers? Then just click "Auto-rename" and it'll rename the three child drivers automatically based on the Master:

THANK YOU!!!!

 

7 hours ago, txfanatic said:

what would higher quality ones cost?  And what brands should i look at?

I bought all my up lights from @jackstone, they are more than $50 each, but I am extremely happy with them. I added a picture, so you can see how bright they are. 

I too, ran wires and conduit all over my landscape for all the lights and I can control each individually.  I even added some pixels (via Falcon F16v2) to my backyard around my pool and bar area and control them via xLights/xSchedule, in C4.   The pool lights are animated, thats why you don't see them all lit at once.

 

 

@jackstone, I finally got my issue figured out on the update.  It turns out my USB to RS232 adapter wasn't syncing correctly with the DMX Engine.  I picked up a Parallax USB to RS232 and it worked a charm.  I do have a question about the new drivers, can I just update my current drivers with the new ones?  Or do I have to install these new ones and reconfigure all the channels?

 

 

No, its a newer dual, I emailed him, but thought I would check here just in case.  I have two of them, and they are doing the same thing.

I am getting a strange error when I upgrade the firmware....it says..checking....loading....verifying.... and then I get an error "Propeller chip lost on COM5" and doesnt finish the update.   Any thoughts?

 

Just downloaded it.  I will have to update my 2 and a customer's.  Looking forward to the new drivers!  And thank you for including the update software!

@jackstone, AWESOME!!!!  Do you know what the firmware version is for the DMX engine?

On 12/21/2016 at 3:05 PM, jackstone said:

I did not know about this one, but it seems somehow pretty similar to LOR, and not so hard to integrate... Yes, writing a driver for this is something feasible. I don't know how it perform though but LOR is a rock solid performer even when used through Control4, impressive system for the price.

If someone is interested to have a driver for E1.31 please let us know, I may work on that next year if there is some interest...

I am interested if you can create one.  I am in the process of switching over to pixel leds for my landscape lighting as well as dumb RGB (BTW, those light you sent me kick a$$!).  I am running everything through a few Falcon F16v2 controllers and I am currently running Vixen for control.  I can change the scene with a http request, but it would be so much better if I could control it directly with C4.

My run fine with those settings. I am running the PX24500 decoders.

@jackstone sent you a PM

Hey @jackstone I need to order 19 more of those outdoor RBGW lights.  I sent you a PM

@jackstone have you developed an E1.31 lighting driver or plan to, since you did one for LOR?  

You may have to adjust the volume depending on the song or type of music to get it to work the way you want.

I had nothing but trouble using the IP2SL with that setup, everything was much better when I switched to wired.  Worth the work to get the line there!

I replaced all my current landscape lighting with RGBW wall washers (from Jackstone of course) and I don't have to switch anything when I do holiday lights (xmas, halloween, 4th of july, etc)  I just set them to WW when its a normal day.

2 hours ago, jackstone said:

We are planing to release a new version of the driver within the next few weeks and you will get a whole new way to customize the Chase with the color you want, really easily. Random Loop will also get the same custom option with a nice Color Picker to chose the precise color you want.

Sorry for keeping you waiting but the next release is a complete new build on certain drivers part of the suite and need more work than expected. You will get the features you requested, you can count on it.

Awesome!!!  Looking forward to it!!

Thats what I was afraid of, but you gave me a good solution.

I would really like to see the chase scene be able to incorporate any color I want, the use current levels doesnt seem to work correctly, I may not know enough about the driver.  I would also like to do random loop, multiple colors with the pallet I choose, not just the presets.  

Does anyone know of PC software that is compatible with the Engineering Solutions DMX engine?  I would like to create some more advanced lighting scenes for the holidays, and then switch back to C4 to control every day stuff.  I was looking at Vixen 3 but I can't seem to find anywhere in the documentation what hardware is compatible.  Any help is greatly appreciated.

I have to say @jackstone,the sound to light driver kicksass!!! I can't wait to get the new outdoor lighting to add to it!!  By far, the best experience for lighting outdoors with music!!

1 hour ago, jackstone said:

Thanks. We are currently working on a new version that will separate the Sound-to-Light feature from the effect switch, thus will enable some more complex effects to be done using sound triggering.

I am more than happy to beta test!

I have to say @jackstone,the sound to light driver kicksass!!! I can't wait to get the new outdoor lighting to add to it!!  By far, the best experience for lighting outdoors with music!!

I have two different voltages running my outdoor lights, the first is a 12volt and the 2nd is a 24volt.  They are all installed in my garage, I have a pic in this thread.  I found this wire to work really well.  I home runned every light, lots of work but worth it.  The gauge depends on your load at the end of the wire run.  

as always, thank you @jackstone, I will give it a shot and see how it does.  I also want to order those IP67 RGBW lights, who should I contact?

On 10/23/2016 at 9:58 AM, jackstone said:

This mean an hardware error with the DMX Engine. I saw some rare boxes that does not handle heavy traffic from the Control4 driver, this should be resolved with the new driver that will operate a higher baud rate, else if you can reproduce the issue steadily, you can get a DMX Engine replacement either from Houselogix or Engineering Solutions.

It locked up again last night.  Says deca box off line.  Here is the LUA output when I try to turn all channels off, but nothing changes:  Its strange that it only started happening when I pulled it off of wireless and updated to 2.9.  Do you think I should try it on the EA5 instead?

Function:    ExecuteCommand(LUA_ACTION):

ACTION

Function:    ExecuteCommand(Blackout):

Function:    SendToProxy (2, STOP_ALL_FADE):

Function:    SendToSerial(1, F000@000:000):

Handle Command: Done

Function:    SendToProxy (2, BLACKOUT):

 

Here is a scene that doesn't work while locked up:

 

 

Received from Proxy: SEND_TO_DMX on binding 2; Call Function SEND_TO_DMX()

Function SEND_TO_DMX

Function:    SendToSerial(1, Z052@255,056@255,060@255,064@255,068@255,072@255,076@255,080@255,084@255,088@255,092@255,096@255:000):

Received from Proxy: SET_PROXY_LEVEL on binding 2; Call Function SET_PROXY_LEVEL()

Function:    SET_PROXY_LEVEL:

Function:    SendToProxy (2, LIGHT_LEVEL):

Received from Proxy: SET_PROXY_LEVEL on binding 2; Call Function SET_PROXY_LEVEL()

Function:    SET_PROXY_LEVEL:

Function:    SendToProxy (2, LIGHT_LEVEL):

Received from Proxy: SEND_TO_DMX on binding 2; Call Function SEND_TO_DMX()

Function SEND_TO_DMX

Function:    SendToSerial(1, Z004@255,008@255,012@255,016@255,020@255,024@255,028@255,032@255,048@255:000):

Received from Proxy: SET_PROXY_LEVEL on binding 2; Call Function SET_PROXY_LEVEL()

Function:    SET_PROXY_LEVEL:

Function:    SendToProxy (2, LIGHT_LEVEL):

Received from Proxy: SET_PROXY_LEVEL on binding 2; Call Function SET_PROXY_LEVEL()

Function:    SET_PROXY_LEVEL:

Function:    SendToProxy (2, LIGHT_LEVEL):

Received from Proxy: SEND_TO_DMX on binding 2; Call Function SEND_TO_DMX()

Function SEND_TO_DMX

Function:    SendToSerial(1, Z036@255,040@255,044@255:000):

Received from Proxy: SET_PROXY_LEVEL on binding 2; Call Function SET_PROXY_LEVEL()

Function:    SET_PROXY_LEVEL:

Function:    SendToProxy (2, LIGHT_LEVEL):

Received from Proxy: SET_PROXY_LEVEL on binding 2; Call Function SET_PROXY_LEVEL()

Function:    SET_PROXY_LEVEL:

Function:    SendToProxy (2, LIGHT_LEVEL):

Received from Proxy: ACTIVATE_SCENE on binding 2; Call Function ACTIVATE_SCENE()

Function:    SendToSerial(1, Z103@255,100@255,104@255,097@255,101@255,105@255,098@255,102@255,099@255:000):

Received from Proxy: SEND_TO_DMX on binding 2; Call Function SEND_TO_DMX()

Function SEND_TO_DMX

Function:    SendToProxy (2, STOP_EFFECT):

Function:    SendToSerial(1, Z001@255,005@255,009@255,013@255,017@255,021@255,025@255,029@255,033@255,037@255,041@255,045@255,049@255,053@255,057@255,061@255,065@255,069@255,073@255,077@255,081@255,085@255,089@255,093@255,002@255,006@255,010@255,014@255,018@255,022@255,026@255,030@255,034@255,038@255,042@255,046@255,050@255,054@255,058@255,062@255,066@255,070@255,074@255,078@255,082@255,086@255,090@255,094@255,003@255,007@255,011@255,015@255,019@255,023@255,027@255,031@255,035@255,039@255,043@255,047@255,051@255,055@255,059@255,063@255,067@255,071@255,075@255,079@255,083@255,087@255,091@255,095@255:000):

Command queued Z001@255,005@255,009@255,013@255,017@255,021@255,025@255,029@255,033@255,037@255,041@255,045@255,049@255,053@255,057@255,061@255,065@255,069@255,073@255,077@255,081@255,085@255,089@255,093@255,002@255,006@255,010@255,014@255,018@255,022@255,026@255,030@255,034@255,038@255,042@255,046@255,050@255,054@255,058@255,062@255,066@255,070@255,074@255,078@255,082@255,086@255,090@255,094@255,003@255,007@255,011@255,015@255,019@255,023@255,027@255,031@255,035@255,039@255,043@255,047@255,051@255,055@255,059@255:000

Function:    SendToProxy (2, LIGHT_LEVEL):

Function:    SendToProxy (2, LIGHT_LEVEL):

Function:    SendToProxy (2, LIGHT_LEVEL):

Received from Proxy: SEND_TO_DMX on binding 2; Call Function SEND_TO_DMX()

Function SEND_TO_DMX

Function:    SendToProxy (2, STOP_EFFECT):

Function:    SendToSerial(1, Z001@255,005@255,009@255,013@255,017@255,021@255,025@255,029@255,033@255,037@255,041@255,045@255,049@255,053@255,057@255,061@255,065@255,069@255,073@255,077@255,081@255,085@255,089@255,093@255:000):

Function:    SendToProxy (2, LIGHT_LEVEL):

Function:    SendToProxy (2, LIGHT_LEVEL):

Function:    SendToProxy (2, LIGHT_LEVEL):

Received from Proxy: SEND_TO_DMX on binding 2; Call Function SEND_TO_DMX()

Function SEND_TO_DMX

Function:    SendToProxy (2, STOP_EFFECT):

Function:    SendToSerial(1, Z002@255,006@255,010@255,014@255,018@255,022@255,026@255,030@255,034@255,038@255,042@255,046@255,050@255,054@255,058@255,062@255,066@255,070@255,074@255,078@255,082@255,086@255,090@255,094@255:000):

Function:    SendToProxy (2, LIGHT_LEVEL):

Function:    SendToProxy (2, LIGHT_LEVEL):

Function:    SendToProxy (2, LIGHT_LEVEL):

Received from Proxy: SEND_TO_DMX on binding 2; Call Function SEND_TO_DMX()

Function SEND_TO_DMX

Function:    SendToProxy (2, STOP_EFFECT):

Function:    SendToSerial(1, Z003@255,007@255,011@255,015@255,019@255,023@255,027@255,031@255,035@255,039@255,043@255,047@255,051@255,055@255,059@255,063@255,067@255,071@255,075@255,079@255,083@255,087@255,091@255,095@255:000):

Function:    SendToProxy (2, LIGHT_LEVEL):

Function:    SendToProxy (2, LIGHT_LEVEL):

Function:    SendToProxy (2, LIGHT_LEVEL):

 

This is what I get after a reboot of the engine, but still won't work until I change the RS232 binding and then manually get the firmware version.

 

Received from Proxy: UPDATE_DMX_BUFFER on binding 2; Call Function UPDATE_DMX_BUFFER()

Received from Proxy: UPDATE_DMX_BUFFER on binding 2; Call Function UPDATE_DMX_BUFFER()

Received from Proxy: UPDATE_DMX_BUFFER on binding 2; Call Function UPDATE_DMX_BUFFER()

ReceivedFromSerial(), idBinding = 1, strData = Done

Done

Handle Command: Done

Last command done

Function:    SendToProxy (2, ENGINE_READY):

Handle Command: Done

Last command done

Function:    SendToProxy (2, ENGINE_READY):

ReceivedFromSerial(), idBinding = 1, strData =       * *  RS-232 Double DMX Engine  * *

        www.response-box.com/gear

Handle Command:       * *  RS-232 Double DMX Engine  * *

Handle Command:         www.response-box.com/gear

 

Once I rebind and then reboot engine, I can click get firmware and this is the LUA output and all is right again.

 

Function:    ExecuteCommand(LUA_ACTION):

ACTION

Function:    GetFirmware():

ReceivedFromSerial(), idBinding = 1, strData = Done

Handle Command:       Done

ReceivedFromSerial(), idBinding = 1, strData =       * *

ReceivedFromSerial(), idBinding = 1, strData =   RS-232

ReceivedFromSerial(), idBinding = 1, strData = Double DM

ReceivedFromSerial(), idBinding = 1, strData = X Engine

ReceivedFromSerial(), idBinding = 1, strData =  * *

Handle Command:       * *  RS-232 Double DMX Engine  * *

ReceivedFromSerial(), idBinding = 1, strData =     www.r

ReceivedFromSerial(), idBinding = 1, strData = esponse-b

ReceivedFromSerial(), idBinding = 1, strData = ox.com/ge

ReceivedFromSerial(), idBinding = 1, strData = ar

Handle Command:         www.response-box.com/gear

ReceivedFromSerial(), idBinding = 1, strData =   Firmwar

ReceivedFromSerial(), idBinding = 1, strData = e v5.02

Handle Command:         Firmware v5.02

ReceivedFromSerial(), idBinding = 1, strData =    System

Handle Command:

ReceivedFromSerial(), idBinding = 1, strData =  Is Activ

ReceivedFromSerial(), idBinding = 1, strData = e & Feeli

ReceivedFromSerial(), idBinding = 1, strData = n' Groovy

ReceivedFromSerial(), idBinding = 1, strData =

Handle Command:    System Is Active & Feelin' Groovy

 

PM sent