Edit: WARNING : Until some correlation is forthcoming, the possibility exists that the following observations are made based on a faulty productA couple of operational "considerations" that I think need to be highlighted.
(from my experience - you mileage may vary)
Remember that Marklin Documentation states not to use the 6021 track output....
But ...
Note 1: ideosyncracies differ depending on the state of DIP switch 2
1) Accessory activity is Bi-directional
- the 6021 thus becomes a nice separate booster for Accessories (up to address 256)
- However - the CS2 (when on STOP) can continue to send changes to the 6021 (on GO) and the 6021 will action them BUT the icons on the CS2 DO NOT reflect this2) Power Stop/Go
IS NOT Bi-directional
- The CS2 Stop key will toggle the 6021 on and off
- The 6021 will "Stop" the
CS2 BUT WILL NOT cause a "GO"
3) Locomotive Speed/Reverse commands
ARE NOT Bi-directional
- Locos on track connected to the 6021 can be controlled by the 6021 as expected, and those commands do get sent to the CS2. However commands to the same loco address from the CS2 do not get sent to the 6021.
- This includes the
Reverse function - therefore the
Up/Down direction arrows on the 6021 will not accurately match the actual direction of the loco on the CS2 if the loco is controlled (over time) by both.
- while Speed Command are not "automatically" sent. Reverse and AUX Function are (maybe). BUT Because the the command for Revers and F0 include a speed value, it will get through. 4) Locomotive Extend Functions (F1,F2,F3,F4) are
sometimes bi-directional
- The first time a loco is dialed up on the 6021 it will not know what EFs the CS2 may have previously set (and the CS2 does not send it an update - I would call this a bug)
- With a loco dialed up (Loco-B), EFs will be reflected both ways
- If a
new loco (Loco-C) is dialed up (one not used on the 6021 since poweron) changes made to LocoB by the CS2
will not be seen when Loco-B is again retrieved on the 6021
- If an
old loco (Loco-A) is dialed up (That had been used on the 6021 since poweron ) then changes made to Loco-B by the CS2
will be seen when Loco-B is again retrieved on the 6021
Separately And this not really a Marklin issue
Uhlenbrock/loconet6021 to LocoNet adapter (at least mine)
- CAN work
- However I am fairly easily able to cause a Hang of the system.
I have not quite worked out exactly what sequence triggers this.
While the situation can be partially cleared by pressing Stop/Go a couple of times, subsequently I encounter a situation where changing a point/signal on a CS2 causes a system STOP. To fully clear, I need to power off the 6021 remove the adapter and Power on - the CS2 does not need to be power cycled or reset.
Intellibox - IB recieves Accessory changes from CS2 but does not send them
- Locomotive commands fail in either direction
Has anyone had similar experience ?
Edited by user 24 January 2010 08:51:57(UTC)
| Reason: Not specified