Hello all,

Time is closing to retire my beloved Intellibox I, but are there better alternatives? In this subject I would like discussions about Loconet capable systems only please. For me it's a demand that the system has full LocoNet, that is, alla commands and feedback signals in the system must be visible to all clients on LocoNet as well. Another demand is that it should be able to send both Motorola commands and DCC, including Motorola old functions.

To my knowledge that gives us this list (please correct me) in order of my current degree of interest:
1. Roco z21.
2. ECoS with Lnet converter
3. Intellibox II
4. IB-com
5. Digitrax; they possibly can send also Motorola commands with one central, but am not sure if they do it simultaneously with DCC.
6. More or less home built soultions, where central functionality.

This is a list of "centrals", that is, that is keep speed, direction etc of Locos, and accessory commands, and converting it to track commands.

My comments:
1. It appears very promising but far away from ripe. I like the apporach very much if only it will show full functionality and quality. I certainly like to use pads and phones for control.
2. Reviews highly appreciated. If I were to buy know, it seems the best.
3. Yes, a definie advantage is that it would allow for LNCV programming of my other utilities. The Intellibox has served me well, but Uhlenbrock is not doing a good customer service, and they do not the best SW in my taste.
4. Smart to avoid monolitic soultions, but doesn't have WIFI and not a good supporting community.
5. Digitrax is not my favourite; I feel a bit angry about how the handled the LocoNet licenses, and they have serveral peculiar solutions to me. No, not interested.
6. Well, I'm somewhat lazy.

Comments anyone? In particular, does anyone own a L.net converter?
/Lars

Ah,
that explains the lack of news regarding L.net cconverter. Seems I'll have to wait then; lets hope on Nürnberg fair. I guess Roco at least may stir up some activity from a sleeping market.

Cheers,
L

Well I also have a mixed setup using Loconet and CSII.
I use loconet for switching operations with the Uhlenbrock Track-Control, Intellilight and Lissy receivers. My sound locs are equiped with Lissy transmitters.
Sole purpose for the Lissy equipment is that I can now switch the sound on/off when a train leaves/enters my hidden parts of the layout.

I use an Uhlenbrock 6021 adapter connected to the Marklin Connect 6021 which is connected to my good old 6021 cu. All turnout controllers (6083)/signals are connected to the 6021.
For block automation and shadow station operation I use the IB-switch.
The Connect 6021 has a connection to my CS2 (60214).

So I use loconet for switching operations via the Track-Control panel and sound on/off operations and the CSII for running my locs.
One thing that does NOT work is giving a switch command on the CSII as this will most of the time results in a STOP situation on the CSII and 6021.
(This behaviour has already been described in the original Connect 6021 thread).
As long as switch commands ONLY come from the Loconet all keeps working ok. I can see the status of all switches/signals on the layout I defined on the CSII.
Furthermore the Track-control is not able to switch signals with 3 or 4 possible positions with a single button but I use an extra button to realise this.

I e-mailed Märklin once asking if a real loconet adapter would ever be made (as ESU has planned) but I never received an answer to that question.
If the Loconet adapter from ESU ever emerges and does REALLY work without limitation for the above setup perhaps I would consider switching my CSII for an ECos.

Correct me if I am wrong, if I understand correctly Digitrax still have enough "ownership" of the loconet protocol that 3rd party developers require their certification. This will probably slow the deployment process of make sure it is stable from the getgo when it does appear.

Other question relating to the likes of ESU, Z21 etc is how they are going to make/promote/certify the various loconet device.

Personally I would always expect to need have a backend infrastructure (loconet) and a separate front end "Central" to convert the commands out to the track. Option 6, with a PC as a mediator, for me is the most realistic way to proceed in order to get/stay productive. If a vendor finally delivers a verifiable solution then by all means bypass the PC. However once the PC is involved other (tailoring) possibilities open up.

If your IB1 is failing, that may make a difference but if not I would retain it as the LocoNet master, even if it did not connect to the track. and find an interface to the Central of your preference.

Please note that there is z21 and Z21 (and little is known about z21, the new starter set controller).

Lars,

I think Tom was politely pointing out that you referred to z21 lower case in post #8, no?


Picking up on what Peter said. There are ownership issues, and it seems there are delays to new items coming to market.

If you we're to purchase an IB II, then use a PC with say iTrain installed, would this meet your needs, and protect your investment?


r/Thomas



http://berros.eu/itrain/en/systems.php

Possibly not a bad idea, given that the professional version of iTrains can interface with more than one digital controller at the same time.

I had been thinking of getting a couple of the ESU Loconet adapters, if only to see if that would allow me to connect a CS1R to an Ecos as remote controllers. Seems I can't do this at the moment as the Loconet adapter is 'vapourware'!

Hi, Lars,
thanks for the link. I clicked on "z21" to find information about "z21" - but you have to click on "Z21" to find what's missing in "z21". As I said elsewhere, "z21" is a "Z21" without the interfaces that aren't working yet ...
And their web site is as intuitive as their controller naming convention.

Still a lot "not yet" in their FAQ list.

Hello Rinus,

thank's for your resume; I wonder - could you tell more about the interface? I could only find p50x on UB site; do you/anyone have what appears to be the new API?

IBII certainly is an option for me. If I will choose another option I think I must either change central for programming, or possibly, using a LocoNet interface do the programming from a computer. Using a computer all the time is not what I desire, but I might be forced to change my mind.

Ok, time has passed.
meanwhile following has happened on my horizon:
1. Z21 have release the x-bus based API, but no signs of a proper LocoNet implementation.
2. My dealer tells that ESU are supposed to release the LocoNet interface this summer.
3. I'm still working with what I really want.

No ideal solution. So at last I started consider a JMRI. I did not want a computer solution, for unclear reasons, but begin to realize that this might might be just what I need. More about that in a separate thread.