1. Recent issues

1.1. No Spotify Search available

There is an update for Spotify search available, requiring software V9.36 or higher. Read here how to update and configure:

1.2. No Spotify Playlists available

Update to software version 9.43 build 13869 on the nightly build channel to have this fixed.

1.3. No TuneIn Menu, Error 403 in TuneIn plugin

If you have older Software V8.x installed you must update to version 8.78, to fix a bug in the TuneIn plugin.

If you have the latest V8 or V9 software already, your system may have been locked out temporarily from TuneIn by it’s internet IP address. This can be caused by too many web radio requests per day. You can verify this by typing in your web browser:

opml.radiotime.com/Browse.ashx

If this also produces a 403 error then you have to wait for one day until the blocking is lifted. Alternatively, change your internet IP address, by disconnecting and then reconnecting the internet (in your router). If your IP does not change although you disconnected the internet then contact your internet service provider for help on that.

1.4. No access to TuneIn favorites

On 12.09.18 there was a change in the TuneIn API which caused blocking of TuneIn favourites by a 403 Error.

If you update to V9.37 (or V8.79 with touchpad 2.15.13617) it will be possible to use favourites again, but please note:

  • old device based favourites are lost. but you can create new ones.

  • TuneIn account linking is possible, but if you don’t see your favourites, you have to go into the web configuration, under Streaming / TuneIn, and select 'Join this device with account' again.

2. Network failure on group play

2.1. Problem:

No sound in some zones, slow controls, blocked network during group play with Installer Line products, or during InStreamer play with Multicast option active.

2.2. Solution:

  1. Update your trivum Installer Line (Reg,Flex,Audiobox) devices to software V 8.68 or higher.
    After that, make sure that this does not appear in the system status: Group play notice: If group play does not work between devices disable IGMP at the network switch, or you may have to repeat the update.

  2. If problems occur while using the trivum InStreamer device then you may disable the Multicast option under: Hardware / Instreamers / Instreamer / Enable InStreamer Multicast. You can then no longer use the same InStreamer directly in multiple zones. But you can still listen to the same InStreamer in multiple zones by creating a group.

  3. If it occurs with group play you may try the Unicast Audio Option available with V9 software, available in the web configuration under:

   System / Setup / Advanced / Use Unicast Audio For Group Play

With this option, audio data in group play is no longer sent by multicast, but by UDP unicast, which should work with every network switch. This works only if not too many trivum devices are part of a group, as it creates a higher load at the master zone that sends the data. It should work safely with 3 devices, for example 3x SC344. It may still work with more devices, so you can just try the option and see if group playback still sounds stable. But, for example, with 10x AudioBox or 10x RP310 systems this option will no longer work. Here you will have to use Multicast and apply Switch configurations as described under 4. below.

  1. Use an IGMP capable network switch.
    At the switch, make sure that IGMP snooping is really used (via the switches configuration surface), including an active "Querier" (possibly Switch dependent).

The group audio play produces a high network traffic. The IGMP protocol makes sure that this traffic reaches only those devices interested in that traffic. But for this the switch needs to understand IGMP, and the trivum device requires the software version listed above.

Switches supporting IGMP are, for example, HP 1920G, HP-E2620-24-PoEP, Cisco SG300-10.

Furthermore, if the system is controlled by iPads, an Apple Airport Express WLAN access point is recommended.

Example configuration with HP 1920G switch:

Screenshot Enabling IGMP Snooping
Figure 1. Screenshot Enabling IGMP Snooping. (use right mouse button, then Open Image)

First enable IGMP globally. But then you must also click below Operation and set:

Screenshot Enabling IGMP Snooping and Querier
Figure 2. Screenshot Enabling IGMP Snooping and Querier

Enable: IGMP, version 3, with Querier.

Then select "Save" at the right top to store all settings permanently.

If you think there may be a network loop in your cabling, also enable: MSTP/Global/Enable STP Globally/Enable

2.3. Possible problems of network topology at the customer:

If multiple switches are used then care must be taken that either all support IGMP, or that the one supporting IGMP is placed at the top, containing all trivum devices.

So the network should look like, for example:

Topology
Figure 3. Topology

To avoid flooding of non trivum devices by unwanted audio messages.

2.4. Configuration of further switches:

With a HP-E2620-24 switch there is only an option "IGMP" by default, without details. It seems that no extra global save option is required. It seems that this switch uses Querier by default. With our tests the IGMP filtering worked immediately. You may also configure details, but for that you need to connect by RS232 cable to that switch. When restarting the switch, to get again to the switch config, you may have to enter it’s IP without any path behind. Same as with 1920G, in case there are still network problems you may enable: Spanning Tree/Tree Management/STP

At a Cisco SG300-28 switch select:

  Multicast
     Properties/Bridge Multicast Filter: Enable
     IGMP snooping/Status: Enable
     IGMP Table: Edit
        IGMP Snooping Status: Enable
        IGMP Querier Status: Enable
        IGMP Querier Version: IGMPV3

After setting these values, wait 2-3 Minutes before filtering becomes active. Select the blinking "save" button at the top then select: source/running config, destination/startup.

The Cisco also supports STP in case of network loops.

Enable IGMP Snooping
Figure 4. Cisco Enable IGMP Snooping

3. Touchpad network failure with static IP

ARM9 based touchpads with Software Version 2.42 or lower and static IP configuration may experience network failure like

  • not visible in the music center, server admin tool etc.

  • software update cannot be done.

To fix this, follow this procedure:

  • check if it’s an ARM9 touchpad under settings/touchpad settings/about

  • check if it has a Version 2.42 or lower

  • and if static IP is configured.

Then you may try to run a software update, but probably it will fail. therefore:

  • change the touchpad to DHCP by:

-  settings/touchpad settings/network
-  enable dhcp
-  scroll down
-  restart touchpad, to activate dhcp settings.
  • then run a software update, which should work.

  • after the update is done, switch back to static IP.
    the new version 2.43 or higher will internally write correct network settings with the configured gateway. again select scroll down and restart.

4. V8 and V9 devices are not compatible.

If you have several trivum music server devices and want to combine them as master/slave then all must be either V8 or V9. If you have a trivum music server with TouchPads, then either all must have V8 software (server version V8.x and Touchpads V2.13) or all must have V9 software (meaning server version V9.x and Touchpads >= V2.40)

5. Weather forecast requires Touchpad V2.11.

Due to a change of the weather forecast provider it is required to update the Touchpads. To do so, select Developer / Keypads at the right top, then click Update per Touchpad.

6. Empty Web Visualization with iOS 9.3.5 iPad, iPhone, Safari browser

If this occurs update your trivum server to v8.75 beta build 11952 or v9.05 nightly build 11952. If your system still runs software version 6 or 7 please contact trivum support.

7. InStreamer: if Digital Input has no sound:

If you get sound by analogue input, but not by digital, perform these checks:

  • check the cable if it shows a light.

  • disable Dolby Digital mode at the audio source, if active. The InStreamer has no Dolby decoder and produces no sound if Dolby is used.

  • compare with a different device that accepts digital input. is sound audible with another device?

  • make sure the InStreamer Firmware is up to date (V1.26 or higher)

  • double check that analogue sound is still audible when disconnecting the digital cable (which has priority over anlogue once connected). make sure that the sound source delivers sound permanently.

  • disconnect the device from power, then reconnect. Old InStreamer devices (delivered around 2015) may fail to provide sound if there was no input for several days, and then need a cold restart.

8. InStreamer: if Digital Input is distorted:

Update InStreamer to Firmware V1.07, available with Build 11532 of the latest V8 or V9 server software.

9. RPx actuators: if unexpected restarts occur:

Update to the latest Beta build 11520 or higher.

10. InStreamer: if Update fails

If you select to update InStreamer at the trivum server, but after a while it still has the same version, this can be caused by active IGMP at the network switch. Normally IGMP is a good and necessary thing to protect the network during group audio playback. But during InStreamer update, the InStreamer runs in a very limited system mode, unable to send correct IGMP announcement messages. This may cause the switch to block important data being sent to the InStreamer.

10.1. How to check:

  • with V9 build 11577, look into: Service / Logs+Warnings / Show Logs / Show recent update log.

  • with V8 build 11577, type in the browser address bar: trivumip/print/messages

If you see a message "device does not react" then the update data was blocked.

10.2. How to fix:

  1. connect both trivum server and instreamer to the same switch

  2. deactivate IGMP temporarily at that Switch

  3. retry the update

Once completed, reactivate IGMP.

