I.AM.D V200 WIFI

Status
Not open for further replies.
Jump to Latest
S

Schmurtz

Member
Joined 2016
#1
Summary :


Description of this topic

This topic is dedicated to the V200 Wifi only. There are many topics about the sound quality and the compatibility with your speakers. Please keep this topic about wifi functionalities of the V200.
After reading this topic you will know how to control your V200 through smartphone apps, through telnet command lines and through web API ! The API is perfect for home automation and the smartphone app will allow you to listen radio, spotify, tidal, qobuz and many other online services directly on your V200.
I will also explain in another article how to make the amp autonomous with the help of an arduino : it means how to switch it on and go to the right input source when you send streaming sound or when you put sound on the auxiliary source.

There are many version of V200. This topic is based on V200.9 .
It is probably compatible with V200.7 too.
 
Last edited:
#2
quick review


I.am.d v200 amp description :
  • 2x150w/4Ω , 2x65w/8Ω
  • amp Texas instrument TAS5614LA
  • USB controller : CM6631A
  • inputs : USB-B,spdif coax and optical,jack analogic , wifi (airplay,DLNA and spotify connect !)
  • output : typical speakers output / heaphone 3.5

I've made a description of the components on the motherboard here :


A really quick review of what I think about the I.am.d v200 :

I replaced a very big Pioneer VSX-527 by this little FDA amp. I'm very satisfied by the sound.
I've got old JBL L100 century and the association with V200 seems good. I was afraid by a lack of punch but it seems good with deep basses and clear mediums. There are many reviews on the web, the V200 is a very good amp for the price ! A good review has been done by Qobuz (in french here, in english with google translate). So I will rather speak about functionalities.

I also have a FX-AUDIO D802C. Globally I found that the FX-D802C has a better finition, a better IR remote controller and Bass and tremble tuning is very useful and don't exist on the V200. It's also easier and quicker to switch input sources. To resume, if you don't need wifi features I recommand the FX-D802C. On neither of the two it is possible to adjust the balance. Shame...

On my Pioneer VSX-527 there was airplay and DLNA that I often use.
The V200 has similar functionnalities : DLNA and airplay are present but it is used in a different way, I will explain it below. A very good surprise : the V200 is compatible with Spotify Connect! It is not showed in the description of the product but it's a really nice feature : I take my smartphone, I launch a playlist on the V200, I can switch off my smartphone the V200 will continue to play the playlist and it is controllable remotely by any other spotify client (on my computer at work for example I can control it remotely, even on another network because it is the spotify connect api which is used !). I also use the jack input of the V200 for a bluetooth receiver.

But a little thing not nice compare to the Pioneeer VSX : airplay,DLNA and spotify connect are only available when the v200 is on the "wifi" source input. If you are on another source you will not see the V200 in your airplay devices, nor DLNA nor Spotify Connect... The wifi board is probably powered off when your not on the wifi input. On the Pioneer VSX, if you are on CD input for example, you still see VSX in airplay devices and you can send your smartphone's sound to the VSX : it switch the input automatically. (It could be even better if it returns automatically on the previous input after airplay ends but I'm a little picky).
The hotspot used for the initial network configuration is not disabled when the wifi connection is etablished so you will always see another wifi hotspot appears when you're on the Wifi input source.

There is a web interface to configure wifi, by default this interface is in chinese and it's pretty difficult to switch in english. The screenshots below can probably helps. Also avoir any firmware update with this interface (you can lost the wifi functionality).

The power supply is a box made by Lenovo (almost as big as the FDA 😀) 24V, 2.5A

Power consumption :

ON with speaker output -> 7W
ON with headphone output -> 4W
OFF -> 3W


A little disappointed by the power consumption in sleep mode. When it's power off it continue to consume half of the power of what it consumes when it's powered on... May be due to the IR which is always powered to be able to switch on the device with the remote control ? The USB chipset always stays online too.


Goods:
  • Price
  • Size
  • Sound quality
  • power consumption
  • functionalities : airplay, UPNP/DLNA ,spotify connect (and many more)

