russound and mcontrol

[heightsaggie]

I am trying to figure out simple controls of my cav 6.6. I don't know xml and am trying to just go by the template. what am I doing wrong? any help would be greatly appreciated. This won't even show up in my editor when restarting the service.

[JNBrook]

Did you install the generic driver?

[heightsaggie]

yes sir. i installed it. and when i put the example xml that is the denon in the server folder, it shows up fine in the editor....am i using an old version? someone pointed me to this generic driver, but when i download the newest driver pack it looks like there is a different version in there. and the generic xml file in this new file pack references a EA.GenericDriver.dll that isn't even in the pack.

[heightsaggie]

ok i was using an old driver pack. there is a lot of old version stuff on the forums. but even now, something is wrong where the xml file i created above still isnt' showing up. i put all the sample xml's for generic driver in the plugins and they are showing up fine. i now see the ea.genericdriver.dll file.

[ddl]

I am having the same problem. yesterday I spent hours trying solutions offered via this forum but still have not been able to use my newly created russound xml file.

Can someone please help with this? I very much would like to communicate with my equipment via rs 232.

Furthermore, I have grown extremely frustrated with the Mcontrol product and the lack of support. This is the last draw for me. If I can't get this to work as it should, then I will be abandoning Mcontrol for good.

[heightsaggie]

this is my latest one...still nothing. I figure I will keep posting stuff until i get an answer. I am sure it is something simple that someone can guide me to the answer quick....

[heightsaggie]

Furthermore, I have grown extremely frustrated with the Mcontrol product and the lack of support. This is the last draw for me. If I can't get this to work as it should, then I will be abandoning Mcontrol for good.

I am a little concerned about this also. Can an administrator please answer why this is a problem? This product was advertised on the microsoft website, so I assumed it had a modern day support system. I know the company wants people to post on the forums, but i have found a number of threads that are never answered. There is also a bunch of posts that are completely irrelevant, as newer versions are out. it can be very confusing. If the forum is where we are supposed to go for help and we aren't getting any help, it seems like there is a flaw in the business model. I wonder if microsoft knows they are endorsing a product that is run in this manner???

[MitchSchaft]

It's just a few guys that run the company. They've been busy doing other projects this year and are supposedly getting back to mcontrol next month.

[heightsaggie]

mitch,

Perhaps you could provide some guidance on our problem then? i see you are pretty good at solving problems from other forums I have been reading. I am not being lazy, i am trying to learn this, and if you provide some good insight, then perhaps i might be able to pass this on to others with similar issues.

[MitchSchaft]

Nah, I don't even know what russound is :D.

[heightsaggie]

i don't think it matters what russound is. it is just a black box that receives commands via rs-232 in hex format, and then takes it from there. i think my problem is on the mcontrol side, and my xml not being in proper format...for opening connection, and showing up in the editor.

[ddl]

Mcontrol support is very, very bad. I am quite dissappointed at their response time. I still have not gotten an answer from them on my xml issue stated above. That said, I am glad to report that I am able to communicate with my Russound equipment via rs 232 using Netremote and Girder.

[brad77]

i don't think it matters what russound is. it is just a black box that receives commands via rs-232 in hex format, and then takes it from there. i think my problem is on the mcontrol side, and my xml not being in proper format...for opening connection, and showing up in the editor.

You're right, heightsaggie. Your XML is malformed. Check it out:

<ModuleCommands>
<group name="EAGA_Sample">
<command name="ZONE1_POWER" label="Power-Z1" />
<component label="ON/OFF" type="LIST" displayList="On|Off" values="\0xF000007F0000710502020000F12300010000000113F7|\0 xF000007F0000710502020000F12300000000000112F7" />
</command>

The bad code is highlighted in red. By putting a "/>" rather than just a ">" in your opening command tag, you are closing it. If you have an opening and closing tag, they need to look like this:

<myname>Brad</myname>

The forward slash is a shorthand way to close the tag without explicitly typing out the closing tag. The following are functionally equivalent:

<myname value="Brad"></myname>

<myname value="Brad" />

See attached for the corrected code.

Please note that I only corrected it in structure. I have no idea if your commands are any good, but at least your doc will parse.

A good way to check if your XML code is good is to open the file in IE (or any other browser). If it fails to parse it should let you know why.

Good luck!

[heightsaggie]

thank you very much brad. these types of tips will help me get to my goal. I will let you know how it works out. There is someone out there with constructive help....i was beginning to wonder. I will try this when I get home.

[heightsaggie]

still not showing up...

[jeffmikan]

Open the XML in IE. This is the easiest way to make sure all the sections are closed properly.

[heightsaggie]

Open the XML in IE. This is the easiest way to make sure all the sections are closed properly.

I have done that. it seems everything is close properly now. what does this line mean?
<mparam name="CommandEndWith" value="CR" note="CR|LF|CRLF|actual characters; default: ASCII[CR], BINARY''" />

I am working with hex numbers, does this not jive with that?
also, the hex values i have to send look like this:
F0 00 00 7F 00 00 71 05 02 02 00 00 F1 23 00 01 00 00 00 01 13 F7

this is how i was told by someone to put them in the xml:
\0xF000007F0000710502020000F12300010000000113F7
is this proper, or does every one have to have a \0x in front of them like this:
\0xF0\0x00\0x00....

[brad77]

what does this line mean?
<mparam name="CommandEndWith" value="CR" note="CR|LF|CRLF|actual characters; default: ASCII[CR], BINARY''" />

This is the character used to end commands. You're communicating via RS-232, right? Different hardware platforms treat end-of-line characters differently. This allows you to specify which one works for your equipment.

CR = Carriage Return
LF = Line Feed
CRLF = Carriage Return-Line Feed
actual characters = Something other than CR, LF or CRLF

Find more info here: http://en.wikipedia.org/wiki/End_of_line

You may need to experiment to find out what works. Better yet, check the specifications in whatever documentation you have for your equipment.

As for the hex commands, you may need to experiment there as well. Try doing without the slash. You can also try adding the prefix, but I don't believe that is correct. Forgive me, but I'd have to do the same as I'm recommending to you to have a definitive answer.

[insitetech@gmail.com]

Casa tunes is a great Software package that interfaces well w/mControl:)
I have used several times

[heightsaggie]

are you sure about this? I have casatunes. I have tried to integrate with mcontrol and when i emailed support about it not working, they told me the driver was incomplete, doesn't work, and not on the list to be worked on. Are you sure you have used this and it is working? This whole thing is starting to really get me mad. i am chasing my tail around and getting nowhere....

If you have done this, and it does work, then do tell please...

in fact, I waited until embedded automation people told me that it worked the first time to buy the casatunes software ($350.00). and it was only after i dropped the coin that i was told about this.

[heightsaggie]

has anyone had luck with casatunes integration. i came across the casatunes serial interface on casatunes. does this have to be enabled and then the casatunes integration works on mcontrol?

[heightsaggie]

here is the latest version of my xml. i noticed that i had eaga_russound for the command button group, and down below under the module commands i had eaga_serial. still not working though. i will keep at it, until someone lets me know what i am doing wrong. hopefully this post will help others when they are trying to use the generic adapter.

[heightsaggie]

I guess i will keep talking to myself. I finally got the russound to show up on the editor (took out the fields group section). one step at a time. now onto the commands i am trying to send them and nothing is happening.
<mparam name="CommandType" value="BINARY" note="[ASCII]|BINARY" />

i have binary checked. but shouldn't there be a value for hex if hex is what i am sending? From what i see there is a difference between binary and hex.

[brad77]

i have binary checked. but shouldn't there be a value for hex if hex is what i am sending? From what i see there is a difference between binary and hex.

I would bet that you want to use ASCII. ASCII refers to the fact that you're sending plain text to the device. If that is strictly adhered to in the driver, you are then limited to 128 characters. More that likely, you are limited to the 94 printable characters.

ASCII is basically the letters, numbers and characters you can generate on a standard keyboard (there may be some exceptions). Additionally, you can use ASCII characters to represent hexadecimal numbers.

Binary isn't generally human readable. They are just ones and zeros. They are sometimes represented as hex codes, binary numbers, decimals or ASCII characters, which may be where some of your confusion is coming from. Don't confuse the representation of the data from the data itself.

Typically it's a pain to use binary data in XML. XML is text based, so you need to either put it into a CDATA block or encode it into a text-based format that your XML encoding supports (which in your case is UTF-8).

Hope that helps. The short answer: try ASCII instead.

[heightsaggie]

unfortunately the device i am sending to is reading HEX.

F0 00 00 7F 00 00 71 05 02 02 00 00 F1 23 00 01 00 00 00 01 13 F7

i can't send it in ascii...

[brad77]

i can't send it in ascii...

Again, I think that you're confusing the representation of the data with the data itself. You simply typed out a text string of numbers and letters meant to represent hex codes. The text itself is ASCII text.

[JBG]

I have gone through and fixed the XML driver for Russound, it is working now. I have only added the main functions(on/off, Volume, Source), this XML have 4 sources per zone, anyone needing more the 4 source to a zone can add the commands.

[heightsaggie]

are you sure you posted the working one? this one that is posted has all six zones, and it doesn't work on my machine.

[JBG]

are you sure you posted the working one? this one that is posted has all six zones, and it doesn't work on my machine.

Check your port settings and cable (should be one to one pin mapping), because one of the other user confirmed that it worked for him.

[ddl]

JB

The russound xml file works just fine. I tried it and works great. Thanks much.

[brad77]

Huh. It looks like it uses binary after all. Nice work, JBG.

[heightsaggie]

2009-09-14 19:20:00.840 00:19:01.7741143 (010) M0 [Music] macro action: [Russound ZONE2_POWER \0XF0\0X00\0X00\0X7F\0X00\0X01\0X71\0X05\0X02\0X02 \0X00\0X00\0XF1\0X23\0X00\0X00\0X00\0X01\0X00\0X01 \0X14\0XF7] (ID=2A67A080)
2009-09-14 19:20:00.840 00:19:01.7742260 (010) E0 [EAGENERICADAPTER] driver is not loaded and could not find an alternate one.
2009-09-14 19:20:01.340 00:19:02.2738800 (010) M0 [Music] macro stopped (total execution time=00:00:00.4990000) (ID=2A67A080)

I have loaded everything in from the 3391 build into my server plugins file. does the above error mean that it can't find this eagenericadapter file? both folders are: mcontrol v2.1 build 3391 - driver pack and v2.1 build 3391 - generic driver....what am i missing?

[ddl]

Are you positively sure that you are using the latest file from JB? Looking at your command, I think your missing some characters. Not sure what it is called but I don't see the "|" character.

[JBG]

heightsaggie,

Make sure that you have EA.DriverBaseGeneric.dll and drv_EAGenericDriver.xml ib the mControl\server\plugins directory, before you can use the russound driver mdl_EAGenericDriverSerial-Russound.xml. additionally the generic driver also need to be enabled in the mControl service manager, once you have done this the n restart the mControl service, wait for all of the drivers to load.

test the Russound driver first by sending manual commands using mControl Editor before you go on with using it in macros.

[heightsaggie]

all of the above are done...still not working..same error.

I looked at the generic driver xml that you speak of in the post and it says a version that is 1.32.1...are you using a differnt version of the generic driver, because i noticed a reference of 1.1 in the xml you posted. do I have a newer version and this is why it is not working?



<?xml version="1.0" encoding="utf-8" ?>
- <mServerDb vendor="EA Generic Driver" version="1.32.1">
- <Protocols>


I also looked at the generic driver dll and it is even a different version;2.1.3391.3.

[heightsaggie]

heightsaggie,


test the Russound driver first by sending manual commands using mControl Editor before you go on with using it in macros.

and i don't see a way to send manual commands. with this russound driver once it is selected and the com port is checked, it doens't have a way to send commands, the only way to trigger is macros. unless i am just completely clueless.

[JBG]

and i don't see a way to send manual commands. with this russound driver once it is selected and the com port is checked, it doens't have a way to send commands, the only way to trigger is macros. unless i am just completely clueless.

Just have a look at this image I attached, which shows the control buttons to send commands, you pick the function and its associated commands from the pull down and fire them out by pressing the apply button.
I also show the device configuration dialog in the image, the device name is whatever you want to call it, but the Adaptor and device module should be as shown. And make sure the com port which connects the PC to Russound is listed.

[heightsaggie]

no wonder i can't send manual commands. see attached.

[heightsaggie]

found this in my log on restart of the manager.

