Dual network, not sending to Net 1

 

Although I have not tried Borealis on the show server, on my tablet after each song, the solid light blicked twice, then went solid for the next song. The same thing for when the show looped. I started and stopped the show a few times, all went well on the tablet. I'd expect the same for the show server. I'll test it on the server ths weekend. :)

 

The net dropping is obnoxious for testing, but not show stopping.

 

Seems like it may be a good idea to do a socket open on run/start, then close on end, just leave it open until a stop event. Also, possibly close/clear on application start? Not that I'm trying to tell you how to work. -- Just a thought I had.

 

Hmmm... I think I can see in the code how this could happen in Aurora, but I do not believe it should affect Borealis during a real show.  You might want to reboot and check Borealis to make sure I'm correct though.

 

Although I can't replicate it here, I believe each loop iteration is rapidly closing/reopening the COM port (instead of holding it open like it should) and the COM driver on your system isn't keeping up.  More specifically, the driver is writing commands from the buffer to the line when the close request comes in (so the buffer has to finish dumping before the close completes), but the open request arrives before the buffer is emptied.  I've seen this situation generate a race condition in the FTDI COM Emulation drivers before.  It puts the adapter into a state where it isn't open, but it isn't closed either.  Sometimes replugging the adapter (with Aurora closed) will reset it, but other times a full reboot is required.

 

We have a fix for the race condition in beta (it was developed as a part of 1.2), but it is far to extensive to successfully roll out for this season.  I'm looking at a simpler patch for this specific issue (improve the COM reset logic so the line holds during looping).  I have a note which says the current reset was put in place due to a Vista issue, so I may have to do a bit of testing to figure out what is going on with Vista before fixing this.

 

I added a single channel to Net1 Controler1 channel 1, then I added Net1 IDE0 (something high), then Net4/4/1, then Net 4/E6/1.

 

Once the network is lost, Aurora does need to be closed out, then restarted to get it back.

 

I also just tried a install/repair, got a message about msxml being locked.

currently there is one physical controllers on each network (ACx16), and thre are six ACx16s configured for each network.