Bug or dumb feature ?

On Ion today, running last OS

Doing an address check from console, so soft key 1 - Address, XX, @ Full, Enter, Next, Next, etc..

All well until console runs into addresses (dimmers in this case) that are not patched to a channel, then it skips to the next patched address.  

On RRFR, iRFR and aRFR, in Channel Check, the console will allow the next consecutive non-patched addresses to be called up using next or last.  

This is really annoying when you are trying to use address check to find units recently plugged, prior to patching.  

Bug ?.

Parents
  • Don't use address, check. Just use address and it will go through all addressees. Check only goes through patched.
  • AFAIK, there is no check mode while Live and for for addresses other then using softkey 1 on the Ion - I.E. you press SK1 and you have access to Addresses, and can then set a value, enter and use next/last to scroll thru the addresses. So if what Skrs8 is saying, the flexi state for channels changes how the address mode accesses channels ? and if you are in Patched Channel flexi state, addresses wile likewise only access patched addresses ?. That's a useless feature if it's the case
  • When I type {Address}[1][Full][Enter] and then press [Next], I always step through address 2, 3, 4... regardless of their patched status or my current flexi view.  Is that what you're looking for?

    Adding the softkey {Check} to the end of it does exhibit strange behavior in Flexi Mode... but it isn't necessary.

  • At all,

    I went back and checked this and found out what Paul has posted. If memory serves and from the desktop using Softkey 1, I threw an error if I used the syntax "Address, XX, Full, Check, Enter" and could only use "Address, XX, Full, Enter" at which point it stepped thru un-patched addresses with no issues (which makes sense). I would have to go back to run some commands to determine how I thru an error where Address was following the Flexi state.
  • I believe that {Address}[x][Full]{Check}[Enter][Next] is supposed to step through patched addresses, but it gets alllll kinds of messed up when you're also in a flexi state.  In it's current state, I'm sure it would throw an error eventually.

    I bet there's an SCR somewhere about this one... if not, it's worth a writeup.  What it's doing now is definitely not desirable!

    ~P

Reply
  • I believe that {Address}[x][Full]{Check}[Enter][Next] is supposed to step through patched addresses, but it gets alllll kinds of messed up when you're also in a flexi state.  In it's current state, I'm sure it would throw an error eventually.

    I bet there's an SCR somewhere about this one... if not, it's worth a writeup.  What it's doing now is definitely not desirable!

    ~P

Children
No Data
Related