Content → Trouble Shooting

• FAQ

This is because Windows hides known file extensions by default.
Change this in the File Explorer:

• Start Windows Explorer, you can do this by opening up any folder.
• Click Organize.
• Click Folder and search options.
• Click the View tab.
• Scroll down until you notice Hide extensions for known file types, un-check this line by clicking the check box.
• Click OK

One possibility is that the window is positioned outside the visible screen.

Remedy:

Click Rocview in the taskbar. Then, hold down the “Windows key” on the keyboard and press the left (or right) arrow on the keyboard up to three times. This causes the invisible window to be placed on the screen in one of three positions: attached to the right side, attached to the left side, or in the middle.

1. Rocview hangs at startup.
   • Remove the rocview.ini and restart Rocview. Some split panel values will keep Rocview from showing up. Or remove the split values from the rocview.ini file. (wxWidgets bug.)
2. Rocview does no longer get update events from server and or freezes.
   • Disable monitoring.
3. Rocview cannot connect to the Rocrail server. (For example: "connection to localhost:8051 failed")
   • The previous port 62842 must be replaced with 8051 in existing rocrail.ini and rocview.ini.
4. Rocview 'hangs' after opening a Workspace.
   • The client TCP port is not set to 8051 in the rocrail.ini found in the selected Workspace.
5. Rocview needs too much CPU power and has a bad performance.
   Check following options:
   • Disable tracing.
   • Disable monitoring
   • Minimize monitor size
   • Disable processing route and block events
   • Disable smooth rendering
   • Disable timer events
   • Remove the loco image column
   • Disable Train Image
   • Disable Loco Widgets
6. Rocview is no longer visible at startup or it shows itself as a small line.
   • Shutdown Rocview (Task manager), delete the rocview.ini and restart Rocview.
7. Missing block context menu items.
   • Check the selected block menu items.

1. Rocrail crash at startup under Windows.
   • Disable check for serial devices at startup
2. "Interface ID is not set"
   • A none existing IID used or no default Command Station set.
3. Rocrail needs too much CPU power, or can't catchup with the Command Station communication.
   • Disable tracing

• Prerequisite: At least one backed up track plan file must exist in a backup directory (backup)
  See Backup in the Rocrail properties.

If the track plan of a workspace is damaged or a revert to an earlier version of the track plan is wanted, the following steps are recommended:

1. Exit Rocrail (Rocview and server) completely.
2. From the subdirectory backup of the workspace copy the file with the desired version (timestamp ) into the workspace.
3. In the workspace delete the (old or damaged) track plan file that is to be replaced.
4. From the copied file remove the timestamp in the file name: 20120824160729833-plan.xml –> plan.xml.
5. Restart Rocview and if necessary Rocrail server.
   When opening the workspace the track plan with the data status of the saved version is now active.

• Do not use a dedicated TV router, mostly delivered combination with pay TV, with a Command Station interfaces which uses the Ethernet UDP protocol.
  UDP is per default disabled in such routers.
• Make sure the used router does not block UDP.
  

1. S88 Feedbacks do not report:
   • S88 feedbacks and network settings.
2. I have problems to setup the CS2 network:
   • S88 feedbacks and network settings.

1. Connection lost after a random time: (transact OSerial 0625 read size=2 rc=-1 read=0 errno=6)
   • Keep transformers far away from the very sensitive USB communication cables! (http://forum.rocrail.net/viewtopic.php?p=21411)
   • Install available device driver updates.
   • Use short cables; A long cable (>3m) can cause problems if it is of poor quality.

To access a serial device the user must be added in the dialout group:

$ sudo adduser xxx dialout

[sudo] password for xxx: 
Adding user `xxx' to group `dialout' ...
Adding user xxx to group dialout
Done.

xxx = Your user name.
Re-login to activate the new settings.

In Manjaro Linux a group called 'dialout' does not exist.
The correct command on Manjaro Linux (and Arch Linux?) is:

sudo usermod -aG uucp username.

• http://forum.rocrail.net/viewtopic.php?p=45899

Note: This is a copy of the forum posting:

When connecting my OpenDCC Z1 to my new laptop (with fresh installed Kubuntu 12.10) I had to get my udev config to fixed:
1st I had to add an udev rules files as described on the OpenDCC webpage. I added a file /etc/udev/rules.d/99-opendcc.rules:

KERNEL=="ttyUSB*" ATTRS{idVendor}=="0403", ATTRS{idProduct}=="bfd8", SYMLINK+="opendcc/opendcc" 
KERNEL=="ttyUSB*" ATTRS{idVendor}=="0403", ATTRS{idProduct}=="bfd9", SYMLINK+="opendcc/schnueffel" 
KERNEL=="ttyUSB*" ATTRS{idVendor}=="0403", ATTRS{idProduct}=="bfda", SYMLINK+="opendcc/throttle" 
KERNEL=="ttyUSB*" ATTRS{idVendor}=="0403", ATTRS{idProduct}=="bfdb", SYMLINK+="opendcc/basestation" 
KERNEL=="ttyUSB*" ATTRS{idVendor}=="0403", ATTRS{idProduct}=="bfdc", SYMLINK+="opendcc/gbm" 

But then the modem-manager always probed the new device. So I got always (in the rocrail terminal output or log):

20130115.170432.860 r9999I main     OSerial  0196 rocs_serial_open:open rc=16 read=0 write=0 [16] [Device or resource busy] 
20130115.170432.860 r9999E main     OP50x    1808 Could not init p50x port! 

To stop modem-manager from to probe the OpenDCC Z1 I added this as /etc/udev/rules.d/70-mm-usb-device-blacklist-opendcc.rules:

ATTRS{idVendor}=="0403", ATTRS{idProduct}=="bfd8", ENV{ID_MM_DEVICE_IGNORE}="1" 
ATTRS{idVendor}=="0403", ATTRS{idProduct}=="bfd9", ENV{ID_MM_DEVICE_IGNORE}="1" 
ATTRS{idVendor}=="0403", ATTRS{idProduct}=="bfda", ENV{ID_MM_DEVICE_IGNORE}="1" 
ATTRS{idVendor}=="0403", ATTRS{idProduct}=="bfdb", ENV{ID_MM_DEVICE_IGNORE}="1" 
ATTRS{idVendor}=="0403", ATTRS{idProduct}=="bfdc", ENV{ID_MM_DEVICE_IGNORE}="1" 

If at moving a dialog moves the entire Rocview window, its time to tweak Gnome.
Install "gnome-tweaks" and disable the "Attach Model Dialogs" option:

Affected distributions: (Please report in the Forum in case a distribution is not listed.)

• Ubuntu
• Debian + Gnome Desktop