Dog Star
Western Thunderer
Where is the back of the class at the moment?
Wireless Whitchcraft
- Thread starter SimonT
- Start date
Heather Kay
Western Thunderer
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
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,
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
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
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 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.
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?
Leave well alone!!!!
Very much a case of not fixing something which is not broken 
.
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
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?
Leave well alone!!!!
Very much a case of not fixing something which is not broken .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