RSLogix500 and RSLogix5 “remember” the Driver and Node settings which were used in the last online session ... sort of like a “last number redial” feature on a cell phone ... when you open the correct file you are probably resetting the Driver and Node entries to the same settings that were used when that particular file was last saved ...
keep your eye on the circled settings the next time you have to jump through those “go online” hoops ... this should give you a good idea of what’s going on ...
another more systematic way of getting online is to always click “Comms” (as shown above) and then click “Who Active Go Online” ... this should bring up a special window for RSLinx ... you should be able to navigate through that window and select the processor that you want to go online with ...
worse case scenario: you get in the habit (rut) of simply clicking “Go Online” every time you hook up without ever checking the Driver and Node settings ... in a networked system this can be very bad ... it’s quite possible to plug a DH+ cable into the front of one processor - and then “go online” with another processor over the network - based on that last number redial feature ... ooops! ... bad things can happen when you subsequently do something drastic like force or toggle a bit, etc., etc. in the WRONG processor ... legends are made of stuff like this ...
final thought ... if RSLinx doesn’t have the correct driver settings dialed in, then you’re STILL going to have to jump through some hoops anyway ... in confusing situations, it’s usually best to get RSLinx “talking” to the processor BEFORE you even start up RSLogix ... then the “Comms” and “Who Active Go Online” approach will usually keep you out of the woods ...
PS Edit ... congratulations, Bernie ... you win again ...