Barix Wiki - User contributions [en]

IP Audio Delay

2013-06-13T09:21:08Z

Achims: /* Barix devices */

Whenever you transport audio over an IP network - that is true for every vendor and every technology, you will incur a delay. That is unavoidable. Why ? This page will explain the general concept of how Audio over IP works, and explain specifically the reasons for an inherent delay.

CURRENTLY WORK IN PROGRESS - NEEDS TO BE REVIEWED

== Concept of Audio over IP ==
=== Sampling ===
To transmit Analog Audio over an IP Network, it needs to be sampled (a measure be taken) with the sample rate. These samples then can be handled in the digital domain and transferred over the network to the decoder, which ultimately will convert the samples back to an analog voltage on the audio output, accurate with the sample frequency.
The original signal as it was present at the input is reproduced on the output.

=== Sending every sample over the network ===
In theory, every sample could be directly sent as a block over the IP network with minimum delay, but doing this will generate a huge amount of traffic (48.000 blocks per second for 48khz sample rate) and bandwidth requirement (a min. ethernet frame is 60bytes, so you are actually using more than 23MBps if you do this) !

Ethersound does this, actually - all channel samples at a given timepoint (one per channel) go together in a frame on the network, one frame per sample set .. generating practically a constant network load of 100Mbps (not over IP, but over Ethernet).

For standard applications where the audio stream needs to coexist on the network with other services, something must be done to generate less network load

=== Collecting samples, sending packets ===
Let us assume the network load, expressed in number of packets per second, needs to be limited to no more than 100 (blocks per second). To achieve that, the device will need to to collect 10ms worth of samples before sending them out together in an IP block.

With a 48kHz sample frequency, that means 480 samples (960 bytes) have to be collected before the block can be sent. That is making perfect sense, as one Ethernet block can carry up to about 1400 bytes of Data.

=== Receiving and decoding ===

At the receiving end (the "Decoder"), a constant stream of samples at the sample frequency must be generated. To do this, the decoder always needs samples "in storage" it can use, if it ever runs out of samples to generate the stream, an "underrun" condition exists, which will cause dropouts and other issues. Consequently, a buffer of samples must be maintained, high enough so that it always is replenished before the D/A runs out of data.

== Delays introduced in the chain ==

=== Packetizing at the encoder ===
As already discussed above, to limit the bandwidth used to a reasonable level, samples must be collected and send as blocks to the destination, via the network. Here is the first delay. It is pretty obvious: The delay incurred, even with an optimum system performance, directly depends on the number of samples per block resp. blocks per second.
if 100 blocks per second is the target, 10ms of samples need to be collected, if 50 blocks per second are allowed, 20ms worth of samples need to be collected before they can be sent.

With MP3, not only is a frame of samples first collected (20..50ms, depending on audio frequency setting), but the collected samples then, once complete, must be processed with computational intensive functions (DSP), which takes significant time (but average less than it took to collect the samples, otherwise the system cannot work reliably).

=== Processing at the encoder ===
While putting PCM samples in a packet and sending them does not really need resources, in the MP3 case, a significant delay is introduced in addition to the delay produced by "holding up" the samples to packetize them. Count in 20ms for MP3.

=== Network delay "in transit" ===

