1srcpd.conf(5) File Formats Manual srcpd.conf(5)
2
3
4
6 srcpd.conf - The configuration file for the srcpd deamon
7
8
10 The file /etc/srcpd.conf is used by the srcpd (8). This file contains
11 the runtime configuration for the deamon and it's connection(s) to
12 model railroad system. See srcpd (8) for instruction how to use the
13 daemon.
14
15
17 The default file is shipped as with the srcpd and contains both default
18 settings and an example bus configuration.
19
20 <?xml version="1.0"?>
21 <srcpd version="2.0">
22 <bus>
23 <server>
24 <tcp-port>4303</tcp-port>
25 <pid-file>/var/run/srcpd.pid</pid-file>
26 <username>nobody</username>
27 <groupname>nogroup</groupname>
28 </server>
29 <verbosity>5</verbosity>
30 </bus>
31 <bus>
32 <loopback>
33 <number_fb>3</number_fb>
34 </loopback>
35 <use_watchdog>no</use_watchdog>
36 <verbosity>5</verbosity>
37 <auto_power_on>yes</auto_power_on>
38 </bus>
39 </srcpd>
40
41
43 The configuration file for srcpd is stored in XML format. As XML files
44 are plain text, experienced users can manipulate such files with the
45 help of a text editor. Less experienced users should select an exter‐
46 nal configuration tool to ensure a syntactically correct format.
47
48 If there are errors during configuration file reading the daemon will
49 send appropriate notifications to the syslog daemon. These messages
50 can be watched using with the syslog facility user.info. This facility
51 is usually sent to the file /var/log/messages (or /var/log/syslog). On
52 some systems the /etc/syslog.conf may need to be edited to access the
53 user.info facility:
54
55 user.info /var/adm/user-info.log
56
57
58 Currently there is no document type definition (DTD) available, to val‐
59 idate the format of a user created configuration file.
60
61 Each configuration file must provide the following base structure:
62
63 <?xml version="1.0"?>
64 <srcpd>
65 ...
66 </srcpd>
67
68 Within this structure (...) the necessary buses are configured, each
69 using a separate substructure:
70
71 <bus>
72 ...
73 </bus>
74 <bus>
75 ...
76 </bus>
77
78 General hints
79 The first configured bus should always be the server-bus. Sequence and
80 number of the following buses are any desired. Numbering of each sin‐
81 gle bus is done according to the sequence in this configuration file.
82 The server bus itself gets number 0, all following buses are numbered
83 continuously starting with 1 up to a maximum limit of 20.
84
85 Only buses that are actually used with the daemon should be filed. Not
86 used buses can be commented out:
87
88 <!--
89 <bus>
90 ...
91 </bus>
92 -->
93
94
95 Please bear in mind the numbering of the following buses will be
96 changed accordingly.
97
98 Universal options
99 The following options are usable for all used bus sections. Universal
100 options must be specified after bus specific options.
101
102 verbosity
103 Depending on this number (valid range: 0..5) the bus will tell
104 you less or more about what is happening. The 0 value gives a
105 minimum output. This option is mainly used for debugging rea‐
106 sons. You can watch these messages using the syslog daemon file
107 /var/log/messages (or /var/log/messages); see srcpd(8) for more
108 information. The default value is 4.
109
110 use_watchdog
111 Some buses provide a watchdog feature to cancel a blocked bus
112 thread. Valid input values are yes or no. The default value is
113 no.
114
115 restore_device_settings
116 Some buses provide a feature to restore serial device settings.
117 Valid input values are yes or no. The default value is no.
118
119 device This is the name of the connected device (like /dev/ttyS0). If
120 bus is server or loopback no assignment is necessary. The
121 default value is /dev/null.
122
123 auto_power_on
124 This option enables/disables automatical power on for a bus on
125 server daemon start. This option is not necessary for server
126 and loopback buses. The default value is no.
127
128 speed Buses using serial devices with a not fixed transfer speed allow
129 to adjust this parameter. Possible values are 2400, 4800, 9600,
130 19200, 38400, 57600 and 115200 baud. For buses with variable
131 interface speed the default value is 2400.
132
133 server
134 This bus is needed every time. The following options can be used for
135 individual setup.
136
137 tcp-port
138 This is the TCP/IP port for communication between srcpd and his
139 clients. Default is 4303 (this port number is assigned to SRCP
140 by IANA).
141
142 pid-file
143 File, where srcpd is storing it's process-id. According to FHS
144 the default is /var/run/srcpd.pid.
145
146 username
147 srcpd runs under this user. Default is nobody.
148
149 groupname
150 srcpd runs under this group. Default is nogroup.
151
152 dccar
153 This driver supports DC-Car Infrared Remote Control. This mode sup‐
154 ports remote control of cars (e.g. Faller Car-System) with a DC-Car
155 decoder or Infracar decoder. A sender must be connected to your PC's
156 seriall port. Some USB/Serial Adapter also work, e.g. Prolifi PL 2303
157 based adapter.
158
159 A description of the sender is available at http://www.dc-car.de/DC-
160 Car_PC_Sender.htm
161
162 mode This option specifies whether DC-Car or Infracar decoders are
163 controled. Currently it is not possible to combine both modes.
164 Possile values are dccar and infracar.
165
166 number_gl
167 This value specifies the address range of the used vehicles
168 (GL). Up to 1024 DC-Cars or 4096 Infracars can be controlled.
169 Default values are 1024 (dccar) and 4096 (infracar).
170
171 pause_between_commands
172 This value specifies the time between two commands The default
173 value is 10 ms.
174
175 Example
176 <bus>
177 <dccar>
178 <mode>dccar</mode>
179 <number_gl>1024</number_gl>
180 <pause_between_commands>10</pause_between_commands>
181 </dccar>
182 <auto_power_on>yes</auto_power_on>
183 <verbosity>4</verbosity>
184 <device>/dev/ttyUSB0</device>
185 </bus>
186
187 ddl
188 Digital Direct for Linux (DDL) via serial line (RS232). With this mod‐
189 ule the PC is enabled to generate a digital control voltage for
190 Maerklin/Motorola (MM) and/or NMRA/DCC using the serial interface
191 (RS232) hardware. Output lines TxD and GND are used by this feature
192 and must be connected to booster inputs properly.
193
194 This module exposes optimal signal performance if special user rights
195 for the srcpd are applied. It is recommended especially for
196 Maerklin/Motorola users to configure a system user srcpd and a group
197 srcpd with these command lines:
198
199 $ addgroup --system srcpd
200 $ adduser --system --no-create-home --ingroup srcpd srcpd
201
202 In order to increase the realtime priority for this user the system
203 file /etc/security/limits.conf must be edited to add following line:
204
205 srcpd - rtprio 99
206
207 According to these measures the configuration file must be adapted as
208 follows:
209
210 <server>
211 ...
212 <username>srcpd</username>
213 <groupname>srcpd</groupname>
214 ...
215 </server>
216
217
218 number_ga
219 Maximum usable decoder address number for generic accessory
220 devices (GA). The default value is 324.
221
222 please note that there is an offset of 4 between the DDL
223 addresses and the addresses according to the documentation from
224 maerklin. The equation ddl-address = maerklin docu address + 4
225 is used. This is due to some interpretation differences what the
226 trits mean. Details can be found at http://vogt-it.com/Open‐
227 Source/DDL/Addrestable.html
228
229
230 number_gl
231 Maximum usable decoder address number for generic locomotive
232 devices (GL). The default value is 81.
233
234 enable_ringindicator_checking
235 The ring indicator (RI) is a line of the serial interface RS232.
236 This line can be used to switch off digital signal power, e.g.
237 by pushing a connected emergency stop button. Signal power is
238 switched off if RI line input voltage changes from -12V (-5V) to
239 +12V (+5V). If this feature is used, the parameter must be set
240 to yes, if not used, it must be set to no. The default value is
241 no.
242
243 enable_checkshort_checking
244 The DSR line of the serial interface RS232 can be used to switch
245 off digital power as response to shortcut detection. The con‐
246 nected booster must provide support for this kind of feature and
247 must be wired to this line accordingly. If used the parameter
248 must be set to yes, if not used, it must be set to no. The
249 default value is no.
250
251 inverse_dsr_handling
252 Some boosters provide inverted output voltage for shortcut
253 detection. If such a booster is used this parameter must be set
254 to yes. The default value is no.
255
256 enable_maerklin
257 This parameter must be set to yes, if decoders for the old (not
258 mfx) Maerklin/Motorola (MM) format are used. If not used, it
259 should be set to no. The default value is yes.
260
261 enable_nmradcc
262 This parameter must be set to yes, if decoders for NMRA/DCC for‐
263 mat are used. If not used, it should be set to no. The default
264 value is yes.
265
266 It is also possible to enable both digital protocol formats, to drive
267 decoders of both digital systems attached to the same power line. In
268 order to minimize CPU load, the not used protocol should always be dis‐
269 abled.
270
271 improve_nmradcc_timing
272 The default baudrate of DDL is 19200 baud, which is slightly
273 higher than allowed by NMRA DCC standard. With a UART 16550A
274 you can change the baudrate to 16457 baud, which is within the
275 specification. This is only needed if you have timing problems
276 with the default. Valid input values are yes or no. The
277 default value is no, which corresponds to 19200 baud.
278
279 nmra_ga_offset
280 This parameter is for backward compatibility to erddcd and
281 alternate usage of different central units, due to the fact
282 there are two ways to handle NMRA/DCC decoder addresses. This
283 parameter allows to add an offset to all used address values.
284 E.g., if all GA decoder addresses are shifted by 4 (i.e. you
285 want to change switch 1, and you have to change switch 5 to do
286 this), then this parameter should be set to 1. Valid values are
287 0 and 1. Default value is 0.
288
289 shortcut_failure_delay
290 Number of micro seconds srcpd waits to switch off digital power,
291 after a shortcut is detected. The default value is 0.
292
293 nmradcc_translation_routine
294 There are 3 implementations for converting the logical command
295 bits into serial line commands, considering the start and stop
296 bits of the serial line. Valid values are 1, 2 and 3. Default
297 value is 3.
298
299 enable_usleep_patch
300 Due to certain issues of the MM protocol its usage results in a
301 significant amount of CPU load for srcpd, caused by busy wait‐
302 ing. This parameter gives the possibility to improve this situ‐
303 ation by introducing a process wait state for a certain amount
304 of time. Normally this does not result in any trouble control‐
305 ling the attached decoders, so the parameter should be set to
306 yes. Valid values are yes and no. The default value is yes.
307
308 usleep_usec
309 Number of micro seconds the signal generating process pauses.
310 This value should be as small as possible; a bigger value can
311 result in improper digital signal generation. There have been
312 good results using values between 100 and 250 usecs. This
313 parameter is only used, if enable_usleep_patch is set to yes.
314 The default value is 100.
315
316 program_track
317 This parameter allows you to suppress commands which are issued
318 for a program track. This parameter should only be used on your
319 main. Valid input values are yes or no. The default value is
320 yes, i.e. all program track commands will be executed by
321 default.
322
323 Example Maerklin/Motorola
324 <bus>
325 <ddl>
326 <number_ga>200</number_ga>
327 <number_gl>81</number_gl>
328 <enable_maerklin>yes</enable_maerklin>
329 <enable_nmradcc>no</enable_nmradcc>
330 <enable_usleep_patch>yes</enable_usleep_patch>
331 <usleep_usec>200</usleep_usec>
332 </ddl>
333 <auto_power_on>no</auto_power_on>
334 <verbosity>4</verbosity>
335 <device>/dev/ttyS0</device>
336 </bus>
337
338 Example NMRA/DCC
339 <bus>
340 <ddl>
341 <number_ga>160</number_ga>
342 <number_gl>60</number_gl>
343 <enable_maerklin>no</enable_maerklin>
344 <enable_nmradcc>yes</enable_nmradcc>
345 <nmradcc_translation_routine>3</nmradcc_translation_routine>
346 </ddl>
347 <auto_power_on>no</auto_power_on>
348 <verbosity>4</verbosity>
349 <device>/dev/ttyS0</device>
350 </bus>
351
352 ddl-s88
353 Digital Direct for Linux S88 via parport (IEEE 1284). This bus pro‐
354 vides up to four S88 data links attached to the parallel port to con‐
355 nect S88-feedback modules. Usage of one S88 line is possible by simply
356 wiring modules to the parallel port connectors; for advanced applica‐
357 tions involving more than one line the wiring scheme is equivalent to
358 the one from the DDL daemon erddcd (http://www.vogt-it.com/Open‐
359 Source/DDL) as shown in the circuit of Martin Wolf. The four S88 data
360 links are managed as separate buses.
361
362 The maximum count of modules (with 16 contacts) which can be connected
363 to a data link is 31; so maximal 496 contacts are supported per link.
364 When using modules with 8 contacts two modules count as one.
365
366 For each data link a separate bus is initialized where the sequence of
367 the feedback contacts of the modules is increasing as the modules are
368 connected to the data link. If there are no modules connected to a
369 data link the respective value of number_fb_x must be set to 0. Never‐
370 theless this bus is initialized, that means also if only one bus is
371 used, all four buses are initialized.
372
373 ioport Input/output address of the printer port. The default value is
374 0x0378. The value for ioport must be given in hexadecimal for‐
375 mat (starting with 0x). Valid values for a typical Linux system
376 are 0x0378, 0x0278 and 0x03BC. The right value can easily be
377 detected searching through the kernel start-up messages:
378 dmesg | grep parport
379
380 clockscale
381 Parameter to adjust the clock rate for reading the modules. In
382 the case of the default value 35 the original S88 clock rate of
383 approximately 8 KHz would be achieved. Smaller values increas‐
384 ing the clock rate but not each module can work with this. In
385 maximum there is approximately 125 KHz possible.
386
387 refresh
388 Delay time in milliseconds after witch the feedback modules are
389 read again. In case of the default value 100 the data is
390 refreshed each 100 ms.
391
392 The higher this value the less often the attached modules are
393 read and the less is the resulting system load. Useful values
394 are between 100 and 250.
395
396 fb_delay_time_0
397 This value in milliseconds determines how long the signal on a
398 feedback contact must be on zero level before it is accepted as
399 valid and will be forwarded to all clients. With this parameter
400 it is in a limited range possible to debounce bad feedback con‐
401 tacts (bouncing contacts). The default value is 0.
402
403 number_fb_1
404 This statement defines the count of feedback modules connected
405 to the data link number 1.
406
407 number_fb_2
408 This statement defines the count of to data link number 2 con‐
409 nected feedback modules.
410
411 number_fb_3
412 This statement defines the count of to data link number 3 con‐
413 nected feedback modules.
414
415 number_fb_4
416 This statement defines the count of to the data link number 4
417 connected feedback modules.
418
419 Inside of the configuration the common values should be arranged before
420 the bus specific values.
421
422 Example
423 <bus>
424 <auto_power_on>yes</auto_power_on>
425 <verbosity>5</verbosity>
426 <ddl-s88>
427 <ioport>0x378</ioport>
428 <number_fb_1>9</number_fb_1>
429 <number_fb_2>0</number_fb_2>
430 <number_fb_3>0</number_fb_3>
431 <number_fb_4>0</number_fb_4>
432 </ddl-s88>
433 </bus>
434
435 hsi-88
436 This driver supports the HSI-88 device from Littfinski connected via
437 serial line. An USB2Serial converter should work fine. The serial
438 line speed setting is fixed to 9600 baud and cannot be changed.
439
440 The HSI-88 device provides three lines for feedback modules. To each
441 line a maximum of 31 modules (each with 16 inputs) can be attached. If
442 modules with 8 inputs are used, two modules count as one.
443
444 number_fb_left
445 This value is the number of feedback-modules (with 16 inputs)
446 connected to the line called left.
447
448 number_fb_center
449 This value is number of feedback-modules (with 16 inputs) con‐
450 nected to the line called center.
451
452 number_fb_right
453 This value is number of feedback-modules (with 16 inputs) con‐
454 nected to the line called right.
455
456 fb_delay_time_0
457 This is the time in milliseconds a feedback input must be zero,
458 before zero is delivered to the attaches SRCP clients. With
459 this feature it is possible to compensate bad feedback bounces
460 in a certain range. The default value is 0.
461
462 refresh
463 The time in microseconds (us) after srcpd will read feedback
464 again from HSI-88. The default value is 10000 us. The lower
465 this value the higher the resulting CPU load.
466
467 Example
468 <bus>
469 <hsi-88>
470 <number_fb_left>8</number_fb_left>
471 <number_fb_center>5</number_fb_center>
472 <number_fb_right>0</number_fb_right>
473 <refresh>10000</refresh>
474 </hsi-88>
475 <auto_power_on>yes</auto_power_on>
476 <verbosity>4</verbosity>
477 <device>/dev/ttyS0</device>
478 </bus>
479
480 i2c-dev
481 Bus driver for i2c-dev interface of the Linux kernel, can be used to
482 access hardware found on http://www.matronix.de/.
483
484 multiplex_buses
485 TODO
486
487 ga_hardware_inverters
488 TODO
489
490 ga_reset_device
491 TODO
492
493 intellibox
494 This driver supports the Intellibox device from Uhlenbrock (IB) con‐
495 nected via the serial port. Only extended mode commands are used (P50X
496 binary protocol); this should be taken into account if protocol compat‐
497 ible devices (e.g. OpenDCC, DiCoStation, EasyControl) are used. Pro‐
498 gramming decoders is currently implemented for DCC only. Possible val‐
499 ues for speed of serial port are depending from device and interface
500 type 2400 baud, 4800 baud, 9600 baud, 19200 baud, 38400 bau and
501 57600 baud.
502
503 fb_delay_time_0
504 This is the time in milliseconds a feedback input must be zero,
505 before this value is delivered to clients. With this feature
506 you can compensate bad feedback in a specific range. The
507 default value is 0 ms.
508
509 pause_between_commands
510 This is the time in milliseconds between two commands the driver
511 must wait. The exact value should be hand tuned. If the system
512 does not respond or drops commands try to increase this value.
513 Default is 250 ms.
514
515 number_ga
516 This is the maximal address number of Generic Accessory decoders
517 (GA). Supported range is 0..1024. A value of 0 means no GA
518 available. Default is 256.
519
520 number_gl
521 Like the number of GA this number limits the maximum address of
522 the Generic Locomotive decoders (GL). Supported range is
523 0..10239. A value of 0 means no GL available. Default is 80.
524
525 number_fb
526 This is the number of S88 modules attached to the Intellibox
527 device. The maximum valid number is 31. The default is 0 (no
528 modules are attached). Please note that Loconet is currently
529 not supported.
530
531 auto_speed_detection
532 This option activates an automatical baudrate detection of the
533 connected Intellibox (BABI, Break and Automatic Baud-rate Iden‐
534 tification). This procedure takes several seconds but if
535 enabled it is not necessary to specify a value for the speed
536 parameter. If disabled the connection initialization is much
537 faster but the given speed value must comply to the actual
538 Intellibox setting. Valid values are yes and no. The default
539 value is yes.
540
541 Example
542 <bus>
543 <intellibox>
544 <number_ga>250</number_ga>
545 <number_gl>100</number_gl>
546 <number_fb>4</number_fb>
547 <fb_delay_time_0>0</fb_delay_time_0>
548 <pause_between_commands>0</pause_between_commands>
549 </intellibox>
550 <speed>19200</speed>
551 <auto_speed_detection>no</auto_speed_detection>
552 <auto_power_on>no</auto_power_on>
553 <verbosity>4</verbosity>
554 <device>/dev/ttyUSB0</device>
555 </bus>
556
557 li100, li100usb
558 This driver connects with the LI100, LI100F, LI101F or LI-USB devices
559 from Lenz connected via the serial port/USB-interface. An USB2Serial
560 converter should not be used. The serial line settings are depending
561 on type of interface. For LI-USB it's fixed to 57600 baud with no
562 chance to change. Autodetection of serial port interface speed is cur‐
563 rently under construction. If connection fails, try restart of srcpd
564 with an other speed. Possible values are 9600 baud, 19200 baud,
565 38400 baud, 57600 baud and 115200 baud, depending on your interface.
566
567 fb_delay_time_0
568 This is the time in milliseconds an feedback input must be zero,
569 before this value is delivered to clients. With this feature
570 you can compensate bad feedback in a specific range. The
571 default value is 0 ms.
572
573 number_ga
574 This is the number of GA. Supported range is 0..1024. A value
575 of 0 means no GA available. Default is 99 (LI-USB 9999).
576
577 number_gl
578 Like the number of GA this number gives the maximum address.
579 Supported range is 0..9999. A value of 0 means no GL available.
580 Default is 99 (LI-USB 9999).
581
582 number_fb
583 This is the number of RS modules attached to the Lenz device.
584 It can be as large as 512. It's assumed, that one module has 8
585 inputs. A value of 0 means no FB available. Default is 256
586 (LI-USB 512).
587
588 For Lenz USB interfaces It is very important to have the kernel module
589 ftdi_sio available. Due to the Lenz concept, the interface unit
590 returns different values after start.
591
592 0 everything is OK
593
594 -1 Central Unit not found. Unable to read version of central unit.
595
596 -2 Central Unit not found. Unable to read version of central unit.
597
598 -3 Interface not found. Unable to read version of interface. This
599 can also happen, if no central unit is connected to interface.
600
601 -4 device not found
602
603 loconet
604 This bus provides a driver for the Loconet system by Digitrax. The
605 device settings may be either serial connections (e.g. MS100,
606 LocoBuffer) or TCP/IP network links (e.g. LbServer, http://locone‐
607 tovertcp.sourceforge.net/).
608
609 sync-time-from-loconet
610 Decode time messages from the loconet and set the SRCP TIME
611 device. Valid values are yes or no. Default is no.
612
613 loconet-id
614 Default is 0x50.
615
616 ms100 Support for the MS100/RS232 device of Digitrax. Valid values
617 are yes and no. Default is no.
618
619 Example
620 <bus>
621 <loconet>
622 <loconet-id>80</loconet-id>
623 <sync-time-from-loconet>no</sync-time-from-loconet>
624 <ms100>no</ms100>
625 </loconet>
626 <device type="network" port="1234">127.0.0.1</device>
627 <!--
628 <device type="file">/dev/ttyS0</device>
629 -->
630
631 </bus>
632
633 loopback
634 This bus does not connect to real hardware. It is used primarily for
635 development tasks but may be useful for real installations too. Every
636 command on this bus does only have an echo effect on the INFO sessions.
637 This device may be used as virtual device for communication tasks.
638
639 number_ga
640 This is the maximal address number of Generic Accessory (GA)
641 devices. Default is 256.
642
643 number_gl
644 This number gives the maximum valid address number of the
645 Generic Locomotive (GL) devices. Default is 80
646
647 number_fb
648 Different to other buses this parameter takes the number of
649 feedback contacts, not modules. Simulation of two feedback mod‐
650 ules, each providing 16 contacts, accordingly needs a parameter
651 value of 32. Default is 0 (no contact).
652
653 Example
654 <bus>
655 <loopback>
656 <number_ga>120</number_fb>
657 <number_gl>100</number_fb>
658 <number_fb>64</number_fb>
659 </loopback>
660 <verbosity>2</verbosity>
661 <auto_power_on>no</auto_power_on>
662 </bus>
663
664 m605x
665 This supports communication with the 6051 or 6050 devices from Maerklin
666 connected via the serial port. An USB2Serial converter should work
667 fine. The serial line settings are fixed to 2400 baud 8N2 and cannot
668 be changed.
669
670 m6020mode
671 In this mode the srcpd does not sent the 4 functions. This is a
672 feature of the 6021 only. Valid values are yes and no. Default
673 value is no.
674
675 fb_delay_time_0
676 This is the time the driver code waits until it recognized the
677 input change in milliseconds. This feature may support a
678 debounce found in the hardware. The default value is 0 ms.
679
680 ga_min_activetime
681 The time in milliseconds a GA device needs to be in active
682 state. The absolute minimum is 75 ms and is needed for stable
683 communication with the 6051. The default value is 75 ms.
684
685 pause_between_commands
686 This is the time between two commands the drivers must wait.
687 The exact values should be hand tuned. If the system does not
688 respond or drops commands try to increase this value. Default
689 is 200 ms.
690
691 pause_between_bytes
692 This is the time the driver waits between 2 bytes in multi-byte
693 commands. The hardware handshake does not work with all devices
694 so this parameter was introduced to support it. The default is
695 2 ms.
696
697 number_ga
698 This is the number of GA. This parameter does not have a real
699 effect since the interface supports the addresses 1..256 only.
700 Keep the default value 256 untouched.
701
702 number_gl
703 Like the number of GA this number gives the maximum GL address.
704 Since this number is limited to 80, keep the default value 80
705 untouched.
706
707 number_fb
708 This is the number of 6088 modules attached to the 6051/6050
709 device. The valid range is from 0..31. The default value is 0
710 (no modules are attached). Please note that 6088 modules
711 attached to other devices (memory) cannot be accessed.
712
713 Example
714 <bus>
715 <m605x>
716 <number_ga>120</number_fb>
717 <number_gl>60</number_fb>
718 <number_fb>8</number_fb>
719 <ga_min_activetime>150</ga_min_activetime>
720 <pause_between_bytes>2</pause_between_bytes>
721 <pause_between_commands>50</pause_between_commands>
722 </m605x>
723 <auto_power_on>no</auto_power_on>
724 <verbosity>4</verbosity>
725 <device>/dev/ttyS0</device>
726 </bus>
727
728 selectrix
729 Selectrix CC-2000 and Rautenhaus SLX852.
730
731 number_ga
732 TODO
733
734 number_gl
735 TODO
736
737 number_fb
738 TODO
739
740 controller
741 TODO
742
743 zimo
744 This bus provides support for the old ASCII based Zimo MX1 interface
745 protocol. The baud rate can not be changed and has an internal preset
746 of 9600 Baud.
747
748 number_ga
749 This value sets the maximum number for the GA address range.
750 For protocol M (Maerklin/Motorola) the upper limit is 63, for
751 protocol N (NMRA/DCC) the upper limit is 2044 (according to
752 Lenz-DCC address scheme). The Z (Zimo) protocol is not sup‐
753 ported yet. The default value is 256.
754
755 number_gl
756 This value sets the maximum number for the GL address range.
757 The default value is 80.
758
759 number_fb
760 Not supported. The default value is 0.
761
762 fb_delay_time_0
763 Not supported.
764
765
767 /etc/srcpd.conf
768
769
771 srcpd (8)
772
773
775 This man page was written by Matthias Trute (mtrute@users.source‐
776 forge.net), Frank Schimschke (schmischi@users.sourceforge.net) and
777 Guido Scholz (gscholz@users.sourceforge.net).
778
779
780
781 December 19, 2009 srcpd.conf(5)