or Connect
AVS › AVS Forum › Audio › Receivers, Amps, and Processors › Anthem D2/D2v/AVM50/AVM50v/ARC1 tweaking guide
New Posts  All Forums:Forum Nav:

Anthem D2/D2v/AVM50/AVM50v/ARC1 tweaking guide - Page 1356

post #40651 of 42686
Quote:
Originally Posted by Bob Pariseau View Post

The RS232 command set for the Anthems is extensive beyond belief -- WAY more functionality than you can get with the IR commands.

Last I checked, the documentation was included in the download for the ARC V3.0.2 install.
--Bob

Absolutely perfect. This will solve the issue of pre-setting the volume to a pre-determined level. So that you can have "Movie late night" and have the volume automatically go to -40, Movie standard go to -15, and reference go to -10 or 0. That alone is just what's needed. Plus programming the sleep, etc. etc. and there's no guess work as to whether or not it was activated.
post #40652 of 42686
I've had a somewhat minor issue since Day 1 that I haven't been able to solve (and may not be solvable).

My display is a RPTV that I still have to calibrate periodically. To do the RGB convergence I use a standard grid template for my set, which is set for 5% overscan all-around.

The problem I am having is that all sources are cut off a bit on all sides - so for instance I can't always see the text crawl at the bottom of the screen when watching cable, I can't see all of the menu on my Roku, etc.

What I've been doing all along is, after calibrating, using the the display's service menu to shrink the image to 3% overscan. But that affects the calibration negatively, especially the geometry near the corners.

I was wondering if there's something I've overlooked in the video settings of my Anthem AVM50 to work around this, to somehow shrink the picture a bit. Zoom Size, which seems to affect that, is already at the max of 100. I've tinkered with most or all of the other settings (except Custom Resolution) without success.

I thought that 5% overscan was assumed, is that not the case?

Thanks,

- Mark
post #40653 of 42686
Quote:
Originally Posted by Kris Deering View Post

Yes, although for some reason the latest update for iRule killed my feedback. I have to figure out why this weekend. But it worked fine before the update.

Thanks Kris, that's perfect and just what I wanted to confirm since I knew that the iRule used the iTach as their primary mode of IP to IR/RS-232 conversion.
post #40654 of 42686
Quote:
Originally Posted by chileboy View Post

I've had a somewhat minor issue since Day 1 that I haven't been able to solve (and may not be solvable).

My display is a RPTV that I still have to calibrate periodically. To do the RGB convergence I use a standard grid template for my set, which is set for 5% overscan all-around.

The problem I am having is that all sources are cut off a bit on all sides - so for instance I can't always see the text crawl at the bottom of the screen when watching cable, I can't see all of the menu on my Roku, etc.

What I've been doing all along is, after calibrating, using the the display's service menu to shrink the image to 3% overscan. But that affects the calibration negatively, especially the geometry near the corners.

I was wondering if there's something I've overlooked in the video settings of my Anthem AVM50 to work around this, to somehow shrink the picture a bit. Zoom Size, which seems to affect that, is already at the max of 100. I've tinkered with most or all of the other settings (except Custom Resolution) without success.

I thought that 5% overscan was assumed, is that not the case?

Thanks,

- Mark

Actually 0% overscan is what you should be aiming for in the Display. Only activate overscan in the Display if you can't make it work any other way.

0% overscan will let you see the entire image in quality content, and, if you have a 1080p native resolution TV this will also mean you aren't scaling 1080p content (as from Blu-ray discs).

Now some displays can not produce a quality image at the edges when set to 0% overscan, and if that's true of your TV then a compromise setting may be what you need. But if the DISPLAY doesn't need overscan, then the only reason to impose it is to get rid of garbage around the edges of lower quality content such as broadcast TV. And that the AVM 50 can do for you by activating Edges On in the Video Source Adjust menu for each such lower quality Source and picking a pixel value. 6 pixels is typical, and will eliminate 6 pixels from all 4 edges -- scaling the rest of the image to still fill your display.

To directly answer your question, there is no function in the AVM 50 to "shrink" an image ("underscan"). So if you HAVE TO use overscan in your current Display, you'll have to live with the loss of some image off the edges until you can move to a better Display.

NOTE: Some Source devices have their own "underscan" mode. For example, the Zoom function in the OPPO players will do that. But even with those, some discs block the player's ability to implement that function.
--Bob
post #40655 of 42686
Quote:
Originally Posted by Bob Pariseau View Post

Actually 0% overscan is what you should be aiming for in the Display. Only activate overscan in the Display if you can't make it work any other way.

0% overscan will let you see the entire image in quality content, and, if you have a 1080p native resolution TV this will also mean you aren't scaling 1080p content (as from Blu-ray discs).