Now that a block is going to the network, some delay already is introduced (let's stick with the example, 10ms for PCM and 60ms for MP3). The block now needs to be sent over the network, potentially fighting with other traffic for bandwidth. On a local LAN, the delay will typically be quite low (msecs maybe), but beware .. if there is "sometimes" a fight over bandwidth/buffering in a switch or router, you may see average very low delays but PEAK delays could be substantially higher.
Why is that a problem ? Well .. the receiving side always needs to be fed with samples before its buffers run empty .. now, if there is a block delayed, let's say 30ms, the receiver must have buffers configured so that it can live with that delay before running into an error condition (empty buffer). The difference between the min. delay and the max. delay of a network block arriving at the decoder is commonly called "jitter". Jitter can be significant especially with Wifi networks, as there are invisible retries happening in a lower level protocol - you might see (ping command shows all this) an average delay of only 5ms, and zero block loss, but a max. delay of 200ms ... any device with a receive buffer configured of less than 200ms will mean that you will encur dropouts. period.

=== Buffers in the receiver ===
Now, let's take a close look at the decoding side. As already stated before, to maintain a constant, consistent stream of samples (which are then converted to an analog value and sent to the audio interface), buffering is a must. The buffers must be able and configured to hold as much data as necessary to cover/survive the longest possible "dry period" when no block comes in from the source, for whatever reason.
If (example above), the source sends a block every 10ms, very precise timing, and zero jitter is introduced by the network (an unlikely scenario), in theory a buffer of one frame is sufficient. When the block arrives from the network, it will be copied into the buffer (let's say, holding 480 samples, in our example with 10ms) and the output can start converting to analog. The buffer now drains, but right when it is getting to "empty", the next block comes in from our perfect encoder through the perfect network infrastructure.
That is, unfortuntately, not a real life scenario, jitter is always introduced somewhere on the way. A realistic setup uses a buffer holding several blocks.

=== Processing in the Receiver ===
Oh yes, and for MP3, you have to add another reason for delay at the decoder side. Once a frame is received, it cannot be output immediately, but it first needs to be decoded, which is resource intensive and can take several ms .. and there is a need for an output buffer for samples ...

=== Sample buffer for the D/A ===
The last addition of delay is not really necessary technology wise, but a fact in Barix devices. We use a Main CPU for network tasks and a DSP driving the D/A, which turns the samples back to analog audio. The DSP is necessary for MP3 (and AAC etc etc) decoding, for PCM it mainly works as a pass-through. The interface between the main CPU and the DSP also introduces a sample buffer at the DSP output side, which is counted in bytes, and can introduce quite significant delays for low bitrate/sample rate streams. Why ? Well, the buffer is counted in Bytes as i said, and let's assume for these examples here it is 2kBytes (2000 bytes), for a PCM 48kHz stream that means 96Bytes per ms, so roughly 20ms - but if you send a 8Khz PCM stream, you get 6x that delay.

== Conclusion ==
So, at the end you have several sources introducing delay, with the buffering for network jitter being often the most significant one, but a "base delay", depending on sample rate, encoding format etc is always present. As you can figure from the above examples, if you have the bandwidth, it often makes sense to configure higher sample rates and bitrate streams, as that will effectively lower the delay due to the fact that the constant (byte wise) buffers in the chain have a smaller through delay.

== Barix devices ==
One last comment, now specific to Barix devices: The Exstreamer 1xx and 2xx decoder devices use a DSP with ample buffering. There is reasons for that, not to be further detailed here. In contrast, the Exstreamer 1000 use a different DSP with lower buffers, and we are currently beta testing a DSP software patch which reduces the buffers much further to almost non-existing !
With the Exstreamer 1000, you can currently achieve delays of below 50ms - the software has not been optimized for very low delay. However, with optimized software, you can get the delay down to well below 20ms - that has been proven in our labs (for a specific project). We are in the process to bring this down further, obviously (goal 5ms ?) this can only be done by sending many more blocks over the network, for example, one per ms - 1000 blocks per second .. ask your Wifi router what it thinks about that ..), so it needs optimized software.

Back to [[Main_Page#Software_Topics]]

IP Audio Delay

2013-06-13T09:20:16Z

Achims: /* Barix devices */

Whenever you transport audio over an IP network - that is true for every vendor and every technology, you will incur a delay. That is unavoidable. Why ? This page will explain the general concept of how Audio over IP works, and explain specifically the reasons for an inherent delay.

CURRENTLY WORK IN PROGRESS - NEEDS TO BE REVIEWED

== Concept of Audio over IP ==
=== Sampling ===
To transmit Analog Audio over an IP Network, it needs to be sampled (a measure be taken) with the sample rate. These samples then can be handled in the digital domain and transferred over the network to the decoder, which ultimately will convert the samples back to an analog voltage on the audio output, accurate with the sample frequency.
The original signal as it was present at the input is reproduced on the output.

=== Sending every sample over the network ===
In theory, every sample could be directly sent as a block over the IP network with minimum delay, but doing this will generate a huge amount of traffic (48.000 blocks per second for 48khz sample rate) and bandwidth requirement (a min. ethernet frame is 60bytes, so you are actually using more than 23MBps if you do this) !

Ethersound does this, actually - all channel samples at a given timepoint (one per channel) go together in a frame on the network, one frame per sample set .. generating practically a constant network load of 100Mbps (not over IP, but over Ethernet).

For standard applications where the audio stream needs to coexist on the network with other services, something must be done to generate less network load

=== Collecting samples, sending packets ===
Let us assume the network load, expressed in number of packets per second, needs to be limited to no more than 100 (blocks per second). To achieve that, the device will need to to collect 10ms worth of samples before sending them out together in an IP block.

With a 48kHz sample frequency, that means 480 samples (960 bytes) have to be collected before the block can be sent. That is making perfect sense, as one Ethernet block can carry up to about 1400 bytes of Data.

=== Receiving and decoding ===

At the receiving end (the "Decoder"), a constant stream of samples at the sample frequency must be generated. To do this, the decoder always needs samples "in storage" it can use, if it ever runs out of samples to generate the stream, an "underrun" condition exists, which will cause dropouts and other issues. Consequently, a buffer of samples must be maintained, high enough so that it always is replenished before the D/A runs out of data.

== Delays introduced in the chain ==

=== Packetizing at the encoder ===
As already discussed above, to limit the bandwidth used to a reasonable level, samples must be collected and send as blocks to the destination, via the network. Here is the first delay. It is pretty obvious: The delay incurred, even with an optimum system performance, directly depends on the number of samples per block resp. blocks per second.
if 100 blocks per second is the target, 10ms of samples need to be collected, if 50 blocks per second are allowed, 20ms worth of samples need to be collected before they can be sent.

With MP3, not only is a frame of samples first collected (20..50ms, depending on audio frequency setting), but the collected samples then, once complete, must be processed with computational intensive functions (DSP), which takes significant time (but average less than it took to collect the samples, otherwise the system cannot work reliably).

=== Processing at the encoder ===
While putting PCM samples in a packet and sending them does not really need resources, in the MP3 case, a significant delay is introduced in addition to the delay produced by "holding up" the samples to packetize them. Count in 20ms for MP3.

=== Network delay "in transit" ===

Now that a block is going to the network, some delay already is introduced (let's stick with the example, 10ms for PCM and 60ms for MP3). The block now needs to be sent over the network, potentially fighting with other traffic for bandwidth. On a local LAN, the delay will typically be quite low (msecs maybe), but beware .. if there is "sometimes" a fight over bandwidth/buffering in a switch or router, you may see average very low delays but PEAK delays could be substantially higher.
Why is that a problem ? Well .. the receiving side always needs to be fed with samples before its buffers run empty .. now, if there is a block delayed, let's say 30ms, the receiver must have buffers configured so that it can live with that delay before running into an error condition (empty buffer). The difference between the min. delay and the max. delay of a network block arriving at the decoder is commonly called "jitter". Jitter can be significant especially with Wifi networks, as there are invisible retries happening in a lower level protocol - you might see (ping command shows all this) an average delay of only 5ms, and zero block loss, but a max. delay of 200ms ... any device with a receive buffer configured of less than 200ms will mean that you will encur dropouts. period.

=== Buffers in the receiver ===
Now, let's take a close look at the decoding side. As already stated before, to maintain a constant, consistent stream of samples (which are then converted to an analog value and sent to the audio interface), buffering is a must. The buffers must be able and configured to hold as much data as necessary to cover/survive the longest possible "dry period" when no block comes in from the source, for whatever reason.
If (example above), the source sends a block every 10ms, very precise timing, and zero jitter is introduced by the network (an unlikely scenario), in theory a buffer of one frame is sufficient. When the block arrives from the network, it will be copied into the buffer (let's say, holding 480 samples, in our example with 10ms) and the output can start converting to analog. The buffer now drains, but right when it is getting to "empty", the next block comes in from our perfect encoder through the perfect network infrastructure.
That is, unfortuntately, not a real life scenario, jitter is always introduced somewhere on the way. A realistic setup uses a buffer holding several blocks.

=== Processing in the Receiver ===
Oh yes, and for MP3, you have to add another reason for delay at the decoder side. Once a frame is received, it cannot be output immediately, but it first needs to be decoded, which is resource intensive and can take several ms .. and there is a need for an output buffer for samples ...

=== Sample buffer for the D/A ===
The last addition of delay is not really necessary technology wise, but a fact in Barix devices. We use a Main CPU for network tasks and a DSP driving the D/A, which turns the samples back to analog audio. The DSP is necessary for MP3 (and AAC etc etc) decoding, for PCM it mainly works as a pass-through. The interface between the main CPU and the DSP also introduces a sample buffer at the DSP output side, which is counted in bytes, and can introduce quite significant delays for low bitrate/sample rate streams. Why ? Well, the buffer is counted in Bytes as i said, and let's assume for these examples here it is 2kBytes (2000 bytes), for a PCM 48kHz stream that means 96Bytes per ms, so roughly 20ms - but if you send a 8Khz PCM stream, you get 6x that delay.

== Conclusion ==
So, at the end you have several sources introducing delay, with the buffering for network jitter being often the most significant one, but a "base delay", depending on sample rate, encoding format etc is always present. As you can figure from the above examples, if you have the bandwidth, it often makes sense to configure higher sample rates and bitrate streams, as that will effectively lower the delay due to the fact that the constant (byte wise) buffers in the chain have a smaller through delay.

== Barix devices ==
One last comment, now specific to Barix devices: The Exstreamer 1xx and 2xx decoder devices use a DSP with ample buffering. There is reasons for that, not to be further detailed here. In contrast, the Exstreamer 1000 use a different DSP with lower buffers, and we are currently beta testing a DSP software patch which reduces the buffers much further to almost non-existing !
With the Exstreamer 500/1000, you can currently achieve delays of below 50ms - the software has not been optimized for very low delay. However, with optimized software, you can get the delay down to well below 20ms - that has been proven in our labs (for a specific project). We are in the process to bring this down further, obviously (goal 5ms ?) this can only be done by sending many more blocks over the network, for example, one per ms - 1000 blocks per second .. ask your Wifi router what it thinks about that ..), so it needs optimized software.

Back to [[Main_Page#Software_Topics]]

Ethersound latency

2013-06-13T09:15:19Z

Achims: /* VLSI based devices */

This page describes the latency of the Ethersound firmware used with different devices.

== Latency ==
The end-to-end latency of an Ethersound encoder and a Barix ES100spkr decoder heavily depends on the codec used.

=== VLSI based devices ===
On '''Exstreamer 1xx, Exstreamer 2xx and all Annuncicom devices in DHW: 2.xx (Device Hardware) ''' the end-to-end latency is approximately '''57ms'''. This is caused by large internal buffers in the VLSI codec.

=== Micronas based devices ===
The internal buffers of the Micronas codec are much smaller which also positively affects the latency.
The end-to-end-latency of the '''Exstreamer 1000 and all Annuncicom devices in DHW: 1.xx (Device Hardware)''' is only about '''6ms'''.

== Latency measurements ==

Both latencies were measured in the below described test.

=== Test environment ===

The latency was measured with the following equipment:
* Digigiram ES220 as an input device
* another ES220 as a reference output device
* Exstreamer 100 as an output device (VLSI based device)
* Annuncicom 100 as an output device (Micronas based device)
* HP procurve 1700-8 switch where all devices were connected to

Both Barix devices were loaded with the version 00.03 of the Ethersound decoder module.

The input of the ES220 was fed with a 500Hz tone from a signal generator. The input, both output Barix devices as well as the reference ES220 device were monitored with an oscilloscope.

A trigger was set to capture the waveform after switching on the signal generator.

=== Test results ===
The below three diagrams show the results of the measurement. The top line (channel 4, green) is the clock source. Channels 1 (yellow), 2 (blue) and 3 (violet) are: the VLSI device (Exstreamer 100), the Micronas device (Annuncicom 100) and the reference ES220.

'''On the first diagram the 57.2ms latency of the VLSI decoder (Exstreamer 100) can be seen.'''

[[Image:vlsi_latency.png]]

'''The second screen shot shows the end-to-end latency using a Micronas based device Annuncicom 100. The latency is significantly lower - only 6ms.'''

[[Image:micronas_latency.png]]

'''The last picture shows the end-to-end delay using the reference ES220 device. The latency is 1.44ms.'''

[[Image:es220_latency.png]]

Ethersound latency

2013-06-13T09:14:53Z

Achims: /* Micronas based devices */

This page describes the latency of the Ethersound firmware used with different devices.

== Latency ==
The end-to-end latency of an Ethersound encoder and a Barix ES100spkr decoder heavily depends on the codec used.

=== VLSI based devices ===
On '''Exstreamer 1xx, Exstreamer 2xx and all Annuncicom devices in DHW: 2.xx ''' the end-to-end latency is approximately '''57ms'''. This is caused by large internal buffers in the VLSI codec.

=== Micronas based devices ===
The internal buffers of the Micronas codec are much smaller which also positively affects the latency.
The end-to-end-latency of the '''Exstreamer 1000 and all Annuncicom devices in DHW: 1.xx (Device Hardware)''' is only about '''6ms'''.

== Latency measurements ==

Both latencies were measured in the below described test.

=== Test environment ===

The latency was measured with the following equipment:
* Digigiram ES220 as an input device
* another ES220 as a reference output device
* Exstreamer 100 as an output device (VLSI based device)
* Annuncicom 100 as an output device (Micronas based device)
* HP procurve 1700-8 switch where all devices were connected to

Both Barix devices were loaded with the version 00.03 of the Ethersound decoder module.

The input of the ES220 was fed with a 500Hz tone from a signal generator. The input, both output Barix devices as well as the reference ES220 device were monitored with an oscilloscope.

A trigger was set to capture the waveform after switching on the signal generator.

=== Test results ===
The below three diagrams show the results of the measurement. The top line (channel 4, green) is the clock source. Channels 1 (yellow), 2 (blue) and 3 (violet) are: the VLSI device (Exstreamer 100), the Micronas device (Annuncicom 100) and the reference ES220.

'''On the first diagram the 57.2ms latency of the VLSI decoder (Exstreamer 100) can be seen.'''

[[Image:vlsi_latency.png]]

'''The second screen shot shows the end-to-end latency using a Micronas based device Annuncicom 100. The latency is significantly lower - only 6ms.'''

[[Image:micronas_latency.png]]

'''The last picture shows the end-to-end delay using the reference ES220 device. The latency is 1.44ms.'''

[[Image:es220_latency.png]]

Ethersound latency

2013-06-13T09:14:03Z

Achims: /* Micronas based devices */

This page describes the latency of the Ethersound firmware used with different devices.

== Latency ==
The end-to-end latency of an Ethersound encoder and a Barix ES100spkr decoder heavily depends on the codec used.

=== VLSI based devices ===
On '''Exstreamer 1xx, Exstreamer 2xx and all Annuncicom devices in DHW: 2.xx ''' the end-to-end latency is approximately '''57ms'''. This is caused by large internal buffers in the VLSI codec.

=== Micronas based devices ===
The internal buffers of the Micronas codec are much smaller which also positively affects the latency.
The end-to-end-latency of the '''Exstreamer 1000 and all Annuncicom devices DHW: 1.xx''' is only about '''6ms'''.

== Latency measurements ==

Both latencies were measured in the below described test.

=== Test environment ===

The latency was measured with the following equipment:
* Digigiram ES220 as an input device
* another ES220 as a reference output device
* Exstreamer 100 as an output device (VLSI based device)
* Annuncicom 100 as an output device (Micronas based device)
* HP procurve 1700-8 switch where all devices were connected to

Both Barix devices were loaded with the version 00.03 of the Ethersound decoder module.

The input of the ES220 was fed with a 500Hz tone from a signal generator. The input, both output Barix devices as well as the reference ES220 device were monitored with an oscilloscope.

A trigger was set to capture the waveform after switching on the signal generator.

=== Test results ===
The below three diagrams show the results of the measurement. The top line (channel 4, green) is the clock source. Channels 1 (yellow), 2 (blue) and 3 (violet) are: the VLSI device (Exstreamer 100), the Micronas device (Annuncicom 100) and the reference ES220.

'''On the first diagram the 57.2ms latency of the VLSI decoder (Exstreamer 100) can be seen.'''

[[Image:vlsi_latency.png]]

'''The second screen shot shows the end-to-end latency using a Micronas based device Annuncicom 100. The latency is significantly lower - only 6ms.'''

[[Image:micronas_latency.png]]

'''The last picture shows the end-to-end delay using the reference ES220 device. The latency is 1.44ms.'''

[[Image:es220_latency.png]]

Ethersound latency

2013-06-13T09:11:37Z

Achims: /* VLSI based devices */

This page describes the latency of the Ethersound firmware used with different devices.

== Latency ==
The end-to-end latency of an Ethersound encoder and a Barix ES100spkr decoder heavily depends on the codec used.

=== VLSI based devices ===
On '''Exstreamer 1xx, Exstreamer 2xx and all Annuncicom devices in DHW: 2.xx ''' the end-to-end latency is approximately '''57ms'''. This is caused by large internal buffers in the VLSI codec.

=== Micronas based devices ===
The internal buffers of the Micronas codec are much smaller which also positively affects the latency.
The end-to-end-latency of the '''Exstreamer 1000, Annuncicom 100 (DHW: 1.xx), Annuncicom 200 (DHW: 1.xx) and Annuncicom 1000 (DHW: 1.xx)''' is only about '''6ms'''.

== Latency measurements ==

Both latencies were measured in the below described test.

=== Test environment ===

The latency was measured with the following equipment:
* Digigiram ES220 as an input device
* another ES220 as a reference output device
* Exstreamer 100 as an output device (VLSI based device)
* Annuncicom 100 as an output device (Micronas based device)
* HP procurve 1700-8 switch where all devices were connected to

Both Barix devices were loaded with the version 00.03 of the Ethersound decoder module.

The input of the ES220 was fed with a 500Hz tone from a signal generator. The input, both output Barix devices as well as the reference ES220 device were monitored with an oscilloscope.

A trigger was set to capture the waveform after switching on the signal generator.

=== Test results ===
The below three diagrams show the results of the measurement. The top line (channel 4, green) is the clock source. Channels 1 (yellow), 2 (blue) and 3 (violet) are: the VLSI device (Exstreamer 100), the Micronas device (Annuncicom 100) and the reference ES220.

'''On the first diagram the 57.2ms latency of the VLSI decoder (Exstreamer 100) can be seen.'''

[[Image:vlsi_latency.png]]

'''The second screen shot shows the end-to-end latency using a Micronas based device Annuncicom 100. The latency is significantly lower - only 6ms.'''

[[Image:micronas_latency.png]]

'''The last picture shows the end-to-end delay using the reference ES220 device. The latency is 1.44ms.'''

[[Image:es220_latency.png]]

Ethersound latency

2013-06-13T09:09:54Z

Achims: /* VLSI based devices */

This page describes the latency of the Ethersound firmware used with different devices.

== Latency ==
The end-to-end latency of an Ethersound encoder and a Barix ES100spkr decoder heavily depends on the codec used.

=== VLSI based devices ===
On '''Exstreamer 1xx, Exstreamer 2xx and Annuncicom 1xx (DHW: 2.xx), Annuncicom 2xx (DHW: 2.xx) ''' the end-to-end latency is approximately '''57ms'''. This is caused by large internal buffers in the VLSI codec.

=== Micronas based devices ===
The internal buffers of the Micronas codec are much smaller which also positively affects the latency.
The end-to-end-latency of the '''Exstreamer 1000, Annuncicom 100 (DHW: 1.xx), Annuncicom 200 (DHW: 1.xx) and Annuncicom 1000 (DHW: 1.xx)''' is only about '''6ms'''.

== Latency measurements ==

Both latencies were measured in the below described test.

=== Test environment ===

The latency was measured with the following equipment:
* Digigiram ES220 as an input device
* another ES220 as a reference output device
* Exstreamer 100 as an output device (VLSI based device)
* Annuncicom 100 as an output device (Micronas based device)
* HP procurve 1700-8 switch where all devices were connected to

Both Barix devices were loaded with the version 00.03 of the Ethersound decoder module.

The input of the ES220 was fed with a 500Hz tone from a signal generator. The input, both output Barix devices as well as the reference ES220 device were monitored with an oscilloscope.

A trigger was set to capture the waveform after switching on the signal generator.

=== Test results ===
The below three diagrams show the results of the measurement. The top line (channel 4, green) is the clock source. Channels 1 (yellow), 2 (blue) and 3 (violet) are: the VLSI device (Exstreamer 100), the Micronas device (Annuncicom 100) and the reference ES220.

'''On the first diagram the 57.2ms latency of the VLSI decoder (Exstreamer 100) can be seen.'''

[[Image:vlsi_latency.png]]

'''The second screen shot shows the end-to-end latency using a Micronas based device Annuncicom 100. The latency is significantly lower - only 6ms.'''

[[Image:micronas_latency.png]]

'''The last picture shows the end-to-end delay using the reference ES220 device. The latency is 1.44ms.'''

[[Image:es220_latency.png]]

Ethersound latency

2013-06-13T09:07:21Z

Achims: /* Micronas based devices */

This page describes the latency of the Ethersound firmware used with different devices.

== Latency ==
The end-to-end latency of an Ethersound encoder and a Barix ES100spkr decoder heavily depends on the codec used.

=== VLSI based devices ===
On '''Exstreamer 100, Exstreamer 110 and Exstreamer 200''' the end-to-end latency is approximately '''57ms'''. This is caused by large internal buffers in the VLSI codec.

=== Micronas based devices ===
The internal buffers of the Micronas codec are much smaller which also positively affects the latency.
The end-to-end-latency of the '''Exstreamer 1000, Annuncicom 100 (DHW: 1.xx), Annuncicom 200 (DHW: 1.xx) and Annuncicom 1000 (DHW: 1.xx)''' is only about '''6ms'''.

== Latency measurements ==

Both latencies were measured in the below described test.

=== Test environment ===

The latency was measured with the following equipment:
* Digigiram ES220 as an input device
* another ES220 as a reference output device
* Exstreamer 100 as an output device (VLSI based device)
* Annuncicom 100 as an output device (Micronas based device)
* HP procurve 1700-8 switch where all devices were connected to

Both Barix devices were loaded with the version 00.03 of the Ethersound decoder module.

The input of the ES220 was fed with a 500Hz tone from a signal generator. The input, both output Barix devices as well as the reference ES220 device were monitored with an oscilloscope.

A trigger was set to capture the waveform after switching on the signal generator.

=== Test results ===
The below three diagrams show the results of the measurement. The top line (channel 4, green) is the clock source. Channels 1 (yellow), 2 (blue) and 3 (violet) are: the VLSI device (Exstreamer 100), the Micronas device (Annuncicom 100) and the reference ES220.

'''On the first diagram the 57.2ms latency of the VLSI decoder (Exstreamer 100) can be seen.'''

[[Image:vlsi_latency.png]]

'''The second screen shot shows the end-to-end latency using a Micronas based device Annuncicom 100. The latency is significantly lower - only 6ms.'''

[[Image:micronas_latency.png]]

'''The last picture shows the end-to-end delay using the reference ES220 device. The latency is 1.44ms.'''

[[Image:es220_latency.png]]

Modbus

2012-07-10T08:02:22Z

Achims:

== Modbus Control commands for R6 extension module: ==

This commands give you the possibility to control the relays on a R6 extension module via a modbus command send as a hex-file in a tcp stack.

It is easy to connect the R6 extension module to the RS485 interface of a Barix device. You have to wire Pin6 (A) and Pin9 (B) of the DB9 connector to Pin2 (A) and Pin3 (B) of the J1 connector on the R6 extension module.

Additional you have to power up the R6 extension module on Pin4 (+) and Pin5 (-) on J1 connector with an external power supply.

The serial settings for the RS485 interface (Serial 2) should set to a baudrate of 19200 Bd, a data bitrate of 8 bits, parity set to even, 1 stopbit, handshake set to RS485 direction control and the local port to 502.

Now it is possible to send a hex-file, which includes the modbus command, via tcp to port 502 of the Barix device. This can be done with the NetCat Application (nc -q 1 ''ip-barix'' ''port'' < ''filename'').

The table shows the modbus commands to control the relays on a R6 extension module:

{| class="wikitable" style="text-align:center" border="1" cellpadding="2"

|-
! !! !! -Modbus Address- !! -Single Coil- !! -Address HI- !! -Address LO- !! -Values HI- !! -Values LO- !! -CRC LO- !! -CRC HI-
|-
! rowspan="2"| -Relay 1-
| -set- || 00 || 05 || 00 || 00 || FF || FF || CD || AB
|-
| -reset- || 00 || 05 || 00 || 00 || 00 || 00 || CC || 1B
|-
! rowspan="2"| -Relay 2-
| -set- || 00 || 05 || 00 || 01 || FF || FF || 9C || 6B
|-
| -reset- || 00 || 05 || 00 || 01 || 00 || 00 || 9D || DB
|-
! rowspan="2"| -Relay 3-
| -set- || 00 || 05 || 00 || 02 || FF || FF || 6C || 6B
|-
| -reset- || 00 || 05 || 00 || 02 || 00 || 00 || 6D || DB
|-
! rowspan="2"| -Relay 4-
| -set- || 00 || 05 || 00 || 03 || FF || FF || 3D || AB
|-
| -reset- || 00 || 05 || 00 || 03 || 00 || 00 || 3C || 1B
|-
! rowspan="2"| -Relay 5-
| -set- || 00 || 05 || 00 || 04 || FF || FF || 8C || 6A
|-
| -reset- || 00 || 05 || 00 || 04 || 00 || 00 || 8D || DA
|-
! rowspan="2"| -Relay 6-
| -set- || 00 || 05 || 00 || 05 || FF || FF || DD || AA
|-
| -reset- || 00 || 05 || 00 || 05 || 00 || 00 || DC || 1A
|-
|}

Please note: It is necessary to calculate a crc-check-sum for each command and add it to the command itself.

Here you can find a online crc-calculator:
[http://www.lammertbies.nl/comm/info/crc-calculation.html http://www.lammertbies.nl/comm/info/crc-calculation.html]

ac

FW Update

2012-05-25T08:35:28Z

Achims: /* Upgrade Bootloader only */

=Firmware Update=
There are 3 methods for operating a FW upgrade on a Barix audio devices: WEB update, Serial Rescue, TFTP, Gold Unit. Each of them is suited for a different situation and purpose.

==WEB update==

The WEB update is done via a standard WEB Browser running on a PC. The device needs to be running on and visible to the IP network.

This method is suited for field upgrade of the FW. It will not change the current configuration settings.

You may need to force the Factory Default (keep reset button pressed 5-10 sec until lights change blinking) if you have major FW differences (implying a different EEPROM layout).

===Detailed procedure===
(as per _readme1st.txt file provided in the rescue package)

1. Open a browser and type the announced IP address into the URL field and hit the ENTER key.

2. Click on the UPDATE button to enter the update page.

3. Click on "Please click here to continue" to launch the update process. The device will restart in a special mode called Bootloader showing a number counting down. Upon start up the following screen appears ready for the update process.

4. To upload and update click on "Browse" to locate the file you want to update. Browse to the folder "update_rescue" and choose the file compound.bin.

5. Once selected, click on "Upload". This process can take a few minutes. After a successful upload click on the "update" link and when the Update window reappears click the "Reboot" button or if there is no button, click on Browse and select the file "reboot". The device will reboot with the new firmware.

===Upgrade Bootloader only===

Sometimes it is necessary to upgrade the Bootloader only. This can be done as follow:

1. Open a browser and type the announced IP address into the URL field and hit the ENTER key.

2. Click on the UPDATE button to enter the update page.

3. Click on "Please click here to continue" to launch the update process. The device will restart in a special mode called Bootloader showing a number counting down. Upon start up the following screen appears ready for the update process.

4. Click on the "Advanced Update" link.

5. Type in a target web page (e.g. WEB14). This page should be unused. Attention: The name must be written in capital letters.

6. To upload and update the Bootloader click on "Browse" to locate the file you want to update. Browse to the folder "update_rescue" and choose the file UNIFULL.SPB.

7. Once selected, click on "Upload". This process can take a few seconds. After a successful upload click on the "update" link and when the Update window reappears click the "Reboot" button or if there is no button, click on Browse and select the file "reboot". The device will reboot with the new Bootloader.

Attention: If the target web page was used this update overwrites the content in the web page. So be careful choosing the web page!

==Serial Rescue==

The Serial rescue operation is done via a serial cable and requires a command shell opened on a local PC.

This method is suited for Rescue operation as it will also load the Boot-loader and restore the Default Settings.

So if you need to keep the actual configuration settings:

Open a browser and type the announced IP address followed by "/status" into theURL field and hit the ENTER key.

Print this page which contains the current configuration settings of the device in order to reenter them after the update.

===Detailed procedure===
(as per _readme1st.txt file provided in the rescue package)

1. Unplug power supply.

2. Connect the supplied serial crossover cable to your PC's serial port and to the devices serial port.

3. Start The following script in the folder "update_rescue" depending on your Barix device model and COM port you are using:

Exstreamer 100/200 Exstreamer Legacy (red box, Digital, Gold)
Instreamer 100 Instreamer Legacy
Annuncicom 100 Annuncicom Legacy
IPAM
-----------------------------------------------------------
COM 1 ipamres1.bat rescue1.bat
COM 2 ipamres2.bat rescue2.bat
COM 3 ipamres3.bat rescue3.bat
COM 4 ipamres4.bat rescue4.bat

4. A message 'Waiting for the device' will be shown on the bottom of the screen.

5. Plug in the power supply now.

6. Wait until a message 'SUCCESSFUL' appears on the second line.

7. Close the rescue program.

8. Unplug power supply.

9. Plug in the power supply.

10. Your device is set to factory defaults and should work now.

11. Reconfigure the Exstreamer to your last configuration.

== TFTP==

The TFTP firmware update allows to update Barix audio devices over network, over this it would be also possible to automate updates (e.g. to many devices over one script).
To update the firmware components, the Barix device must be in Bootloader mode,
only then the FTP Server is active.

A firmware consists of different parts, over TFTP all these parts must/can be loaded separately with a separate TFTP command. An overview about the parts of the firmware is available in the "Gen.bat" (contained in FW package), this lists the files for the update and the target positionwhere the files must be loaded to.
Here is an example (Gen.bat) from the ABCL SIP firmware:

''load_win.exe -g compound.bin abclw.rom 0xc000 fs.bin 0xc100 sg.bin 0xc200 abclapp.cob 0xc400 custom1.cob 0xc600 esnd.rom 0xc800 bclio.bin 0xc900 applications.cob 0xcA00''

When only the ABCL application should be changed but not the complete firmware, then the file "applications.cob" can be load to target "WEB10" (address 0xCA00 = target "WEB10").
When only the file "custom1.cob" should be updated the this must be loaded to "WEB6" (address 0xC600 = target "WEB6").

When the complete firmware package should be updated over TFTP then then all components must be loaded by separate TFTP commands. In this case the file for target "WEB0" (abclw.rom , the firmware file it self) should be loaded as last, because this is causing an automatic reboot on the Barix device and returning to normal operation mode.

Syntax of the TFTP command (in windows) :

''TFTP -i [ip-address] PUT [file] [target]''

e.g. ''TFTP -i 192.168.1.25 put abclapp.cob WEB4''

The following options can be used to bring a Barix device into bootloader mode:

- power off, press reset button and keep it pressed while power on (for approx. 3 seconds)

or

- press the "Update" button from the Barix device´s web setup

or

- send the command "c=100" (e.g. over CGI) to bring the device into Bootloader mode

== Gold Unit==

Barix Gold Unit is a standard Exstreamer 100 device loaded with a special SW.
The Gold Unit has a USB memory stick attached which contains the binary files to be loaded to the other devices.

The update operation is done via an Ethernet cross cable and optionally requires a serial Terminal running on a local PC for monitoring.

This method is suited for programming in production and can be tailored in terms of modules to be loaded.

If customer needs new Default Settings to be loaded, Barix can provide a customized version of the configuration file (config.bin).

===Detailed procedure===

''Prepare USB files''

The files on the USB sticks must follow a name convention in order to be loaded automatically i.e. a file on the memory
stick called WEB03 will be loaded into the flash page 3, a file named WEB10 will be loaded into the flash page 10 and so on.
The file FBOOT will replace the bootloader. The name EEPRO is used to write to the configuration memory (i.e. the eeprom).

The files will be available soon in standard rescue kits.

''Update new Units''

For the units to be loaded containing already a firmware the user would need to:

1. attach the unit to be updated to the Gold Unit via Ethernet connection (direct cross cable or isolated switch) with DHCP enabled (no fixed IP allowed).

2. start the unit to be updated in the boot-loader mode (by keeping the reset button pressed during start-up).

3. after a short delay (1-2seconds) the boot-loader comes up and the file transfer will start automatically. The update operation will be completed in few seconds.

Optionally use a serial Terminal on the unit to be updated to verify that the download is started and finished OK.

FW Update

2012-05-25T08:35:04Z

Achims: /* Upgrade Bootloader only */

FW Update

2012-05-25T08:22:53Z

Achims: /* Detailed procedure */

=Firmware Update=
There are 3 methods for operating a FW upgrade on a Barix audio devices: WEB update, Serial Rescue, TFTP, Gold Unit. Each of them is suited for a different situation and purpose.

==WEB update==

The WEB update is done via a standard WEB Browser running on a PC. The device needs to be running on and visible to the IP network.

This method is suited for field upgrade of the FW. It will not change the current configuration settings.

You may need to force the Factory Default (keep reset button pressed 5-10 sec until lights change blinking) if you have major FW differences (implying a different EEPROM layout).

===Detailed procedure===
(as per _readme1st.txt file provided in the rescue package)

1. Open a browser and type the announced IP address into the URL field and hit the ENTER key.

2. Click on the UPDATE button to enter the update page.

3. Click on "Please click here to continue" to launch the update process. The device will restart in a special mode called Bootloader showing a number counting down. Upon start up the following screen appears ready for the update process.

4. To upload and update click on "Browse" to locate the file you want to update. Browse to the folder "update_rescue" and choose the file compound.bin.

5. Once selected, click on "Upload". This process can take a few minutes. After a successful upload click on the "update" link and when the Update window reappears click the "Reboot" button or if there is no button, click on Browse and select the file "reboot". The device will reboot with the new firmware.

===Upgrade Bootloader only===

Sometimes it is necessary to upgrade the Bootloader only. This can be done as follow:

1. Open a browser and type the announced IP address into the URL field and hit the ENTER key.

2. Click on the UPDATE button to enter the update page.

3. Click on "Please click here to continue" to launch the update process. The device will restart in a special mode called Bootloader showing a number counting down. Upon start up the following screen appears ready for the update process.

4. Click on the "Advanced Update" link.

5. Type in a target web page (e.g. WEB14). This page should be unused. Attention: The name must be written in capital letters.

6. To upload and update the Bootloader click on "Browse" to locate the file you want to update. Browse to the folder "update_rescue" and choose the file UNIFULL.SPB.

7. Once selected, click on "Upload". This process can take a few seconds. After a successful upload click on the "update" link and when the Update window reappears click the "Reboot" button or if there is no button, click on Browse and select the file "reboot". The device will reboot with the new bootloader.

Attention: If the target web page was used this update overwrites the content in the web page. So be careful choosing the web page!

==Serial Rescue==

The Serial rescue operation is done via a serial cable and requires a command shell opened on a local PC.

This method is suited for Rescue operation as it will also load the Boot-loader and restore the Default Settings.

So if you need to keep the actual configuration settings:

Open a browser and type the announced IP address followed by "/status" into theURL field and hit the ENTER key.

Print this page which contains the current configuration settings of the device in order to reenter them after the update.

===Detailed procedure===
(as per _readme1st.txt file provided in the rescue package)

1. Unplug power supply.

2. Connect the supplied serial crossover cable to your PC's serial port and to the devices serial port.

3. Start The following script in the folder "update_rescue" depending on your Barix device model and COM port you are using:

Exstreamer 100/200 Exstreamer Legacy (red box, Digital, Gold)
Instreamer 100 Instreamer Legacy
Annuncicom 100 Annuncicom Legacy
IPAM
-----------------------------------------------------------
COM 1 ipamres1.bat rescue1.bat
COM 2 ipamres2.bat rescue2.bat
COM 3 ipamres3.bat rescue3.bat
COM 4 ipamres4.bat rescue4.bat

4. A message 'Waiting for the device' will be shown on the bottom of the screen.

5. Plug in the power supply now.

6. Wait until a message 'SUCCESSFUL' appears on the second line.

7. Close the rescue program.

8. Unplug power supply.

9. Plug in the power supply.

10. Your device is set to factory defaults and should work now.

11. Reconfigure the Exstreamer to your last configuration.

== TFTP==

The TFTP firmware update allows to update Barix audio devices over network, over this it would be also possible to automate updates (e.g. to many devices over one script).
To update the firmware components, the Barix device must be in Bootloader mode,
only then the FTP Server is active.

A firmware consists of different parts, over TFTP all these parts must/can be loaded separately with a separate TFTP command. An overview about the parts of the firmware is available in the "Gen.bat" (contained in FW package), this lists the files for the update and the target positionwhere the files must be loaded to.
Here is an example (Gen.bat) from the ABCL SIP firmware:

''load_win.exe -g compound.bin abclw.rom 0xc000 fs.bin 0xc100 sg.bin 0xc200 abclapp.cob 0xc400 custom1.cob 0xc600 esnd.rom 0xc800 bclio.bin 0xc900 applications.cob 0xcA00''

When only the ABCL application should be changed but not the complete firmware, then the file "applications.cob" can be load to target "WEB10" (address 0xCA00 = target "WEB10").
When only the file "custom1.cob" should be updated the this must be loaded to "WEB6" (address 0xC600 = target "WEB6").

When the complete firmware package should be updated over TFTP then then all components must be loaded by separate TFTP commands. In this case the file for target "WEB0" (abclw.rom , the firmware file it self) should be loaded as last, because this is causing an automatic reboot on the Barix device and returning to normal operation mode.

Syntax of the TFTP command (in windows) :

''TFTP -i [ip-address] PUT [file] [target]''

e.g. ''TFTP -i 192.168.1.25 put abclapp.cob WEB4''

The following options can be used to bring a Barix device into bootloader mode:

- power off, press reset button and keep it pressed while power on (for approx. 3 seconds)

or

- press the "Update" button from the Barix device´s web setup

or

- send the command "c=100" (e.g. over CGI) to bring the device into Bootloader mode

== Gold Unit==

Barix Gold Unit is a standard Exstreamer 100 device loaded with a special SW.
The Gold Unit has a USB memory stick attached which contains the binary files to be loaded to the other devices.

The update operation is done via an Ethernet cross cable and optionally requires a serial Terminal running on a local PC for monitoring.

This method is suited for programming in production and can be tailored in terms of modules to be loaded.

If customer needs new Default Settings to be loaded, Barix can provide a customized version of the configuration file (config.bin).

===Detailed procedure===

''Prepare USB files''

The files on the USB sticks must follow a name convention in order to be loaded automatically i.e. a file on the memory
stick called WEB03 will be loaded into the flash page 3, a file named WEB10 will be loaded into the flash page 10 and so on.
The file FBOOT will replace the bootloader. The name EEPRO is used to write to the configuration memory (i.e. the eeprom).

The files will be available soon in standard rescue kits.

''Update new Units''

For the units to be loaded containing already a firmware the user would need to:

1. attach the unit to be updated to the Gold Unit via Ethernet connection (direct cross cable or isolated switch) with DHCP enabled (no fixed IP allowed).

2. start the unit to be updated in the boot-loader mode (by keeping the reset button pressed during start-up).

3. after a short delay (1-2seconds) the boot-loader comes up and the file transfer will start automatically. The update operation will be completed in few seconds.

Optionally use a serial Terminal on the unit to be updated to verify that the download is started and finished OK.

FW Update

2012-05-25T08:22:20Z

Achims: add "Update Bootloader only" section

=Firmware Update=
There are 3 methods for operating a FW upgrade on a Barix audio devices: WEB update, Serial Rescue, TFTP, Gold Unit. Each of them is suited for a different situation and purpose.

==WEB update==

The WEB update is done via a standard WEB Browser running on a PC. The device needs to be running on and visible to the IP network.

This method is suited for field upgrade of the FW. It will not change the current configuration settings.

You may need to force the Factory Default (keep reset button pressed 5-10 sec until lights change blinking) if you have major FW differences (implying a different EEPROM layout).

===Detailed procedure===
(as per _readme1st.txt file provided in the rescue package)

1. Open a browser and type the announced IP address into the URL field and hit the ENTER key.

2. Click on the UPDATE button to enter the update page.

3. Click on "Please click here to continue" to launch the update process. The device will restart in a special mode called Bootloader showing a number counting down. Upon start up the following screen appears ready for the update process.

4. To upload and update click on "Browse" to locate the file you want to update. Browse to the folder "update_rescue" and choose the file compound.bin.

5. Once selected, click on "Upload". This process can take a few minutes. After a successful upload click on the "update" link and when the Update window reappears click the "Reboot" button or if there is no button, click on Browse and select the file "reboot". The device will reboot with the new firmware.

===Upgrade Bootloader only===

Sometimes it is necessary to upgrade the Bootloader only. This can be done as follow:

1. Open a browser and type the announced IP address into the URL field and hit the ENTER key.

2. Click on the UPDATE button to enter the update page.

3. Click on "Please click here to continue" to launch the update process. The device will restart in a special mode called Bootloader showing a number counting down. Upon start up the following screen appears ready for the update process.

4. Click on the "Advanced Update" link.

5. Type in a target web page (e.g. WEB14). This page should be unused. Attention: The name must be written in capital letters.

6. To upload and update the Bootloader click on "Browse" to locate the file you want to update. Browse to the folder "update_rescue" and choose the file UNIFULL.SPB.

7. Once selected, click on "Upload". This process can take a few seconds. After a successful upload click on the "update" link and when the Update window reappears click the "Reboot" button or if there is no button, click on Browse and select the file "reboot". The device will reboot with the new bootloader.

Attention: If the target web page was used this update overwrites the content in the web page. So be careful choosing the web page!

==Serial Rescue==

The Serial rescue operation is done via a serial cable and requires a command shell opened on a local PC.

This method is suited for Rescue operation as it will also load the Boot-loader and restore the Default Settings.

So if you need to keep the actual configuration settings:

Open a browser and type the announced IP address followed by "/status" into theURL field and hit the ENTER key.

Print this page which contains the current configuration settings of the device in order to reenter them after the update.

===Detailed procedure===
(as per _readme1st.txt file provided in the rescue package)

1. Unplug power supply.

2. Connect the supplied serial crossover cable to your PC's serial port and to the devices serial port.

3. Start The following script in the folder "update_rescue" depending on your Barix device model and COM port you are using:

Exstreamer 100/200 Exstreamer Legacy (red box, Digital, Gold)
Instreamer 100 Instreamer Legacy
Annuncicom 100 Annuncicom Legacy
IPAM
-----------------------------------------------------------
COM 1 ipamres1.bat rescue1.bat
COM 2 ipamres2.bat rescue2.bat
COM 3 ipamres3.bat rescue3.bat
COM 4 ipamres4.bat rescue4.bat

4. A message 'Waiting for the device' will be shown on the bottom of the screen.

5. Plug in the power supply now.

6. Wait until a message 'SUCCESSFUL' appears on the second line.

7. Close the rescue program.

8. Unplug power supply.

9. Plug in the power supply.

10. Your device is set to factory defaults and should work now.

11. Reconfigure the Exstreamer to your last configuration.

== TFTP==

The TFTP firmware update allows to update Barix audio devices over network, over this it would be also possible to automate updates (e.g. to many devices over one script).
To update the firmware components, the Barix device must be in Bootloader mode,
only then the FTP Server is active.

A firmware consists of different parts, over TFTP all these parts must/can be loaded separately with a separate TFTP command. An overview about the parts of the firmware is available in the "Gen.bat" (contained in FW package), this lists the files for the update and the target positionwhere the files must be loaded to.
Here is an example (Gen.bat) from the ABCL SIP firmware:

''load_win.exe -g compound.bin abclw.rom 0xc000 fs.bin 0xc100 sg.bin 0xc200 abclapp.cob 0xc400 custom1.cob 0xc600 esnd.rom 0xc800 bclio.bin 0xc900 applications.cob 0xcA00''

When only the ABCL application should be changed but not the complete firmware, then the file "applications.cob" can be load to target "WEB10" (address 0xCA00 = target "WEB10").
When only the file "custom1.cob" should be updated the this must be loaded to "WEB6" (address 0xC600 = target "WEB6").

When the complete firmware package should be updated over TFTP then then all components must be loaded by separate TFTP commands. In this case the file for target "WEB0" (abclw.rom , the firmware file it self) should be loaded as last, because this is causing an automatic reboot on the Barix device and returning to normal operation mode.

Syntax of the TFTP command (in windows) :

''TFTP -i [ip-address] PUT [file] [target]''

e.g. ''TFTP -i 192.168.1.25 put abclapp.cob WEB4''

The following options can be used to bring a Barix device into bootloader mode:

- power off, press reset button and keep it pressed while power on (for approx. 3 seconds)

or

- press the "Update" button from the Barix device´s web setup

or

- send the command "c=100" (e.g. over CGI) to bring the device into Bootloader mode

== Gold Unit==

Barix Gold Unit is a standard Exstreamer 100 device loaded with a special SW.
The Gold Unit has a USB memory stick attached which contains the binary files to be loaded to the other devices.

The update operation is done via an Ethernet cross cable and optionally requires a serial Terminal running on a local PC for monitoring.

This method is suited for programming in production and can be tailored in terms of modules to be loaded.

If customer needs new Default Settings to be loaded, Barix can provide a customized version of the configuration file (config.bin).

===Detailed procedure===

''Prepare USB files''

The files on the USB sticks must follow a name convention in order to be loaded automatically i.e. a file on the memory
stick called WEB03 will be loaded into the flash page 3, a file named WEB10 will be loaded into the flash page 10 and so on.
The file FBOOT will replace the bootloader. The name EEPRO is used to write to the configuration memory (i.e. the eeprom).

The files will be available soon in standard rescue kits.

''Update new Units''

For the units to be loaded containing already a firmware the user would need to:

1. attach the unit to be updated to the Gold Unit via Ethernet connection (direct cross cable or isolated switch) with DHCP enabled (no fixed IP allowed).

2. start the unit to be updated in the boot-loader mode (by keeping the reset button pressed during start-up).

3. after a short delay (1-2seconds) the boot-loader comes up and the file transfer will start automatically. The update operation will be completed in few seconds.

Optionally use a serial Terminal on the unit to be updated to verify that the download is started and finished OK.

FW Update

2012-05-25T07:58:38Z

Achims: structure change

=Firmware Update=
There are 3 methods for operating a FW upgrade on a Barix audio devices: WEB update, Serial Rescue, TFTP, Gold Unit. Each of them is suited for a different situation and purpose.

==WEB update==

The WEB update is done via a standard WEB Browser running on a PC. The device needs to be running on and visible to the IP network.

This method is suited for field upgrade of the FW. It will not change the current configuration settings.

You may need to force the Factory Default (keep reset button pressed 5-10 sec until lights change blinking) if you have major FW differences (implying a different EEPROM layout).

===Detailed procedure===
(as per _readme1st.txt file provided in the rescue package)

1. Open a browser and type the announced IP address into the URL field and hit the ENTER key.

2. Click on the UPDATE button to enter the update page.

3. Click on "Please click here to continue" to launch the update process. The device will restart in a special mode called Bootloader showing a number counting down. Upon start up the following screen appears ready for the update process.

4. To upload an update click on "Browse" to locate the file you want to update. Browse to the folder "update_rescue" and choose the file compound.bin.

5. Once selected, click on "Upload". This process can take a few minutes. After a successful upload click on the "update" link and when the Update window reappears click the "Reboot" button or if there is no button, click on Browse and select the file "reboot". The device will reboot with the new firmware.

==Serial Rescue==

The Serial rescue operation is done via a serial cable and requires a command shell opened on a local PC.

This method is suited for Rescue operation as it will also load the Boot-loader and restore the Default Settings.

So if you need to keep the actual configuration settings:

Open a browser and type the announced IP address followed by "/status" into theURL field and hit the ENTER key.

Print this page which contains the current configuration settings of the device in order to reenter them after the update.

===Detailed procedure===
(as per _readme1st.txt file provided in the rescue package)

1. Unplug power supply.

2. Connect the supplied serial crossover cable to your PC's serial port and to the devices serial port.

3. Start The following script in the folder "update_rescue" depending on your Barix device model and COM port you are using:

Exstreamer 100/200 Exstreamer Legacy (red box, Digital, Gold)
Instreamer 100 Instreamer Legacy
Annuncicom 100 Annuncicom Legacy
IPAM
-----------------------------------------------------------
COM 1 ipamres1.bat rescue1.bat
COM 2 ipamres2.bat rescue2.bat
COM 3 ipamres3.bat rescue3.bat
COM 4 ipamres4.bat rescue4.bat

4. A message 'Waiting for the device' will be shown on the bottom of the screen.

5. Plug in the power supply now.

6. Wait until a message 'SUCCESSFUL' appears on the second line.

7. Close the rescue program.

8. Unplug power supply.

9. Plug in the power supply.

10. Your device is set to factory defaults and should work now.

11. Reconfigure the Exstreamer to your last configuration.

== TFTP==

The TFTP firmware update allows to update Barix audio devices over network, over this it would be also possible to automate updates (e.g. to many devices over one script).
To update the firmware components, the Barix device must be in Bootloader mode,
only then the FTP Server is active.

A firmware consists of different parts, over TFTP all these parts must/can be loaded separately with a separate TFTP command. An overview about the parts of the firmware is available in the "Gen.bat" (contained in FW package), this lists the files for the update and the target positionwhere the files must be loaded to.
Here is an example (Gen.bat) from the ABCL SIP firmware:

''load_win.exe -g compound.bin abclw.rom 0xc000 fs.bin 0xc100 sg.bin 0xc200 abclapp.cob 0xc400 custom1.cob 0xc600 esnd.rom 0xc800 bclio.bin 0xc900 applications.cob 0xcA00''

When only the ABCL application should be changed but not the complete firmware, then the file "applications.cob" can be load to target "WEB10" (address 0xCA00 = target "WEB10").
When only the file "custom1.cob" should be updated the this must be loaded to "WEB6" (address 0xC600 = target "WEB6").

When the complete firmware package should be updated over TFTP then then all components must be loaded by separate TFTP commands. In this case the file for target "WEB0" (abclw.rom , the firmware file it self) should be loaded as last, because this is causing an automatic reboot on the Barix device and returning to normal operation mode.

Syntax of the TFTP command (in windows) :

''TFTP -i [ip-address] PUT [file] [target]''

e.g. ''TFTP -i 192.168.1.25 put abclapp.cob WEB4''

The following options can be used to bring a Barix device into bootloader mode:

- power off, press reset button and keep it pressed while power on (for approx. 3 seconds)

or

- press the "Update" button from the Barix device´s web setup

or

- send the command "c=100" (e.g. over CGI) to bring the device into Bootloader mode

== Gold Unit==

Barix Gold Unit is a standard Exstreamer 100 device loaded with a special SW.
The Gold Unit has a USB memory stick attached which contains the binary files to be loaded to the other devices.

The update operation is done via an Ethernet cross cable and optionally requires a serial Terminal running on a local PC for monitoring.

This method is suited for programming in production and can be tailored in terms of modules to be loaded.

If customer needs new Default Settings to be loaded, Barix can provide a customized version of the configuration file (config.bin).

===Detailed procedure===

''Prepare USB files''

The files on the USB sticks must follow a name convention in order to be loaded automatically i.e. a file on the memory
stick called WEB03 will be loaded into the flash page 3, a file named WEB10 will be loaded into the flash page 10 and so on.
The file FBOOT will replace the bootloader. The name EEPRO is used to write to the configuration memory (i.e. the eeprom).

The files will be available soon in standard rescue kits.

''Update new Units''

For the units to be loaded containing already a firmware the user would need to:

1. attach the unit to be updated to the Gold Unit via Ethernet connection (direct cross cable or isolated switch) with DHCP enabled (no fixed IP allowed).

2. start the unit to be updated in the boot-loader mode (by keeping the reset button pressed during start-up).

3. after a short delay (1-2seconds) the boot-loader comes up and the file transfer will start automatically. The update operation will be completed in few seconds.

Optionally use a serial Terminal on the unit to be updated to verify that the download is started and finished OK.

Howto remove scrolling title from the Exstreamer 110 display

2010-03-17T09:20:31Z

Achims:

Howto remove scrolling title from the Exstreamer 110 display:

To remove the scrolling stream and song title it is necessary to edit the ex110.ddf file. Please remove the following entries and keep the rest of the file as it is.
<pre>
T(!p(s1));G(31);
# radio station name is present
F31:S(0,1,2,16,s1,3);
</pre>

Here the original file:
<pre>
# print song name/channel nr/URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(!p(s1));G(31);T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# radio station name is present
F31:S(0,1,2,16,s1,3);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
</pre>

The result should look like this:
<pre>
# print channel nr or URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
</pre>

Howto remove scrolling title from the Exstreamer 110 display

2010-03-17T09:17:52Z

Achims:

Howto remove scrolling title from the Exstreamer 110 display:

To remove the scrolling stream and song title it is necessary to edit the ex110.ddf file. Please remove the sections marked with red. Keep the rest of the file as it is:

<pre>
# print song name/channel nr/URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(!p(s1));G(31);T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# radio station name is present
F31:S(0,1,2,16,s1,3);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
</pre>

The result should look like:
<pre>
# print channel nr or URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
</pre>

Howto remove scrolling title from the Exstreamer 110 display

2010-03-17T09:17:08Z

Achims:

Howto remove scrolling title from the Exstreamer 110 display:

To remove the scrolling stream and song title it is necessary to edit the ex110.ddf file. Please remove the sections marked with red. Keep the rest of the file as it is:

<prev>
# print song name/channel nr/URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(!p(s1));G(31);T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# radio station name is present
F31:S(0,1,2,16,s1,3);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
</prev>

The result should look like:
<prev>
# print channel nr or URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
</prev>

Howto remove scrolling title from the Exstreamer 110 display

2010-03-17T09:16:23Z

Achims:

Howto remove scrolling title from the Exstreamer 110 display:

To remove the scrolling stream and song title it is necessary to edit the ex110.ddf file. Please remove the sections marked with red. Keep the rest of the file as it is:

---------------------
# print song name/channel nr/URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(!p(s1));G(31);T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# radio station name is present
F31:S(0,1,2,16,s1,3);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
---------------------

The result should look like:
---------------------
# print channel nr or URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
---------------------

Howto remove scrolling title from the Exstreamer 110 display

2010-03-17T09:04:11Z

Achims:

To remove the scrolling stream and song title find the following lines in the ex110.ddf file and remove the sections marked with red. Keep the rest of the file as it is:

---------------------
# print song name/channel nr/URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");[[T(!p(s1));G(31)]];T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
[[# radio station name is present
F31:S(0,1,2,16,s1,3);]]
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
---------------------

The result should look like:
---------------------
# print channel nr or URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
---------------------

Howto remove scrolling title from the Exstreamer 110 display

2010-03-17T09:02:52Z

Achims:

Howto remove scrolling title from the Exstreamer 110 display

2010-03-17T09:02:18Z

Achims:

Howto remove scrolling title from the Exstreamer 110 display:

To remove the scrolling stream and song title it is necessary to edit the some lines in the ex110.ddf file. Please remove the sections marked with red. Keep the rest of the file as it is:

<pre>
# print song name/channel nr/URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(!p(s1));G(31);T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# radio station name is present
F31:S(0,1,2,16,s1,3);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
</pre>

The result should look like:
<pre>
# print channel nr or URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
</pre>

Howto remove scrolling title from the Exstreamer 110 display

2010-03-17T09:01:18Z

Achims:

Howto remove scrolling title from the Exstreamer 110 display:

To remove the scrolling stream and song title find the following lines in the ex110.ddf file and remove the sections marked with red. Keep the rest of the file as it is:

<pre>
# print song name/channel nr/URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(!p(s1));G(31);T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# radio station name is present
F31:S(0,1,2,16,s1,3);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
</pre>

The result should look like:
<pre>
# print channel nr or URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
</pre>

Howto remove scrolling title from the Exstreamer 110 display

2010-03-17T09:00:21Z

Achims:

To remove the scrolling stream and song title find the following lines in the ex110.ddf file and remove the sections marked with red. Keep the rest of the file as it is:

<pre>
# print song name/channel nr/URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(!p(s1));G(31);T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# radio station name is present
F31:S(0,1,2,16,s1,3);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
</pre>

The result should look like:
<pre>
# print channel nr or URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
</pre>

Howto remove scrolling title from the Exstreamer 110 display

2010-03-17T08:59:35Z

Achims:

To remove the scrolling stream and song title find the following lines in the ex110.ddf file and remove the sections marked with red. Keep the rest of the file as it is:

<pre>
# print song name/channel nr/URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");[[T(!p(s1));G(31)]];T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# radio station name is present
F31:S(0,1,2,16,s1,3);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
</pre>

The result should look like:
<pre>
# print channel nr or URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
</pre>

Howto remove scrolling title from the Exstreamer 110 display

2010-03-17T08:59:08Z

Achims:

o remove the scrolling stream and song title find the following lines in the ex110.ddf file and remove the sections marked with red. Keep the rest of the file as it is:

<pre>
# print song name/channel nr/URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");[[T(!p(s1));G(31)]];T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# radio station name is present
F31:S(0,1,2,16,s1,3);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
</pre>

The result should look like:
<pre>
# print channel nr or URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
</pre>

Howto remove scrolling title from the Exstreamer 110 display

2010-03-17T08:58:29Z

Achims:

o remove the scrolling stream and song title find the following lines in the ex110.ddf file and remove the sections marked with red. Keep the rest of the file as it is:

<pre>
# print song name/channel nr/URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");[[T(!p(s1));G(31)]];T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# radio station name is present
F31:S(0,1,2,16,s1,3);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
</pre>

The result should look like:
---------------------
# print channel nr or URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
---------------------

Howto remove scrolling title from the Exstreamer 110 display

2010-03-17T08:58:13Z

Achims:

o remove the scrolling stream and song title find the following lines in the ex110.ddf file and remove the sections marked with red. Keep the rest of the file as it is:

<nowiki>
# print song name/channel nr/URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");[[T(!p(s1));G(31)]];T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# radio station name is present
F31:S(0,1,2,16,s1,3);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
</nowiki>

The result should look like:
---------------------
# print channel nr or URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
---------------------

Howto remove scrolling title from the Exstreamer 110 display

2010-03-17T08:57:08Z

Achims:

o remove the scrolling stream and song title find the following lines in the ex110.ddf file and remove the sections marked with red. Keep the rest of the file as it is:

<nowiki># print song name/channel nr/URL</nowiki>

F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");[[T(!p(s1));G(31)]];T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# radio station name is present
F31:S(0,1,2,16,s1,3);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);

The result should look like:
---------------------
# print channel nr or URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
---------------------

Howto remove scrolling title from the Exstreamer 110 display

2010-03-17T08:56:36Z

Achims:

o remove the scrolling stream and song title find the following lines in the ex110.ddf file and remove the sections marked with red. Keep the rest of the file as it is:

<nowiki># print song name/channel nr/URL</nowiki>
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");[[T(!p(s1));G(31)]];T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# radio station name is present
F31:S(0,1,2,16,s1,3);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);

The result should look like:
---------------------
# print channel nr or URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
---------------------

Howto remove scrolling title from the Exstreamer 110 display

2010-03-17T08:56:09Z

Achims:

o remove the scrolling stream and song title find the following lines in the ex110.ddf file and remove the sections marked with red. Keep the rest of the file as it is:

<source># print song name/channel nr/URL</source>
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");[[T(!p(s1));G(31)]];T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# radio station name is present
F31:S(0,1,2,16,s1,3);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);

The result should look like:
---------------------
# print channel nr or URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
---------------------

Howto remove scrolling title from the Exstreamer 110 display

2010-03-17T08:55:31Z

Achims:

o remove the scrolling stream and song title find the following lines in the ex110.ddf file and remove the sections marked with red. Keep the rest of the file as it is:

<pre># print song name/channel nr/URL</pre>
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");[[T(!p(s1));G(31)]];T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# radio station name is present
F31:S(0,1,2,16,s1,3);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);

The result should look like:
---------------------
# print channel nr or URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
---------------------

Howto remove scrolling title from the Exstreamer 110 display

2010-03-17T08:55:04Z

Achims:

o remove the scrolling stream and song title find the following lines in the ex110.ddf file and remove the sections marked with red. Keep the rest of the file as it is:

<nowiki># print song name/channel nr/URL</nowiki>
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");[[T(!p(s1));G(31)]];T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# radio station name is present
F31:S(0,1,2,16,s1,3);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);

The result should look like:
---------------------
# print channel nr or URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
---------------------

Howto remove scrolling title from the Exstreamer 110 display

2010-03-17T08:54:25Z

Achims:

o remove the scrolling stream and song title find the following lines in the ex110.ddf file and remove the sections marked with red. Keep the rest of the file as it is:

<pre># print song name/channel nr/URL</pre>
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");[[T(!p(s1));G(31)]];T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# radio station name is present
F31:S(0,1,2,16,s1,3);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);

The result should look like:
---------------------
# print channel nr or URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
---------------------

Howto remove scrolling title from the Exstreamer 110 display

2010-03-17T08:53:53Z

Achims:

o remove the scrolling stream and song title find the following lines in the ex110.ddf file and remove the sections marked with red. Keep the rest of the file as it is:

# print song name/channel nr/URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");[[T(!p(s1));G(31)]];T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# radio station name is present
F31:S(0,1,2,16,s1,3);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);

The result should look like:
---------------------
# print channel nr or URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
---------------------

Howto remove scrolling title from the Exstreamer 110 display

2010-03-17T08:53:30Z

Achims:

Howto remove scrolling title from the Exstreamer 110 display

2010-03-17T08:52:33Z

Achims:

Howto remove scrolling title from the Exstreamer 110 display

2010-03-17T08:51:27Z

Achims:

o remove the scrolling stream and song title find the following lines in the ex110.ddf file and remove the sections marked with red. Keep the rest of the file as it is:

<pre>
# print song name/channel nr/URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");[[T(!p(s1));G(31)]];T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# radio station name is present
F31:S(0,1,2,16,s1,3);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
</pre>

The result should look like:
---------------------
# print channel nr or URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
---------------------

Howto remove scrolling title from the Exstreamer 110 display

2010-03-17T08:50:31Z

Achims:

o remove the scrolling stream and song title find the following lines in the ex110.ddf file and remove the sections marked with red. Keep the rest of the file as it is:

<pre>
# print song name/channel nr/URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");
</pre>
[[T(!p(s1));G(31)]]
<pre>
;T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# radio station name is present
F31:S(0,1,2,16,s1,3);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
</pre>

The result should look like:
---------------------
# print channel nr or URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
---------------------

Howto remove scrolling title from the Exstreamer 110 display

2010-03-17T08:49:43Z

Achims:

o remove the scrolling stream and song title find the following lines in the ex110.ddf file and remove the sections marked with red. Keep the rest of the file as it is:

<pre>
# print song name/channel nr/URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");[[T(!p(s1));G(31)]];T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# radio station name is present
F31:S(0,1,2,16,s1,3);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
</pre>

The result should look like:
---------------------
# print channel nr or URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
---------------------

Howto remove scrolling title from the Exstreamer 110 display

2010-03-17T08:48:55Z

Achims:

Howto remove scrolling title from the Exstreamer 110 display

2010-03-17T08:48:10Z

Achims:

o remove the scrolling stream and song title find the following lines in the ex110.ddf file and remove the sections marked with red. Keep the rest of the file as it is:

<nowiki>
# print song name/channel nr/URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(!p(s1));G(31);T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# radio station name is present
F31:S(0,1,2,16,s1,3);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
</nowiki>

The result should look like:
---------------------
# print channel nr or URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
---------------------

Howto remove scrolling title from the Exstreamer 110 display

2010-03-17T08:45:41Z

Achims:

o remove the scrolling stream and song title find the following lines in the ex110.ddf file and remove the sections marked with red. Keep the rest of the file as it is:

<source lang="csharp">
# print song name/channel nr/URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(!p(s1));G(31);T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# radio station name is present
F31:S(0,1,2,16,s1,3);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
</source>

The result should look like:
---------------------
# print channel nr or URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
---------------------

Howto remove scrolling title from the Exstreamer 110 display

2010-03-17T08:44:26Z

Achims:

o remove the scrolling stream and song title find the following lines in the ex110.ddf file and remove the sections marked with red. Keep the rest of the file as it is:

<source>
# print song name/channel nr/URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(!p(s1));G(31);T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# radio station name is present
F31:S(0,1,2,16,s1,3);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
</source>

The result should look like:
---------------------
# print channel nr or URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
---------------------

Howto remove scrolling title from the Exstreamer 110 display

2010-03-17T08:40:54Z

Achims:

o remove the scrolling stream and song title find the following lines in the ex110.ddf file and remove the sections marked with red. Keep the rest of the file as it is:

---------------------
# print song name/channel nr/URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(!p(s1));G(31);T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# radio station name is present
F31:S(0,1,2,16,s1,3);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
---------------------

The result should look like:
---------------------
# print channel nr or URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
---------------------

Howto remove scrolling title from the Exstreamer 110 display

2010-03-17T08:39:06Z

Achims:

