E1.31 Driver Questi...
 
Notifications
Clear all

E1.31 Driver Question

6 Posts
4 Users
0 Reactions
2,030 Views
Posts: 87
Topic starter
(@tfmacz)
Estimable Member
Joined: 19 years ago
[#39994]

As I understand it, when you are using the E1.31 driver in Vixen 3.2u2 The data stream is continuous.

Thus the network led is flickering constantly.

During my show the E1.31 data stream stops for up to 3 seconds. No flickering on the network interface and the show freezes.

is there a way to get an error log from the E1.31 driver? Is this a PC issue? It is a 2gig dual core athlon with 8 gigs of ram.

The Vixen memory display shows a couple gigs free and CPU use at around 30 - 40%.

Any Ideas???


5 Replies
jchuchla
Posts: 8698
(@jchuchla)
Illustrious Member
Joined: 15 years ago

There's no logging for this specifically. Logging every packet would be way too much to keep up with.
Typically this kind of symptom is indicative of a system that is pushed well past its capabilities. You could monitor the stream with sacnview. Ideally you'd do this from a separate computer so as to not further burden the struggling one. But this isn't going to tell you much more than you can already see with the blinking light on the controller.
The problem is not likely the streaming ACN output module. It's more likely the execution engine getting data prepared and into that module. Intermittent pauses are usually a garbage collection issue. Vixen will reach a point where it consumes all of the available memory and needs to dispose of things it's done with and compact the space to make room for new data. This happens when .net says it needs to and is outside of the control of vixen. More ram would decrease the frequency of garbage collections. And a better processor could help the collections happen faster.
You can also review your sequences and configuration to make sure it's set ho efficiently and not wasting resources that you don't have. The things to be looking for are unused output channels. If you're not using them, get rid of them. Don't define full universes if you're only using part of them. Don't start new universes for each output on the controller. If your controller supports spanning universes, use continuous channel ranges and fill the gaps.
If your sequences are imported sequences, make sure you've properly gone thru them and converted as much as possible over to proper V3 effects and methods. The importer gives you a great starting point, but it leaves a mess of tiny simple effects that usually should be cleaned up into proper v3 effects.
You can view the instrumentation panel in vixen and monitor the rates of each controller. If you're running default update interval, you should see the rate of the controller at a steady 20 frames per second. If it's frequently dipping by more than 1 you have performance issues. Your computer can't keep up with what vixen is pumping thru.
AMD processors often show performance issues long before Intel processors.

--Jon Chuchla--

Sent from my iPhone using Tapatalk


Reply
Posts: 384
(@burtonmadness)
Honorable Member
Joined: 14 years ago

If you are running multicast and have another PC (or laptop), you could run wireshark to capture the output filtering on the either the E1.31 addresses or the src address of your PC.

If running unicast, you will need a port mirroring switch to perform the same and confirm no data from the PC.

/BM


Reply
jchuchla
Posts: 8698
(@jchuchla)
Illustrious Member
Joined: 15 years ago

Also worth looking into is if you're using wifi. I know you mentioned a wired controller. But that doesn't rule out a wireless bridge or something you might be using in between. The problems could be in the wifi link.

--Jon Chuchla--

Sent from my iPhone using Tapatalk


Reply
Posts: 87
Topic starter
(@tfmacz)
Estimable Member
Joined: 19 years ago

Thank you for your explanation. I have reduced the channel counts on the E1.31 controller interface to only the necessary channels. This has helped substantially. All my sequences are imports from V2. I have gone through all of them to update the effects but there are a couple substantial sequences that have no equivalent effect in V3. They were created with a V2 add-in called Waveform. I have not found a way to do a similar effect in V3.
This is why I like Vixen. all the support.
Thanks for your help.


Reply
Posts: 366
(@technician)
Reputable Member
Joined: 12 years ago

I had a router do that like clockwork, run freeze run freeze. ACN View showed exactly what the lights did. A sub router worked fine. This was in a Multicast over WiFi link. That router was from last year so I don't remember make, model, and firmware version. It was G54 and the replacement is too, but an older Buffalo brand. I use it because I can run on 2.0.0.X and 10.0.0.X networks. Many routers are locked to 192. and net mask of 255.255.255.X


Reply
Share: