Sign up Calendar Latest Topics
 
 
 


Reply
  Author   Comment   Page 6 of 15     «   Prev   3   4   5   6   7   8   9   Next   »
Dave Thaler

Registered:
Posts: 414
Reply with quote  #76 
Quote:
Originally Posted by Drachondius
AT LEAST I can see the colours changing now when i turn shields on and off. And they don't stay i.e. green... but they are still the wrong colour.


If you see wrong colors even without Artemis Bridge Tools, then something is probably wrong in your DMXcommands file.   When using Artemis Bridge Tools, you can use the Validate button on the command editor to check for common problems.   Otherwise, if you post a link to your DMXcommands file here in the forums, one of us might be able to help debug it if the problem is in there.
woolfben

Registered:
Posts: 4
Reply with quote  #77 
Hi,

First off, awesome tool! This was a definite factor in choosing colour capable bulbs for my first foray into smart home lights [smile]

I picked up a couple of LIFX Original bulbs for fairly cheap, but I'm having trouble getting them to play nicely. Bridge Tools picks the bulbs up fine in Associated Output Devices, and the Test button there changes the colours of the right bulb, but when I test an actual profile, the bulbs don't do anything. The emulator changes colours as expected, so I think the profile is OK, and the bulbs respond perfectly to the LIFX app. I have the same problem from both of my computers, with wired and wireless connections. Any ideas?
Dave Thaler

Registered:
Posts: 414
Reply with quote  #78 
Quote:
Originally Posted by woolfben
Bridge Tools picks the bulbs up fine in Associated Output Devices, and the Test button there changes the colours of the right bulb, but when I test an actual profile, the bulbs don't do anything. The emulator changes colours as expected, so I think the profile is OK, and the bulbs respond perfectly to the LIFX app. I have the same problem from both of my computers, with wired and wireless connections. Any ideas?


When you say the emulator responds, do you mean when you change the command profile to use emulated DMX lights rather than the LIFX bulbs?

Some ideas of other things to try if you haven't already:
  • Does the "Validate" button on the command editor screen report anything unusual?
  • Do the LIFX lights respond to changes in the the "Test Active..." dialog?
  • Does it work if you only use a single LIFX light?
Dave Thaler

Registered:
Posts: 414
Reply with quote  #79 
Quote:
Originally Posted by Dave Thaler
If you see wrong colors even without Artemis Bridge Tools, then something is probably wrong in your DMXcommands file.


Drachondius, another possibility if you see wrong colors is that you might have a light that use a color order other than RGB.  In the Device Configuration screen, you can change the color order of each light to any other order (GBR, BRG, etc.).
woolfben

Registered:
Posts: 4
Reply with quote  #80 
Quote:
Originally Posted by Dave Thaler


When you say the emulator responds, do you mean when you change the command profile to use emulated DMX lights rather than the LIFX bulbs?

Some ideas of other things to try if you haven't already:
  • Does the "Validate" button on the command editor screen report anything unusual?
  • Do the LIFX lights respond to changes in the the "Test Active..." dialog?
  • Does it work if you only use a single LIFX light?


I have a profile that runs both emulated DMX and the LIFX, yes. Emulated changes, LIFX sit there with no change.

Validate says no problems.

Test Active is what I meant by testing a profile, sorry - so emulator changes, LIFX does nothing.

I tried profiles with one LIFX, both LIFX, and both LIFX with emulator - none of them seem to trigger the LIFX bulbs.
woolfben

Registered:
Posts: 4
Reply with quote  #81 
OK, had a chance today to take a look at the packets being produced with Wireshark. It looks like the MAC address portion of the LIFX packet sent is empty but it's (correctly) tagged as being for a target address. If I send the same packet manually with the MAC address filled in, or change the tag to general broadcast, it works. No idea why the MAC is missing, since it fills it in successfully when using Test in the output devices panel.

Any ideas on what might be the cause?
Dave Thaler

Registered:
Posts: 414
Reply with quote  #82 
Interesting.  LIFX must have changed their firmware recently to be more strict about this, since the bulbs I have work fine even when the MAC address isn't filled in.  Anyway, I've now fixed this in my local copy, and I plan to publish a new version tomorrow that will contain this fix among other things.

Thanks for the detailed analysis!
Cap Naes

Registered:
Posts: 36
Reply with quote  #83 
Dave, this may be related to the error you already discovered, but if it helps here are the issues I've recently had with Lifx bulbs-

I'm using 2 different colored bulbs, identical, (with ALLSEEN support), and have each on different networks (for home games vs portable games).

Initially, (2 months ago) everything worked like a charm on the first bulb set-up.

A few weeks later while trying to setup the second bulb I spent hours having bridgetools be unable to even detect the bulb, while verifying that everything was working properly through the lifx app, and network settings were all appropriate. I reset the bulbs and the game multiple times, and eventually used a second computer that it worked on. Meanwhile I had lost the ability to connect to the first one as well. After wiping and reinstalling both artemis and bridgetools from the original computer, it started working again. Interestingly I would have intermittent issues with both bulbs (on either network) from either computer, sometimes detecting a bulb and sometimes not. I've never been sure why, or what I ever did to successfully fix it.

Just this week while bulb #1 is working fine (as are conventional DMX lights when I switch profiles- I don't yet use them together), but I could not for the life of me get bulb #2 to be detected (not visible at all in the output device section). Eventually I tried searching for it as an older "not-ALLSEEN" compatible bulb with 3 channels, and it actually worked. This is currently where I am at: I have bulb #1 on network 1 that works as a 4 channel alljoyn light, and an identical bulb #2 on network #2 that only works as a 3 channel "lifx" bulb, and is not discoverable as alljoyn. Again, both bulbs work normally with the lifx app, and both are fully firmware updated (although updated several months apart).