To remove the scrolling stream and song title find the following lines in the ex110.ddf file and remove the sections marked with red. Keep the rest of the file as it is:

---------------------
# print song name/channel nr/URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");[[T(!p(s1));G(31)]];T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
[[# radio station name is present
F31:S(0,1,2,16,s1,3);]]
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
---------------------

The result should look like:
---------------------
# print channel nr or URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("033[1;0H");T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
---------------------

Howto remove scrolling title from the Exstreamer 110 display

2010-03-17T08:37:21Z

Achims:

To remove the scrolling stream and song title find the following lines in the ex110.ddf file and remove the sections marked with red. Keep the rest of the file as it is:

---------------------
# print song name/channel nr/URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");
[[T(!p(s1));G(31)]];T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
[[# radio station name is present
F31:S(0,1,2,16,s1,3);]]
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
---------------------

The result should look like:
---------------------
# print channel nr or URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
---------------------

Howto remove scrolling title from the Exstreamer 110 display

2010-03-17T08:36:04Z

Achims:

To remove the scrolling stream and song title find the following lines in the ex110.ddf file and remove the sections marked with red. Keep the rest of the file as it is:

---------------------
# print song name/channel nr/URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");
[[T(!p(s1));G(31)]];T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
[[# radio station name is present
F31:S(0,1,2,16,s1,3);]]
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
---------------------

