I suspect your problem is that Rocrail is doing a namespace search for your cs2, but you don't have a namespace server.
I presume these then report back with their IP address which allows the program to then interact with the cs2/3. I know the CS2PC program probes the local network by sending a broadcast message to find any cs2/3 devices 'out there'. The cs2 may well have a Linux firewall in it, but if so I have never seen any information on configuring it.
FORUM ROCRAIL PC
I cannot connect from Rocrail unless I start the CS2 PC programĭoes the CS2 have any form of firewall? What does the CS2 PC program open which then also allows Rocrail to communicate? I can connect the Maerklin CS2 PC program I can connect with the CS2 directly from Google by typing in the IP address I can ping the CS2 from my laptop and have both successful received and sent info Rocrail of course is blaming McAfee first, then the CS2 firmware. As usual in these type of situations, they blamed the App. They turned off all protection and I still got the 10061 error in Rocrail. No communication to my CS2 was blocked by their software.
I have spent an hour on a Chat with McAfee and they took control of my computer and could not resolve or identify an issue. So it does not appear to be a McAfee issue but a weird network issue. Once I shut the laptop off and restart, the whole issue repeats. I can restart Rocrail numerous times after that with no issues as long as I don't shut down the laptop.
FORUM ROCRAIL SOFTWARE
I can shut down the CS2 PC software and the Rocrail control stays on. After the PC CS2 program has established connection and control capability, the Rocrail connection error disappears and I get complete Rocrail control. Then this is where it becomes interesting.
FORUM ROCRAIL WINDOWS
I checked the Windows CS2 software that was issued a few years ago for PC control and it connected to the CS2 IP address with no problem.
FORUM ROCRAIL UPDATE
I checked the CS2 Network communication with the Maerklin update site, no problem. I disabled McAfee and it still didn't work. The tricks I used the first time by switching to DHCP and back again did not work. After restarting my laptop I once again got the message from Rocrail that it cannot connect to the CS2 IP address. These had a detrimental knock on effect to the communications between RM and the eLink / Elite controllers.Well I knew it was too good to be true. HRMS changed RM settings relating to the 'Hand Held' Application. These bugs were introduced as a result of fixing the issues with 'users' using the 'Hand Held' mobile control options. Then potentially you will be stuck on the 1.69.2 release forever. If you don't resolve the 1.70.2 issues now by implementing the. Bad idea.RM updates are incremental, so the changes in 1.70.2 will carry forward into future releases. I'll leave everything running on version 1.69.2 and wait for a 1.71 version to be released. INI file changes down to a working solution for the majority. It is these LATER pages that fine tuned the. INI file changes highlighted in the LATER pages of the thread. As I said, read through the WHOLE of the thread but focus on the. The above are just the edited highlights of the posted content in the linked thread. I joined the iTrain and Rocrail forums but none of them seem to compare to this one. What i liked is the almost immediate suggestion that automation was not only possible but built in from day 1. This task seems to process more effectively if a different USB port is used for your eLink to plug into. Rocrail - I have set up Rocrail and am quite impressed but so far I have only used the intro section and not connected to my DCC controller. You will more than likely also have to play around with the COM port allocation in Device Manager and make sure it syncs with the COM port shown in the RailMaster 'System Settings' screen.
You will need to try some experimentation with setting the values ofĪlso make sure that the two lines above are the last two lines in the. Read through the WHOLE of this previous thread that detailed the issues. Particularly if using the eLink controller. With the RailMaster 1.70 to 1.70.2 releases it becomes necessary (for many users) to modify their railmaster.ini files to get their systems working again.
0 kommentar(er)