Now some displays can not produce a quality image at the edges when set to 0% overscan, and if that's true of your TV then a compromise setting may be what you need. But if the DISPLAY doesn't need overscan, then the only reason to impose it is to get rid of garbage around the edges of lower quality content such as broadcast TV. And that the AVM 50 can do for you by activating Edges On in the Video Source Adjust menu for each such lower quality Source and picking a pixel value. 6 pixels is typical, and will eliminate 6 pixels from all 4 edges -- scaling the rest of the image to still fill your display.

To directly answer your question, there is no function in the AVM 50 to "shrink" an image ("underscan"). So if you HAVE TO use overscan in your current Display, you'll have to live with the loss of some image off the edges until you can move to a better Display.

NOTE: Some Source devices have their own "underscan" mode. For example, the Zoom function in the OPPO players will do that. But even with those, some discs block the player's ability to implement that function.
--Bob

Bob, he has an RPTV - analog CRT's bouncing off a mirror
overscan is standard to hide the distortion in the corners
& he is correct, changing the picture size changes the convergence
there is no solution to get to 0%, the best we aimed for while calibrating these was 3%, but it required a lot of work on the convergence

mark
post #40656 of 42686
In the early days of HDTV you would have been safe with 5% but that was an unwritten rule, long since forgotten.

A more advanced processor like the Lumagen would be able to underscan the picture for you, but it costs more than a new TV.
post #40657 of 42686
^3 Well, I can see where this is going, something I already knew, I need a new display! Just a little hard for me to swing right now, plus hard to justify when the calibrated picture on my Toshiba 65HX81 still looks pretty great IMO.I am feeding the Anthem 1080p from my PS3, scaled to 1080i for my display, and Blu-rays look fantastic

But a new display is on the list with an OPPO BDP-103 - and of course a D2v. I have to say the current crop of Panasonic plasmas are tempting, not sure I can wait for OLED.

I had thought overscan was intentional and necessary, otherwise one would end up seeing boom mikes, etc., intended to be offscreen. But maybe I'm really showing my age.

Thanks everyone.

- Mark
post #40658 of 42686
Quote:
Originally Posted by chileboy View Post

I can't always see the text crawl at the bottom of the screen when watching cable, I can't see all of the menu on my Roku, etc.

Are any of these Sports/News channels broadcasting in 720p still? Can you run the Roku at 720p? You can setup new "sources" and disable the upscaling in Anthem (set it to No Scaling in the SCALE OUT menu) and that will give you a smaller image centered in the screen. Under this sub-menu there are custom settings for output size and position but they do not appear to be working correctly (50v latest beta firmware). So it would be OK for brief, non-critical viewing but I wouldn't suggest that on a permanent basis.
Quote:
in the video settings of my Anthem AVM50 to work around this, to somehow shrink the picture a bit. Zoom Size, which seems to affect that, is already at the max of 100.

I just tried these controls and they aren't behaving like I would expect:
1) Horizontal & Vertical Size are simply cropping the image, which is duplication of the CROP INPUT menu, rather than scaling it. Bug?
2) Horizontal & Vertical Position are not doing anything. Bug?
post #40659 of 42686
Quote:
Originally Posted by chileboy View Post

I had thought overscan was intentional and necessary, otherwise one would end up seeing boom mikes, etc., intended to be offscreen. But maybe I'm really showing my age.

In the analog days it was. With NTSC (and PAL) there it was essentially all just a single analog waveform and it carried both the picture and other data (like closed captions), plus analog displays were hard (impossible) to calibrate to perfectly fit the screen so there was overscan, partially by practical engineering and partly by necessity to keep non-picture data off screen. I don't think it was ever to keep picture "goofs" from being seen.
post #40660 of 42686
Quote:
Originally Posted by mkaye View Post

Quote:
Originally Posted by Bob Pariseau View Post

Actually 0% overscan is what you should be aiming for in the Display. Only activate overscan in the Display if you can't make it work any other way.

0% overscan will let you see the entire image in quality content, and, if you have a 1080p native resolution TV this will also mean you aren't scaling 1080p content (as from Blu-ray discs).

Now some displays can not produce a quality image at the edges when set to 0% overscan, and if that's true of your TV then a compromise setting may be what you need. But if the DISPLAY doesn't need overscan, then the only reason to impose it is to get rid of garbage around the edges of lower quality content such as broadcast TV. And that the AVM 50 can do for you by activating Edges On in the Video Source Adjust menu for each such lower quality Source and picking a pixel value. 6 pixels is typical, and will eliminate 6 pixels from all 4 edges -- scaling the rest of the image to still fill your display.

To directly answer your question, there is no function in the AVM 50 to "shrink" an image ("underscan"). So if you HAVE TO use overscan in your current Display, you'll have to live with the loss of some image off the edges until you can move to a better Display.

NOTE: Some Source devices have their own "underscan" mode. For example, the Zoom function in the OPPO players will do that. But even with those, some discs block the player's ability to implement that function.
--Bob

