It's been a hard weekend.
A fellow club member had set up a Raspberry Pi so we could use our smart phones as throttles to operate the layout using Engine Driver.
It was working a treat until just after he left mid afternoon when suddenly the throttles lost contact with the modem. I tried various things, ending with a couple of reboots of the whole system, but to no avail.
It was then that I lost my presence of mind as someone once put it, and as the Pi booted up I held down Shift. I did get a warning about losing all my data but didn't heed it. It seems I then reinstalled the OS and in the process deleted all the JMRI stuff.
I realised I was then in deep trouble but not to worry I thought, I can make an image file from the JMRI download, follow the instructions and all will be sweet.
Well, no actually. I did as it says. With the DCC system all connected and the Pi turned off I inserted the SD card with image file on it and then powered up the Pi. Once it had booted some lines of code started filling the screen but it only got about 4/5 the way down the first screen when it hung.
There are two image file versions on the JMRI website so 'maybe I'm using the wrong one' I thought. Much time went by while I download the other zip file, unzipped it, Diskimagered it and wrote it to the SD card. I then followed the procedure, exact same result.
So I then turned to my laptop. I got some help from this group last year with getting this to work, and it did, last year. Same equipment, same everything, but this time the phones and the modem refused to speak to each other.
The DCC system is Lenz LZV100 with 23151 USB interface.
Pi is over a year old, so I assume a 3.
I've uploaded screenshots into a photo album named Petrosnz showing the hung Pi, the working DecoderPro throttle and the non-working Wi Throttle.
The phones were not receiving any broadcast and entering its IP address and the correct port into a phone did not work. (The phones were of course connected by wi fi to the modem ... and the interface connected by cable to a Lan port on the modem.)
The DecoderPro throttle was working fine, so the problem appears to be with the modem/phone communication ... which had been working the previous day, you may recall.
The previous day's IP address didn't work either, by the way.
As I've said, there are a couple of photos.
Can somebody make sense of this please.
Peter
---
This email has been checked for viruses by AVG.
