Elkrms + two Russound controllers problems!!

dykwok

Member
Hi,
I have two Russound controllers and just installed Elkrms.
The capability of Elkrms allows for 6 controllers and 36 zones.
When I connected 2 Russound controllers with 12 zones using ip232,
only the first 9 zones work in elkrms.
Whenever I clicked on the last 3 zones (out of the 12), it will always
say

"Unhandled exception has occurred in your application. If you click
Continue, the application will ignore this error and attempt to continue.
If you click Quit, the application will close immediately.

Arithmetic operation resulted in an overflow."

I am hoping that somebody can tell me if this is Elkrms or my setup.
There was a similar message in Elk's discussion site, but no reply from
Elk's technical support so far.

Thanks.

There is also a detail button that reveals the following message:
-----------------------------------------------------------------------------------------------------------------------------------------
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.OverflowException: Arithmetic operation resulted in an overflow.
at ElkRM.cRUSSOUND.Get_ZoneMeta(Int32 ZoneNum, Int32 Source)
at ElkRM.cRUSSOUND.AUDIOSELECT_Click(Object sender, EventArgs e)
at ElkRM.picTRANSPARENT.OnMouseUp(MouseEventArgs e)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
ElkRM
Assembly Version: 2.0.0.0
Win32 Version: 2.0.0.0
CodeBase: file:///C:/Program%20Files/ElkRM/ElkRM.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
 
Sounds like a software issue to me!

Contact Elk Technical 800-797-9355 and you will be routed to the proper culprit. ;)
 
Thanks Spanky for your quick reply. I was busy the last few days and
didn't have time to call the tech up.

I am hoping they will answer my phone tomorrow. If not, it has to be Monday.
Thanks and I will post again. :hesaid:

Sounds like a software issue to me!

Contact Elk Technical 800-797-9355 and you will be routed to the proper culprit. :)
 
Hi Spanky,

Just want to update what I found.

I added another Russound controller (Now, a total of 3)
and making it a total of 6 + 6 + 2 (extra) zones = 14 zones.
I am consistently having problems with only zone 10, 11 and 12
as I described in my first post.
Now, after connecting my No.3 controller (I only put in 2 zones here in No.3),
these new two zones (zones 13 and 14) work like a charm using elkrms.
Yet.... zones 10, 11, 12 remain having problem as described earlier.
It looks like that it is something specific to these zones and perhaps
a bug?

I will try to call the tech next week and see what they say.
Any insight before that?

Thanks.

The person you need to talk with will be in Monday.
 
Since I have the the 3rd controller, I decided to add more zones to
the Elk rms. Now, zone 17 and 18 are having the same problem.

Then, I thought if this is a bug with the software, there is nothing that
requires a prior the physical controller.

I then started adding more zones to the other controllers (5 and 6) as dummies.
This is what I found consistently:

Controller 1: no problem with all zones.
Controller 2: zones 4, 5, and 6 are not working.
Controller 3: zones 5 and 6 are not working.
Controller 4: zones 4, 5 and 6 are not working.
Controller 5: zones 5 and 6 are not working.
Controller 6: zones 4, 5 and 6 are not working.

It does appear to me that it might be index in the loop of the
software that is causing a problem consistently.
4, 5 and 6... then... 5 and 6... this pattern then repeats itself.



Hi Spanky,

Just want to update what I found.

I added another Russound controller (Now, a total of 3)
and making it a total of 6 + 6 + 2 (extra) zones = 14 zones.
I am consistently having problems with only zone 10, 11 and 12
as I described in my first post.
Now, after connecting my No.3 controller (I only put in 2 zones here in No.3),
these new two zones (zones 13 and 14) work like a charm using elkrms.
Yet.... zones 10, 11, 12 remain having problem as described earlier.
It looks like that it is something specific to these zones and perhaps
a bug?

I will try to call the tech next week and see what they say.
Any insight before that?

Thanks.

The person you need to talk with will be in Monday.
 
Ok. I just called the Elk tech support.
Apparently, they said they have nothing to say and is currently investigating
the problems that have been reported here.
The person that I was talking to was by the name "Brad".

One of the reasons why I purchased ElkRms is due to the fact that
they allow control of 3 of my Russound Controllers, but now it only works partially <_<

I really hope that they can have a resolution soon and anybody who
has Elkrms can try this out yourself as it does not need the REAL controller
to replicate the problems that I am reporting here.

Thanks.
 
If you are only using zones 13 and 14 on the 3rd controller perhaps you can reallocate zones 10,11,12 to the 3rd controller until the problem is fixed. At the very minimum it will take away the urgency of a fix/resolution, and hopefully in the long run the problem will be solved.
 
Thanks for your suggestion and I thought about that too.

The problem is that I have the full 17 zones already allocated in my 3 russound controllers
and all 17 zones working (and not from ElkRMS). I had only 14 before and now a full working 17 zones.

The last one (zone 18) is going to be that in the Garage and it will have to after the
installation and dry wall. <_<

Thanks.



If you are only using zones 13 and 14 on the 3rd controller perhaps you can reallocate zones 10,11,12 to the 3rd controller until the problem is fixed. At the very minimum it will take away the urgency of a fix/resolution, and hopefully in the long run the problem will be solved.
 
Clearwater,
The ELKRMS guru is looking into the issue. You may have to be the field tester because we only have one Russound CAV6.6 to work with.
 
Hi Spanky,

No problem and I would be very happy to test it out if I can be of any help.
I actually have 4 Russound controllers but this last one is
not producing perfect sound. I can even use this No. 4 to test out
if need be.

Thanks.

Clearwater,
The ELKRMS guru is looking into the issue. You may have to be the field tester because we only have one Russound CAV6.6 to work with.
 
Clearwater,
The problem on multiple Russound Controllers has been found and fixed. Software retesting is underway. It was an indexing problem with multiple controllers.

Thanks for the headsup. You will get a beta copy ASAP.
 
Hi Spanky,

That's great. You guys are amazingly fast and I enjoy working
with you all.
I look forward to the new beta update.

Great job and it is worth spending every single penny on the Elk. :)

Thanks.

Clearwater,
The problem on multiple Russound Controllers has been found and fixed. Software retesting is underway. It was an indexing problem with multiple controllers.

Thanks for the headsup. You will get a beta copy ASAP.
 
Back
Top