I have no idea what the issue here is, but it seems to be an intermittent inability for bridgetools to identify my bulbs on the network. Once they are detected though, I have had no troubles with running them in test mode or a game. Obviously, if they are not visible to bridge tools, they don't work at all. And for the record, when they are working, they work great!

Thanks.


Dave Thaler

Registered:
Posts: 414
Reply with quote  #84 
Artemis Bridge Tools v3.3 is now released.  Changelog:
  • Added ability to play a video on a specified monitor (attached to the server, or main screen computer of another ship) in response to a DMX cue (requested by AmnonLiu)
  • Added a way to cancel a video played by a mission script or socket command
  • If Artemis is upgraded to a newer version than the one Artemis Bridge Tools understands the protocol for, protocol parsing will be skipped rather than potentially crashing
  • Fixed bug with (non-AllSeen) LIFX bulbs
  • Fixed display of "Change" button in Artemis DMX Editor when a timeblock has devices of different media types (e.g., both audio and lights)
LawsonThompson

Registered:
Posts: 505
Reply with quote  #85 
Quote:
Originally Posted by Dave Thaler
Artemis Bridge Tools v3.3 is now released.  Changelog:
  • Added ability to play a video on a specified monitor (attached to the server, or main screen computer of another ship) in response to a DMX cue (requested by AmnonLiu)


Aaaand there goes all my spare evenings as I being crafting a myriad of custom AVI files and adding monitors to my bridge setup! I have big ideas for this feature...

Thanks, Dave!

__________________
----
Visit us at http://www.ltebridge.com
Dave Thaler

Registered:
Posts: 414
Reply with quote  #86 
And a note for anyone with Artemis 2.5.1 regarding this recent change to Artemis Bridge Tools:

  • If Artemis is upgraded to a newer version than the one Artemis Bridge Tools understands the protocol for, protocol parsing will be skipped rather than potentially crashing
According to the TSN Nexus site, version 2.5.1 apparently works fine with Artemis Bridge Tools already, but since I don't have 2.5.1 it wasn't marked as one that it understands the protocol for.   Artemis Bridge Tools can be configured to work with any version of Artemis (i.e., enabling protocol parsing anyway) via the following method.  In the next version I'll add an option from the UI, and also update it to accept 2.5.1 as already tested, but didn't get to it yet so here's the workaround to use it with Artemis 2.5.1.

Run Artemis DMX Editor, do File->Open File Location.  Right click "DmxDevices.xml", select Edit.  Change this line:
<DMX_DEVICES>
to this:
<DMX_DEVICES alpha="true">,
notsabbat

Avatar / Picture

Registered:
Posts: 1,163
Reply with quote  #87 
I have been playing on 2.5.1 and it seems to work fine.



__________________
-Captain of the TSN Gungnir JN-001
-Eastern Front online group member
-My continuing bridge build:
http://artemis.forumchitchat.com/post/immersion-bridge-build-in-progress-7335195?pid=1290158413
woolfben

Registered:
Posts: 4
Reply with quote  #88 
Quote:
Originally Posted by Dave Thaler
Artemis Bridge Tools v3.3 is now released.  Changelog:
  • Added ability to play a video on a specified monitor (attached to the server, or main screen computer of another ship) in response to a DMX cue (requested by AmnonLiu)
  • Added a way to cancel a video played by a mission script or socket command
  • If Artemis is upgraded to a newer version than the one Artemis Bridge Tools understands the protocol for, protocol parsing will be skipped rather than potentially crashing
  • Fixed bug with (non-AllSeen) LIFX bulbs
  • Fixed display of "Change" button in Artemis DMX Editor when a timeblock has devices of different media types (e.g., both audio and lights)


Tested it out today, bulbs working beautifully now, thanks! Looking forward to giving them a spin in an actual game sometime soon! [smile]
BillCat

Registered:
Posts: 7
Reply with quote  #89 
I'm trying to get ABT 3.3 working with my uDMX setup. I've downloaded the latest uDMX drivers, and both FreeStyler and the uDMX configuration tools can see the single par can light and turn the LEDs up and down, select colors etc etc. As a result, I'm pretty sure I've got the lights and DMX addressing part of things right. The fact that FreeStyler works, tells m the interface works, but I can't seem to get ABT to impact them at all.

Can you please let me know which version of the uDMX drivers ABT 3.3 was tested with? I'm going nuts here trying to make this work, and I don't know what else to try.

Dave Thaler

Registered:
Posts: 414
Reply with quote  #90 
Quote:
Originally Posted by BillCat
I'm trying to get ABT 3.3 working with my uDMX setup. I've downloaded the latest uDMX drivers, and both FreeStyler and the uDMX configuration tools can see the single par can light and turn the LEDs up and down, select colors etc etc. As a result, I'm pretty sure I've got the lights and DMX addressing part of things right. The fact that FreeStyler works, tells m the interface works, but I can't seem to get ABT to impact them at all.

Can you please let me know which version of the uDMX drivers ABT 3.3 was tested with? I'm going nuts here trying to make this work, and I don't know what else to try.


uDMX is listed on the ABT web site with "(needs testing)" which means no one with an actual uDMX controller has, to my knowledge, tested it since ABT v1.9 when it was first added, and so there may be a bug.   I implemented support based on the uDMX spec but I don't have access to a uDMX controller to test it with. 

The version of the uDMX drivers it was tested with (without a controller) was udmx.dll version 1.0.0.3.  If you're willing to keep trying, I can work with you offline to figure out the issue and get udmx support working.
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.