• Date
    alistermorton
  • Date
  • Replies 5 replies
  • Subscribers 185 subscribers
  • Views 2509 views
  • Users 0 members are here

Problems after upgrading to 2.2

Since upgrading our Ion to 2.2 I've noticed two things. First, the aRFR often won't connect for up to ten minutes after the console has booted. Second, when selecting a moving light (in our case a Mac 550) the parameters no longer appear on the encoder wheels (and there are no LEDs lit in the encoder category keys) so we have to use the onscreen ML controls. The only control which appears on the encoder, regardless of which category key is pressed, is Rate. Both of these features used to work perfectly before updating the software  - what are we missing?

Parents

  • The aRFR issue sounds like a general WiFi network issue - see the various i/aRFR threads for suggestions.

    Your encoders are sat in "Effects" mode, which is for controlling the 'parameters' of the running Effects.

    This should switch back to fixture parameters mode when you deselect the running Effects.

    If it isn't, that's a bug which we need to fix.
    Can you save a copy of the log files and email that to eos (at) etcconnect (dot) com, with a brief description of the problem along with the date (and if possible, rough time) that you first noticed this, so we can try to idenifty the cause.

    Then, save your show, Exit and do a Deep Clear. (Save your show first!)

    This should clear it up.

  • in reply to Richard

    OK, I'll look into it when I get a chance but the show opens tonight (it's all plotted now, so we won't need to adjust the movers during the run) so it will be about two weeks until I'm able to take over the desk. There are no effects running as far as I know - certainly none have been started, but I will check. The previous show had effects running in one or two cues, but all effects were stopped by the last cue of the show. 

  • in reply to alistermorton

    Checked last night and there are no effects running or selected in the effects tab (I closed the tab) so it looks like a bug. I'll get logs after the current show comes down, so that won't be until Nov 3rd.

  • in reply to alistermorton
    We see the encoder problem and it is fixed in 2.2.1 which hasn't released yet. For now, if you want to fix the encoders, save your showfile, exit to the shell, [Maintenance] [deep clear], then load your showfile again after you start. This will clear your display settings, including which page the encoders should be on, which is where the defect is. If you use snapshots, firing a snapshot that was recorded while the encoders were in this defective state will put them back in this state.
  • in reply to Dan Duffy
    Thanks, I'll try that when I get a chance.
Reply Children
No Data
Related

www.etcconnect.com