|
Re: DR5033 Wiring to DR5088RC Diag wrong?
Thanks Dennis. Good to confirm and rule out. I had an issue in one area on the layout. It would short and shutdown. Coupled with that, I decided to move all electronics from a slide out tray to a front mount on the layout. During this move I am verifying all wiring (that¡¯s how I spotted this). I am in the process of moving all equipment and it¡¯ll take awhile. If after that, and a problem still exists, I¡¯ll post the issue in detail. Cheers and thank you kindly.
|
|
DR5033 Wiring to DR5088RC Diag wrong?
I think I have some shorting issues.? Now, I suspect it is because I wired my YD7001 (ex DR5000) and the DR5033 boosters to the DR5088RCs as per the diagram provided. But I think they may have drawn it wrong and crossed over K & J output/Inputs.? See Diagram below.? ? YD7001 (ex DR5000) shows K output is on the Left & J on the right.? But on the DR5033 Booster (which is facing downwards) K & J seem reversed on the Booster based on the K & J labelling on the DR5088RC.? Am I right, or, doesn't it matter which output used on the YD7001 (DR5000) or the DR5033 Boosters?
Peter |
|
Re: YD7001 LocoNet connection problem
Karst,
I did a bit more testing. I have seen it fail within as little as four minutes. I observed that the client LED went dark on the command station hardware but not on the windows app desktop image. This was with a LAN connection. So, I thought this might be related and switched to a USB connection and tested. I worked on other things and went back to it 30 minutes later and observed the LED was dark on both the command station and app image. The JMRI track power button toggle failed. -- - Bob |
|
Re: YD7001 LocoNet connection problem
Karst, I provided my connection in another posting but neglected to include that I have always used Static IP addresses as I reserve these in my router for all household devices. Regards,
Bob Gamble On Tue, Oct 10, 2023 at 5:30?PM karst.drenth <karst.drenth@...> wrote:
--
- Bob |
|
Re: YD7001 LocoNet connection problem
Karst, It is not intuitive that an unselected protocol would still consume a port resource. Thank you for adding a check for duplication and a kind warning against conflicts. I use multiple JMRIs. One is on a Raspberry Pi that comes on with the layout power and supports WiThrottle through the home WiFi access point. The other is on a desktop and is used for dispatching (as required, not always on). I would not use the second in testing this error but have noticed no difference in either case. Since I have changed the port settings on my JMRI instances to 5550 to support my DR5000 connection I will alleviate the conflict by changing the
XpressNet's 5550 to another value and keep the LocoNet as it is. I'll report back later after testing. My connections are: YD7001 has Ethernet to a local switch which is connected to a main switch. Raspberry Pi has Ethernet to that same local switch and implements WiThrottle with the JMRI roster passed to Engine Driver. Desktop has Ethernet to the main switch. Ubiquity access point has Ethernet to the main switch. The main switch attaches to an Edgerouter. The router attaches to a fiber modem. The only WiFi active is the access point. At some point, I hope to run WiThrottle either through the Pi WiFi or YD7001. I need the roster support in YD7001 to make this feasible. Thanks again for all your support. Regards,
Bob Gamble On Tue, Oct 10, 2023 at 5:26?PM karst.drenth <karst.drenth@...> wrote:
--
- Bob |
|
Re: YD7001 LocoNet connection problem
Karst, In my tests, the failure would not become apparent until an action on the JMRI side was attempted. The System Console monitor and the YD7001 log would be clear in a full idle. The drop would become apparent when I would click the track power button in JMRI or attempt to toggle track power in Engine Driver. Then I would see the LocoNet error messages in the JMRI console. So you can see that it is difficult to pinpoint the duration of the timeout error since any attempt to test would reset the clock. But this is absolutely repeatable on my end. Regards,
Bob Gamble On Wed, Oct 11, 2023 at 4:14?AM karst.drenth <karst.drenth@...> wrote:
--
- Bob |
|
Re: YD7001 LocoNet connection problem
Well, ? Both I and the YD7001 + JMRI had a good nights sleep. :) that is: on and connected now for over 10 hours, JMRI completely idle. No disconnect happened.? This is easy to check by looking at the green "Client" LED on the YD7001. That one turns off when a connection is lost. But also the JMRI log is clean, as is the YD7001 log. ? So I cannot conclude that there is a structural problem in either JMRI nor in the YD7001/YD9401. I will conduct the same test the coming night. And then get the logfiles from both YD7001 and JMRI and upload them here. ? Greets, Karst |
|
Re: YD7001 LocoNet connection problem
Question to both Don and Robert: ? How is your PC connected to the network where the YD7001 is on ? I assume you both have your YD7001 plugged in with a cable to your router? And the PC as well? If running DHCP/Dynamic IP, you might want to try STATIC IP instead.? ? Greets, Karst |
|
Re: YD7001 LocoNet connection problem
Hi, ? ? Please set the port for LBServer back to 1234 as is the default for JMRI ? . Now you created a conflict with XpressNet's 5550. Turning it off does not mean it does not occupy that port. ( I will make a tighter check in upcoming releases, that will prohibit in a very demanding way the double use of port numbers ? ) ? Second, next to the JMRI log, please also make a YD7001 Logging.txt.? ? To prevent flooding the log with Temp and Current Messages,? Turn off this checkmark. ? Greets, Karst |
PJCwasHere
Bob Gamble
karst.drenth