I havent tried it yet, but it should work.  I ran it through the debugger and it worked as expected.  I will test it out today on the boat.

Be interesting to see how it works. It seems the slider might be possible to work with it as well. I made the widget last night and will hopefully mess around with it today - seems to open up so many possibilities

Well, no luck getting this to work for me - nothing shows on the button and an error symbol comes up each time. Would have been nice if the whole strings were shown in the example =]

After some suggestions from the gf that the remote was too sluggish, I scrapped the 2-second volume polling today and got to work creating a volume status widget that runs only when the hard buttons for Vol Up / Vol Down are pressed. (The widget also runs every 30 seconds.)

There's still about a second delay between pressing the vol button, seeing the receiver respond, and receiving feedback ... I'm not sure whether this is just as fast as the Nevo gets or if it could be improved. However, there is a noticeable improvement in overall remote speed and responsiveness (over the 2-second feedback widget) ... buttons no longer fail to respond.

Here's a screenshot of the widget in case it gives anyone ideas:


[No, I haven't figure out the correct regex to deal with +ve volume levels, but I never have it turned up that high...]

Hi Guys,

Just a word of warning.

NSP 3.0 is not guaranteed to work with unsolicited feedback. So the above widget may not work completely as expected. I think 3.1 will be better with unsolicited feedback.

The better way to do it is:
In the normal part of NSP put your volume commands as per normal.
You widget should only be asking for volume feedback status and sending a volume command.

I also find it pointless for a volume timer feedback as I am only changing the volume from the remote (i think I would know if i change it :) ). So a request on release is best.

I found this to be the most reliable method.

I would post a image but have nowhere to put it!


D.

When you say unsolicited, do you mean equipment which automatically issues a notification upon any status change (volume, input, etc)? As far as I can tell from the Marantz serial protocol docs, the receiver responds to any serial volume commands with a serial string indicating the new volume level, but it doesn't issue such information unless prompted.


I'll have to try that method....


I put the timer in because I rarely adjust the volume ... I just like knowing what it is (especially now that I have my receiver hidden from view). Plus that way, if I adjust it manually, or with the factory remote, the Nevo will eventually catch on. Eventually I'll figure out how to make the volume appear in a pop-up button (& disappear after 5-10 seconds or so)...


I signed up for Photobucket to post this one but I think I have a free account somewhere else.

Fwiw, the biggest gripe I have with the widgets is that every time I alter the code, I have to delete and re-add the widget on every page of the remote I have copied it to. Already written UEI about it, but a "refresh widget" option would be nice.

 the Marantz will do auto status feedback.  the command to set the status layer feedback is at the bottom of the excel sheet that lists all the commands. (I didn't use the auto status feedback in the following widgets)

here are the widgets that I made for a recent Marantz project.  If anyone wants the files, let me know.

Volume Status

I prefer to use IR commands for volume control instead of RS232, the volume ramping feels more natural. The widget asks for a volume status when the volume button is released.

Sirius Channel Status

FM Channel Status


AM Channel Status


For some reason I could not get the Marantz receiver to respond to requests for Sirius channel info (song title, artist, etc) This wasnt a nevo problem though.

Okay, I get it now.
I had thought in the NSP3 Widget Guide that you couldn't have both a command and a Widget triggering off the same button press. But I see there's nothing preventing the widget from being active on that page.

Duct Tape, I'm totally copying that FM channel status. Nice!

Hi PeterN,

I will look at photo bucket. Thanks.

EDIT-------

Sorry it was late and I got it all muddled up.

Here is the correct descriptions:

Un-solicited feedback:

You change input on the front panel of the amp and it sends a rs232/IP command saying the input changed.

or

lets say you have a IP mediaplayer that sends the song progress information every second.


Solicited feedback:
You ask a question and the amp replies.

or

When you send a code and the amp replies with the status. IE change input and the amp replires with the input change.

Nevo widgets info:
Whenever the widget device block has another block attached to its output it expects the device to send a response to all commands. If that response includes the current volume level or only says “OK”: both are good and both are considered solicited feedback.
In other words, Nevo doesn’t discriminate between sending function commands or sending questions to devices. As long as it’s Nevo doing something first before the device sends information back.


I will get clarification about you widget peterN later tonight. I think it should be OK but I cant be certain.

D.

Hi,

So to follow up.

PeterN, What you are doing in terms of sending a volume command and then using the reply string is correct.

What won't work is if you change the volume from the amp (or other than the Nevo) and then the remote being updated. This is where your timer would come in.

Personally I would not use the timer, but that is just me.

Also.
Just as a test. Try removing the \r from your constants (commands). It should take the info from the device driver info.





D.

syd - care to share those widgets? =]

I would be more than happy to once Dan sets up an area in RC.

Unless some else knows of where we can put these for athers to grab?

D.

I use MediaFire, it's free.


Cheers
Jason

 [Link: mediafire.com]

Here are my first two files:

[Link: mediafire.com]

Remember to change out the RS232 device. I have been messing around with mine so it may not be relaible. The are 3 devices in the tuner module.


D.

Very nice. Everything works great when testing, but real world stuff still fails constantly - might have to try swapping out another NC50 and/or try a Q50 to see if one of these devices is faulty.