Device Manager - No devices

[Mortie]

Hi,

I've tried on a couple of occations to get the device manager to work, but no luck.

I have the latest G5 build, and the latest RussoundRNET plugin, but I'm not able to get it to show in the device manager list.
If I do a DeviceManager:Print() I get nothing.

Is there anything I'm missing in setting this up?
My Russound plugin is working like a charm, just not in the device manager :-)

Regards,
Morten

[Ron]

Most likely the Russound is built against the latest DM sources which you do not have I'll try to get a new build of G5 in your hands asap.

[Mortie]

Exellent, can hardly wait :-)

Thank's Ron!

//Morten

[Mortie]

Hi,

I did a clean installation of the 504 build, reinstalled the Russound RNET plugin. Then I get this trace in the LUA console:

Welcome to Promixis Girder 5.0!
Error in subscriber callback
...Promixis\Girder5\/plugins/treescript/Russound UI.lua:31: attempt to index a boolean value
stack traceback:
...les\Promixis\Girder5\luascript\Classes/Publisher.lua:28: in function <...les\Promixis\Girder5\luascript\Classes/Publisher.lua:25>
...Promixis\Girder5\/plugins/treescript/Russound UI.lua:31: in function <...Promixis\Girder5\/plugins/treescript/Russound UI.lua:26>
...les\Promixis\Girder5\luascript\Classes/Publisher.lua:37: in function <...les\Promixis\Girder5\luascript\Classes/Publisher.lua:36>
[C]: in function `xpcall'
...les\Promixis\Girder5\luascript\Classes/Publisher.lua:40: in function <...les\Promixis\Girder5\luascript\Classes/Publisher.lua:32>
...les\Promixis\Girder5\luascript\Classes/Publisher.lua:151: in function `SendEvent'
...les\Promixis\Girder5\luascript\Classes/Publisher.lua:138: in function `Event'
.\Russound_RNET.lua:1518: in function `Event'
.\Russound_RNET.lua:1127: in function `SetSystemStatus'
.\Russound_RNET.lua:998: in function <.\Russound_RNET.lua:981>
(tail call): ?
...er5\luascript\Classes/DelayedExecutionDispatcher.lua:40: in function <...er5\luascript\Classes/DelayedExecutionDispatcher.lua:38>
Error in subscriber callback
...Promixis\Girder5\/plugins/treescript/Russound UI.lua:31: attempt to index a boolean value
stack traceback:
...les\Promixis\Girder5\luascript\Classes/Publisher.lua:28: in function <...les\Promixis\Girder5\luascript\Classes/Publisher.lua:25>
...Promixis\Girder5\/plugins/treescript/Russound UI.lua:31: in function <...Promixis\Girder5\/plugins/treescript/Russound UI.lua:26>
...les\Promixis\Girder5\luascript\Classes/Publisher.lua:37: in function <...les\Promixis\Girder5\luascript\Classes/Publisher.lua:36>
[C]: in function `xpcall'
...les\Promixis\Girder5\luascript\Classes/Publisher.lua:40: in function <...les\Promixis\Girder5\luascript\Classes/Publisher.lua:32>
...les\Promixis\Girder5\luascript\Classes/Publisher.lua:151: in function `SendEvent'
...les\Promixis\Girder5\luascript\Classes/Publisher.lua:138: in function `Event'
.\Russound_RNET.lua:1518: in function `Event'
.\Russound_RNET.lua:1127: in function `SetSystemStatus'
.\Russound_RNET.lua:1215: in function <.\Russound_RNET.lua:1200>
Error in subscriber callback
...Promixis\Girder5\/plugins/treescript/Russound UI.lua:31: attempt to index a boolean value
stack traceback:
...les\Promixis\Girder5\luascript\Classes/Publisher.lua:28: in function <...les\Promixis\Girder5\luascript\Classes/Publisher.lua:25>
...Promixis\Girder5\/plugins/treescript/Russound UI.lua:31: in function <...Promixis\Girder5\/plugins/treescript/Russound UI.lua:26>
...les\Promixis\Girder5\luascript\Classes/Publisher.lua:37: in function <...les\Promixis\Girder5\luascript\Classes/Publisher.lua:36>
[C]: in function `xpcall'
...les\Promixis\Girder5\luascript\Classes/Publisher.lua:40: in function <...les\Promixis\Girder5\luascript\Classes/Publisher.lua:32>
...les\Promixis\Girder5\luascript\Classes/Publisher.lua:151: in function `SendEvent'
...les\Promixis\Girder5\luascript\Classes/Publisher.lua:138: in function `Event'
.\Russound_RNET.lua:1518: in function `Event'
.\Russound_RNET.lua:1127: in function `SetSystemStatus'
.\Russound_RNET.lua:998: in function <.\Russound_RNET.lua:981>
(tail call): ?
...er5\luascript\Classes/DelayedExecutionDispatcher.lua:40: in function <...er5\luascript\Classes/DelayedExecutionDispatcher.lua:38>
Error in subscriber callback
...Promixis\Girder5\/plugins/treescript/Russound UI.lua:31: attempt to index a boolean value
stack traceback:
...les\Promixis\Girder5\luascript\Classes/Publisher.lua:28: in function <...les\Promixis\Girder5\luascript\Classes/Publisher.lua:25>
...Promixis\Girder5\/plugins/treescript/Russound UI.lua:31: in function <...Promixis\Girder5\/plugins/treescript/Russound UI.lua:26>
...les\Promixis\Girder5\luascript\Classes/Publisher.lua:37: in function <...les\Promixis\Girder5\luascript\Classes/Publisher.lua:36>
[C]: in function `xpcall'
...les\Promixis\Girder5\luascript\Classes/Publisher.lua:40: in function <...les\Promixis\Girder5\luascript\Classes/Publisher.lua:32>
...les\Promixis\Girder5\luascript\Classes/Publisher.lua:151: in function `SendEvent'
...les\Promixis\Girder5\luascript\Classes/Publisher.lua:138: in function `Event'
.\Russound_RNET.lua:1518: in function `Event'
.\Russound_RNET.lua:1127: in function `SetSystemStatus'
.\Russound_RNET.lua:1215: in function <.\Russound_RNET.lua:1200>
Error in subscriber callback
...Promixis\Girder5\/plugins/treescript/Russound UI.lua:31: attempt to index a boolean value
stack traceback:
...les\Promixis\Girder5\luascript\Classes/Publisher.lua:28: in function <...les\Promixis\Girder5\luascript\Classes/Publisher.lua:25>
...Promixis\Girder5\/plugins/treescript/Russound UI.lua:31: in function <...Promixis\Girder5\/plugins/treescript/Russound UI.lua:26>
...les\Promixis\Girder5\luascript\Classes/Publisher.lua:37: in function <...les\Promixis\Girder5\luascript\Classes/Publisher.lua:36>
[C]: in function `xpcall'
...les\Promixis\Girder5\luascript\Classes/Publisher.lua:40: in function <...les\Promixis\Girder5\luascript\Classes/Publisher.lua:32>
...les\Promixis\Girder5\luascript\Classes/Publisher.lua:151: in function `SendEvent'
...les\Promixis\Girder5\luascript\Classes/Publisher.lua:138: in function `Event'
.\Russound_RNET.lua:1518: in function `Event'
.\Russound_RNET.lua:1127: in function `SetSystemStatus'
.\Russound_RNET.lua:998: in function <.\Russound_RNET.lua:981>
(tail call): ?
...er5\luascript\Classes/DelayedExecutionDispatcher.lua:40: in function <...er5\luascript\Classes/DelayedExecutionDispatcher.lua:38>
Error in subscriber callback
...Promixis\Girder5\/plugins/treescript/Russound UI.lua:31: attempt to index a boolean value
stack traceback:
...les\Promixis\Girder5\luascript\Classes/Publisher.lua:28: in function <...les\Promixis\Girder5\luascript\Classes/Publisher.lua:25>
...Promixis\Girder5\/plugins/treescript/Russound UI.lua:31: in function <...Promixis\Girder5\/plugins/treescript/Russound UI.lua:26>
...les\Promixis\Girder5\luascript\Classes/Publisher.lua:37: in function <...les\Promixis\Girder5\luascript\Classes/Publisher.lua:36>
[C]: in function `xpcall'
...les\Promixis\Girder5\luascript\Classes/Publisher.lua:40: in function <...les\Promixis\Girder5\luascript\Classes/Publisher.lua:32>
...les\Promixis\Girder5\luascript\Classes/Publisher.lua:151: in function `SendEvent'
...les\Promixis\Girder5\luascript\Classes/Publisher.lua:138: in function `Event'
.\Russound_RNET.lua:1518: in function `Event'
.\Russound_RNET.lua:1127: in function `SetSystemStatus'
.\Russound_RNET.lua:1215: in function <.\Russound_RNET.lua:1200>
Error in subscriber callback
...Promixis\Girder5\/plugins/treescript/Russound UI.lua:31: attempt to index a boolean value

