P10, controller names

P10 observed a naming conflict: if online.xml contains devices from other TANGO_HOSTs, it is important to have different 'extensions' (here: 'exp' and 'lcx')

<device>
  ...
  <device>p10/smaractmcs2motor/exp.10</device>
  <hostname>haspp10e2:10000</hostname>
  ---
</device>

Conflict, different device name, different TANGO_HOST, but also 'exp': 
<device>
  ...
  <device>p10lcx/smaractmcs2motor/exp.10</device>
  <hostname>haspp10lcx:10000</hostname>
  ---
</device>

No conflict:
<device>
  ...
  <device>p10lcx/smaractmcs2motor/lcx.10</device>
  <hostname>haspp10lcx:10000</hostname>
  ---
</device>

This happens because the pool controller names are created like this (DESY feature):

controller/hasymotorctrl/tm_smaractmcs2motor_exp
controller/hasymotorctrl/tm_smaractmcs2motor_lcx

Notice there differ only in the last 3 letters. The ambibuity can be resolved by adding the remote TANGO_HOST name to the controller name:

controller/hasymotorctrl/haspp10lcx_tm_smaractmcs2motor_lcx

This has been prepared. Needs testing.