Bob, he has an RPTV - analog CRT's bouncing off a mirror
overscan is standard to hide the distortion in the corners
& he is correct, changing the picture size changes the convergence
there is no solution to get to 0%, the best we aimed for while calibrating these was 3%, but it required a lot of work on the convergence

mark

Yep. As I said, with some TVs you have no choice but to accept Overscan. But that is not a desirable condition -- it's making the best you can with what you've got. That's where the "better Display" comment comes in. biggrin.gif

In any event, there is no "underscan" function offered in the Anthem. And "underscan" applied by the Source device will result in a loss of image quality. (In general, any time you are scaling by small amounts, where the content is almost the same size as the end result, you are going to get artifacts. Basically, visible rounding errors in the scaling.)
--Bob
post #40661 of 42686
Quote:
Originally Posted by AVfile View Post

I just tried these controls and they aren't behaving like I would expect:
1) Horizontal & Vertical Size are simply cropping the image, which is duplication of the CROP INPUT menu, rather than scaling it. Bug?
2) Horizontal & Vertical Position are not doing anything. Bug?

Not bugs. Zoom is a different, and MUCH LOWER QUALITY way of doing the Crop. The only time you should EVER be using the Zoom function is for diagnostic purposes during setup. (Zoom is done before the scaling, which will generate more artifacts.)

As for the Crop, Horizontal and Vertical position shift the Crop, but only if a Crop is actually in effect. I.e., if you are set to extract just a portion of the image, the positioning sets whether that is the center of the image or shifted in some direction. This can be useful, for example, if you open up the Crop on a "scope" film to include subtitles positioned under the film (in a Constant Image Height projection setup for example). But now you have a black bar on top as well. So you shrink the Crop vertically and shift it down so the film is in the top of the Crop (no black bar on top) and then subtitle is still included at the bottom. Examples of this are given in the technical post links in the first post of this thread. Note that Anamorphic vs. Pillar Box scaling can confuse you on this. Again see those tech posts.
--Bob
post #40662 of 42686
Got it, thanks Bob!
post #40663 of 42686
Quote:
Originally Posted by chileboy View Post

^3 Well, I can see where this is going, something I already knew, I need a new display! Just a little hard for me to swing right now, plus hard to justify when the calibrated picture on my Toshiba 65HX81 still looks pretty great IMO.I am feeding the Anthem 1080p from my PS3, scaled to 1080i for my display, and Blu-rays look fantastic

But a new display is on the list with an OPPO BDP-103 - and of course a D2v. I have to say the current crop of Panasonic plasmas are tempting, not sure I can wait for OLED.

I had thought overscan was intentional and necessary, otherwise one would end up seeing boom mikes, etc., intended to be offscreen. But maybe I'm really showing my age.

Thanks everyone.

- Mark


I still have the same TV in my living room, but have a front projector in my theater room.

It is a wonderful TV considering that I think it is almost 14 years old...


Ed
post #40664 of 42686
Hi,

I am owner of Anthem AVM 50V... I want to update with the last firmware so When I try to update... the software said...cannot connect to OKI bootloader... somedoby can help me?

I used the usb adapter include with my Anthem

Thanks

Yvan
Edited by yvan630 - 4/29/13 at 7:53pm
post #40665 of 42686
Quote:
Originally Posted by yvan630 View Post

Hi,

I am owner of Anthem AVM 50V... I want to update with the last firmware so When I try to update... the software said...cannot connect to OKI bootloader... somedoby can help me?

I used the usb adapter include with my Anthem

Thanks

Yvan

Yvan, your first attempt to load the firmware failed in a way that left the hardware unable to accept a new attempt at the firmware install. This is not common, but it happens from time to time.

There is an easy fix, which involves running a piece of software on your Windows PC called the "Flash Eraser" which communicates with the AVM 50v over the serial cable connection you already have set up and forces all the programmable parts of the AVM 50v into the proper state to accept a new firmware install. Then you re-install the firmware to complete the task. An unfortunate side effect is that all of your settings will be lost -- you'll have to reenter them after the firmware install -- but you won't have to send the unit in for service.

Now, the Flash Eraser utility program is on Anthem's password protected download page. Give Anthem Tech Support a call an they'll tell you how to get it and explain the simple instructions for running it. The only trick is to make sure you run the correct Flash Eraser (there are two of them on that page). One of them is for units like the AVM 50v that have video processors, and that's the one you want to download and run. By the way, there's no special installation procedure for the Flash Eraser utility. You just download it to your Windows PC and run it.
--Bob
post #40666 of 42686
Hi Bob,

Thank you for the info...so...On the Anthem's paasword protected download page I saw two Flash Eraser utility program...V0.1 (AVM 20) and V2.3 (AVM20-HD and up)... Can you confirm me that the V2.3 is fine for my AVM 50V?

Yvan
post #40667 of 42686
^ Yep That's the one.

Some folks recommend running it a couple times, but just once should be sufficient.
--Bob
post #40668 of 42686
Thank you Bob...I will try this Flash Eraser this week-end

Yvan
post #40669 of 42686
Quote:
Originally Posted by Bob Pariseau View Post

Not bugs. Zoom is a different, and MUCH LOWER QUALITY way of doing the Crop. The only time you should EVER be using the Zoom function is for diagnostic purposes during setup. (Zoom is done before the scaling, which will generate more artifacts.)

As for the Crop, Horizontal and Vertical position shift the Crop, but only if a Crop is actually in effect. I.e., if you are set to extract just a portion of the image, the positioning sets whether that is the center of the image or shifted in some direction. This can be useful, for example, if you open up the Crop on a "scope" film to include subtitles positioned under the film (in a Constant Image Height projection setup for example). But now you have a black bar on top as well. So you shrink the Crop vertically and shift it down so the film is in the top of the Crop (no black bar on top) and then subtitle is still included at the bottom. Examples of this are given in the technical post links in the first post of this thread. Note that Anamorphic vs. Pillar Box scaling can confuse you on this. Again see those tech posts.
--Bob

Quote:
Originally Posted by AVfile View Post

Got it, thanks Bob!

Yes, that's very helpful Bob - thanks!

- Mark
post #40670 of 42686
Quote:
Originally Posted by chileboy View Post

...the calibrated picture on my Toshiba 65HX81 still looks pretty great IMO....

- Mark
Quote:
Originally Posted by esander3 View Post

I still have the same TV in my living room, but have a front projector in my theater room.

It is a wonderful TV considering that I think it is almost 14 years old...


Ed

That Toshiba was one of the best investments I ever made. I had it professionally calibrated the first few years, then started doing it myself, and when it's dialed-in it looks great. And never had a bit of trouble with it.

I've been streaming Game of Thrones via HBOGo on my Roku (1080p -> Anthem -> 1080i -> HDFury2) and I couldn't be happier. Much better experience than the nearly-new 40" Samsung LED in the bedroom.

- Mark
post #40671 of 42686
Owners-

are you guys liking the Anthem receivers?
post #40672 of 42686
RS-232 issues? Good morning all, I'm trying to get Roomie Remote configured with RS-232 commands with the AVM50/D2 set of commands.

I hooked up my serial connection to the AVM and then have used hyperterm on Windows to see exactly what the Anthem is sending back. I'm continually getting "Invalid Command" on every key except for the '?" and the ';'. The ? properly sends back the current firmware of the unit and ; is the stop command so I get a line break.

I find it very odd that I cannot, for example, Send P1P1 to turn the unit on. As soon as I hit the "P" key, I get invalid command.

I likewise looked at the MRX series serial commands and it has some overlapping commands, such as "power on". But even using the MRX serial config in Roomie to "power on" the AVM doesn't work--even though the serial command is the same?!

I've never had any problems using the serial connection to upload or tweak ARC settings or to upload firmware updates. I find all this behavior odd and I must be doing something wrong or missing something.

I used standard settings to connect, 19200, 8bits, 1, flow control none.

Can anyone give me any insight on this as to what I'm doing wrong with the command syntax?

Here's a sample from the command file... I know commands are not followed by ; in this.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<array>
<dict>
                <key>brand</key>
                <string>Anthem</string>
                <key>cat</key>
                <string>50v-3D</string>
                <key>codes</key>
                <dict>
                        <key>POWER OFF</key><string>P1P0</string>
                        <key>POWER ON</key><string>P1P1</string>

                        <key>VOLUME DOWN</key><string>P1VMD</string>
                        <key>VOLUME UP</key><string>P1VMU</string>
                        <key>MUTE OFF</key><string>P1M0</string>
                        <key>MUTE ON</key><string>P1M1</string>

                        <key>.STATUS</key><string>P1?</string>
                        <key>.VOLUME FORMAT</key><string>1</string>
                        <key>.VOLUME STATUS</key><string>P1VM?</string>
                        <key>.VOLUME SET</key><string>P1V##</string>
                        
                        <key>INPUT 2-CH BAL</key><string>P1S1</string>
                        <key>INPUT 6-CH S/E</key><string>P1S2</string>
                        <key>INPUT AUX</key><string>P1S9</string>
                        <key>INPUT CD</key><string>P1S0</string>
                        <key>INPUT DVD1</key><string>P1S5</string>
                        <key>INPUT DVD2</key><string>P1Sd</string>
                        <key>INPUT DVD3</key><string>P1Se</string>
                        <key>INPUT DVD4</key><string>P1Sf</string>
                        <key>INPUT FM/AM</key><string>P1S4</string>
                        <key>INPUT SAT1</key><string>P1S7</string>
                        <key>INPUT SAT2</key><string>P1Sj</string>
                        <key>INPUT TV1</key><string>P1S6</string>
                        <key>INPUT TV2</key><string>P1Sg</string>
                        <key>INPUT TV3</key><string>P1Sh</string>
                        <key>INPUT TV4</key><string>P1Si</string>
                        <key>INPUT TAPE</key><string>P1S3</string>
                        <key>INPUT VCR</key><string>P1S8</string>
                </dict>
                <key>method</key>
                <string>lineio</string>
                <key>type</key>
                <integer>16</integer>
        </dict>
