The port must differ from the client service port to avoid conflicts.
Use this service if a faster clock is wanted and/or all clients must be synchronized.
The time divider is used to setup the clock speed: 1…100. (Example: A divider of 10 will run the model time 10 times faster than real time.)
The next field is the Client update frequency in model minutes: 1…60. Default is every model minute.
This is the start time for the clock service.
The computer time is used if the values are set to 24:60.
With this option all fast clock options are available if the divider is set to one. (Otherwise clock commands are rejected.)
Note: The clock will no longer be in sync with the hardware computer clock.
Stop the fast clock in case of a power off event. (Short cut)
This is the port at which Rocview clients must connect to become all data and events needed to function.
The official assigned port by IANA is 8051.
Prevent secondary clients controlling the Rocrail server; only the first one connected has control.
A better solution is the use of Control or Slave Code.
Enables monitoring of WIO reachability. The timeout ist defined in units of 10 ms.
Default: 500 x 10 ms = 5 secounds.
The client must provide this control code to get write access if set.
If the slave code is set, and a connected client cannot provide this code, the following selected features will be rejected:
Optional serial device to service SRCP.
Line settings are fixed:
Activates the SNMP v1/2c Agent in the Rocrail server.
By default port 161 is used for the SNMP service which requires extra user privilege:
OSNMP 0658 SNMP bind OSocket 0513 bind() failed  [Permission denied]
<SnmpService port="161" trapport="162" traphost="192.168.100.77"/>
$ snmpget -v 2c -c public localhost 18.104.22.168.22.214.171.124.0 iso.126.96.36.199.188.8.131.52 = STRING: "Rocrail 2.0.2508 Sunrise"
$ snmpget -v2c -c public localhost SNMPv2-MIB::sysDescr.0 SNMPv2-MIB::sysDescr.0 = STRING: Rocrail 2.0.2508 Sunrise $ snmpget -v2c -c public localhost SNMPv2-MIB::sysUpTime.0 SNMPv2-MIB::sysUpTime.0 = Timeticks: (3443) 0:00:34.43
The location of the @Box.
Clients can use the MQTT Broker to communicate with the Rocrail Server.
| ||All server broadcasts are published with this topic name.|
| || Clients can publish commands with this topic.
A valid support key is necessary; Without key only 5 demo minutes.
| ||Clients can publish hardware events with this topic.|
| ||Command station commands for User Libraries.|
The DNS name or TCPIP address of the MQTT Broker.
The service port number of the MQTT Broker.
The default port number used by Mosquitto is 1883.
Use the Item Names in the Broadcast Topic.
With both topics, field and command, it is possible to implement a user defined CS library without Rocrail Source dependencies.
Only Quality of Service 1 is supported.
Clients may use QoS 0, but we strongly recommend QoS 1.
The only known Client for this service is the command line utility of Mosquitto:
mosquitto_pub -p 60123 -t rocrail/service/client -m "<sys cmd=\"stop\"/>" -q 1
1467710159: New connection from 127.0.0.1. 1467710159: New client connected from 127.0.0.1 as mosq_pub_2323_rob-Virt. 1467710159: Sending CONNACK to mosq_pub_2323_rob-Virt (0) 1467710159: Received PUBLISH from mosq_pub_2323_rob-Virt (d0, q1, r0, m1, 'rocrail/service/client', ... (17 bytes)) 1467710159: Sending PUBACK to mosq_pub_2323_rob-Virt (Mid: 1) 1467710159: Sending PUBLISH to RocrailService (d0, q1, r0, m1, 'rocrail/service/client', ... (17 bytes)) 1467710159: Received DISCONNECT from mosq_pub_2323_rob-Virt 1467710159: Received PUBACK from RocrailService (Mid: 1) 1467710159: Received PUBLISH from RocrailService (d0, q1, r0, m3, 'rocrail/service/info', ... (51 bytes)) 1467710159: Sending PUBACK to RocrailService (Mid: 3) 1467710159: Received PUBLISH from RocrailService (d0, q1, r0, m4, 'rocrail/service/info', ... (175 bytes)) 1467710159: Sending PUBACK to RocrailService (Mid: 4) 1467710160: Received PUBLISH from RocrailService (d0, q1, r0, m5, 'rocrail/service/info', ... (60 bytes)) 1467710160: Sending PUBACK to RocrailService (Mid: 5)
An UDP Multicast discovery service is also available for other devices which wants to use the same broker.
The device must send a message withe the following content:
It will get the following reply:
Both lines ends with a linefeed:
If the Rocrail MQTT-Broker connection get lost, the Last Will can be observed in topic