Any ideas to what's going wrong?
In the variable inspector I can also see that the devicemanager has a variable called ConfigFile with the value set to DeviceManager.cfg.
There is no such file in my girder5 folder.

Regards,
Morten

[Rob H]

This error should be mostly harmless - does it persist? It looks as though it should only happen when the config page for the RussSound hasn't yet loaded.

Try replacing the file in plugins\treescript with this one.

[Mortie]

There's got to be something I'm missing.

What needs to be done/configured to get the divemanager to see my Russound device?
In settings->devicemanager I get "no devices".
I've tred G5 alpha in different versions but never got the devicemanager to work. I'll bet it's something I have not done correctly....

All I've done is install G5 build 504, the latest Russound plugin.
RNET works, but not showing up in device manager.
What am I missing?

Regards,
Morten

[Rob H]

It should show up automatically if the RNET device is installed. I'll have to leave this one for Mike to diagnose.

[Mortie]

When you say RNET device, would that be the same as installing the RNET plugin? (http://www.promixis.com/forums/showthread.php?t=15037?)


//Morten

[Rob H]

Yes, you said that it was working.

Can you try enabling some of the components in File|Component Manager e.g. Custom Weather and let's make sure that you at least see the weather device.

[Mortie]

First off all thank you for helping me debug this!

Yes, the RNET plugin works.

The custom weather compnent works, and shows up in Device Managers device list :-)