</array>
</plist>

post #40673 of 42686
^ Sounds like a "lf" is getting sent with the letter when you press a key.

Do you have to press enter when you do a "?" or ";"?
Edited by obie_fl - 5/1/13 at 9:56am
post #40674 of 42686
Quote:
Originally Posted by obie_fl View Post

^ Sounds like a "lf" is getting sent with the letter when you press a key.

Do you have to press enter when you do a "?" or ";"?

Hi Obie,

There are two scenarios here 1) Hyperterminal and 2) Roomie: I'm trying to debug things with hyperterminal first so that I can then convey what's what with Roomie Support. So I'm going to report on what I'm seeing with hyperterminal here.

To your question, no, I don't have to press 'enter'. As soon as I press the key, the command it executed. I didn't notice that so good observation. That raises the question as to why.
post #40675 of 42686
I have it working. I'll be posting a sample serial file if anyone is a Roomie user and interested in testing it out for the D2 and AVM series (20,30,40,50)
post #40676 of 42686
Great what was the secret? I'm getting ready to give the iRule serial connection a shot.
post #40677 of 42686
Quote:
Originally Posted by Thxtheater View Post

I have it working. I'll be posting a sample serial file if anyone is a Roomie user and interested in testing it out for the D2 and AVM series (20,30,40,50)

Were you able to get feedback from the D2V back to Roomie (volume, input, etc.), or is there something the developers need to add on their end?

I created a custom device file for the D2V as well, but I did not have the feedback working.
post #40678 of 42686
Quote:
Originally Posted by mludviksen View Post

Were you able to get feedback from the D2V back to Roomie (volume, input, etc.), or is there something the developers need to add on their end?

Obie and mludviksen,

I created a custom device file for the D2V as well, but I did not have the feedback working.

So here's where things stand:
  1. I'm posting the current serial config file below. I'd appreciate it if you all wouldn't mind cross-testing it. I have it labeled as an AVM50v-3D right now so you can rename it to whatever you want. Just copy the code into a standard txt editor and call the file RoomieCodes.plist as you probably already know.
  2. You may notice a few non-standard items I've included to test various command sets. For example, I have a string of commands to auto-set the volume to a pre-determined level so that it can be used in various contexts and listening environments. I have -42, -35, -25, -20, -15 set as standard volume levels at the press of a button.
  3. In terms of the file, everything seems to work fine except for the SLEEP commands and the display feedback does not (yet) work. For SLEEP, the commands are correct, unless my eye sight has failed me; but the unit won't respond to them. I'd be curious if it works for you. I need to try a direct serial connection from my computer to see if there's any feedback and also do a session capture for roomie and send them the logs.
  4. WIth regards to visual feedback on the iOS app, I'm working with Roomie on that right now. I'm going to go through a specific set of procedures and send over the data to them so that we can get the visual feedback working. This doesn't seem to be too daunting.
  5. I've reached out to Anthem support that I'm working on this and they've been great (as usual). I didn't realize that Anthem had their own data analyzer, so I'll be using that going forward instead of my local communications tools.
  6. What I finally figured out on my end was that the likely cause of the initial problem was the iTach Flex serial unit. I have one of the earliest releases of the iTach Flex serial , so I am not surprised if I find something odd. The unit wouldn't initially work without a firmware upgrade that had just been released that day. Also, when the support folks at Roomie told me that the logs were blank from the iTach, I had a hunch that the iTach was the problem. So, I did like every incredibly smart engineer does. I rebooted it. wink.gif That fixed the issue instantly. I had previously rebooted the unit. I still think I have something anomalous with the iTach Flex because there are some instances where commands won't go through. I'm getting confirmation on the remote side that the command has been successful, but the Anthem doesn't execute. I'll keep an ongoing eye on that and this may be specific to my situation.

