开云体育

On Mon, Oct 9, 2023 at 01:45 PM, Robert Gamble wrote:

I am still experiencing connection drops with LocoNet over TCP/IP. The timeout is set to zero as recommended. I have only two protocols selected. On startup I can run just fine but if I let the system idle for something on the order of an hour or two, it looses the connection. It was a problem this morning when I had a DR5000 owner over to look at my upgrade and I had to go through a series of restarts of the YD7001 and JMRI in order to be able to run trains. I think he is going to hold off on his upgrade for a while...

We both have similar set-ups. His and my old one ran flawlessly with the DR5000. We have the command station connected to JMRI via Ethernet and use household Wi-Fi for Engine Driver throttles.

I see this on the JMRI system console:

2023-10-09 16:12:33,181 loconetovertcp.LnOverTcpPacketizer??? WARN? - sendLocoNetMessage: IOException: java.net.SocketException: Connection reset by peer: socket write error [LocoNet transmit handler]
2023-10-09 16:12:33,492 loconetovertcp.LnOverTcpPacketizer??? WARN? - sendLocoNetMessage: IOException: java.net.SocketException: Connection reset by peer: socket write error [LocoNet transmit handler]
2023-10-09 16:12:33,802 loconetovertcp.LnOverTcpPacketizer??? WARN? - sendLocoNetMessage: IOException: java.net.SocketException: Connection reset by peer: socket write error [LocoNet transmit handler]
2023-10-09 16:12:34,112 loconetovertcp.LnOverTcpPacketizer??? WARN? - sendLocoNetMessage: IOException: java.net.SocketException: Connection reset by peer: socket write error [LocoNet transmit handler]









- Bob Gamble

?On Mon, Oct 9, 2023 at 01:45 PM, Robert Gamble wrote:

I am still experiencing connection drops with LocoNet over TCP/IP. The timeout is set to zero as recommended. I have only two protocols selected. On startup I can run just fine but if I let the system idle for something on the order of an hour or two, it looses the connection. It was a problem this morning when I had a DR5000 owner over to look at my upgrade and I had to go through a series of restarts of the YD7001 and JMRI in order to be able to run trains. I think he is going to hold off on his upgrade for a while...

We both have similar set-ups. His and my old one ran flawlessly with the DR5000. We have the command station connected to JMRI via Ethernet and use household Wi-Fi for Engine Driver throttles.

I see this on the JMRI system console:

2023-10-09 16:12:33,181 loconetovertcp.LnOverTcpPacketizer??? WARN? - sendLocoNetMessage: IOException: java.net.SocketException: Connection reset by peer: socket write error [LocoNet transmit handler]
2023-10-09 16:12:33,492 loconetovertcp.LnOverTcpPacketizer??? WARN? - sendLocoNetMessage: IOException: java.net.SocketException: Connection reset by peer: socket write error [LocoNet transmit handler]
2023-10-09 16:12:33,802 loconetovertcp.LnOverTcpPacketizer??? WARN? - sendLocoNetMessage: IOException: java.net.SocketException: Connection reset by peer: socket write error [LocoNet transmit handler]
2023-10-09 16:12:34,112 loconetovertcp.LnOverTcpPacketizer??? WARN? - sendLocoNetMessage: IOException: java.net.SocketException: Connection reset by peer: socket write error [LocoNet transmit handler]









- Bob Gamble

?Hi,
? ? I am currently experiencing this same issue of dropped connections using Loconet over TCP/IP. I only have LB server protocol active and the timeout is set to 0. In my troubleshooting I find that as long as there is activity from the Engine Driver throttle things work fine. If trains are just running with an idle throttle, the dropouts seem to occur. I had no dropout issues with the DR5000 before the YD9401 upgrade, everything worked flawlessly for hours. I'm running Windows 10 with JMRI version 5.5.5 and the latest Engine Driver App version for Android. The YD7001 is running build 59 software and firmware. Any insight to this issue is appreciated. Thanks.
Don

I am still experiencing connection drops with LocoNet over TCP/IP. The timeout is set to zero as recommended. I have only two protocols selected. On startup I can run just fine but if I let the system idle for something on the order of an hour or two, it looses the connection. It was a problem this morning when I had a DR5000 owner over to look at my upgrade and I had to go through a series of restarts of the YD7001 and JMRI in order to be able to run trains. I think he is going to hold off on his upgrade for a while...

We both have similar set-ups. His and my old one ran flawlessly with the DR5000. We have the command station connected to JMRI via Ethernet and use household Wi-Fi for Engine Driver throttles.

I see this on the JMRI system console:

2023-10-09 16:12:33,181 loconetovertcp.LnOverTcpPacketizer??? WARN? - sendLocoNetMessage: IOException: java.net.SocketException: Connection reset by peer: socket write error [LocoNet transmit handler]
2023-10-09 16:12:33,492 loconetovertcp.LnOverTcpPacketizer??? WARN? - sendLocoNetMessage: IOException: java.net.SocketException: Connection reset by peer: socket write error [LocoNet transmit handler]
2023-10-09 16:12:33,802 loconetovertcp.LnOverTcpPacketizer??? WARN? - sendLocoNetMessage: IOException: java.net.SocketException: Connection reset by peer: socket write error [LocoNet transmit handler]
2023-10-09 16:12:34,112 loconetovertcp.LnOverTcpPacketizer??? WARN? - sendLocoNetMessage: IOException: java.net.SocketException: Connection reset by peer: socket write error [LocoNet transmit handler]









- Bob Gamble

This has gone far enough on this topic.?

I am locking this topic.

--
Dennis Cherry
Owner/Moderator

Well Mister Anonymous,

?

This is getting really ugly/aggressive in my opinion. I have no idea to what your nitpicking has to lead to. I think I answered all your questions sufficiently.

That is exactly why I became member to this group: To answer (serious) questions from users of ex-Digikeijs and YaMoRC products. And I have pleasure in doing so.

But as it seems, there is quite some hate/aggression against whomever or whatever that had something to do with Digikeijs in the past. I will not continue to defend me against that. But instead only answer decent, seriously meant questions.

Posts which are not at least signed by a first name, will not be answered nor replied to by me.

?

Greets,

Karst

On Mon, Oct 9, 2023 at 06:36 AM, karst.drenth wrote:

Well... That OPC_IMM_PACKET is a generic command in LocoNet land to send any DCC packet to the rails. So also DCCext... It enables a.o. the DIY software like JMRI so send DCCext aspect packets through LocoNet.?

JMRI does support the DCCext via other protocols e.g. NCE or XpressNet.

But... all other software does not !.

Please can you be more specific what does it mean "all other software does not". Any SW which correctly implements the LocoNet with OPC_IMM_PACKET? can send DCCext.

So YaMoRC implemented it natively together with Roco in V8.1.9. So the DCCext aspects could be sent via all available protocols. Not only with the OPC_IMM_PACKET Swiss-LocoNet-Knife ?

Roco uses DCCext extensively in their Z21 App. But after YaMoRC paved the way for protocols other than Z21, also iTrain, RocRail, WinDigiPet all started supporting DCCext for controlling signals

Are you saying that the SW you mentioned can send the DCCext only if I use exclusively the YaMoRC CS connected to those respective SWs ?

Thanks

On Mon, Oct 9, 2023 at 06:36 AM, karst.drenth wrote:

Sorry, but it does not. Only by the grace of the OPC_IMM_PACKET command being implemented, also DCCext can be sent. A were coincidence.

It looks like to me those 2 statements are contradictory.....Either it does or it does not. You stated in the first statement it does not but in the 2nd statement you clearly stated "also DCCext can be sent.". The user eventually does not need to know what is the transport protocol and what is the implementation "how",? the key is that DCCext can be sent as you stated. The fact that the CS may or may not support this feature for all available protocols is different story.

Please can you explain what is meant by "native DCCext", specifically any reference to a standard which describes "native DCCext".

Thanks

Hi I just typed quite an answer to your previous remarks. But it got lost when your new post came in ?

?

So again:

Iain,

you stated: " The DR5000 doesn’t support DCC Aspects (aka DCC Ext)". May I know which version do you use ?

The manual (see my previous reference) clearly says, it does.
2 questions to Karst:
1) Does the DR5000 support DCC aspects (aka DCC Ext) or not ?
2) If yes, which version ? The manual says 1.5.1.

Thanks for reading my post

If the Karst introduced DCCExt in v1.4.7 (which Karst has said is incorrect) it is very strange that in v1.6.3? Digikeijs didn't include a function that according to you was already there since v1.4.7 :(


The new features announced in the??for this release (Withrottle?and DCCExt) are apparently not included.

On Sun, Oct 8, 2023 at 01:38 PM, karst.drenth wrote:

Well, then that understanding is incorrect ;)

just to be sure, are you saying that the manual of DR5000 is describing the functionality which DOES NOT EXIST ? Please explain what is incorrect in my understanding.

Author of the latest version (1.4) of the python script performing the test for DCC aspects. This script is a part of JMRI distribution.....https://www.jmri.org/jython/

Here is the copy of the statement (chapter 11.2 page 69) from DR5000 manual Firmware ab V1.5.1 (2018.09.27)
Version V1.5.0: Firmware: -
? The whole programming track operation has been thoroughly overhauled and improved.
? Regardless of the DR5000 revision it is now possible (at the demo system) to read almost every decoder error-free.
? Daisy II and IB Basic-slave can read and write CVs.
? Programming track = read & write, main track = write only (because the Uhl devices can not read POM)
? Read address and program (option on Daisy II) are not (yet) supported.
? n the programming area both POM read and write are revised and made faster and more reliable.
? With e.g. JMRI you can now read all decoders quickly and conveniently via POM.
? OPC_IMM_PACKET Now this LocoNet command is fully implemented so that e.g. JMRI the so called Signal mast aspects can be sent to so called Exten-ded Accessory Decoders.

