Wireless Whitchcraft

Dog Star

Western Thunderer
With the help of Ian I have a better understanding in the case of Wireless Witchcraft versus Model Railways.

The default settings for the Lenz Lan/Xpressnet interface are:-
* fixed IP;
* IP address of 192.168.0.200;
* subnet mask of 255.255.255.0.

This information comes from a manual which can be downloaded from a Lenz website... and is not present in the paperwork which comes with the product. The download manual states that the IP settings can be changed by use of a PC connected to the device - a method which Simon found to be diabolical.

The Touch cab software on the i-pad uses the tplink device to connect to the Lenz interface... and needs to be configured with the IP address of the Lenz interface (IP address as above).

Finally, Ian advises that the connectivity shown in Simon's original sketch, in the first post, can be met by configuring the tplink box as an "Access Point".

So overall looks as if we had a configuration error when setting up the bits and pieces last week.

regards, Graham
 

SimonT

Western Thunderer
Graham,

we had a configuration error
Not quite. We tried to contact the Lenz interface using the Lenz supplied 192.168.0.200 address through the web browser and the interface refused to respond. You should also be able to contact it by entering "http://xpressnet" into the address but even the Lenz American instructions admit that this does not always work. This suggest to me that the built in web server in the Lenz is poor. I also have doubts about the Lenz instructions. I should be able to connect the laptop to the Lenz interface using a Xover LAN cable; following the Lenz instructions got me nowhere but I can connect to other devices using LAN from the laptop.

The conclusion that I draw is that if you decide to use the Lenz interface, you should be prepared to to spend a fair bit of time faffing about.

Simon
 

Dog Star

Western Thunderer
We tried to contact the Lenz interface using the Lenz supplied 192.168.0.200 address through the web browser and the interface refused to respond.
Ah, so that is what we were doing.... a side effect of sitting in the back row - actually in Simon's comfy chair - is that I did not see all that you and Peter were doing.
I also have doubts about the Lenz instructions.
I agree with that sentiment... the paperwork which is shipped with the device is not much use and seems to rely upon peeps nosing through the CD which comes with the interface.
The conclusion that I draw is that if you decide to use the Lenz interface, you should be prepared to to spend a fair bit of time faffing about.
Just so... could "faffing" be a local dialect for "buffonery"?

All of which is a pity because the end result is rather good.
 

Dog Star

Western Thunderer
A follow-up conversation with Ian Roll this morning... something along the lines of "Is there still a problem and, if there is a problem still, what is the problem and/or next step"? Good question. To summarise where Peter and I are in the case of "puzzling Witchcraft versus Wireless buffoonery":-

1/ I know more about the theory of the communication between the various devices now than I did one week ago and that is down to the interest shown by Ian.

2/ Our Wireless case works for us with a tplink nano box configured as an "Access Point".

3/ Neither Peter nor I know why we failed to get a tplink nano box to work as a "Router" (although Simon is probably correct in his assessment that to get things working requires a fair degree of finger dexterity, a lot of patience and some witchcraft).

So what next? :confused:


Leave well alone!!!! :) Very much a case of not fixing something which is not broken :cool: .

Well, not quite... I shall purchase a second tplink nano device whilst PC World is selling the item at a reduced price. When we have a spare I shall be able to substitute the "new and non-configured" box for the "old and configured" box thereby allowing us to try again in slow time.

regards, Graham
 

Dog Star

Western Thunderer
Leave well alone was good medicine... Almost ten years to the day and our case of voodoo continues to satisfy without revealing secrets.
 

SimonT

Western Thunderer
I've had a successful time with the kit and much prefer it to ******** pick ups. Unfortunately my Tam valley transmitter has stopped working (half a dozen receivers can't be wrong) and it looks as if Tam Valley have given up R/C frequency devices and now want to sell just Bluetooth devices. None of the other available transmitters seem to be able to pass the required information.
There was another problem that I didn't get around to sorting. The new range of Zimo chips seem to have something like 500+ CVs and thus require more power. Running sound only increases this power requirement. Unfortunately the voltage regulator in use cannot keep up with demand and the whole thing grinds to an awful noise and half the progress along the track.

