That's quite a controller setup. Makes my 6021+6036 and 7072 blue boxes seem way out of date! Still, I'm glad to hear that if I'm ever able to afford a CS2 (probably about the time the CS4 comes out!) I can still use my current controllers with it. Thanks!

-James

sorry ,I can't give you any results.
On Stummi's forum, it is said that it is about MFX loks only. When re-starting the CS2 it is still possible to drive those mfx loks with the 6021 through the newly assigned adress. Only the display on CS2 screen disappears but the loks are still available through the "modified adress" on the 6021.
One guy thinks that it could be made intentionnally by Marklin. He says that it is to avoid ,for the user , a risk of "double occuppancy of the address" or something like that......I'm not sure to understand ...( I'm even sure not to understand what he means with "double occupancy" in this case...
But , to control the MFX loks with CS2 you don't need this "new adress". While for MM2 loks it seems to be clear.



About the 2 or 3 seconds "freeze" of CS2 screen: it happens to only one guy. Other guys seem not to have it...

One thing I like very much is : it seems that there is a way for building/modifying a route on CS2 screen, then assign it to a key on the Memory...(really ?)

Edited by user 10 January 2010 01:03:58(UTC)  | Reason: Not specified

Goofy, that's because you don't have any controllers yet. So for you, you would go and buy a CS2 or an Ecos and start that way. Other people already have lots of older Marklin Digital equipment, and want to be able to continue to use it with their CS2's.

I know someone with a very large layout (over 12m long) who has 6021 / 6036 / 6040 / 6017 located all over his layout. He would still want to use that equipment if he got a CS2. The 60128 Connect - 6021 allows him to do that.

It isn't so much to do with driving MM as you put it, rather it is to do with being able to continue to use remote throttles and keyboards people have on their layouts.

Remember here then in case,that Marklin don´t producing old system anymore time.
So when you are using often old system,it will been not holding so long as you might and restore at Marklin company don´t last all the times.

This makes perfect sense to me.

- leveraging the graphical capabilities of the CS2 to "build" the route (And edit it later)
- put the Memory into input mode
- Playing the route from the CS2.
- End Memory input mode.

Even doing this manually from the "layout" tab, has got to be more intuative.

Today test: verify loconet
Good news friends, all seems ok, I've connect the IR/loconet adapter to the 60128.
The net included a IB control IB switch and S88 module, all the devices run as usual, the IB switch respond to the S88 input driving turnouts or its routes memorized, the IB control runs like the C80f (plus its functions).
Please note that CS2 don't receive the s88 signal via loconet, consider loconet as a separate world translated by 6021.





Turn off the system mean lost the assigned mfx loco -> 6021, but it doesn't matter to me.

Another thing, only to know, if you have a separate layout connected to the 6021 it respond directly to the 6021/loconet command.
The turnouts respond also to the same CS2 command, the loco only to the 6021/loconet.

And Goofy, the reasons why you would do it have already been explained!

Then in case,accept that i have right!
Don´t argements against me,when you know it yourself what I DID wrote about the new system and old system by using 60128 connecting box.
It was my rights,by writing like this anyway!
It´s nothing you can do about it!



P.S.
I think 60128 is an limited product,so it wont last for good.

Hi Jos,
I don't have a lissy to test, but all the signal produced by loconet are converted by the IR interface and sent to CS2 via 60128>6021, included switching F2/F3, lissy only push a virtual button, no?
No problem observed for the second question.
Thanks for your comment :-)

Yes i know it!
But i´m just only writing about realism by presentation 60128 connecting box as unnecessary.
Why...?
Because if you shall using old system via 60128,you must divided up tracksection anyway and that means you loss mfx repeating on the old system track area when you are using mfx locomotiv.
You must divided up section anyway!
That makes not good senses by acting like this by using 60128 still afterall!
You are using booster or mfx booster too by divided up sections at layout.

The story is about by using 60128 or not...
So anything that has to do about 60128,allows by writing like this.
Or perhaps you want to ask Lutz Hemmerich first...???

Hi Alberto,

Yes, I programmed Lissy to 'push the F2 or F3 button'. So if the 60128 communicates function keys to the CSII than all should work as I would like.

About the second problem, this afternoon when demonstrating this function to a friend of mine we noticed that this problem always occurred at the same spot of the layout when a loc was running there. (Near a breaking section). So i'm gonna investigate this week if there is some short occurring. Furthermore if the problem persist I will open a new topic as this has nothing to do with the 60128 topic.