mludviksen, if you don't mind helping me out with the Roomie config file, I'd certainly welcome the opportunity to have some peer help.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<array>
        <dict>
                <key>brand</key>
                <string>Anthem</string>
                <key>cat</key>
                <string>50v-3D</string>
                <key>codes</key>
                <dict>
                        <key>.INPUT FORMAT</key><string>6;</string>
                        <key>.INPUT STATUS</key><string> ;</string>
                        <key>.MODE FORMAT</key><string>6;</string>
                        <key>.MODE STATUS</key><string>P1D?;</string>
                        <key>.POWER STATUS</key><string>P1P?;</string>
                        <key>.STATUS</key><string>P1?;</string>
                        <key>.STATUS FORMAT</key><string>6;</string>
                        <key>.VOLUME FORMAT</key><string>6;</string>
                        <key>.VOLUME SET</key><string>P1V##;</string>
                        <key>.VOLUME STATUS</key><string>P1VM?;</string>
                        <key>BACK</key><string>P1Ue;</string>
                        <key>CURSOR DOWN</key><string>P1Ud;</string>
                        <key>CURSOR ENTER</key><string>P1Us;</string>
                        <key>CURSOR LEFT</key><string>P1Ul;</string>
                        <key>CURSOR RIGHT</key><string>P1Ur;</string>
                        <key>CURSOR UP</key><string>P1Uu;</string>
                        <key>DIGIT 0</key><string>P1U0;</string>
                        <key>DIGIT 1</key><string>P1U1;</string>
                        <key>DIGIT 2</key><string>P1U2;</string>
                        <key>DIGIT 3</key><string>P1U3;</string>
                        <key>DIGIT 4</key><string>P1U4;</string>
                        <key>DIGIT 5</key><string>P1U5;</string>
                        <key>DIGIT 6</key><string>P1U6;</string>
                        <key>DIGIT 7</key><string>P1U7;</string>
                        <key>DIGIT 8</key><string>P1U8;</string>
                        <key>DIGIT 9</key><string>P1U9;</string>
                        <key>DYNAMICS RANGE LATE NIGHT</key><string>P1C2;</string>
                        <key>DYNAMICS RANGE NORMAL</key><string>P1C0;</string>
                        <key>DYNAMICS RANGE REDUCED</key><string>P1C1;</string>
                        <key>EXIT</key><string>P1Uq;</string>
                        <key>INPUT 2-CH BAL</key><string>P1S1;</string>
                        <key>INPUT 6-CH S/E</key><string>P1S2;</string>
                        <key>INPUT AUX</key><string>P1S9;</string>
                        <key>INPUT CD</key><string>P1S0;</string>
                        <key>INPUT DVD1</key><string>P1S5;</string>
                        <key>INPUT DVD2</key><string>P1Sd;</string>
                        <key>INPUT DVD3</key><string>P1Se;</string>
                        <key>INPUT DVD4</key><string>P1Sf;</string>
                        <key>INPUT FM/AM</key><string>P1S4;</string>
                        <key>INPUT SAT1</key><string>P1S7;</string>
                        <key>INPUT SAT2</key><string>P1Sj;</string>
                        <key>INPUT TAPE</key><string>P1S3;</string>
                        <key>INPUT TV1</key><string>P1S6;</string>
                        <key>INPUT TV2</key><string>P1Sg;</string>
                        <key>INPUT TV3</key><string>P1Sh;</string>
                        <key>INPUT TV4</key><string>P1Si;</string>
                        <key>INPUT VCR</key><string>P1S8;</string>
                        <key>MODE 2CH ALL CHANNEL MONO</key><string>P1Ec9;</string>
                        <key>MODE 2CH ALL CHANNEL STEREO</key><string>P1Ec8;</string>
                        <key>MODE 2CH ANTHEMLOGIC-CINEMA</key><string>P1Ec2;</string>
                        <key>MODE 2CH ANTHEMLOGIC-MUSIC</key><string>P1Ec1;</string>
                        <key>MODE 2CH MONO</key><string>P1Eca;</string>
                        <key>MODE 2CH MONO ACADEMY</key><string>P1Ecb;</string>
                        <key>MODE 2CH Neo:6-CINEMA</key><string>P1Ec7;</string>
                        <key>MODE 2CH Neo:6-MUSIC</key><string>P1Ec6;</string>
                        <key>MODE 2CH OFF</key><string>P1Ec0;</string>
                        <key>MODE 2CH PROLOGIC</key><string>P1Ec5;</string>
                        <key>MODE 2CH PROLOGIC IIx MOVIE</key><string>P1Ec4;</string>
                        <key>MODE 2CH PROLOGIC IIx MUSIC</key><string>P1Ec3;</string>
                        <key>MODE 2CH PROLOGIC IIx-Game</key><string>P1Ecd;</string>
                        <key>MODE 2CH PROLOGIC IIx-Matrix</key><string>P1Ecc;</string>
                        <key>MODE 2CH THX CINEMA</key><string>P1ETc1;</string>
                        <key>MODE 2CH THX OFF</key><string>P1ETc0;</string>
                        <key>MODE 7.1 THX CINEMA</key><string>P1EWc1;</string>
                        <key>MODE 7.1 THX OFF</key><string>P1EWc0;</string>
                        <key>MODE DD 2.0 ALL CHANNEL MONO</key><string>P1EFc9;</string>
                        <key>MODE DD 2.0 ALL CHANNEL STEREO</key><string>P1EFc8;</string>
                        <key>MODE DD 2.0 ANTHEMLOGIC-CINEMA</key><string>P1EFc2;</string>
                        <key>MODE DD 2.0 ANTHEMLOGIC-MUSIC</key><string>P1EFc1;</string>
                        <key>MODE DD 2.0 MONO</key><string>P1EFca;</string>
                        <key>MODE DD 2.0 MONO Academy</key><string>P1EFcb;</string>
                        <key>MODE DD 2.0 Neo:6-CINEMA</key><string>P1EFc7;</string>
                        <key>MODE DD 2.0 Neo:6-MUSIC</key><string>P1EFc6;</string>
                        <key>MODE DD 2.0 OFF</key><string>P1EFc0;</string>
                        <key>MODE DD 2.0 PROLOGIC</key><string>P1EFc5;</string>
                        <key>MODE DD 2.0 PROLOGIC IIx MOVIE</key><string>P1EFc4;</string>
                        <key>MODE DD 2.0 PROLOGIC IIx MUSIC</key><string>P1EFc3;</string>
                        <key>MODE DD 2.0 PROLOGIC IIx-Game</key><string>P1EFcd;</string>
                        <key>MODE DD 2.0 PROLOGIC IIx-Matrix</key><string>P1EFcc;</string>
                        <key>MODE DD 2.0 THX CINEMA</key><string>P1EUc1;</string>
                        <key>MODE DD 2.0 THX Games</key><string>P1EUc2;</string>
                        <key>MODE DD 2.0 THX OFF</key><string>P1EUc0;</string>
                        <key>MODE DD 5.1 DOLBY DIGITAL EX</key><string>P1EXc9;</string>
                        <key>MODE DD 5.1 Neo:6</key><string>P1EXca;</string>
                        <key>MODE DD 5.1 Neo:6+THX</key><string>P1EXcb;</string>
                        <key>MODE DD 5.1 OFF</key><string>P1EXc0;</string>
                        <key>MODE DD 5.1 PLIIx MOVIE</key><string>P1EXc6;</string>
                        <key>MODE DD 5.1 PLIIx MOVIE+THX</key><string>P1EXc7;</string>
                        <key>MODE DD 5.1 PLIIx MUSIC</key><string>P1EXc8;</string>
                        <key>MODE DD 5.1 THX CINEMA 5.1</key><string>P1EXc1;</string>
                        <key>MODE DD 5.1 THX Games Mode</key><string>P1EXc5;</string>
                        <key>MODE DD 5.1 THX MUSIC MODE</key><string>P1EXc3;</string>
                        <key>MODE DD 5.1 THX SURROUND EX</key><string>P1EXc4;</string>
                        <key>MODE DD 5.1 THX ULTRA2 CINEMA</key><string>P1EXc2;</string>
                        <key>MODE DD EX DOLBY DIGITAL EX</key><string>P1EEc1;</string>
                        <key>MODE DD EX Neo:6</key><string>P1EEc6;</string>
                        <key>MODE DD EX Neo:6+THX</key><string>P1EEc7;</string>
                        <key>MODE DD EX OFF</key><string>P1EEc0;</string>
                        <key>MODE DD EX PLIIx MOVIE</key><string>P1EEc3;</string>
                        <key>MODE DD EX PLIIx MOVIE+THX</key><string>P1EEc4;</string>
                        <key>MODE DD EX PLIIx MUSIC</key><string>P1EEc5;</string>
                        <key>MODE DD EX THX SURROUND EX</key><string>P1EEc2;</string>
                        <key>MODE DTS 5.1 DOLBY DIGITAL EX</key><string>P1EDc9;</string>
                        <key>MODE DTS 5.1 Neo:6</key><string>P1EDca;</string>
                        <key>MODE DTS 5.1 Neo:6+THX</key><string>P1EDc4;</string>
                        <key>MODE DTS 5.1 OFF</key><string>P1EDc0;</string>
                        <key>MODE DTS 5.1 PLIIx MOVIE</key><string>P1EDc6;</string>
                        <key>MODE DTS 5.1 PLIIx MOVIE+THX</key><string>P1EDc7;</string>
                        <key>MODE DTS 5.1 PLIIx MUSIC</key><string>P1EDc8;</string>
                        <key>MODE DTS 5.1 THX CINEMA 5.1</key><string>P1EDc1;</string>
                        <key>MODE DTS 5.1 THX GAME MODE</key><string>P1EDc5;</string>
                        <key>MODE DTS 5.1 THX MUSIC MODE</key><string>P1EDc3;</string>
                        <key>MODE DTS 5.1 THX ULTRA2 CINEMA</key><string>P1EDc2;</string>
                        <key>MUTE OFF</key><string>P1M0;</string>
                        <key>MUTE ON</key><string>P1M1;</string>
                        <key>POWER OFF</key><string>P1P0;</string>
                        <key>POWER ON</key><string>P1P1;</string>
                        <key>SET VOLUME -15</key><string>P1VM-15.00;</string>
                        <key>SET VOLUME -20</key><string>P1VM-20.00;</string>
                        <key>SET VOLUME -25</key><string>P1VM-25.00;</string>
                        <key>SET VOLUME -35</key><string>P1VM-35.00;</string>
                        <key>SET VOLUME -42</key><string>P1VM-42.00;</string>
                        <key>SETUP</key><string>P1Uo;</string>
                        <key>SLEEP 30</key><string>P1z1;</string>
                        <key>SLEEP 60</key><string>P1z2;</string>
                        <key>SLEEP 90</key><string>P1z3;</string>
                        <key>SLEEP OFF</key><string>P1z0;</string>
                        <key>STATUS</key><string>P1s;</string>
                        <key>VOLUME DOWN</key><string>P1VMD;</string>
                        <key>VOLUME UP</key><string>P1VMU;</string>
                </dict>
                <key>method</key>
                <string>lineio</string>
                <key>type</key>
                <integer>16</integer>
        </dict>
