FAQ
Rocview
- 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.)
- Rocview does no longer get update events from server and or freezes.
- 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.
- Rocview 'hangs' after opening a Workspace.
- The client TCP port is not set to 8051 in the rocrail.ini found in the selected Workspace.
- Rocview needs too much CPU power and has a bad performance.
Check following options:
Rocrail
- Rocrail crash at startup under Windows.
- “Interface ID is not set”
- A none existing IID used or no default Command Station set.
- Rocrail needs too much CPU power.
Märklin CentralStation 2
- S88 Feedbacks do not report:
- I have problems to setup the CS2 network:
USB
- 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.
Serial device user access (Linux)
To access a serial device the user must be added in the dialout group:
Command:
$ sudo adduser xxx dialout
Output:
[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.
Device or resource busy (Linux)
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"
Trace: » faq-en