11. WLAN Errors while streaming Audio with AudioActuators

11.1. Problem

trivum uses multicast messages to send audio from a master AudioActuator synchronized to it’s slaves. Depending on the switch used in your network,it may or may not be able to filter multicast traffic.

11.2. Solution

Make sure to use a switch that supports an option Enable IGMP Snooping. With this option, the multicast messages are sent ONLY to devices that subscribed to this kind of traffic, but NOT to the whole network, like the WLAN. Read all details about switch configuration here: Network failure on group play

12. Distorted, cracking or interrupted sounds

12.1. Reason

The sound disturbances could be clippings caused by a wrong DSP setting.

12.2. Solution

Check "Amount" parameters in Zones → Zone name → DSP/Sounds. If any of the Amount parameters is > 0, then Volume adjust at the top must be 0 minus that value, or better -1 minus that value.

If Amount parameter = +5dB,
then Volume adjust = 0 - 5dB - 1 = -6dB

Furthermore, if Bass enhance level is active, Volume adjust may even require further reduction.

In general, it is a better idea NOT to boost frequencies by Amounts > 0, but to reduce those frequencies that you do NOT want to hear by negative amounts.

If any warnings are shown in red, strictly follow the instructions. For example, EQ with +db AND BassEnhance/virtualSurround are NOT allowed in combination, as the latter one already lifts the sound volume.

If you still hear distortion and clipping and don’t know what the cause is, always select Preset → Load → Preset 1 (Flat / default) at the top, and then try again.

13. The sound is interrupted every few seconds

13.1. Reason

It could be system overloads by excessive tracing.

13.2. Solution

In the Actuator web GUI, see Basic Setup → Advanced options. If the field contains traceplayer=9 then this will internally produce massive trace output, leading to interrupted sound.

Simply clear the field.

14. StreamSource card hangs until restart with no audio

14.1. Problem

Some StreamSource cards delivered in 2014 show the following behavior: * First, everything seems OK, it plays audio. * After a random time, sometimes seconds, sometimes hours the card stops to play audio but no error message is shown anywhere. * The green "C" LED at the card goes off. * Furthermore in the cardlist the card may show a red message Slave inactive.

When trying to use the card an error CardHost inaktiv may appear.

After a full restart of the trivum system, it should work again, until the next error. The reason for this is a change in specifications of a chip on the card, causing incompatibility with V1.30 firmware. You may identify those cards by looking on the biq square chip "LPC2365". In the lowest line, if you see "NSD1317D", with a "D" at the end, then the error may occur (with the older "NSD1317B" revision it should not occur). Even if the number is not 1317 but different, errors may occur - relevant is the "D" at the end.

14.2. Solution

  1. Update toolkit
    If you received a card update toolkit, you can fix this yourself by flashing the card with the latest V1.31 Firmware:

  2. Read the toolkit documentation:

    1. Read Me - trivum toolkit DE.txt

    2. Read Me - trivum toolkit EN.txt

  3. Look as well the toolkit screenshot

  4. Follow all instructions.

  5. Use the latest firmware file:
    StreamSource-1.31.hex you can find here: ftp://service.trivum.com/firmware/Karten/

Do NOT use the contained StreamSource-1.30.hex file

14.3. Repair service

Or you may send us the card back for repair.

15. No sound from some StreamSource cards

15.1. Problem

When using 3 cardhosts with many StreamSource cards (STS) and PowerAmpConnect cards (PAC) be aware of the following restrictions:

  • STS (or any source card like RDSTunerSource) must be placed within slots 1-8 of a cardhost only

  • PAC can be placed in any slot, but normally they are placed in the higher slots, as the lower ones are used by sources

  • sound produced by STS in slots 1-8 of the first cardhost can be played on any PAC in any cardhost

  • sound produced by STS in slots 1-8 of the second cardhost can only be played on local PAC within the second cardhost.
    Same applies for third or even further cardhosts: sound can only be linked locally within the cardhost.

This means, for example, that sound from STS in slot 1 of 2nd cardhost can NOT be played on a PAC in the first cardhost.

On a C4 system with 2 cardhosts, these restrictions do not exist, so sound from a STS in the 2nd cardhost can be played on a PAC in the first.

16. Short Sounds may not play correctly

16.1. Problem

If you try to play short music files with less than 15 seconds, it may happen that only a few seconds or even less is played and then the track is repeated or skipped. This also depends on the sample rate used (22 kHz versus 44 kHz).

16.2. Solution

To achieve correct playback, you may

  • Create a longer music file that contains the same sound many times

OR

  • Extend your music file by up to 15 secondes silence

You can use the free audio editor Audacity. (http://audacityteam.org/)

17. AudioBox P150 sound dropout every 2 seconds

17.1. Problem

In the second zone of a slave device, sound drops out every 2 seconds.

17.2. Solution

Check the configuration for redundant output mappings. For example, if both the first and second zone of the device use the same Cinch output, it causes a conflict.

18. /xml/zone/runCommand.xml for TuneIn Favorites does not work

18.1. Problem

Since V8.53 there is a page print example commands listing command ID’s for external visualisation. Unfortunately, until V8.56 this page documented four internal commands as select TuneIn favorites 1 to 4:

 /xml/zone/runCommand.xml?zone=@0&command=56
 /xml/zone/runCommand.xml?zone=@0&command=57
 /xml/zone/runCommand.xml?zone=@0&command=58
 /xml/zone/runCommand.xml?zone=@0&command=59

From V8.57 on these commands no longer select TuneIn favorites, but line inputs.

18.2. Solution

If you use one of these commands, replace them by:

 /xml/zone/set.xml?zone=@0&source=@i1
 /xml/zone/set.xml?zone=@0&source=@i2
 /xml/zone/set.xml?zone=@0&source=@i3
 /xml/zone/set.xml?zone=@0&source=@i4

The "@i" syntax however allows to select more than 4 favourites directly.

19. 4 Zone Actuator, RP341/RP340 no sound in zones 3 and 4

19.1. Problem

No sound in zones 3 and 4 by using a RP341 or RP340.

19.2. Solutions

19.2.1. Insufficient power supply.

There might be an insufficient power supply. The RP341/RP340 needs

  • 2x 5A power supplies or

  • 1x 10A power supply

Check that the power supply/supplies is/are connected correctly
  • 2x 5A power supplies:

    • connect one power supply to the left "24V DC (+) (-)" field

    • connect one power supply to the right "24V DC (+) (-)" field

  • 1x 10A power supply:

    • connect the + cable to both "24V DC (+)" screws

    • connect the - cable to both "24V DC (-)" screws

    • Check the cable for damages

    • Check the functionality of the speakers

If you have two power supplies, swap them.
If the system fails to start, or after startup outputs 1+2 produce no sound, the power supply is faulty.

19.2.2. Defective Fuse

In rare cases a defective fuse may be the cause of the fault. Normally this should show an error in the web configuration.

20. AirPlay with iOS9 requires V8.68 software or higher.

AirPlay produced by iOS9 iPhones or iPads requires at least trivum software version v8.68.

21. AirPlay problem with C4 on 2nd, 3rd streamsource card:

The zone will not switch on unless you update to V8.73 beta build 11441.

22. AirPlay sound dropouts

22.1. Problem

AirPlay sound dropouts, which are primarily caused by WLAN reception problems.

22.2. Solution

  1. Compare AirPlay via WLAN vs. LAN cable.

  2. Install iTunes on PC or Mac

  3. Make sure the PC/Mac is connected to network only by LAN cable, but not (also) by WLAN

  4. Select trivum as AirPlay output in iTunes
    (at the top of iTunes, right near the volume slider)

  5. Play an .mp3 music file

→ If music plays well from iTunes via LAN cable, but not from an AirPlay device via WLAN, the problems are caused by bad WLAN reception.

Furthermore, check direct play of music files at trivum. If sound is interrupted with direct music file play, then the problem is not AirPlay related.

23. AirPlay Inputs cannot be found in the network

23.1. Problem

trivum AirPlay inputs are not listed on an iPhone.

23.2. Solution

  • With iOS 10, Apple changed the user interface on iPad/iPhone.
    There are two Airplay input selectors.
    Do not use the left one, as it is for screen mirroring only, and will not list trivum.
    Swipe from right to left, then use the right input selector where trivum should appear.
    Furthermore, once you select the trivum input it will jump to the list start.

  • Check if your AirPlay Input name contains a dot ".".
    If so remove the dot, or update to V9.39 build 13654 where it is replaced by ":" automatically.

  • Maybe WLAN as such is the problem.
    Try to use AirPlay via normal LAN cable.
    To do so, install iTunes on a PC or Mac, then click on the blue speaker selection symbol, at the top, right to the volume bar.
    If trivum AirPlay inputs are shown there then it is a problem of your WLAN switch, router, or access point.
    For example:

    • the WLAN router may be configured not to send multicast messages into the WLAN. Check your router configuration.

    • the WLAN router may need a firmware update. In rare cases, routers are blocking multicast before the update, and passing through multicast after an update.

    • maybe the WLAN router needs to be replaced by a different WLAN access point. We recommend Apple AirPort Express.

  • a network using multiple sub networks like, for example
    subnet 192.168.1.x via cable
    subnet 192.168.2.x via WLAN
    will normally block all multicast traffic by default, allowing no Airplay, no detection of any trivum device by the trivum iphone app or ServerAdmin tool, and no KNX IP router traffic!
    in such cases tell your network adminitrator to configure

    • full send-through of bonjour protocol messages via multicast group 224.0.0.251 port 5353 in both directions:

      • from WLAN to LAN for Bonjour Discovery Requests

      • from LAN to WLAN for Bonjour Discovery Replies

    • full send-through of trivum discovery messages via multicast group 239.255.84.83 port 4002 and via multicast group 224.0.0.100 port 4002 at least from LAN to WLAN

    • full send-through of KNX messages via multicast group 224.0.23.12 port 3671 in both directions

  • Also compare with other (non trivum) devices that support AirPlay. For example, try to stream music to some Apple AirPlay speakers. If their inputs do not show up, or are lost after some time, then there is a network problem.

  • While your client application (e.g. an iPhone App) is running, open the Multiroom Setup Tool and select Admin → Quick Restart. The server does not permanently announce its AirPlay inputs but only from time to time. By restart you enforce an immediate sending of these announcements

  • If you have no alternative devices to test AirPlay in your network:

    • Buy an Apple Airport Express Base. this is a WLAN access point that also provides an AirPlay input, with analogue output.

    • Connect the AirPort to the same switch where the trivum server is connected to. Do not connect it to a different switch.

    • Configure your AirPort to provide an AirPlay input, via the AirPort Utility software

    • Select the AirPort access point in your iPhone as your WLAN access point.

    • Play some music on your iPhone. Select AirPlay outputs.

    • Check if the AirPort appears for selection.
      → if it does not appear then your iPhone may need to be reconfigured to make it appear, or the AirPort itself requires a reconfiguration.
      → if it appears, however, like in a small Window showing

          +-----------------------+
          |        AirPlay        |
          |-----------------------+
          |))) iPhone             |
          |[O] AirPort            |
          +-----------------------+
  • Then touch the area with "AirPort", keep it touched, and try to scroll it up by moving the finger in the direction of "AirPlay".
    → trivum inputs must show up then, like:

          +-----------------------+
          |        AirPlay        |
          |-----------------------+
          |[O] trivum: #175 Room 1|
          |[O] trivum: #175 Room 2|
          +-----------------------+