</array>
</plist>


Edited by Thxtheater - 5/2/13 at 12:08pm
post #40679 of 42686
Thxtheater,

Thanks for posting your work. I noticed that you use a semi-colon after each command - I did not do that in my file, but it works fine. I also noticed that several of your keys that start with a '.' have a string of '6;' - what does that do? I posted my original attempt on the Roomie Support Forums and I noticed that you posted on that thread too - hopefully you had a chance to see my file or the updated file that the Roomie guys tweaked and cleaned up with the correct command names.

As far as the feedback goes for volume, etc., I'm pretty sure that the Roomie developers need to add a format that is specific to the Anthem D2V. They already have one for the MRX series, but the D2V is slightly different so we can't use that one. It sure would be nice if they took what we started and finished it off and made it an officially supported receiver!

I'm afraid I can't dive too deeply into the file you posted tonight, but I hope to spend some time on it this weekend.


Mark
post #40680 of 42686
Quote:
Originally Posted by mludviksen View Post

Thxtheater,

Thanks for posting your work. I noticed that you use a semi-colon after each command - I did not do that in my file, but it works fine. I also noticed that several of your keys that start with a '.' have a string of '6;' - what does that do? I posted my original attempt on the Roomie Support Forums and I noticed that you posted on that thread too - hopefully you had a chance to see my file or the updated file that the Roomie guys tweaked and cleaned up with the correct command names.