The result should look like:
---------------------
# print channel nr or URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
---------------------

Howto remove scrolling title from the Exstreamer 110 display

2010-03-17T08:33:38Z

Achims:

To remove the scrolling stream and song title find the following lines in the ex110.ddf file and remove the sections marked with red. Keep the rest of the file as it is:

---------------------
<pre>
# print song name/channel nr/URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");[[T(!p(s1));G(31)]];T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
[[# radio station name is present
F31:S(0,1,2,16,s1,3);]]
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
---------------------

The result should look like:
---------------------
# print channel nr or URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
---------------------

Howto remove scrolling title from the Exstreamer 110 display

2010-03-17T08:32:26Z

Achims:

To remove the scrolling stream and song title find the following lines in the ex110.ddf file and remove the sections marked with red. Keep the rest of the file as it is:

---------------------
<nowiki>
# print song name/channel nr/URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");[[T(!p(s1));G(31)]];T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
[[# radio station name is present
F31:S(0,1,2,16,s1,3);]]
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
<pre>
---------------------

The result should look like:
---------------------
# print channel nr or URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
---------------------

Howto remove scrolling title from the Exstreamer 110 display

2010-03-17T08:31:06Z

Achims:

To remove the scrolling stream and song title find the following lines in the ex110.ddf file and remove the sections marked with red. Keep the rest of the file as it is:

---------------------
<nowiki>
# print song name/channel nr/URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");[[T(!p(s1));G(31)]];T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
[[# radio station name is present
F31:S(0,1,2,16,s1,3);]]
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
---------------------

The result should look like:
---------------------
# print channel nr or URL
F30:S(0,1,2,16,"",0);P("\033[1;0H");B(16);P("\033[1;0H");T(z(i6));G(34);T(m("channels.ini",i5));G(32);G(33);
# channel number: channels.ini record exists -> print channel name
F32:M("channels.ini",i5);
# channel number (record does not exist)
F33:P("Channel ");I("03",i5);
# not channel based URL: print simply URL 1/2/3
F34:P("URL ");I("",i7);
---------------------