In response to a query re Lococards

The 60667 MS2 WLAN no longer has a card reader integrated in the device.
The space in the unit was needed for the additional technology.

I am on the fence on the conveyed meaning, and whether it is the MS2 WLAN that has the "web user interface" or if it is in the 60117.

it seems to me to be rather overkill to factor this into the MS2 WLAN itself when it (for operation) must connect to either a CS (home network) or the 60117 anyway!
The stability (hardwired to power through the 60113/6) of the 60117 would appear to be a more logical coordination point, and maybe beter able to provide the file space for firmware images to ALL
- MS2 legacy
- MS2 WLAN
- Trackbox

I concur, and would be inclined to cancel my order if not for my technical curiosity.

you are refering to one aspect of transferring data.

I am more interested in the operational selection of trains. I.e aleviating the non-ergonomic and time consuming need to change glasses and pick through 40 meaningless dots having to read the screen as you go.

I would rather look at the trains

Got a response from Märklin on the card reader removal and how to use cards Lok Cards in a System with the MS 2 wlan.

If you have connected the first 60657 Mobile Station 2 to the track box, you can read in the locomotives via the card reader. The data of the locomotives are stored on the track box. When you then plug in the MS 2 WLAN, the data is transferred from there to the new WLAN MS2.

So the wlan version can access the database stored in the trackbox or the CS.

That means for running a small seasonal layout, the MS2 WLAN is a non starter of the loco is a DCC one where access to the higher functions is needed and dealing with the resetting that one has to occasionally go through with the MS2. Maybe the firmware will get more stable in the future. Or just stick to the mfx locos on those seasonal layouts.

Manuals for Marklin 60667 - MS2 WLAN and Marklin 60117 - WLAN Box is now Online :

https://static.maerklin.de/damcontent/42/84/4284cf4f34932f44c48d8fc41a1e03bb1681286109.pdf ( 60667 - MS2 WLAN )

https://static.maerklin.de/damcontent/b2/aa/b2aa90eea289731f61a6bebe4c9e51ba1681286133.pdf ( 60117 - WLAN Box )

Umm.

60117 ( 60117 WLAN Box is a WLAN receiver)
"
Web Interface

A Smartphone or a PC (with WLAN) can access the WLAN
Box as long as the 60117 WLAN Box is not connected to the
60667 Mobile Station WLAN.
"

60667
"
Web Interface

When the Mobile Station WLAN is not connected to
a router or the 60117 WLAN Box, you can access the
Mobile Station from a PC (with WLAN) or a Smartphone.
"

Personally I remain unsatisfied to either


It might be a bit derogatory for me to suggest that the statements come from a test set up that had both the PC and the MS-WLan set statically to the same address. i.e. the tester would obviously encounter conflicts and may not know any different

As to the use of "Web Interface" (emphasis on the "Web")
Then while it may be that the units have the bloated WebApp ("Control") of a CS3 , I might suggest it is more likely to be terser API (CAN over Ethernet) - with maybe an improved TCP rather than UDP implementation


There is a need to differentiate configuration/management vs operation.
Setup of configuration, including address mapping of the 4 IR addresses, an code updates are one thing and require a rather simple UI
For operation, even a stunted "layout diagram" WebApp would be a big plus for MS only users

Are you sure about that?
Customer who buy Brawas digital loco for the Märklin tracks follow a card with mfx protocol to read up in the system like MS2 or CS3.
The problem is just that there was complain about Brawas card and Märklin did react this problem too.
Märklin decides to let the market produce decoder to allow mfx protocol in the decoder and not to use cards like Brawas.
However Brawa don´t want to stop use cards for theirs ac locomotives.
Next step is to stop cards in the CS3?
That will be possible when Märklin decides to stop use cards in the system.