David Nicholson told me that chips which combine the radio control and the DCc are being manufactured but I have to yet to see evidence for sale.
 

simond

Western Thunderer
I spoke to Andreas Pieter Ziegler (corrected) boss of Zimo, on this subject a few years ago. Radio control DCC was “not on his product strategy” at that time. :(

just had a look and can’t find the emails. It was whilst I was playing with the second hand Duchess here

 
Last edited:

simond

Western Thunderer
How on earth could you utilise even half of those 500 CVs?
I guess 28 or 128 of them are speed steps, and there are a dozen or so for the four basic functions ACC, DEC, VMIN & VMAX, and the address. The ones we learned before sound became a thing.

There will be a fairly huge block to deal with sounds, and function mapping, each sound being triggered by a function button, having a volume and a duration, a random on/off, and if on, a delay time, that’s five cvs per sound (and maybe more) and there might be over twenty sounds. And of course there’s chuff synchronisation, plus triggers for things like the condensate drain cocks sound. And similar options for diesel and electric loco noises.

The Germans & Austrians seem to be into automated train operation, so they have automated braking, with braking rates, slow speeds, etc, and associated triggers. I have no idea how many variables that might add. It seems to be a big chunk of the manual.

but the project you buy comes with most of the cvs preloaded, so you probably only need to adjust the big four, and two for the chuff synch.

https://www.zimo.at/web2010/documents/MX-small-decoders_EN.pdf. Over 800 CVs! See pages 72.. for details.
 

SimonT

Western Thunderer
My feeling is that Zimo have completely lost the plot. I only stay with Zimo for the YouChoos brake function on F2. Shunting becomes even more fun and I missed it when I operated the Yard on Heyside; thankfully no incidents!
We are probably all dinosaurs for wanting to drive a train and not leave it up to a computer. Believe me, letting the computers drive the aircraft is bloody boring until the "Have you ever seen it do that?" conversation;)
 

jcm@gwr

Western Thunderer
We are doing a similar thing at our club, but we are using the MERG modules, the handsets only
cost about £45, but they come in kit form.
It is set up to use Engine Driver on Android phones or tablets, this is enabled through the club's
own Wi-Fi set-up, which we decided to install as it has other benefits as well.
The advantage is that those that aren't tech savvy can use the handsets we've built, the downside
is that the handsets are a bit small, so we're developing a larger one to make it easier for those
members who might struggle.
The Engine Driver (free app) is easy to use.
The point controls are still on panels located near the stations/areas they control, this is on a large
0 gauge layout, approx 39' x 18', so you need to be near the pointwork you are operating, to avoid
mistakes that you can't see.
 

Caggers

Western Thunderer
This is an interesting read, especially as it started 10 years ago... I think someone got the Buffoonery spelt incorrectly, should it not have been buf-phone-ery...

I've been using the Gaugemaster Prodigy with their WiFi module on my android phone for my layout, along with a couple of wired handset for those that want to use them. Works quite seemlessly, although I am still on switches for points (but not far from DCCing them) and still need to install signals, but they will work in the same manner as my point. These use the Peco Smartswitch and servos...

Cheers
Simon
 

SimonT

Western Thunderer
I'm of the handset/wifi for driving only persuasion. We had the point and signals controlled by switches set up in a mock lever frame (long box full of relays, wires and switches 1-50). At shows we ran a signal man part time driver and another driver who moved trains to schedule out of the fiddle yards up to wherever a signal checked the move. Personnally, I canot see the point of DCC control of points and signals and the gang voted against bells and so forth.

I've just fitted a Zimo Goldcap Energy Storage set to a 64XX. It gives power to the motor for a good 15 seconds and thus needs some consideration when driving. I've already had it lose comms with the DCC and continue moving on it's own! It does however give relief to one of my considerations when moving to R/C and battery; this is the guarantee of it moving off when asked.

Ten years - where did they go?
Simon
 
Top