Hi,

?

My understanding is that it does starting with FW 1.4.9

Well, then that understanding is incorrect ;)?

?

Greets,

Karst which made FW 1.0.0 thru 1.5.5 and 8.1.0 thru .... ;)?

On Thu, Oct 5, 2023 at 10:23 AM, Iain Morrison wrote:

The DR5000 doesn’t support DCC Aspects (aka DCC Ext)

My understanding is that it does starting with FW 1.4.9

Thank You for your comment

--
Dennis Cherry
Owner/Moderator

On Fri, Oct 6, 2023 at 10:42 PM, Oldngrey wrote:

The last thing I want to do is to criticize your software

Hi, I did not take it that way ;) Neither to Robert's remarks.

?

In general I love positive critisism. It only makes the product better ( I think many members of this and other Fora can witness taht ) . But also I have my, more or less strong, opinion on how our software should look and feel like... Referring to Win 95 maybe helps you, but I have to tell you, that back then I was already programming for windows (3.11 ;) ) And the one thing I always followed, were the MicroSoft GUI guidelines. And still I am doing so. That in the same time does not always have to be the best, but it's a guarantee for consistency over my Apps and the OS and with that also other Apps. MicroSoft advises to let your App's look and feel to blend with the OS. And basically that's what I have been doing for over 30 years now :) ( and the last couple of years for YaMoRC :) )

?

And yes, I understand the need for a lot of products we announced when we first started. The estimates were quite realistic back then... But what really made the S hit the F was:

- 1st an unbelievable good reception of our portfolio ( 5-fold more demand than expected )

- 2nd an even bigger resonance to the YD9401 ( which started of more or less as a joke... :) )

- 3rd DK's bankruptcy and with that a lot of troubles, as well in the area of quadruple- 10 tenfold demand, but mainly because of people thinking we were a) tha cause of the bankruptcy and b) the successors.?

I can tell you that mai june an july were far from pleasant months to be representing YaMoRC...?

?

All that S caused development to grind to an halt, even in areas where the chip crisis did not hit us. So we are facing our worst nightmare, something we also wanted to avoid: Backlog, Backorder, Delay and Cancellation...

So, yes it will all come. We are are a healty company, we can invest in goods. Just time ist the factor in the moment that we're missing dire.

?

Greets,

Karst

?

Karst,
The last thing I want to do is to criticize your software. I love what you are doing.
It might be a case of Europe and USA/Australia/UK?? not thinking along the same lines. Maybe us Aussies are simply used to the traditional Windows interfaces with File, Edit, View pull-down menus. I know that's a Windows 95 thing, but, hey I was first in line for that and its methodologies stuck. Every bit of software has its own 'quirks' and yours are by no means the hardest to use. (Logitech mouse apps are amazingly obscure - a different league altogether!) So not to worry, but it could of course improve.
On other matters:

• I didn't subscribe to the Facebook YaMoRC page simply because it announced it was in Gernam. I was hoping there was another way to find out the lastest news. This group seemed to be it. Not so sure now. Your web site doesn't have a latest news page.
• I have seen that red error message saying the YD7001 needed a USB connection. Didn't suspect that the picture next to it was a button. We need to hover over stuff a lot more to find out what is an action. I won't forget it now.
• I see that the website has just updated us on the YD6016LN-RC module being delayed.? :(? Yep 3rd quarter was over. This is the module I am most interested in. You probably have no idea when I might be able to buy? 8 ot them, but just so you know it's crucial to someone at least!

All the best.

On Thu, Oct 5, 2023 at 06:59 AM, Ebenezer Devadarshan wrote:

Also is there a replacement for reverse loop on YD?

?

On it's way ;)

Yes

Sorry to hear that Heath, did not know that... apologies.

?

Greets,

Karst

On Thu, Oct 5, 2023 at 08:29 AM, Robert Gamble wrote:

Instead of saying "Attention, Update only possible with USB connection !", something like: "Update requires USB connection. Click button to change ->" might be a bit more clear.

Well... that sounds to me like: "...Do not put your dog in the microwave to dry..."? My guess that Europeans like a different way of being advised ;)?

And make the button look like a button. Don't expect that users will mouse over everything to discover what is clickable.

Well, to be honest I also had to get used to the new way of "Looks" that came with upgrading the UI to Win 10/11. What you see here is an example of a trend that is called "Flat UI" It comes "for free" when using newest Microsoft tools to create software...

In general, I like your products and I love the support you provide. But it is often difficult to understand how to use the software.

In general, thanks! But I have to be honest on this one as well. You are exactly the first person to complain about the intuitivity of the Programs. At least in Europe, even in the well known magazines, the software is quoted to be very simple to use and being very intuitive. But again, it might be a difference in Computer Culture between the ancient Europe and the advanced Nothern Americas ;)?

?

Greets,

Karst

?

I think you also asked which version?