chris.cytexone

As an added FYI, this is the Global Cache device I'm using:

https://www.amazon.com/Global-Cache-iTach-Flex-IP/dp/B00C6FRPIC

Yes, it was set to 115200.

That's what enabled me to read the firmware of the DMX Engine from the v2 driver. However, if I try to send it any commands to control the DMX (eg, All Channels On/Off), nothing happens.

1 hour ago, poisenoire said:

Chris,

 

I'm interested in  your GC response as I am running a GC itach w/ dual output DMX box but still on old firmware.  My installation requires the GC itach due to location constraints, so won't be upgrading until I see what you come up with!

 

 

GC didn't have much to say, they were actually surprised the device isn't working properly. There is something of note with the iTach Flex. Apparently they had a version 1 Flex Serial Cable and a version 2. Version 2 is only certified for 57600 and 115200. He didn't have an exact science to confirming my cable other than to look at it. The RS232 end should have "RS232" in the plastic molding of both sides of the connector. That's how you know you have a version 2.

I do have a Version and it still wouldn't work. As soon as I switched over to an HC250, everything worked perfectly. So unfortunately unless Jack has more to add/troubleshoot with the GC, I'm sticking with the HC250. I brought the GC back to my office for future testing if I'm given any other way to diagnose this from Jack.

10 minutes ago, jackstone said:

Do you have the single output red dmx engine or the dual ouput? (With two xlr connectors)

Dual output, I'm on-site now and you were dead on with your suspicions. The Global Cache iTach Flex seems to be the issue. I was able to get it working with an HC250 instead of the GC device. I'm going to leave as is, but would love to be able to get the GC device working. I'm going to call Global Cache about this but if you have any other ideas on how I can get it working with the GC device that would be greatly appreciated.

Thanks for all the help Jack!

12 hours ago, jackstone said:

Ok... so 1: retry the "get firmware" action and see if it can still get the firmare version.

2: confirm if you have a single output DMX engine or the dual output model, chance the new firmware does not work with the older single output version of the engine.

3: if you have the older engine, then yes you can revert to the driver version 1.5 but don't try to revert the baudrate to 9600, send me an email and i will send you a modified version of 1.5 that run at 115200bps, you will not get the new features of v2.x but it will react bit faster than before.

1. Performing "Get Firmware" action produces "Online (Firmware v5.071)". However, after a few moments the status changes back to "Offline. Check DMX Engine connection."

2. It's a dual output DMX engine: https://response-box.com/gear/2016/10/announcing-the-rs-232-driven-double-dmx-engine/

3. I have two engines available, one on-site with the new firmware at 115200bps. One in my lab with the new firmware at 9600bps (was going to bring it back onsite this morning to try some stuff out).

Here's the LUA output when I hit the "Get Firmware" command:

Started Standard DMX: 3
System Is Active & Feelin' Groovy
Handle Command: www.response-box.com/gear
Handle Command:  * *  RS-232 Double DMX Engine  * *
Handle Command: Firmware v5.071
Handle Command:
Handle Command: Started Standard DMX: 3
Handle Command: System Is Active & Feelin' Groovy
Last command done
ReceivedFromSerial(), idBinding = 1, strData = Startup Scene:  None, Delay:  None
Handle Command:
Handle Command: Startup Scene:  None, Delay:  None
Last command done
Recovering from buffer...
Function:	SendToSerial(1, Z053@000,077@000,073@000,063@000,047@000,037@000,067@000,057@000,212@000,027@000,017@000,013@000,023@000,042@000,052@000,062@000,072@000,036@000,046@000,056@000,066@000,239@000,092@000,040@000,210@000,016@000,025@000,201@000,012@000,022@000,083@000,071@000:000):
Sending Command...
Function:	SendToSerial(1, Z061@000,085@000,075@000,065@000,090@000,091@000,035@000,059@000,049@000,039@000,029@000,099@000,089@000,079@000,110@000,001@000,218@000,003@000,002@000,005@000,004@000,007@000,006@000,009@000,008@000,135@000,097@000,031@000,021@000,011@000,096@000,060@000:000):
Sending Command...
Trying to reconnect...
ReceivedFromSerial(), idBinding = 1, strData = Syntax erro
Last command done
ReceivedFromSerial(), idBinding = 1, strData = r
10
Handle Command: Syntax error
Syntax error	Bad command is:  Z061@000,085@000,075@000,065@000,090@000,091@000,035@000,059@000,049@000,039@000,029@000,099@000,089@000,079@000,110@000,001@000,218@000,003@000,002@000,005@000,004@000,007@000,006@000,009@000,008@000,135@000,097@000,031@000,021@000,011@000,096@000,060@000:000
Handle Command: 10
Last command done

Let me know what you think, thanks.

25 minutes ago, jackstone said:

Don't revert to 1.5, v2 work best and i'm sure we can dig out what is your issue... so now you can see the dmx engine firmware? Havr you tried the action/all on and see if your dmx lights turns on?

Yes, I've tried that command under the driver, nothing happened on the lighting end. 

On 9/15/2017 at 10:47 AM, PaulYork said:

No I Haven't, how do you do that?

Curious to see what you come up with Paul. I've unfortunately had nothing but difficulties with the v2.0 driver.

I was able to get everything working perfectly with the 1.5 driver (DMX control, was able to cycle the colors on the LED strip, etc). Not satisfied being on an older version, I've been trying to work with Jack over e-mail to resolve my issues (HouseLogix is near useless, they refer me to Domaudeo aka Jack). Like he is saying, the baud rate driver is key (although it's not mentioned in the main documentation, when you add the driver in it has its own documentation tab). Connect the engine to this driver and hit the action button on the driver to change the engine's baud speed from 9600 to 115200 (note, you need to power cycle the engine after this).

Once I did that, I was able to switch the binding to the V2 driver (it was able to talk to the engine and retrieve the firmware). However, now I'm stuck with no DMX control. I had functional control of LED colors under 1.5 and now since updating to the 2.0 driver it's broken. I've verified the DMX ID's are back in as they should be and nada, nothing. I've actually been trying to figure out how to revert back to the 1.5 driver (to see if it starts working again and confirm the issue I'm solely having is with v2). I found the proper serial command to change the engine back to 9600 baud so now I just need to go back onsite to test with the legacy driver.

I'll provide an update once I have more.

Composer Pro is only available for download from Control4's Dealer Site. You CANNOT download Composer Pro legally from anywhere but Control4's Dealer Site.

Please refrain from requesting a download link to Composer Pro. If a member makes a request for this software, they will be issued one warning and the offending topic will be locked. If a member violates this rule again, they will be banned.

For those long-time members who already know this rule, please spread the word. Whenever an OP requests a download link to Composer Pro, please refrain from egging them on by suggesting a Torrent site or posting an unrelated link that is meant to cause the OP distress. There's no need to get in to "the download is useless without a login." Just keep it simple -- simply inform the OP that Composer Pro is only for certified Control4 Dealers and can only be obtained from Control4's Dealer Site.   Composer Pro = Dealer Only. If they come here asking for the software, they're clearly not a dealer.

DO NOT POST ANY LINKS TO COMPOSER PRO SOFTWARE THAT ARE REAL OR FAKE. YOU WILL BE BANNED WITHOUT WARNING.

Sorry for the CAPS but I had to make sure everyone understands that this will not be tolerated. Thank you all for your help and understanding with this matter. It is much appreciated. Enjoy the forums!