Clearing Engine Info Data with LSU is Not the Same as Clearing Engine Info Data with CAB 2!

Chuck,

The behavior is correct, best I can tell from your explanation.  When you use LSU to modify an engine record, a flag is set in the engine record (which is in the base).  This flag prevents the sensor track from modifying the record until the CAB-2 clear engine record is selected.

This prevents the sensor track changing back a record modified by the LSU.  For example, if you change the road name, then run the loco back over the sensor track, you lose your edit.  The flag prevents this from happening.

You can always reset things with the CAB-2.  The reset on the LSU could be used to clear the flag in the base record, but we felt the CAB-2 was the best place to clear the flag after play testing.

Ah, thanks for the response. Makes perfect sense and makes me happy to know that it's a feature that I can use rather than an anomaly. 

I wondered about the LSU manual details on this and page 19 states:

"Clear Engine By clicking the Clear Engine button, you may completely remove an engine definition from your command base and all connected CAB-2 hand-held remotes and any other device which displays the Legacy engine roster. Only the currently visible engine record will be deleted. After clicking this button, a confirming warning message will be displayed. Click Cancel to abort or click OK to remove the engine permantly. This function is equivilent to using the Clear Engine function on your Legacy handheld remote."

This manual probably preceded the sensor track details, but the difference between the two methods of clearing an engine might be noted here in the next manual update.

Thanks again for the excellent response to these operational questions of Lionel products.

I ran into this some time ago with the CAB2.  I ended up that I could not program any engine into ID #2.  Well, I could program it, but it wouldn't work!  I tried a number of engines, same result.  One day I had the LSU connected, and I cleared out #2 with that, and it suddenly worked normally again when I programmed an engine into #2.