Adrian! posted:Barry Broskowitz posted:all 5 TIU Serial ports are totally bare here.
Them why not try a "Hail Mary" - replace the USB cables between the TIUs and WIUs with USB to Serial cables. It should make no difference, however, you never know...
Hi Barry, I own a lot of USB to serial converters now but I'm still stuck in the same place on the app.
However your mention of the static IP is interesting and I made an interesting discovery.... in the 5 TIU system the read is much faster if the TIUs 1-5 have static IPs in accending order. They don't need to be consecutive x.x.x.1 x.x.x.2 and so on..... just monotonically increasing. In this config the read is down to 10 seconds from over a minute. I changed it back and forth 5-6 times to be sure it wasn't coincidence..... the ip order definitely had a big effect.
I still get the timeout, but it comes much faster now so that's a start I guess. I'll keep poking it this week.
Adrian
Adrian,
I might be a little late here with a response, but wanted to add to your comment.
Our club layout has 5 TIU/WIU's which are statically assigned an IP address in ascending order. This was done by pure coincidence, and when I was recently onsite, I tested your idea about reversing the order of the assigned IP's. I can confirm your results. I'm glad my OCD about not using DHCP and assigning things in order has paid off! Even phones and tablets are statistically assigned to the network with a dedicated IP address.
I went a step further.
I plugged all of the WIU's into an old school network HUB (not a switch), and plugged in a PC running wire-shark to capture all of the network data flowing to each WIU and the wireless router. The apps will scan pretty much every available IP address in the subnet to discover all WIU's. This didn't take very long. I then shut down two of the WIU's (selectively random 2 & 5) and the traffic was interesting. The DCS app was aware that a WIU should be at these two IP addresses and continuously tried to communicate with them which resulted in a long wait time on the app side up to the time out.
It appears the app retains information about where each WIU is on the network. When we humans take that away the app doesn't rescan the network to determine which WIU are now offline. It appears that this "scan" only happens when we hit the "run trains" button on the first screen.
When I get back there, I am going to do some more testing and tinkering.