2009-09-17 18:01:19.787 00:00:00.1972909 (004) I0 Loading objects from "C:\Program Files (x86)\Embedded Automation\mControl\server\plugins\drv_EAGenericDr iver.xml" ...
2009-09-17 18:01:19.787 00:00:00.1972999 (004) I0 mServer plug-in drivers definitions file vendor: "EA Generic Driver", version=1.32.1
2009-09-17 18:01:19.787 00:00:00.1974549 (004) E0 % Can not find the driver assembly [C:\Program Files (x86)\Embedded Automation\mControl\server\plugins\EA.GenericDrive r.dll] for adapter [EAGENERICADAPTER]. Loaded NullDriver instead.


does this have something to do with it?

[heightsaggie]

I am starting to think the generic adapter doens't work with 64 bit? has anyone gotten this to work on 64 bit?

[JBG]

From what you are say above, it looks like you copy the drv_EAGenericDriver.xml but not the EA.GenericDriver.dll file in the plugins directory.

[heightsaggie]

there is no file by that name in the download located here:
http://www.embeddedautomation.com/EAHAmControl.htm

under the driver packs.

did they forget to include this fie? Please tell me that is not the case. i have wasted a TON of hours on this.

[heightsaggie]

i found the file in an older download of the pack from 5-15-08. i put it in the directory and now this error

Loading objects from "C:\Program Files (x86)\Embedded Automation\mControl\server\plugins\drv_EAGenericDr iver.xml" ...
2009-09-18 11:05:27.299 00:00:00.1875704 (004) I0 mServer plug-in drivers definitions file vendor: "EA Generic Driver", version=1.32.1
2009-09-18 11:05:27.324 00:00:00.2119112 (004) X0 Error loading the driver [EmbeddedAutomation.GenericDriver.GenericDriverMana ger] for adapter [EAGENERICADAPTER] from [C:\Program Files (x86)\Embedded Automation\mControl\server\plugins\EA.GenericDrive r.dll].
2009-09-18 11:05:27.324 00:00:00.2119112 (004) X1 System.IO.FileNotFoundException: Could not load file or assembly 'EADriverBaseGeneric, Version=2.1.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
2009-09-18 11:05:27.324 00:00:00.2119112 (004) X2 File name: 'EADriverBaseGeneric, Version=2.1.0.0, Culture=neutral, PublicKeyToken=null'
2009-09-18 11:05:27.324 00:00:00.2119112 (004) X3 at System.Reflection.Assembly._GetType(String name, Boolean throwOnError, Boolean ignoreCase)
2009-09-18 11:05:27.324 00:00:00.2119112 (004) X4 at System.Activator.CreateInstanceFrom(String assemblyFile, String typeName, Boolean ignoreCase, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, Evidence securityInfo)
2009-09-18 11:05:27.324 00:00:00.2119112 (004) X5 at System.Activator.CreateInstanceFrom(String assemblyFile, String typeName, Object[] activationAttributes)
2009-09-18 11:05:27.324 00:00:00.2119112 (004) X6 at System.AppDomain.CreateInstanceFrom(String assemblyFile, String typeName)
2009-09-18 11:05:27.324 00:00:00.2119112 (004) X7 at System.AppDomain.CreateInstanceFromAndUnwrap(Strin g assemblyName, String typeName)
2009-09-18 11:05:27.324 00:00:00.2119112 (004) X8 at EmbeddedAutomation.mServer.Lib.NullAdapterDriver.L oadFromXml(XPathNavigator xnav, String pluginsPath)
2009-09-18 11:05:27.324 00:00:00.2119112 (004) X9 WRN: Assembly binding logging is turned OFF.
2009-09-18 11:05:27.324 00:00:00.2119112 (004) X: To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2009-09-18 11:05:27.324 00:00:00.2119112 (004) X; Note: There is some performance penalty associated with assembly bind failure logging.
2009-09-18 11:05:27.324 00:00:00.2119112 (004) X< To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

[heightsaggie]

alright i stripped everything down, and started over and it works now. thanks to JB for his help. I finally think i can close this chapter in my home control book. when i downloaded the driver pack files for the nth time after the xml file was fixed by JB i downloaded the additional drivers and not the actual driver pack...nice one!