So that narrows it down to RNET.

ONe thing that strikes me is that even though I've completly unistalled girder4 and 5(and deleted the folders) before reinstalling the latest girder5 build, girder still knew the names of my CAV6.6 sources. I don't think that info is stored in the CAV6.6 unit, I might be wrong though.

Edit: ok me being dim, the sourece config is stured under the user profile dho :-) I guess I can try to delete all thats there?
Edit2: No luck deleting all config files either :-(
//Morten

[Rob H]

It will be saved in the config directory which is in Documents and Settings\<user>\Application Data\Promixis or somesuch place (I can never find it first time).

By the way, the RNET plugin is installed with G5 anyway I believe, so you shouldn't need to install it again unless it is updated at a later date.

[Mortie]

As far as I can tell the RNET plugin is not a part of the G5 distribution.

(I also tried to delete the user settings, no luck :-( )

[Promixis]

Hi

Uninstall G5 and G4, make sure that you erase there directories.

Install G5. Install the RNET plugin from the announcement forum.

Start G5. Goto the Settings page, select Audio/Video devices. Enable RNET on the correct serial port (you may need to enable the serial plugin first)

[Mortie]

Hi Mike,

That's what I've been doing without any luck.

Don't know if it's relevant but the RNET plugin has always got stuck on "Getting info zone 1 on controller 2" (I only have one controller) Should it time out?
But as you know the RNET plugin works in other aspects for me, just can't get in up and running in the device manager...

/Morten

[Promixis]

Hi Mike,

That's what I've been doing without any luck.

Don't know if it's relevant but the RNET plugin has always got stuck on "Getting info zone 1 on controller 2" (I only have one controller) Should it time out?
But as you know the RNET plugin works in other aspects for me, just can't get in up and running in the device manager...

/Morten



Morton, is there an error dump in the console?

And when you say RNET gets stuck on enumerating controllers, what is it doing?

[Mortie]

There are only warnings, that the devicemanager.cfg file does not exsists, but that gets created as expected on the first exit of girder. On next start no error what so ever.

Regarding RNET getting stuck, it's in Settings -> Audio/Video components, the status is always "Getting info zone 1 on controller 2" after the it's done scanning controller 1.

This can also be verified in the variable inspector; RNET.Status has the same value.

//Morten

[Promixis]

Morten

What Russound device is this.

[Mortie]

Mike,

It's a CAV 6.6, don't have the exact build and version of the firmware right here now.

//Morten

[Promixis]

Do you have the rnet - work file in your serial directory? if so remove it.

[Mortie]

Mike,

The only Russound related file I have int the \plugins\serial foler is:
Russound_RNET.lua containing:
--[[

Girder to Russound CAV RNET Serial Plugin

(c) Promixis

PluginID = 902

--]]

if not extras then
return
end

if not extras.LoadRussoundRNET then
return
end

extras.LoadRussoundRNET()

//Morten

[Mortie]

Mike,

not to bug or rush you, but do you have any suggestions as to what to do about this? :-)

Anything you'd like me to try to debug the issue?

Regards,
MOrten

[Mortie]

ok, so I've treied with another computer running WinXp sp2 and then the device manager works as it should :-)
Now, I was running Windows Server 2003 on the server that I initially was trying with, so in the interest of debugging, I loaded up WinXP on that computer. Then I get the same problem, the RNET plugin does not finish up.
It get's stuck, so there has to be something with the serial interface on that machine, it's a standard Compaq EN, a few years old I'll admit but I can't figure out why it's not working...
It's nothing sprecial about the hardware at all...

Any ideas where to go from here?

//Morten

[Ron]

when you tried the other computer where all cables the same cables as you used on the winxp machine?

[Mortie]

hehe, was just trying that as I saw your message :-)
And yes! It was the cable!
There has got to be some defect to it?!?

Before you gous made the plugin I had a c# class that handled the CAV and it workd without a glitch, so I never expected the cable!

Damn this had me going mad! So glad we figured it out!

Thank you for all your support! Mike, no wonder you could not find anything ;-)

//Morten

Now, finally I can start and look at the device manager and NetRemote.

I think I can ask right away; how is one supposed to utilize the device manager from NetRemote?

[Ron]

We'll have a specialized CCF that hooks into the Device Manager. We hope to be able to release the whole package very soon. The DM stresses NR quite hard so we needed to make sure it's all stable.