Some technical infos: the AirPlay inputs are announced in the network via UDP multicast messages. Actually the Bonjour protocol is used, which sends messages to a multicast group 224.0.0.251 on port 5353.

23.3. Analysis with sfk.exe

While iTunes is in use, you can check if trivum actually sends AirPlay Input announcement messages. For example, you may use the command line tool sfk for further analysis.

      C:
      cd \trivum
      sfk udpdump -bonjour

Then you should see messages like:

      [#001 received 295 bytes from 192.168.1.119]
       >00008400 ... 6976756D< ............ 94ACCA02B026@trivum 00000000
       >3A202331 ... 616C0000< : #119 Room 4._raop._tcp.local.. 00000020
       >21800100 ... 4F001C80< !.....x.........twister-8.8.O... 00000040
       >01000000 ... 01000000< ....x................. .O....... 00000060
       >780004C0 ... 20233131< x.....w 94ACCA02B023@trivum: #11 00000080
       >3920526F ... 1F393441< 9 Room 2.-.!.....x.........O.94A 000000A0
       >43434130 ... C02D0021< CCA02B021@trivum: #119 Kuche.-.! 000000C0
       >80010000 ... 30407472< .....x.........O"94ACCA02B020@tr 000000E0
       >6976756D ... 78000800< ivum: #119 Schlafen.-.!.....x... 00000100

which contain a binary data dump, also shown as text.

If you see messages containing "@trivum" then these are AirPlay input announcements by a trivum server.

If you see no messages at all, but there must be (also non trivum) AirPlay devices in the network, open CMD.EXE as administrator and check your Windows Firewall settings.

If you see far too many AirPlay messages, you may filter like

     sfk udpdump -bonjour -from=192.168.1.119

which will show only messages from IP address 192.168.1.119, or

     sfk udpdump -bonjour -data "@trivum"

which will show only messages containing the text "@trivum".

If the trivum server seems to send nothing:
  1. Open the Multiroom Setup Tool.

  2. Click Admin → Quick Restart

→ The trivum server must send those announcements on restart.

24. AirPlay cannot be used from a Desktop Mac or PC

24.1. Problem

XMBC may cause incompatibilities.

24.2. Solution

Check if AirPlay is working with any AirPlay device, for example AppleTV.

If not:
  • Check if XMBC is installed on your system.

  • Check if XMBC has AirPlay support active. (This may cause incompatibilites.)

  • If so, uninstall XMBC and retry.

25. KNX IP Router cannot be found or sends nothing

25.1. Problem

the trivum music server does not receive any KNX messages. A KNX IP router is not shown in the web configuration.

25.2. Solution

  • make sure you are really using a KNX IP router, but not a KNX interface.

    • An interface uses TCP communication with only one partner at a time, only through normal LAN IPs like 192.168.1.x.

    • A router uses UDP multicast communication, typically via address 224.0.23.12.

  • do not use WLAN. if your IP router is connected by WLAN it is very probable that UDP multicast messages (required for all KNX traffic) are not passed through your local network.

  • do not use sub networks. for example, if your IP router is located in a network like 192.168.2.x but your trivum system is in a network 192.168.1.x then all kind of multicast messages is blocked, including those via 224.0.23.12.

  • connect as direct as possible. connect the IP router to the same network switch as trivum, at least temporary for testing. if there are many network switches between trivum and the IP router some may refuse to pass on UDP multicast messages.

  • compare with the ETS group monitor on your PC or notebook. To do so,

    • deactivate WLAN at the notebook.

    • Connect it by cable to the same network switch as trivum.

    • Configure the ETS group monitor to use IP router mode by multicast.

    • Check if expected messages appear.

  • open the trivum web configuration under: KNX / setup KNX communication.

    • Enable "trace bus communication".

    • Show the KNX log. Here you see all incoming messages.

    • Press reload (F5) repeatedly to see the updates.
      Compare the KNX log with input shown in the ETS group monitor.

  • send a KNX test message directly from the ETS group monitor.
    This must always arrive at trivum, if you really connected your notebook by cable to the same switch.
    Verify at the trivum KNX log that the test message arrives.

  • if the ETS test message arrives

    • press a real KNX button in the wall

    • see if it produces input in the ETS

    • compare with the KNX log at trivum.

  • if only ETS shows input, but not trivum,

  • sometimes it may also help to restart network switches or the router.

26. Unexpected Zone On with unexpected music play

26.1. Problem

Zone switches on and plays unexpectedly

26.2. Solution

Look carefully which source is active, and what is played.

You may also look into the system’s Eventlog, in the web configuration under:
Information / About / Show Event Log.
There it tells clearly what event caused switch on of what zone.

Possible activation reasons:

  • SpotifyConnect: if you had a guest in the days before and allowed them to play SpotifyConnect on your trivum system then it may play unexpectedly anytime later, even if your guest is out of the house, far away. This is a design issue of the SpotifyConnect network, which cannot be changed.
    You may protect against this by the following option:
    Music / Streaming / SpotifyConnect / Limit SpotifyConnect play to selected user names.

  • Play may be caused by a misconfigured alarm. Look which zone is active, and check it’s alarm settings.

  • Play may be caused by a KNX automation event, or by a HTTP API request.

  • If the Eventlog tells HTTP as the event source, look at the IP address part given. For example, "HTTP .222 GET" normally tells that IP 192.168.1.222 sent a request, if your network is 192.168.1.x. Look into the list of control units. Identify the origin, like a Touchpad or Tablet.

27. SpotifyConnect changes volume on next track

27.1. Problem

SpotifyConnect play starts, then at trivum the volume is changed.
As soon as the track end is reached, and the next track starts, the volume jumps back to the volume used before at the tablet.

27.2. Solution

Check your SC device configuration if multiple zones use the same Streamer:

  • Configuration / Zones / zone / Basic settings

  • look at: Default streamer

normally Zone 1 has Streamer 1, Zone2 has Streamer 2, and so on.
If, for example, Zone 2 also uses Streamer 1, then the system refuses to send volume changes in a zone to SpotifyConnect as it is amibiguous.

Reconfigure the system to use one streamer per zone exclusively.

28. SpotifyConnect shows only one input with SC

28.1. Problem

Normally an SC device provides 4 SpotifyConnect inputs to the network, but only one can be seen.

28.2. Solution

Check your SC device configuration if multiple zones use the same Streamer.

  • Configuration / Zones / zone / Basic settings

  • look at: Default streamer

If, for example, all zones use Streamer 1 (which makes no sense in most cases) then there will be only one SpotifyConnect input.

Reconfigure the system to use one streamer per zone exclusively.

29. An webcam image appears and freezes for several seconds on TouchPad

29.1. Problem

An image appears, then the TouchPad freezes for several seconds, then the next image appears.

29.2. Solution

This happens if the webcam image resolution is far too high, e. g. 1280x480.

30. AudioActuator cannot update / no internet or nameserver

30.1. Problem

Reconfigure your webcam to use a lower resolution.

The AudioActuator needs configuration data from a DHCP server. A DHCP server gives the AudioActuator an IP address, and it tells about which Name Server to use. A Name Server is required to connect to the internet to allow

  • web radio playback

  • software updates

  • NTP automatic time setting.

30.2. Solution

Therefore make sure that your Router/Switch/Modem that connects your local network to the internet provides a DHCP service which also gives correct Name server information.

Follow these steps:
  1. Open your Router’s web configuration GUI in a web browser

  2. Search for settings like: DHCP and Name Server

  3. Make sure that DHCP is active

  4. Make sure that Name Server information is sent into your network.
    If you see some Nameserver address like n.n.n.n then verify that this server actually exists.
    On the commandline with a command like

ping n.n.n.n

And if you have no idea what Name Server IP address to use for configuration, try 8.8.8.8 (Google Nameserver)

  1. After changes to the network configuration,first check with a PC or Notebook if Internet access is still working, by opening some internet website.

  2. Then restart the AudioActuator.

31. Bad sound with stereo speaker

31.1. Problem

Bad sound with stereo speakers.

31.2. Solution

Please check the polarity of the speaker connection, if + and - are correct both for the left and right channel.

If, for example, the left channel is correct but the right channel has + and - swapped it must cause bad sound as audio waves from left and right will wipe out each other.

32. Cannot use Touchpad or iPad during group play

32.1. Problem

You can’t control your trivum system while playing audio in a group.

32.2. Solution

This is relevant with Installer Line products like FLEX, REG, DESIGN (AudioBox).

Please read the following article on software versions and network switch configuration: Network failure on group play

33. Coverart does not show in Audioplayer screen

33.1. Problem

After a System V8 (e. g. AudioActuator) software upgrade, it can happen that music is listed with cover art in the artist/album search, but when playing one of these tracks, the player screen does not show cover art.

33.2. Solution

Clear the whole music DB (with all cover art), as described here.

Rescan everything.

34. Controller C4 is down although cabling is correct

34.1. Solution

Restart not only the local switch, but also the main router in the network (which makes the internet connection). This may block multicast messages required to communicate with the controller C4.

35. Coverart does not show in Audioplayer screen

35.1. Problem

After a System V8 (e. g. AudioActuator) software upgrade to V90, it can happen that music is listed with cover art in the artist/album search, but when playing one of these tracks, the player screen does not show cover art.

35.2. Solution

Clear the whole music DB (with all cover art), as described here. Rescan everything.

36. Crestron fails to send commands to trivum after a while

36.1. Problem

If you program Crestron to send HTTP commands to trivum it is important that, after each command, the connection must be closed. If you configure Crestron to keep the connection open then it seems to work for a few commands, but suddenly the connection is closed (a forced close by trivum server after some time) and no further communication seems possible, although sending commands by a web browser still works.

37. Devices at IR/RS232 Adapter do not react

Devices are configured at the trivum server and connected via RS-232 adapter.

37.1. Adapter is not active, not found in network

  1. Check the Adapter power supply and LAN cabling.

  2. Check the Cat-5 LAN connector
    → If LEDs are blinking, then both power supply and LAN connection is working

37.2. Adapters are detected

Adapters are detected, devices can be activated by TouchPad or web keypad, but they do not physically react, and errors show up like:

  • does not get any data from device

  • does not get valid data from device

  • device noanswer

    1. Enter the device overview page.
      → Adapters should appear in one of three colors:

    2. green
      Adapter is active, has sent messages to device AND received replies from the device

    3. red
      adapter is not active at all (showing "0/0") OR has communication problems (e. g. IP range too small, OR other device like a TouchPad using an IP within the IP range that conflicts with adapter).

    4. blue
      adapter is active, but the device never sends a reply. There is an info (n/0) meaning
      n = number of sent messages
      0 = number of received messages
      → if the device is bi-directional, meaning it should sent replies to trivum, then the physical connection does not work. In this case, check the cabling.

37.3. Possible test

To check if the adapter is physically able to receive any data:

  1. unplug the RS-232 from the target device

  2. connect (shortcut) RX and TX lines, so the adapter receives it’s own RS-232 commands.
    → The receive count must then go up

37.4. Connection from RS-232 adapter to device

Within the cable, TX/RX lines must be crossed. The pin number for TX/RX is different from device to device. Cable pin layouts on the trivum connector side are documented in http://www.trivum.de/downloads/documents/MusicCenter-V7-Setup.pdf

trivum side RS-232 connector pins

Excerpt from page 5 MusicCenter-V7-Setup.pdf

plain RJ-45

SUB-D9 adapter i-rj45

1

TX (Output)

orange/white

blue

2

GND

orange

orange

3

RX (Input)

green/white

black

[6]

[GND]

green

Pin 6 of plain RJ-45 will no longer be used in future adapter versions.

target device side connector pins

The kind of connectors vary from device to device, and even when using SUB-D9 connectors pin assignments can change from device to device. Therefore consult the device manual for an exact pin assignment description.

how to connect

The TX/RX lines must be crossed.

  • connect trivum TX to device RX

  • connect trivum RX to device TX

  • connect trivum GND to device GND

When measuring the TX line it should show -5 to -9 volts.

Table 1. Adapter cables available from trivum

part number

type

i-loewe-c*

RJ-45 o RJ-12 to connect Loewe TV’s

500018

generic RJ-45 to Sub-D9 kit (2 parts) that allows to configure pin assignments individually

'* No longer be available.

If you can send commands to the device, e. g. you press track skip on the TouchPad and a DVD player actually skips to the next track, but you still see the error no valid data on the TouchPad, then since V7.76/8.17 there is also an option in the advanced device settings to disable device reply warnings. This, however, should be used only if you are absolutely sure that the device is connected and reacts to commands. The message device has no connection cannot be disabled. See also Tracing IR/RS232 Adapter communication.

38. Music purchased through iTunes cannot be synchronized to the trivum System

38.1. Problem

Music purchased through iTunes cannot be synchronized to the trivum System, showing an error file too short, skipping.

Possible reason: If you purchased the music through AppleTV, it is possible that it isn’t synchronized yet to your local apple machine where your music library tracks are stored normally. In this case, you have to synchronize AppleTV manually with your apple server (PC, notebook) to make those tracks fully available for synchronization.

38.2. Solution

Check the downloaded music tracks
  1. Open iTunes

  2. Select your newly imported or purchased music track

  3. Right-click on this Track to open the context menu

  4. Select Get Info

  5. Check the size field

→ A real, complete music file usually contains multiple MB of data.

→ If you see only a very small size (smaller than 32768 Bytes) then this is no valid music file, but either a damaged file, or some kind of reference to a track that the trivum Sync tool cannot use.

In this case, try to play the track in iTunes. If playing succeeds, check the size again - if it’s now several MB, then iTunes did some internal on-demand download action.

If you checked your new files this way, making sure that every track has a reasonable size, you may create a new playlist, drag them therein, then synchronize and check this playlist in the trivum system. The trivum Sync tool will create a statistic for this playlist listing how many tracks were valid for synchronization.

39. ITunes database on NAS does not use Library.xml

39.1. Problem

When creating an iTunes database directly on the NAS as described in here then iTunes will store all song information in a file: iTunes Library.xml

If, however, such a file does not exist on a NAS, check this:

  1. if you instead find an .itl file enable the creation of .xml format, within iTunes, under:

  Preferences / Advanced / Share iTunes Library XML with other applications
  1. if you instead find a file Mediathek.xml with contents looking similar to an iTunes database, then this is no live database! It is just a manually exported copy or backup, created in iTunes by: File → Library → Export Library. trivum does not use this file for good reason, as it will never be updated if the user changes his playlists within iTunes.

39.2. Solution

  1. Create a real iTunes library on the NAS as described here: NAS and iTunes

  2. Delete the Library.xml-File

40. DHCP Server cannot be reached

40.1. Problem

The green and red LED of the AudioActuator will stay on permanently with the red LED blinking shortly inbetween.

40.2. Solution

By default, the device requires a network with a DHCP server to get its IP address. If no DHCP server can be reached, the LEDs behave as described above.

In such a case:

  • ask your network administrator to provide a DHCP server

  • make sure the trivum device is fully connected to the LAN network so that it can physically reach the DHCP server

  • then press reset at the device, or disconnect it from power temporarily for a restart

If DHCP is available at least once then the device can be reconfigured to use static IP in the future. See Using static IP for more information. To do so, download and run the trivum Administration Tool from ftp://service.trivum.com/Installer/Install-ServerAdmin.exe

41. Fuse Broken

41.1. Problem

All power connections must be connected, otherwise this error appears.

41.2. Solution

Look for the Power - + marks on the actuator and connect both sides to the power supply.

42. Zone is undefined

42.1. Problem

The message Zone is undefined appears, if a TouchPad is using an AudioActuator in Installer Master mode. As a result, the AudioActuator’s mode is changed to "Slave".

A direct control of a Slave AudioActuator by TouchPad is not possible. In consequence, the TouchPad loses the connection and zones referenced on that AudioActuator become invalid or undefined.

42.2. Solution

On the TouchPad…​

  1. Press the trivum icon (upper right corner) to open the System Menu.

  2. Press Setup → TouchPad Settings → MusicCenter link.

  3. Select another AudioActuator which is in Master mode.

42.3. TouchPad alarm icon shows no time

The time is shown only if there will be an alarm within the next 24 hours.

43. AirPlay Startup Errors

43.1. Problem

AirPlay Error: Network (old switch?) uses a unicast .local domain.

This means there is a network configuration that uses a name .local to identify the local DNS domain, which is incompatible to the Bonjour protocol required to use AirPlay. In general this is caused by old router/switch hardware, or wrong configuration within such a switch.

43.2. Solution

  • Ask your network administrator to reconfigure the local network NOT to use .local as the local unicast DNS domain name

AND/OR

  • to replace the router or switch by a newer or different one

43.3. Aternative

Enter the following at the trivum server:

 http://serverip/xml/system/fix-airplay.xml

It will correct some system internal files trying to work around the problem.

44. Static IP cannot be configured with AudioActuator

44.1. Problem

Full support for static IP is available only from Software Version 8.29. If you update to 8.29 you may have to run the update twice.

44.2. Solution:

To find the static IP settings, follow these steps (V 8.49 or higher):

  1. Open the Multiroom Setup Tool.

  2. Click System → Basic Setup

  3. Activate Use expert mode for configuration
    → Further expert mode settings for this installation will be displayed.

  4. Activate Use static Ip instead of DHCP

45. WebTouch Visu does not work correctly on TouchPanel PC

45.1. Problem

Things like the Off-button at the right bottom, or Alarm Time changes will not work correctly on a WebTouch Visu displayed on a TouchPanel PC with Windows.

45.2. Solution

You must configure the correct Pointer Device Click Mode on the TouchPanel PC.

45.2.1. Windows XP/Vista/7

In your Windows System…​
  1. Click Start → System Settings → Pointer Device Settings → Click Mode

  2. Select Click and Move

By default, there is a wrong mode "interactive touch" selected, which:

  • produces a popup menu if you press for a longer time on the Windows desktop

  • makes it impossible to switch a zone off by the off button at the right bottom of a web visu

  • makes it difficult to change alarm time, as long presses on +/- of alarm do not work

45.2.2. Windows 8

On Windows 8, look for similar settings, and always make sure that a long press does not produce a Windows Popup.

46. Security Warning with Web Visu

46.1. Problem

If you modified InternetExplorer settings to allow Flash installations, afterwards running the Web Visu (and many other web pages) may show a line: Security settings are a risk for this computer

46.2. Solution

This can be disabled by the registry editor.

  1. Run regedit

  2. Look into HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Security

  3. Create a string entry Safety Warning Level

  4. Set the value Deactivated

47. Resource sharing conflict

47.1. Problem

Resource sharing conflict appears if

  1. an AudioActuator B was a Slave of another AudioActuator A

  2. then AudioActuator B’s mode was changed to "Installer Master" without unregistering AudioActuator B at AudioActuator A.

47.2. Solution

  1. Enter web configuration of primary AudioActuator A

  2. Go to Zones

  3. Delete AudioActuator B from the list of active AudioActuators.

48. Unexpected source (music file/webradio) appears after switching sources

48.1. Problem

Just for C4 systems!

The trivum system has a technical limitation: archive (playlist) playback and web radio playback are using the same source, a StreamingSource Card.

Therefore switching like Archive Play → Local → Webradio means to switch like StreamSource Card → InputConnect → StreamSource Card and when you’re back to the same StreamSource Card, all it does is to continue in the playback mode that was active most recently - so if Playlist play was active, it will do this, but if webradio was active, it will play the same web radio again.

The distinction Play current stream or run as internet radio on Keypad Keys / Commands applies only when selecting the StreamSource Card for the first time after system restart.

49. TouchPad time differs from trivum Server

If you want the Touchpad to receive its time from the trivum Server, make sure that NTP is disabled locally on the Touchpad:

On the TouchPad…​
  1. Press the trivum icon (upper right corner) to open the System Menu.

  2. Press Info.

  3. Scroll down the table Informations.

  4. Press Special settings

    • Enter manually ntp off

If you want the Touchpad to use NTP, but it always displays GMT time, then the time zone infos have not been installed yet. To solve this issue, run a software update:

On the TouchPad…​
  1. Press the trivum icon (upper right corner) to open the System Menu.

  2. Press Setup → Online software update.

49.1. InStreamer Update Fails

If you select to update InStreamer at the trivum server, but after a while it still has the same version, this can be caused by active IGMP at the network switch. Normally IGMP is a good and necessary thing to protect the network during group audio playback. But during InStreamer update, the InStreamer runs in a very limited system mode, unable to send correct IGMP announcement messages. This may cause the switch to block important data being sent to the InStreamer.

49.1.1. How to check:

  • with V9 build 11577, look into: Service / Logs+Warnings / Show Logs / Show recent update log.

  • with V8 build 11577, type in the browser address bar: trivumip/print/messages

If you see a message "device does not react" then the update data was blocked.

49.1.2. How to fix:

  • connect both trivum server and instreamer to the same switch

  • deactivate IGMP temporarily at that Switch

  • retry the update

  • once completed, reactivate IGMP.

50. Zone Actions cannot be edited

50.1. Solution

  1. You have to enable the expert mode:

  2. Open the Multiroom Setup Tool

  3. Click System → Basic Setup

  4. Activate Use expert mode for configuration

51. TuneIn uses wrong city or country location

51.1. Problem

TuneIn tries to auto detect your country by your IP address. If this fails you may enter the latitude/longitude of your city in the trivum server configuration manually.

51.2. Solution

  1. Open the web configuration

  2. Go to Database&Media → Database → Settings → webradio latitude/longitude

  3. Enter the latitude/longitude of your city

HINT: Visit the help section of the TuneIn setup page.

Example locations:
  • 48.1, 11.5 for Munich, Germany

  • 51.5, 0.0 for London, UK

  • 48.8, 2.3 for Paris, France

52. TouchPad cannot be opened by web browser

52.1. Problem

The trivum 4.3" TouchPad WebSetup cannot be opened by a web browser.

52.2. Solution

Check the TouchPad IP:

  1. Press the trivum icon (upper right corner) to open the System Menu

  2. Press Info
    → The TouchPad IP is displayed in the left Informations area

  3. Compare this IP to the IP of your Computer from which you want to access the TouchPad. The first three parts of the IP should be identical.

 Computer-IP: 192.168.1.30
 TouchPad-IP: 192.168.5.50

Example: Bad. Connection is probably not possible, as TouchPad is in a different subnet (.5) than computer (.1)

 Computer-IP: 192.168.1.30
 TouchPad-IP: 192.168.1.50

Example: Good. Connection should be possible.

52.3. Special case

If the TouchPad has an IP 169.254.231.13, then it probably failed to get a DNS address from a DNS server.

  • check if any DNS server at all exists in the LAN

  • check if TouchPad has connection to that server

OR

  • configure TouchPad to use a static IP address.

In such a case, high addresses like .190 are recommended to avoid later conflicts with future DNS servers that typically use low area IP’s.

53. Coverart does not show in Audioplayer screen

53.1. Problem

After a System V8 (e. g. AudioActuator) software upgrade, it can happen that music is listed with cover art in the artist/album search, but when playing one of these tracks, the player screen does not show cover art.

53.2. Solution

  • Clear the whole music DB (with all cover art), in WebConfig of MusicCenter

  • Rescan everything.

54. Red LED light is permanently active after Software Update on AudioActuator

54.1. Reason 1: Incorrect flashing

When updating with a huge version jump, e. g. from 8.16 to 8.47, it may happen that flashing of internal components does not fully succeed in the first step, and this may cause the red LED to be active permanently although the configuration GUI does not show an error.

54.2. Solution

Repeat the software update (up to 3 times) until the LED goes off after full reboot.

54.3. Reason 2: Jammed reset Button

Another reason can be a jammed reset button.

54.4. Solution

Check if the reset button is somehow locked by the casing. Try to press reset once and check if the system reacts normally.

55. 4Zones Actuator: Voltage too low Alert

55.1. Problem

  • No power connected to the lower part of the AudioActuator 4x
    If the upper part has no power, the system cannot run at all…​.

OR

  • Fuse broken for the lower part.

OR

  • There is power connected, but really too low voltage (it must be 24 V).

HINT: Due to the technical reason, the Voltage too low-Alert will appear on all 4 zones even if the voltage is only too low in 2 zones.

56. simulateKeyPress must be called twice

56.1. Problem

In a Homeserver visualization, the command

 /xml/keypad/simulateKeyPress.xml?id=n ...

must be called twice to activate a source.

56.1.1. Solution

Append parameter

 &once

otherwise the system waits for a press and then release event and/or key repeats.

57. TouchPad does not accept any touch presses

57.1. Problem

The trivum TouchPad does not react to any touch press, but everything else (music status display etc.) seems normal.

A a cold restart (by power disconnect) doesn’t help as well.

57.2. Solution

Possibly a display connector inside the trivum TouchPad got loose.

  1. Check the inside display connector

  2. Remove the cover (8 screws)

  3. Check display connector (foil conductor, foil connector)

    1. g. by opening the retainer, then remove the connector, plug it in again, close the retainer

  4. Check if the TouchPad is working correct.

58. Stealth DSP Preset Configuration

If DSP presets for Stealth LR3G etc. do not appear automatically after software update they can be added manually with these data:

 Stealth LR3G
 09B83F000F0201C8000F0201F4011AFD01E80312020170171803000000010064241F0000

 Stealth LR6G
 09B8760214FD01881314FD01F4011A0000E803120000701718030000000100641A340000

 Stealth LR8G
 09B8500022FD01F40124F801F4011A0000E8031200007017180300000001006479200000

59. RGB dimmer color wheel is not shown on TouchPad

59.1. Problem

The RGB dimmer color wheel is not shown on KNX TouchPad.

59.2. Solution

  • Touch the dimmer object in the KNX page, and keep it touched for 3-5 seconds.
    →The color wheel popup should be shown then.

60. Group Play with external volume control does not work

60.1. Problem

If the volume of a zone is NOT controlled by the zone itself, for example in case of an AudioBox with independent Line-Out with RTI controlled amplifier, then this zone can NOT participate in group play, i.e. nothing will be audible as volume control for group play mode is not available.

61. No sound from some StreamSource cards

61.1. Problem

When using 3 cardhosts with many StreamSource cards (STS) and PowerAmpConnect cards (PAC) be aware of the following restrictions:

  • STS (or any source card like RDSTunerSource) must be placed within slots 1-8 of a cardhost only

  • PAC can be placed in any slot, but normally they are placed in the higher slots, as the lower ones are used by sources

  • sound produced by STS in slots 1-8 of the first cardhost can be played on any PAC in any cardhost

  • sound produced by STS in slots 1-8 of the second cardhost can only be played on local PAC within the second cardhost.
    Same applies for third or even further cardhosts: sound can only be linked locally within the cardhost.

This means, for example, that sound from STS in slot 1 of 2nd cardhost can NOT be played on a PAC in the first cardhost.

On a C4 system with 2 cardhosts, these restrictions do not exist, so sound from a STS in the 2nd cardhost can be played on a PAC in the first.

62. No webcam image appears on TouchPad

62.1. Problem

If you open the webcam App in the TouchPad’s KNX pages, there is no image.

62.2. Solution

  • Make sure the TouchPad SW version is 1.69 or higher
    older versions send fixed authentication data (user="admin", password="1234") that can be misunderstood by webcams

  • Check if the camera allows anonymous access
    If not, enter webcam username and password in the trivum webcam configuration (The password field appears as soon as the user name is set.)

  • Check if the camera allows parallel access by multiple clients. Maybe it allows only single client access. This might block the access of the TouchPad, because the image is already shown in a web browser.+Create an empty tab in your web browser and open the camera image URL therein, to make sure it actually delivers JPEG images.

  • You might have to restart the TouchPad. However in most cases this shouldn’t be necessary if the configuration data is correct.

63. Webcam authorization error

63.1. Access by user/password not possible

  • Configure your webcam to use HTTP Basic Authorization, but not HTTP Digest authorization.

  • the latest Touchpad software will show an error "Webcam digest authorization not supported", older software will only tell "Webcam authorization error".

64. NAS access to a Windows PC share requires username

64.1. Problem

Even if you allowed anonymous network access by "Everyone" to a Windows folder, access is blocked if you leave the username blank.

64.2. Solution

It seems that, for Windows shares, a non empty user name must always be supplied. You don’t even have to supply a valid username. Just type anything, for example "anonymous", and keep the workgroup and password empty.

Sometimes not even that is working. Maybe you want to share a folder with wrong access rights, or for some reason anonymous access isn’t possible to your Windows shares. In this case:

  1. Create a new user on your Windows machine username=music, password=music

    • Create an easy, simple music folder on your hard disk C:\TestMusic

    • Edit the Properties of C:\TestMusic and share it on the network with read access for user music

    • Enter at the trivum server

 smb://yourwindowsip/TestMusic
 user: music
 password: music

If you don’t know your workgroup then try to type WORKGROUP, or leave it blank.

65. Change Volume without a Slider by defining + and - Actions

The trivum web visualization shows a volume slider which is convenient to use, however, in some cases like very large groups and slow or instable WLAN network the many volume events sent may cause inconvenience in handling.

As an alternative you may define Volume + and - actions via

Configuration / Zones / zone name / actions / change action / control a zone / Volume + (or -)

and then touch those actions to increment/decrement volume safely one step.

Furthermore if you feel unsafe about the volume slider going too high set the zone’s maximum volume limit to a safe value under

Configuration / Zones / zone name / basic settings / max. volume for this zone

you may have to do this for all zones that may take part in a group.

66. AudioActuator cannot update / no internet or nameserver

66.1. Problem

The AudioActuator needs configuration data from a DHCP server. A DHCP server gives the AudioActuator an IP address, and it tells about which Name Server to use. A Name Server is required to connect to the internet to allow

  • web radio playback

  • software updates

  • NTP automatic time setting.

66.2. Solution

Therefore make sure that your Router/Switch/Modem that connects your local network to the internet provides a DHCP service which also gives correct Name server information.

Follow these steps:
  1. Open your Router’s web configuration GUI in a web browser

  2. Search for settings like: DHCP and Name Server

  3. Make sure that DHCP is active

  4. Make sure that Name Server information is sent into your network.
    If you see some Nameserver address like n.n.n.n then verify that this server actually exists.
    On the commandline with a command like
    ping n.n.n.n
    And if you have no idea what Name Server IP address to use for configuration, try 8.8.8.8 (Google Nameserver)

  5. After changes to the network configuration,first check with a PC or Notebook if Internet access is still working, by opening some internet website.

  6. Then restart the AudioActuator.

67. A webcam image appears and freezes for several seconds on TouchPad

67.1. Problem

An image appears, then the TouchPad freezes for several seconds, then the next image appears.

67.2. Solution

This happens if the webcam image resolution is far too high, e. g. 1280x480.

  • Reconfigure your webcam to use a lower resolution.

68. How to identify trivum Components by Serialnumber

  • C4 Professional System:

    • find the serial number on the C4 Processor card.
      This card typically contains an "Eth" LAN connector, a "Fan" connector, and at the right top a small serial number.

    • with software V7, you will not find a valid serial number in the web configuration (there are only dummy values 520 or 12326).

    • with software V8, you may also find the Serialnumber in the web configuration GUI at the top near SNR.

  • Audio Actuator: find the serial number

    • printed on the Actuator itself, and

    • in the web configuration GUI at the top after "SNR".

69. RS232 Adapter can be listed but not connected/programmed

Check your network switch if "IGMP Snooping" is active. The trivum IrTool Software uses Multicast messages to send commands to the adapter, but so far it does not use the IGMP protocol. Disable IGMP Snooping at your switch (e.g. within D-Link DGS 1100-16 under "L2 Features") and it should work.

however, that if you are ALSO using trivum Actuators with synchronized audio play back AND a WLAN, then IGMP
Snooping must be active, so the above deactivation should be temporary for programming only.

70. IR/RS232 Adapter power supply connection

Possible options for power supply:

  • A POE switch that delivers 48 V via CAT 5 cable

OR

  • A CAT 5 Power Injector, which itself is connected to a 48 Volts power supply.

never connect this 48 Volts power supplydirectly to the adapter!

OR

  • A 15 (!) Volt Power supply connected directly to the IR/RS232 adapter.

71. How to trace IR/RS232 Adapter communication

If a device connected by IR/RS232 adapter does not react, follow these steps to trace the communication:

71.1. activate device I/O tracing at server side

System V7: select Addons / Devices / open device, then advanced / verboseMode

Then send test commands: Addons / Devices / open device, select Commands, select Send at the left side.

Then open in the web browser:

 http://{serverip}/print/controller-trace

If you see messages like:

 << send: "MYCOMMAND {0D}{0A}"

this means a command was SENT to the Adapter, and the Adapter tried to forward to the device.

If you see messages like:

 >> recv:

this means a response was received from the device.

If reponses are listed, however, also depend on the kind of device driver chosen. Unidirectional drivers may never list a response.
In such a case, the following may help:

71.2. trace communication directly at the Adapter

To do so, find out * the IR/RS232 Adapter IP address * the IR/RS232 Adapter Serial Number * the IR/RS232 Adapter Firmware Version

System V7: IP and SNr are listed under Addons / Devices in the Status column.
Firmware Version is listed under Adapters.

Then download the trivum trace tool from ftp://service.trivum.com/Installer/servicetools/

Windows: download trace.exe AND libgcc_s_dw2-1.dll Mac : download trace-mac

Then open a Shell or Command Line Window (e.g. Windows: select Run then type CMD.exe) and go into the folder of the downloaded tools.

  • RS232 Adapter Version 1.12 and lower:

    • Windows: type: trace adapterip

    • Mac : type: chmod 777 trace-mac, then: ./trace-mac adapterip
      Now you should see something like

   Tracing: 192.168.1.133
   trivum TraceMonitor V1.08 (Port=1222 Target=192.168.1.133, VMar 14 2013/11:11:41)
and you may press
'i' for information
't' to toggle event tracing outputs
  • IR+RS232 Adapter Version 1.13 and higher:
    Make sure you are using trace tool 1.09 or higher, otherwise you cannot trace the adapter.

    • Windows: type: trace ir adapterSerialNumber

    • Mac : type: chmod 777 trace-mac then: ./trace-mac ir adapterSerialNumber
      no interactive options are available.

71.3. control the device manually

Instead of sending commands via trivum to the device, also try to control the device directly, e.g. by switching on a DVD player by it’s power key, then loading a DVD and skipping tracks manually, to produce possible RS232 replies that may show up in traces as described above.

71.4. Typical RS232 Adapter replies

depending on the adapter firmware, more or less informations are shown.

71.4.1. RS232 Adapter V 1.03 examples:

Got cmd #64
   -> means adapter got an RS232 command
      from the trivum server which will be
      forwarded to the actual RS232 device.
Sent message to device
   -> typically after cmd #64, the command
      was sent to the actual RS232 device.
Got cmd #67
   -> means adapter got an AdapterInfo request
Sent device reply to controller {IP}
   -> means adapter got data from the actual
      RS232 device and sends it to the server

This firmware allows interactive 'i' command to check some cable pin status.

72. Short Sounds may not play correctly

If you try to play short music files with less than 15 seconds, it may happen that only a few seconds or even less is played and then the track is repeated or skipped.

This also depends on the sample rate used (22 kHz versus 44 kHz).

To achieve correct playback, you may

  • create a longer music file that contains the same sound many times

  • or extend your music file by up to 15 seconds of silence

with an audio file editor like Audacity.

LED Blink Codes:
  • as long as the device is starting, yellow and red flash synchroneously once per second

  • as soon as the software is fully operational, yellow and green should be flashing, with red being off.

if an actuator is blinking Red, and you press Reset, the red blinking may continue for a while
until the device has fully restarted. Please allow one minute after pressing Reset until the blinking stops.

74. Actuator red LED light is permanently active on first use

The red LED is on during start phase. If it stays on permanently, please check the following:

By default, the device requires a network with a DHCP server to get it’s IP address.

If no DHCP server can be reached,

  • green and red LED will stay on permanently

  • with the red LED blinking shortly inbetween

In such a case,

  • ask your network administrator to provide a DHCP server

  • make sure the trivum device is fully connected to the LAN network so that it can physically reach the DHCP server

  • then press reset at the device, or disconnect it from power temporarily for a restart.

If DHCP is available at least once then the device can be reconfigured to use static IP in the future. To do so, download and run the trivum Administration Tool from ftp://service.trivum.com/Installer/Install-ServerAdmin.exe

75. Actuator red LED light is permanently active after Software Update

When updating with a huge version jump, e.g. from 8.16 to 8.47, it may happen that flashing of internal components does not fully suceed in the first step, and this may cause the red LED to be active permanently although the configuration GUI does not show an error.

In this case, repeat the software update (up to 3 times) until the LED goes off after full reboot.

Another reason can be a jammed reset button.

Check if the reset button is somehow locked by the casing, try to press reset once and see if the system reacts normally.

76. KNX Scene Configuration example

Example: a trivum actuator should be controlled by KNX scenes.

By selecting two different scenes through GA 1/5/99 the first zone should either be off, or it should play a station of the FM tuner.

  1. System / KNX Setup:

    • enable Use EibNetIP for EIB access

    • GA scene save/restore: enter '1 5 99'

  2. Zones / first zone / KNX settings:

    • GA to include/exclude in scene: enter '1 5 90'

  3. Scene programming:

    1. scene 1: off state

      • make sure the zone is off.

      • tell first zone it is part of a scene:
        send through KNX 1 Bit, Value 1, to 1/5/90
        → to verify if this KNX command was accepted, look under Developer/Traces/KNX Trace where it should say: "Zone 'first zone' will handle scene part '1' telegram"

      • store the current (off) state as scene number one:
        calculate the scene index

         index   = scene number - 1

calculate the command code

         Store   = 128 plus scene index
         Restore =   0 plus scene index

send through KNX: 1 Byte, Value 128, to 1/5/99
→ verify if the KNX trace says: "will save scene 1. scene 1 save included 1 zones." .. scene 2: FM tuner station * activate FM tuner in the zone, select station 3. * store the current (on) state as scene number two:
send through KNX: 1 Byte, Value 129, to 1/5/99
→ verify if the KNX trace says: "will save scene 2. scene 2 save included 1 zones."

  1. Use the scenes:

    1. use the "off" scene:
      send through KNX: 1 Byte, Value 0, to 1/5/99
      → the zone should switch off.
      → verify if the KNX trace says: "will restore scene 1. included 1 zones."

    2. use the FM tuner scene:
      send through KNX: 1 Byte, Value 1, to 1/5/99
      → the zone should play FM tuner station 3.
      → verify if the KNX trace says: "will restore scene 2. included 2 zones."

It is not required to have "trace bus communication" active to see the KNX trace messages shown above.
The important action messages for scene handling are always traced.

77. create Windows Desktop Shortcut to Web Visualization

If you defined a web visu under control units, you may create a Windows Desktop Shortcut like:

Google Chrome Browser:

  • select "Show" to open a new Browser Window with a web visu.
    At the top, you see the address like http://192.168.1.119/visu/iapp?id=20

  • create a new Tab. enter the same address into that Tab, e.g. http://192.168.1.119/visu/iapp?id=20

  • look at the right top side for the striped button.
    Select: Tools / create application shortcuts.
    Check only "Desktop", then click on create.

Now you have a shortcut on your windows desktop that opens without an address bar.

78. How to control multiple Actuators or AudioBoxes via one Web Visualization

To allow this they must be combined as master/slave devices.

  • one device stays master (default mode)

  • on all other devices: select admin / set mode to installer slave

  • on the master, go to the zone list, then wait and reload (via circle button) until all other devices show up in green.

  • then select on the other devices: use this actuator

This way the slaves are added to the master as new zones. Then use only the web visualization of the master. There, enter the new zones and play music.

with the 4 zone actuator restrictions in group play apply, for example, starting a group play from a slave zone and then
adding zones from the master may not work.

79. Maximum possible Streams (StreamSources) per device ===

A single C4 system may play

  • up to 6 streams in parallel with sample rates up to 96 khz using file formats mp3, aac, alac, flac (16 bit)

  • up to 5 streams in parallel with Flac 192 khz 16 bits, or with Flac 96 khz 24 bits (requires Software V 8.67)

  • up to 3 streams in parallel with ALAC 192 khz files, or with Flac 192 khz 24 bits (requires Software V 9.41)

Trivum does not support .dsf files or any files with sample rates beyond 192 khz.

80. C4 with 2 or more Cardhosts: Noise or unexpected sound

80.1. Problem

Multiple Card Hosts are used within a large C4 system.

When playing a source, like analogue input, not only the sound of that source is audible, but also unexpected sound like FM tuner. When disconnecting the analogue in source, only the noise is audible.

80.2. Solution:

  1. Make sure you are using Shielded Twisted Pair cables.
    These are marked as STP or SFTP.
    Do not use Unshielded Twisted Pair cables, marked as UTP.

  2. Make sure you are using the correct cabling scheme.
    For example, with one master and two slave card hosts then connections must be

    • TXA from 1st → RXA of 2nd device

    • TXB from 1st → RXB of 2nd device

    • TXA from 2nd → RXA of 3rd device

    • TXB from 2nd → RXB of 3rd device

81. How to test if a card is broken

81.1. Problem:

A C4 card like FM tuner, Streamsource etc. does not work at all.

81.2. Solution:

Analyze if the problem is caused by the card itself, or by the cardhost, or a specific slot of the cardhost.

  1. see if there is another free slot in the same cardhost.
    Mind that sources need to be placed in slots 1-8.
    If so, put the card in the free slot and restart the system.

    • if it is working then the slot is defective.

    • if it is still not working then the card is defective.

  2. if there is no free slot available exchange the card with another card of the same type, for example another FM tuner in another cardhost.

    • if the card is working in the other cardhost, but the exchanged card no longer works, then the slot is defective.

    • if the card is still not working, even in the other cardhost, then the card is defective.

If the tests clearly show a defective card then give us feedback so we can arrange a replacement.

82. 4 Zone Actuator: Amplifier channel overload

Please check the device temperature under

   Zones / left near device select: Show details

If the Temperature line shows more than 65 Degrees this could cause device malfunction.

  • make sure that the device gets enough air for cooling.

  • look carefully at the device enclosure, near the speaker and power connectors, if there are enclosure caps without holes (gaps) that prevent air circulation.
    If so you may remove some or all of these caps.

83. Web Visu Volume Slider Error with Chrome on TouchPanel PC

On a Windows 10 Touchpanel PC the Google Chrome browser is by default configured to react to these gestures:

  • swipe right to left: navigate to previous page

  • swipe left to right: navigate to next page

This makes a proper use of the Volume slider in the trivum Web Visu impossible.

Basically you have to run the Chrome browser with a parameter -overscroll-history-navigation=0.

To do so, create an icon on the Desktop to run the Chrome Browser, then edit it to run something like

   C:\Program Files (x86)\GoogleChromeApplication\chrome.exe -overscroll-history-navigation=0

84. [229] Instreamer cannot update

This may happen with Switches having IGMP snooping active.

During an update the InStreamer must switch into a very limited operation mode where it cannot correctly announce IGMP to the switch, therefore update data for the Instreamer may get blocked.

Therefore:
  • connect both trivum server and instreamer to the same switch

  • deactivate IGMP temporarily at that Switch

  • retry the update

  • once completed, reactivate IGMP.

85. number of wires required with a LAN connection

  • 100 mbit → 4

  • Gigabit → 8

86. cannot delete web radio favourite with touchpad

There is a problem with web radios which are no longer supported by TuneIn, marked as "Not supported". These may fail to delete with the Touchpad. Try it with the web visualization instead, this should always work.

86.1. 7 inch touchpad compatible POE switches

POE Switches for power supply:

do NOT use:
  • TP-Link TL-SF 1008P Rev. 1.6 (Revision 3 works)

  • D-Link DGS-1008P Rev. B1 (technically same as TL-SF above)

otherwise the power supply is too weak, and the touchpad may start only a few seconds, then switch off.

Power works normal with:
  • TP-Link TL-SF 1008P Rev. 3

  • HP 1920

  • Intellinet 524155

86.2. 7 inch touchpad startup failure

Problem: when connecting power there is a short white flash, then (with a black screen) background light is active, but (for longer then a minute) no activitiy is visible. Ethernet network LEDs also do not blink.

Solution: look at the LEDs at the network switch where the touchpad is connected. When connecting power at the touchpad, orange should be on permanently, and green should start to blink after a few seconds. If there is no blinking, then the SD card in the touchpad may have got loose during transport. Open the device (by 4 screws) then search for the sd card. Take it out, and push it in again. Then reconnect the device to power.

87. how to reduce the web visualization functions

If not all functions, like not all sources, should be shown in a web visualization, the following options are available:

  • hide FM Tuner:
    system / setup / user interface details / show fm tuner as source

  • hide Line Input:
    configuration / zones / zone / basic settings / Default Line Input

  • restrict visu to a specific zone:
    hardware / control units / visu / basic settings / specify possible zones

    • V8: check this, then click on "zonelist" at the right top

    • V9: check this, then click on "specify possible zones" that appears

  • hide Setup in the web visu: (V8.72 or higher)
    system / setup / user interface details / hide 'system setup' in WebTouch clients

  • hide a zone from selection by any visu:
    configuration / zones / zone / basic settings / zone is available in zone select menu

88. maximum number of webcams with trivum touchpad

The trivum A13 Touchpad supports up to 8 web cams, with resolution 320x240, and one image update every 5 seconds.

The trivum ARM9 Touchpad supports up to 4 web cams, with resolution 320x240, and one image update every 5 seconds.

If higher resolutions or more frequent updates are used then less web cams will work.

89. Invalid NAS reply while scanning music files

The NAS uses an old Firmware which is not suitable to scan music files. It returns a wrong reply to "seek" commands used to jump forward and backward within a file, which is required to scan informations from music files.

This means that most or all of the music on a NAS cannot be read. Scanning may still work with .mp3 files using simple ID3v1 tags, but .m4a and other files will not work.

The only solution is to replace the NAS, or to update it’s firmware, if an update is available.

90. Touchpad: no rows/system/data found error

This error occurs when the TouchPad is connected to a wrong server. This might be caused if the TouchPad was correctly connected to a machine 192.168.1.119 but the next day the machine changed it’s IP and now .119 is a different (non trivum) system.

Solution:

On the TouchPad…​
  1. Press the trivum icon (upper right corner) to open the System Menu.

  2. Press Setup ? TouchPad Settings ? MusicCenter link.

  3. Select the trivum server again.

91. No sound, no radio reception with FM Tuner

  • try a different antenna, at least a simple wire that you plug into the antenna input, for a comparison.

  • try a different (non trivum) device with the same antenna cable that you use with trivum, to verify if any reception is possible.

  • configure a station with a known frequency, instead of just running the station search. check if it produces a (weak) sound.

92. 4 Zone Actuator Power Supply Connection

Instead of using 2 times a 5 A power supply you may also use a single 10 A power supply, but make sure

  • that the + power supply cable is connected by an y parallel cable to both "24 DC +" connectors

  • that the - power supply cable is connected by an y parallel cable to both "24 DC -" connectors.

It is not sufficient to wire only one DC+ and one DC- connector.