As far as the feedback goes for volume, etc., I'm pretty sure that the Roomie developers need to add a format that is specific to the Anthem D2V. They already have one for the MRX series, but the D2V is slightly different so we can't use that one. It sure would be nice if they took what we started and finished it off and made it an officially supported receiver!

I'm afraid I can't dive too deeply into the file you posted tonight, but I hope to spend some time on it this weekend.


Mark

No worries! The ; may indeed be redundant. Now that I determined that the iTach was the problem I can remove the ; and see if it still works. The reason why I included it was that the roomie folks sent me over the MRX serial file, which is in binary, and it had the end of line marker. Since I was having no luck getting the commands to work, I added the semi-colon. Good to know it works without it. Because the serial command set is identical between the D2v and the 50v (and older AVM models), my assumption is that the feedback should therefore work across all the AVM and D2 models as well. The intent here is to certainly finish off the file with Roomie support's guidance and then submit it to them to have the D2v and AVM series supported with serial connectivity. The serial command base is extensive and very flexible; and with the ability to have IP to serial adapters that solves the lack of IP-ready interfacing on those models with a mature and proven command set.

Now, the reason for the '6' is because in the Roomie DDK, the number 6 corresponds to the Anthem-formatted volume response. You'll notice that '1' will give you the raw display back from any unit while the number '6' is specifically for Anthem. Don't take too much stock in my .INPUT FORMAT or .MODE FORMAT, etc. My assumption was that the DDK was written like some language texts in such a way to convey concepts as opposed to explaining every single occurrence. Therefore, if you extrapolate out the formatting for the volume status feedback you should logically use the same structure for other feedback elements you want to get from the Anthem. My goal is to try and run a quick serial test and grab off the AVM50v later this weekend or Monday and then send that grab back to Roomie. Getting the serial interface working with visual feedback on the Roomie platform is a pretty big deal as I have Roomie deployed in several locations and in some instances, it's really critical to get visual feedback without having direct access to the unit.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Receivers, Amps, and Processors
AVS › AVS Forum › Audio › Receivers, Amps, and Processors › Anthem D2/D2v/AVM50/AVM50v/ARC1 tweaking guide