Cons :
  • impossible to update the firmware on wifi version without bricking the device
  • Wifi functionnalities only avaible when the FDA is on Wifi source (no automatic switch)
  • no geek/domotic functionalities : you can't switch off the FDA remotely, no smartphone app to change volume... (see my blog article soon to modify it)
  • rotary encoder not very precise (I prefer to have one pysical per source it's faster and easier but it is the same on Pioneer VSX...)
  • Buttons on the remote badly named
  • No balance
  • No informations about different firmware versions
  • No "real" user manual
  • Changing the volume requires pressing repeatedly on the remote control
 
Last edited:
#3
Under the skin of the v200 : Reverse engineering

OK now looking under the skin of the V200...

The little additional network card with a little linux on it is very interesting.

Firstly a network scan of opened ports :
Code: 
* + 192.168.0.x   v200
    |___    23
    |___    53
    |___    80
    |___  4515
    |___  5001
    |___  5356
    |___  8899
    |___ 19004
    |___ 21001
    |___ 21021
    |___ 21022
    |___ 21023
    |___ 21024
    |___ 21025
    |___ 21026
    |___ 21027
    |___ 21028
    |___ 21029
    |___ 21030
    |___ 21031
    |___ 21032
    |___ 21033
    |___ 21034
    |___ 21035
    |___ 21036
    |___ 49152
    |___ 59152
OK telnet seems opened take a look on it...

Code: 
V200 login:

OK need a password....
Some basic tries... Bingo ! login : admin , password : admin !

By default the display is not optimal... In putty configuration click on Terminal -> "Implicit CR every CF"

Some inforamtions about the filesystem :
Code: 
# free
             total       used         free       shared      buffers         
Mem:        28204        26612         1592            0         2860
Swap:           0            0            0
Total:      28204        26612         1592
--------------------------------------------------------------------------------

Code: 
# df
Filesystem           1k-blocks      Used Available Use% Mounted on
rootfs                    5056      5056         0  100%  /
/dev/root                 5056      5056         0  100%  /
/dev/mtdblock8             512       196       316   38%  /mnt
/dev/mtdblock9            6144       324      5820   5%   /vendor


List of running process:

Code: 
# ps -w
  PID USER       VSZ STAT COMMAND
    1 admin     1736 S    init
    2 admin        0 SWN  [ksoftirqd/0]
    3 admin        0 SW<  [events/0]
    4 admin        0 SW<  [khelper]
    5 admin        0 SW<  [kthread]
   34 admin        0 SW<  [kblockd/0]
   37 admin        0 SW<  [khubd]
   47 admin        0 Z    [swapper]
   52 admin        0 SW<  [kswapd0]
   53 admin        0 SW   [pdflush]
   54 admin        0 SW   [pdflush]
   55 admin        0 SW<  [aio/0]
  104 admin        0 SW   [mtdblockd]
  151 admin     1384 S    nvram_daemon
  152 admin     1644 S    goahead
  154 admin     1744 R    telnetd
  156 admin     1740 S    /bin/sh
  235 admin        0 SW   [RtmpCmdQTask]
  236 admin        0 SW   [RtmpWscTask]
  280 admin     1352 S    iwevent
  287 admin        0 SWN  [jffs2_gcd_mtd8]
  298 admin        0 SWN  [jffs2_gcd_mtd9]
  308 admin     4464 S    rootApp
  324 admin     2636 S    mv_ioguard
  327 admin     2636 S    mv_ioguard
  328 admin     2636 S    mv_ioguard
  329 admin     2636 S    mv_ioguard
  330 admin     2636 S    mv_ioguard
  332 admin     2636 S    mv_ioguard
  333 admin     2636 R    mv_ioguard
  334 admin     2636 S    mv_ioguard
  341 admin     2092 S    volumeprompt
  343 admin     2392 S    a01remoteupdate
  350 admin     2392 S    a01remoteupdate
  351 admin     2392 S    a01remoteupdate
  353 admin     4548 S    mv_netguard
  354 admin     4464 S    rootApp
  355 admin     4464 S    rootApp
  356 admin     4464 S    rootApp
  365 admin     4548 S    mv_netguard
  369 admin     1220 S    dnsmasq
  371 admin     4548 S    mv_netguard
  372 admin     4548 S    mv_netguard
  375 admin    10352 R    multiplayer
  377 admin     2040 S    iperf -s
  381 admin     4548 S    mv_netguard
  382 admin     4548 S    mv_netguard
  383 admin     4548 S    mv_netguard
  384 admin     4548 S    mv_netguard
  391 admin     1128 S    ntpd -l
  392 admin     2040 S    iperf -s
  393 admin     2040 S    iperf -s
  394 admin     2040 S    iperf -s
  400 admin     6492 S    airplay
  404 admin     2092 S    apple_remote
  411 admin    10832 S    a01controller
  413 admin     2092 S    apple_remote
  414 admin     2092 S    apple_remote
  421 admin    10832 S    a01controller
  422 admin    10832 S    a01controller
  423 admin    10832 S    a01controller
  424 admin    10832 S    a01controller
  435 admin    10832 S    a01controller
  436 admin    10832 S    a01controller
  437 admin    10832 S    a01controller
  474 admin     6540 S    airplay
  475 admin     6540 S    airplay
  477 admin    10832 S    a01controller
  478 admin    10832 S    a01controller
  479 admin    10832 S    a01controller
  480 admin    10832 S    a01controller
  481 admin    10832 S    a01controller
  482 admin    10832 S    a01controller
  527 admin     1732 S    udhcpc -i apcli0 -T 5 -H V200 -s /sbin/udhcpc_wl.sh -
  536 admin    10832 S    a01controller
  538 admin    10832 S    a01controller
  539 admin    10832 S    a01controller
  540 admin    10832 S    a01controller
  541 admin    10832 S    a01controller
  542 admin    10832 S    a01controller
  543 admin    10832 S    a01controller
  544 admin    10832 S    a01controller
  545 admin    10832 S    a01controller
  546 admin    10832 S    a01controller
  548 admin    10832 S    a01controller
  551 admin    10832 S    a01controller
  552 admin    10832 S    a01controller
  553 admin    10832 S    a01controller
  554 admin    10832 S    a01controller
  555 admin    10832 S    a01controller
  556 admin    10832 S    a01controller
  557 admin    10832 S    a01controller
  558 admin    10832 S    a01controller
  559 admin    10832 S    a01controller
  560 admin    10832 S    a01controller
  561 admin    10832 S    a01controller
  562 admin    10832 S    a01controller
  564 admin    10832 S    a01controller
  565 admin    10832 S    a01controller
  566 admin     6540 S    airplay
  569 admin     1740 S    -sh
  570 admin    10352 S    multiplayer
  571 admin    10352 S    multiplayer
  572 admin    10352 S    multiplayer
  573 admin    10352 S    multiplayer
  583 admin    10832 S    a01controller
  620 admin     1744 S    -sh
  710 admin     1732 S    sh -c wget  -O /tmp/products.xml 'http://114.215.143.
  711 admin     1140 S    wget -O /tmp/products.xml [url=http://114.215.143.128:8020]?????????[/url]
  712 admin     1736 S    tee /tmp/remoteupdatewget.log
  725 admin     1740 S    -sh
  738 admin     1736 R    ps -w

Here a list export of all filesystem files -> To DO

--------------------------------------------------------------------------------
Sound card :

Code: 
# cat /proc/asound/cards
 0 [RT5350         ]: wm8918 - RT5350
                      RT5350 (wm8918)

--------------------------------------------------------------------------------
Native commands list :
Code: 
# busybox
BusyBox v1.12.1 (2015-09-24 14:22:57 CST) multi-call binary
Copyright (C) 1998-2008 Erik Andersen, Rob Landley, Denys Vlasenko
and others. Licensed under GPLv2.
See source distribution for full notice.

Usage: busybox [function] [arguments]...
   or: function [arguments]...

        BusyBox is a multi-call binary that combines many common Unix
        utilities into a single executable.  Most people will create a
        link to busybox for each function they wish to use and BusyBox
        will act like whatever it was invoked as!

Currently defined functions:
        [, [[, ash, basename, cat, chmod, chpasswd, cp, date, df, du, echo,
        expr, find, free, grep, halt, hostname, ifconfig, init, init, insmod,
        kill, killall, ln, login, ls, lsmod, lzmacat, mdev, mkdir, mknod,
        mount, mv, nice, ping, ping6, pkill, poweroff, printf, ps, pwd, reboot,
        rm, rmmod, route, sed, sh, sleep, sync, tee, telnetd, test, top,
        touch, udhcpc, umount, unlzma, uptime, vconfig, vi, wc, wget

I have soldered a FTDI on the UART port (PIN 39 and 40) : you will find a full export of the U-boot, a lot of informations.

Code: 
U-Boot 1.1.3 (Sep 24 2015 - 14:21:58)

Board: Ralink APSoC DRAM: 32 MB
relocate_code Pointer at: 81f68000
spi_wait_nsec: 42
spi device id: c2 20 18 c2 20 (2018c220)
find flash: MX25L12805D
TOTAL_FLASH_SIZE: 16 MBytes
raspi_read: from:30000 len:1000
.*** Warning - bad CRC, using default environment

i2s_slave init
============================================
Ralink UBoot Version: 3.6.0.0
--------------------------------------------
ASIC 5350_MP (Port5<->None)
DRAM_CONF_FROM: Boot-Strapping
DRAM_TYPE: SDRAM
DRAM_SIZE: 256 Mbits
DRAM_WIDTH: 16 bits
DRAM_TOTAL_WIDTH: 16 bits
TOTAL_MEMORY_SIZE: 32 MBytes
Flash component: SPI Flash
Date:Sep 24 2015 Time:14:21:58
============================================
icache: sets:256, ways:4, linesz:32 ,total:32768
dcache: sets:128, ways:4, linesz:32 ,total:16384

##### The CPU freq = 360 MHZ ####
estimate memory size =32 Mbytes

Please choose the operation:
  0: Boot system code via Flash (default).
  1: Entr boot command line interface.
  2: Load Boot Loader code then write to Flash via TFTP.
  3: Load backup system code then write to Flash via TFTP.
  4: Load system code then write to Flash via TFTP.
  5: Load system code to SDRAM via TFTP.
  6: Load user1 code then write to Flash via TFTP.
  7: Load user2 code then write to Flash via TFTP.

choose the operation update via UDisk:
  a: Load boot loader then write to Flash via UDisk.
  b: Load backup system then write to Flash via UDisk .
  c: Load system kernel then write to Flash via UDisk.
  d: Load system code to SDRAM via UDisk.
  e: Load user1 code then write to Flash via UDisk.
  f: Load user2 code then write to Flash via UDisk.
0

0: System Boot system code via Flash.
## Booting image at bc250000 ...
raspi_read: from:250000 len:40
. Image Name: Linux Kernel Image
  Created: 2015-09-24 6:29:29 UTC
  Image Type: MIPS Linux Kernel Image (lzma compressed)
  Data Size: 1387707 Bytes = 1.3 MB
  Load Address: 80000000
  Entry Point: 80414000
raspi_read: from:250040 len:152cbb
...................... Verifying Checksum ... OK
  Uncompressing Kernel Image ... OK
No initrd
## Transferring control to Linux (at address 80414000) ...
## Giving linux memsize in MB, 32

Starting kernel ...

LINUX started...

 THIS IS ASIC
Linux version 2.6.21 (root@wiimu-virtual-machine) (gcc version 3.4.2) #1 Thu Sep 24 14:29:19 CST 2015
...

Full Export here.



OK now we know that we have a wifi card based on Ralink RT
This card is compatible with openWRT but this is not openwrt with the V200, this is a personalized distrib made by Wiimu

By visual identification I determine that the card is a Nixcore X1 . This card is compatible with OpenWRT but it is not the case with the V200.
This Nixcore is personnalised by Wiimu... And Wiiimu domain name = LinkPlay... linkplay and bingo ! This very interesting, once you know that, you'll find a lots of apps, technical informations and an API ! Each manufacturer referenced by linkplay gives smartphone apps compatible with the V200.

--------------------------------------------------------------------------------


Now I take a look to the /tmp/ folder :



The list of files in tmp folder :

Code: 
# ls

mv_udhcpc_action_lan             update_successed.mp3             ftrwa_wps_result.log             MVver_new
general.dat                      delay_reboot.sh                  ftrwa_apcli_result.log           cur_playback_meta_data
uart_pass_port                   RequestGoheadCmd                 ftrwa_channel                    airplay_stop
RequestIOGuard                   RequestAppleRemote               ntp_result                       goahead.log.ftrwa
volumeprompt                     RequestAirplay                   region                           ftrwa_imuzo_fifo_client
a01remoteupdate                  a01controller_player_status.txt  products.xml                     mv_ping_result
CN_update_successed.mp3          Requesta01controller             product.xml                      mv_tmp_apcli0.console_out
RequestNetguard                  mv_udhcpc_action                 remoteupdatewget.log

Below the content of each files :
----------------------------------------------------
Code: 
# cat mv_udhcpc_action_lan
deconfig
----------------------------------------------------
Code: 
# cat general.dat
customuuid=FF960740
uuidstart=c94cb48e3c09e8dd
uuidend=6f105678fdfa6b2f
expirecheck=0
USBAutoPlay=1
resDir=/vendor/res
extweb=0
----------------------------------------------------
Code: 
# cat mv_udhcpc_action_lan
deconfig

----------------------------------------------------
Code: 
# cat general.dat
customuuid=FF960740
uuidstart=c94cb48e3c09e8dd
uuidend=6f105678fdfa6b2f
expirecheck=0
USBAutoPlay=1
resDir=/vendor/res
extweb=0
----------------------------------------------------
Code: 
# cat uart_pass_port
8899
This port is interesting because you can see last commands send to the wifi card, for example :
Code: 
ÖæFÖFAXX+PLY+000
×AXX+MUT+000
----------------------------------------------------
Code: 
# cat delay_reboot.sh
#!/bin/sh

sleep 3
reboot
sleep 3
reboot
sleep 3
reboot
----------------------------------------------------
Code: 
# cat a01controller_player_status.txt
10,0#
----------------------------------------------------
Code: 
# cat mv_udhcpc_action
bound
----------------------------------------------------
Code: 
# cat ftrwa_wps_result.log
apcli0    stat:
Tx success                        = 11
Tx retry count                  = 0
Tx fail to Rcv ACK after retry  = 0
RTS Success Rcv CTS             = 0
RTS Fail Rcv CTS                = 0
Rx success                      = 77
Rx with CRC                     = 0
Rx drop due to out of resource  = 0
Rx duplicate frame              = 0
False CCA (one second)          = 0
RSSI-A                          = -64
RSSI-B (if available)           = 0
RSSI-C (if available)           = 0

WPS Information:
Enrollee PinCode(ra0)           10564448

Enrollee PinCode(ApCli0)        10564455
Ap Client WPS Profile Count     = 0

----------------------------------------------------
Code: 
# cat ftrwa_apcli_result.log
apcli0    apclistat:
apcli connect to:
BSSID                           = xx:xx:xx:xx:xx
SSID                            = Something
AuthType                        = WPA2PSK
EncrypType                      = AES
PSK                             = xxxxxx
ShareKey                        = ABCFEF123456FFFBBB2222

----------------------------------------------------
# cat ftrwa_channel
Code: 
ra0       RTWIFI SoftAP  ESSID:"V200"  Nickname:""
          Mode:Managed  Channel=1  Access Point: 00:22:XX:XX:XX:XX
          Bit Rate=-0.001 kb/s
----------------------------------------------------
Code: 
# cat ntp_result
 9 Jan 16:15:56 ntpdate[596]: step time server 129.6.15.29 offset 537293708.205995 sec
----------------------------------------------------

Code: 
# cat region
{"ret":1,"start":-1,"end":-1,"country":"\u6cd5\u56fd","province":"Nord-Pas-de-Calais","city":"Lille","district":"","isp":"","type":"","desc":""}#

----------------------------------------------------

Code: 
cat products.xml
<?xml version="1.0" encoding="ISO-8859-1"?>
<productList>
  <product>
    <productid>wfnftrwabox</productid>
    <hardwareversion>FTR-AW2</hardwareversion>
        <UUID>FF960740</UUID>
    <major-url>http://114.215.143.128:8020/ftr_aw_image/20160111/product.xml</major-url>
  </product>
</productList>

Mhhh... Interesting !
----------------------------------------------------
Code: 
# cat product.xml
<?xml version="1.0" encoding="ISO-8859-1" ?>
<product>
  <major-version>20160111</major-version>
  <ver-url>http://114.215.143.128:6000/wifiaudio/upgrade/20160111/MVver</ver-url>
  <layout-url>http://114.215.143.128:6000/wifiaudio/upgrade/20160111/layout</layout-url>
  <image-kernel>http://114.215.143.128:6000/wifiaudio/upgrade/20160111/kernel_rootbox.img</image-kernel>
</product>

This file is very interesting because it show where is the new firmware. I remind you that you should not update your wifi card on V200 otherwise it will not work anymore!

Below the firmware downloaded with the link above (do not use it, I suspect that the I2S pinout output is not the same on this firmware) :
MVver
Code: 
FTR.1.2.2016
FTR
FTR-AW2
wfnftrbox
release
20160111
layout.txt
Code: 
#offset :max_size:min_size:ver:flag:fstype:name:img_size
00050000:00200000:00000040:00002130:0:null:backup:2031035
00000000:00030000:00000040:00002130:0:null:uboot:166944
00a00000:00600000:00000040:00000000:2:jffs2:user2:1
00980000:00080000:00000000:00000000:2:jffs2:user:1
00250000:007B0000:00000040:00002224:0:null:kernel:7638331
kernel_rootbox.img


----------------------------------------------------
Code: 
# cat remoteupdatewget.log
Connecting to 114.215.143.128:6000 (114.215.143.128:6000)
MVver_new            100% |*******************************|    53   0:00:00 ETA
# cat MVver_new
FTR.1.2.2016
FTR
FTR-AW2
wfnftrbox
release
20160111
----------------------------------------------------
Code: 
# cat cur_playback_meta_data
<?xml version="1.0" encoding="UTF-8"?>
<DIDL-Lite xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:upnp="urn:schemas-upnp-org:metadata-1-0/upnp/" xmlns:song="www.wiimu.com/song/" xmlns="urn:schemas-upnp-org:metadata-1-0/DIDL-Lite/">
<upnp:class>object.item.audioItem.musicTrack</upnp:class>
<item id="0">
<song:bitrate>0</song:bitrate>
<song:type_description>un_known</song:type_description>
<song:pick_count>0</song:pick_count>
<song:id>0</song:id>
<song:like>0</song:like>
<song:singerid>0</song:singerid>
<song:albumid>0</song:albumid>
<res protocolInfo="http-get:*:audio/mpeg:DLNA.ORG_PN=MP3;DLNA.ORG_OP=01;" duration="00:08:02.000">spotify:track:47H09jVxrZLalZBv0MnD0R</res>
<dc:title>333</dc:title>
<dc:creator>Flea</dc:creator>
<upnp:artist>Flea</upnp:artist>
<upnp:album>Helen Burns</upnp:album>
<upnp:albumArtURI>http://o.scdn.co/320/ff477865f7123136d7b71cbde0d8080ca5e295c7</upnp:albumArtURI>
</item>
</DIDL-Lite>

This file contain all tags informations about the stream currently played.


Code: 
# cat goahead.log.ftrwa
/httpapi.asp?command=IOSimuRead:17# cat ftrwa_imuzo_fifo_client
This file contains the last API command


Code: 
# cat mv_ping_result
PING qq.com (61.135.157.156): 56 data bytes
64 bytes from 61.135.157.156: seq=0 ttl=43 time=363.378 ms
64 bytes from 61.135.157.156: seq=1 ttl=43 time=361.895 ms

There are many ping to chinese websites (on baidu.com) in this firmware. There is also web script to determine your geographic position. I hope this is just for proposing radios of proximity.

These file are particularly interesting :
a01controller_player_status.json -> contains current state in json format
a01controller_player_status.txt -> send the current status, for example : "2,0" = DLNA stop, "2,1" DLNA play , "2,3" DLNA pause ...
cat cur_playback_meta_data -> contains very detailed metadata of the current stream
 
Last edited:
#4
Smartphone Apps and remote control through API

OK previously reverse engineering taught us a lot, now we know that the wifi board firmware comes from linkplay. If you look on the featured products page you'll find a lot of smartphone apps compatible.

For example the Ieast :


Awesome isn't it ?
Many new features like playing tunein radios, syncing sound between many V200, autosleep, WPS, rename Hotspot quickly ...
And there are many more apps often similar but some manufacturers offers some modified apps, just search for it 😉

And this is not finished ! For home automations fans, you'll find below a guide of the API and a listing of all commands below.
For example to play a stream :
Code: 
http://192.168.0.100/httpapi.asp?command=setPlayerCmd:play:[url]http://185.52.127.155/fr/30001/mp3_128.mp3[/url]
To get the next song :
Code: 
http://192.168.0.100/httpapi.asp?command=setPlayerCmd:prev

Click here to download the full API Guide.

These commands one must be verified (extracted from the firmware) :
Code: 
key_id_press:wps
key_id_press:wpss
GUARD_WPS_SERVER:1  GUARD_WPS_CANNEL
key_id_press:PlayPause  /tmp/Requesta01controller
setPlayerCmd:onepause
key_id_press:prev
setPlayerCmd:prev
key_id_press:next
setPlayerCmd:next
key_id_press:key_circle
setPlayerCmd:channel_next
key_id_press:like
setPlayerCmd:song_like
MCUKeyShortClick:1  MCUKeyPlay  MCUKeyCircle--  MCUKeyCircle++
setPlayerCmd:stop
setPlayerCmd:pause  setPlayerCmd:resume setPlayerCmd:play
setPlayerCmd:ext_getPlayStatus  setPlayerCmd:ext_getPlayMode
 setPlayerCmd:ext_getLoopMode
 key_id_press:mic
 /tmp/RequestASRTTS  talkstart:0 talkstop
 TtsTime TtsWeather  SetPresetNum:%d
key_id_press:voldown
setPlayerCmd:vol--  key_id_press:volup  setPlayerCmd:vol++  setPlayerCmd:slave_vol:%d
setPlayerCmd:slave_mute:%d  key_id_press:mute
setPlayerCmd:ext_vol_get
setPlayerCmd:ext_mute_get
setPlayerCmd:ext_slave_vol:%d
setPlayerCmd:ext_slave_mute:%d  setPlayerCmd:switchmode:udisk
setPlayerCmd:switchmode_by_mcu:wifi setPlayerCmd:switchmode_by_mcu:line-in  setPlayerCmd:switchmode_by_mcu:bluetooth
setPlayerCmd:switchmode_by_mcu:optical  setPlayerCmd:switchmode_by_mcu:udisk
setPlayerCmd:switchmode_by_mcu:mirror
key_id_press:mode
setPlayerCmd:switch_DAC_by_mcu:wifi setPlayerCmd:switch_DAC_by_mcu:line-in  setPlayerCmd:switch_DAC_by_mcu:bluetooth
setPlayerCmd:switch_DAC_by_mcu:optical  setPlayerCmd:switch_DAC_by_mcu:udisk
setPlayerCmd:switch_DAC_by_mcu:mirror
AirplayGet
shutdown
 
#5
Docs and url

 
Last edited:
#6
Subscribed.

Please note that D802 measures and sounds better than D802C. I don't know if this is also the case with V200 versus V200 WiFi. Never owned one.

Secondly there seem to exist many revisions of the standard V200, maybe it is a good idea to mention revision number of the V200 WiFi you have. New revisions with different features or changes can pop up in days.
 
Last edited:
#7
@jean-paul : Can you delete you post and copy/paste here after my last post (the next one) , just for readability

Ideas

I.am.D, if you read this, here some ideas to improve the V200 :
  • Add RJ45 ethernet port
  • On initial netword configuration the first thing to display is language selection
  • A separate button to switch input sources and volume (a press button for each source ?)
  • If you don't change the scroll wheel button you must display when we are in "input selection mode" and "volume change mode"
  • A better power consumption when the device is powered off
  • Always stay wifi online with an autoswitch when airplay/DLNA/spotify-Connect is used (go back on the previous source when the streaming is ended could be the luxury 😉 )
  • change remote control sticker to have right buttons names 😀 Make it possible to let VOL+ pushed to turn up the volume instead of pressing it a lot of time)
  • include other multimedia technologies in the network board (squeezebox, MPD, sc2mpd (to stream computer sound without delay) ... and let it opened for tweakers !
  • implement telnet (or web) commands to control the FDA remotely and be able to developp smartphone apps.
  • Implement a channel balance in the firmware
 
Last edited:
#8
DIY and informations

I'm not an expert in audio mods but some guys like globulegl made some very interesting mods. You can take a look here:
http://www.diyaudio.com/forums/clas...-d802-optimisation-tpa3116-4.html#post4501047
Amplificateurs FDA - Page 38 - 30063064 - sur le forum Amplificateurs Intégrés - 1030 - du site Homecinema-fr.com
List of improvements :
Amplificateurs FDA - Page 38 - 30063064 - sur le forum Amplificateurs Intégrés - 1030 - du site Homecinema-fr.com
Change sc8416 by ak4113 :
Amplificateurs FDA - Page 38 - 30063064 - sur le forum Amplificateurs Intégrés - 1030 - du site Homecinema-fr.com for 10$
add IS2 input :
Amplificateurs FDA - Page 38 - 30063064 - sur le forum Amplificateurs Intégrés - 1030 - du site Homecinema-fr.com


Soon I'll explain how to automate V200. You will find the link here on this post (I will update it)

OK go for comments ! 🙂
 
Last edited:
#10
brochette.jpg

my v200 with power supply it s the best on the pict (qa690, d310 stock, d310 tweak)

my v200 tweak :

double power suply 35v with 2x30000uf
12 power low noise
tablett battery 7.4v 45ah for dsp and other chip
low noise clock for dsp
big coil craft inductor
copper coler
tas5614 remplacement by tas5624
i2s in by rj45
 
#13
globulegl said:
brochette.jpg

my v200 with power supply it s the best on the pict (qa690, d310 stock, d310 tweak)

my v200 tweak :

double power suply 35v with 2x30000uf
12 power low noise
tablett battery 7.4v 45ah for dsp and other chip
low noise clock for dsp
big coil craft inductor
copper coler
tas5614 remplacement by tas5624
i2s in by rj45
Click to expand...

As much as I like your modifications, you can hardly call this a V200 anymore when even the amplifier chip has been replaced.
 
#17
lgreen said:
I am not seeing it as a device on Spotify connect, is it a speaker, computer or TV?
Click to expand...
Oh, now I see that Spotify Connect is a premium feature and I'm using the free version? That's probably it? (note- android phone)

I've had this thing in my garage for over 2 years now, maybe 3 years. I must have gotten it when it first came out. Still working but I only use it about 4 times a year. I tried moving it to a new network today and searched for a manual online and found this thread.

- The tiny little guy does get hot when playing at normal levels.
- the volume control is weird, when you rotate it up the level goes up and then falls. So say you are are volume =90 and you turn clockwise, it goes from say 90-93-89-90-93-91-94 all while turning slowly clockwise. Turning counterclockwise has the same effect but in reverse. As a result you have to turn it a lot to make it go higher or lower. Its kind of funny, just when you think you are there one more click undoes your changes.
- the remote volume control has no continuous mode, you have to press the button one time every time. Lots of clicking from 0 to 90.
- the gain is low, thanks for the tip on the +20db mode.
- the device does show up as a speaker option on Apple Airplay enabled devices. So you can cast via Airplay from Apple ipad mini for example to the i.am.d. One of the few ways to cast internet radio apps to a remote speaker.
- the text on the remote is inaccurate or lets say not precise for some of the buttons, don't have it here so can't go into detail. I think the one that switches inputs is labeled in an interesting manner.
 
Last edited:
#18
nicolak said:
Hello friends. This amplifier is very interesting and functional. But one disadvantage it frustrates me - when connecting via DLNA/Airplay not working volume control. Have you solved this problem?
Click to expand...

I have version 2 and when you use Airplay both the device volume and the amp volume are functional- can use either one or both. Have not tried DLNA. Just confirmed with Pandora, Tunein Radio, Google Play Music and iHeart Radio as well as Apple music player.
 
#19
USB Audio

Just a mention about the USB input and portable devices. The I.am.D works great to decode digital audio via USB with portable Android/ Apple devices as discussed below.

Android- To output digital audio from an Android device- I.am.D. works fine with an "OTG" cable and my Samsung Galaxy Note 3. All audio from spotify/pandora, etc... playing on the phone is digitally output and decoded by the I.am.D. via USB connection. Android device-->OTG cable-->USB cable-->I.am.D.

For Apple IOS- also works fine. Instead of an OTG cable use the camera connect kit. I have Apple part MD821AM/A connected to my ipad mini, then the I.am.D, via USB. This works great, all audio on the iPad is output digitally and decoded via USB on the I.am.D. IOS Device-->camera connect kit-->USB cable--->I.am.D

It has been reported that the USB handshake protocol for IOS devices must indicate <5mA consumption in order to enable USB connectivity. I have 2 stand-alone AC powered DACS that (apparently via error message) exceed this threshold and need to be fooled with a hub. The I.am.D doesn't need to be tricked, so it must report low or no current consumption to connected USB devices. Maybe this is evident from the extracted FW code posted earlier?

FYI- in order to trick an IOS device (if you need to), connect a passive hub to the camera connect kit. The hub (if its the right kind configured from the factory the right way) will report no power consumption to the IOS device and everything **should** work fine. I used this hub.
Plugable USB Hub.

Link for more info- JDS Labs Blog
 
Last edited:
#20
Sorry to resurrect an old thread but I'm looking for a wifi amp like this. This thread hasn't been updated for years can I assume there is now a better Chinese wifi amp like this out there now and thats why this is no longer active?
 
Last edited:
Status
Not open for further replies.
Top Bottom