Ion Sluggish and delayed.

Sorry to hear that you are having problems with delays on your Ion.  Do you mind sending your show and log files to eos@etcconnect.com?  Also, we are aware of some delays when you are in 100 ch mode and a flexi state at the same time.  Be sure that if you are using flexi to not be in 100ch mode.

If this does not fix your problem feel free to call us in Tech Services.

Our hours are 8am - 5pm Mon thru Fri Cent. time. 

Matt

After I did the deep clear the board seemed to be running OK but once I got back into programming and running shows, cues lists and subs, the board went back to having a horrible delay.  I counted 15 second to go from patch to live and the fader wing is a good second behind. So bad that I had 2 touring LD's extremely unhappy and unconvinced that there wasn't a problem.  I really hope I can get this issue resolved because it is slowly becoming ridiculous.

Update....After going threw all the things that I thought may be causing the delay I have stumbled upon a fix for one problem.  I have cured the delay with the Sub-masters / Fader wing.  I unplugged the USB in the back of the fader wing and reset the board and that completley fixed the problem.  Although, the board still has the delay between the Patch, Blind, Live.

False Alarm...the faders are back to being steppy and delayed...crap!

Definitely time to call support!

USA:   +1 800 688 4116

UK:     +44 (0)20 8896 1000

Called a few times.  Sent Log files and was told that they would look in to it.  That was over a week ago.

Hi,

I am very sorry that you haven't received a response from us.  For some reason, we have not yet received the logs in the Eos mailbox.  I don't know what has gone wrong, but could you please try to send the show file and the logs again to eos@etcconnect.com and mark is "Attention: AFoster"?  Any information you can give us about the symptoms and the approximate time and date would be very useful.  I will email you back to let you know that we received the files.

We have fixed several lag issues in the 1.9 code, which was released earlier this week.  This version also has additional logging to aid in troubleshooting this kind of problem.  If at all possble, we would urge you to upgrade to 1.9 and see if this makes a difference.

Thanks,

Ann