I have the CS2 but the '6021' not showing on CS2 screen without 60128.

If i plugged 60128 to CS2 and '6021' Show up on CS2 Screen?

Thanks very much.

Lutz,
Know I now why you and the Märklin system work so well together.
Märklin must of realized the potential genetic similarities:
Still needs certain enhancement and shows some limitations, difficult to communicate with, complicated wire and system connections, responding in a simple fashion to the new and old.,

I wonder sometimes, is it you or the system, or both, that needs constant updating, corrections and reminders.

Alberto, thanks for your valid input, mind you it is a jungle of components and I don't think there will be an end to it all, with new technology around the corner every day.
It could be, your components will take up more room than your layout itself.
Not many people know, Goofy is a genius, he always answers his own questions, over and over again.

regards.,
John

Once again, posts have been deleted, although I do have a copy of them somewhere!

Let us to start to vote,for how many of you member who are using this kind of connecting between two different digitalsystem like what Alberto did!
I don´t think anyone of others member would buy an connecting 60128,when there is already all functional at CS2 which is enough to control train layout!

So am I. Want to connect my existing setup 6021-6040-6043-loconet adapter with track-control and lissy to the CSII.

Old system is in place, connect 6021 bought yesterday.
Still waiting for my CSII to arrive.

Hi all:

Great topic: but I am wondering if in the end the topic should be renamed:

What MARKLIN DID TO ME TODAY!! To match the earlier topic WHAT DID YOU DO FOR
MARKLIN TODAY!!

Thanks to mainly Alberto P. and Peter C. who kept all on topic.

I have been on the edge of the new CS2 or whatever it is currently called,
but I think the new marklin stuff? ( term used loosely) isn't for the faint of
heart.

All of this rings up the early days of personal computers and the related software.
The pointy fingers in both directions.

As it is with me now, I will wait for another 2+ years until it (hopefully) gets
sorted out. I myself don't want to be another pilgrim. I have a couple
kof's loks (36801) that won't run. So they have to go back. Then there is the PA-1
Alco NY Central whose marker lites won't lite. Again I guess I don't know the secret
handshake.

Thanks again to Alberto and Peter who toughed it all out for us outsiders.

Gene

Edit: WARNING : Until some correlation is forthcoming, the possibility exists that the following observations are made based on a faulty product

A 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 this

2) 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/loconet
6021 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

I think you read it correctly Roland, Peter has been experimenting with track being connected to the output of the 6021.

In theory there should be no risk in doing this, providing there is no possibility of track connected to a 6021 being bridged to track connected to a CS2.

I have updated my original post,
Because of the number of ideosyncracies I have encounted I cannot discount a faulty unit.

I really would appreciate some confirmation or contradiction to my experiences.

2 items in particular

- the basic Stop/Go obesrvation
- The 6021 not keeping in sync with the CS2 (the state of the F0,F1,F2,F3,F4)

HI to all,

Has someone conducted tests with the connect-6021 with the 6043 memory unit?
I do have some problems using them.

One memory is always working correctly (mem3), this is that when a route is switched on this memory the corresponding keyboard lights are getting set and also the track switches are placed in correct order via the CS2.

Another memory does this also (mem1) , but ONLY when it is the only memory connected to the connect-6021. When I add another memory (with a different address) the only thing that happens is that the lights on the attached keyboard change but nothing happens in the CS2. The other memory that is always working correctly is still doing the job. Also when i switch memories in the chain the problem still occurs.

So
keyboard-mem1-connect6021-6021=ok
keyboard-mem3-connect6021-6021=ok
but
keyboard-mem1-mem3-connect6021-6021 -> mem3=ok, mem1 only switches lights on keyboard not in CS2
keyboard-mem3-mem1-connect6021-6021 -> mem3 still ok, mem1 partially working.

also i have another memory (mem2) that is not working at all, even when used in the keyboard-mem2-c6021-6021 configuration.

I think memory 3 is the newest one, on the bottom there are the following indications:
mem1: 14AB9801823
mem2: D2108441
mem3: 14AB0002575

If someone has tested their memory unit and it's working ok, please check the label on the bottom of the unit.
Perhaps Märklin tested only the newest version of this device ....

Regards, Jos

Thanks Jos, appreciate the sanity check!