Version 1.300-1.300
- some minor bug fixes
- added new mode change user interface: while
the old style successive pressing of the [mode] key still works as
usual, it is now possible to directly select a specific mode.
This is how it works:
- press the [mode] key;
- now, while the display still shows the
next mode which would be activated in absence of further
key-presses, press the digit key corresponding to the
desired mode. This shall lead to the showing of a message
announcing the new mode. (At which point, should you change
your mind, you can still press a different digit key, etc.)
Depending on whether a particular
Intellibox features the memory mode or not (i.e., routes),
up to 4 modes are defined.
This is how they are numbered:
- Intellibox with memory mode (routes):
1: keyboard mode
2: memory mode
3: s88 monitor mode
4: programming mode
- Intellibox without memory mode
(routes):
1: keyboard mode
3: s88 monitor mode
4: programming mode
The amount of time the mode message
stays on the Intellibox display can be controlled through SO
#817 in 10 ms units (this SO is also available in older
software versions). The default value for SO #817 is 100,
i.e. 1 second.
|
- added new submenu in the main
configuration menu: LocoNet Prog.
This submenu is to be used in order to
read and program the configuration of LocoNet modules, like, e.g., the
Uhlenbrock 63340 and 63350 feedback modules.
- the "search" submenu of the
"Programming mode" is now disabled by default. It can be
re-enabled by changing the value of SO #836. That is:
SO #836 = 0 (default) -> no
"search" submenu SO #836 = 1 -> "search"
submenu enabled We adopted this change because unfortunately users
keep ‘misusing’ the search submenu in order to read the address
also of decoders which can be electronically read (in which case, of
course, a direct read - e.g., of CV #1 - is the right (and reliable)
way to proceed).
- new SO controlling whether the IB,
while reading or writing a long address, also sets Bit #5 of CV #29:
SO #662:
Bit #0 = 0 -> no Bit #5 set when reading
Bit #0 = 1
(default) -> Bit #5 is set when reading
Bit #1 = 0 ->
no Bit #5 set when writing
Bit #1 = 1
(default) -> Bit #5 is set when writing
Furthermore, Bit #2 of SO #662 tells
the IB whether to ignore or not any error during writing of Bit #5 of
CV #29. Since the SO edit submenu of the main settings menu does not
allow bit editing of an SO, these are the possible values of SO #662
along with the corresponding values of Bit #0 and Bit #1:
SO #662 value:
0 Bit #2=0, Bit #1=0, Bit #0=0
1 Bit #2=0, Bit
#1=0, Bit #0=1
2 Bit #2=0, Bit
#1=1, Bit #0=0
3 Bit #2=0, Bit
#1=1, Bit #0=1
4 Bit #2=1, Bit
#1=0, Bit #0=0
5 Bit #2=1, Bit
#1=0, Bit #0=1
6 Bit #2=1, Bit
#1=1, Bit #0=0
7 Bit #2=1, Bit
#1=1, Bit #0=1
This SO has been introduced in order to
provide a workaround for a bug of some recent Lenz decoders (LE010/011
(only some versions) and LE1024/5): these decoders, when asked to
write a bit of a CV do indeed perform the requested bit write albeit
without generating any acknowledge - what normally (without changing
SO #662 from its default value (3)) impedes long address reading and
also makes any long address write terminate with an error (though the
address has indeed been written and ‘activated’).
The suggested value for SO #662 in
order to apply the workaround is 7.
N.B. for reading or writing an
LE1024/5 decoder it may be needed to set SO #455 to the value
63 (the default of that SO being 51).
- Programming Mode menu: the SX programming
submenu can now be entered even if the SX decoder cannot be read. In
this case, the IB shall assume typical default values for the
decoder programmable parameters - with exception of the decoder
address: in order to make the read error apparent, the decoder
address is shown as 255 (an illegal SX address).
- fixed bug related to the generation of a DCC
broadcast packet with Speed = minimum.
This bug lead to the fact that, under specific
circumstances, locos equipped with some types of DCC decoders would
start at minimum speed without having been commanded to do so.
|