What amp do you have?
I'm very new to girder 4.0 so I hope I'm not way off track, but here goes anyways. Not sure what emooney is trying to do but what I'm looking for is to get G4 to work like G3 did with its yamaha plugin. So besides putting the 2 yamaha lui files into G4 I also loaded the GML file from G3 expecting to be able to "Test the Action" and the RX-V1500 would follow the command. Right now besides the "Communication with receiver unsuccessful", the commands in the main G4 window all say "Plugin Command (unavailable)" under the General side window. I haven't got into doing anything with NetRemote yet and not sure if I will be. My end goal is to setup my HTPC software (Meedio) to send commands to my receiver via girder and also maybe a web interface to control from my laptop.
So in saying all that I'm wondering if the NetRemote part of this is causing the problem?
Or maybe I'm completely Out to Lunch!!!
kevin
An RX-V1500Originally Posted by danward79
Hi,
Kevin, the G3 GML will definitely not work with this script, there's a completely new syntax implemented. I'll try to post an example GML (which I thought I had already) tonight for G4.
The response you receive from the amp is really weird though. Looks nothing like anything I've seen.
If you don't want to use NetRemote with this you can just comment the require "netremot..." line in the serial init file, as well as edit the JYamaha.lua script and change the line JYamaha.SendToNR = 1; to JYamaha.SendToNR = 0;
However, as long as you get that type of response it probably won't work anyways, perhaps sending commands will work.
Eric, I'm gonna try and take a look at the serial init file tonight, problem is I'm really stuffed with work at the moment, and I find it hard to make time to sit with this.
Cheers,
Jens
\"Video games don\'t affect kids. I mean, if Pac Man affected us as kids, we\'d all run around in darkened rooms, munching pills and listen to repetitive music.\" - Kristian Wilson, CEO of Nintendo, 1989
thanks for the info jens. looking forward to the sample gml file that will help a lot once I get the Yamaha RX-V1500 plugin functioning properly.
The dam thing comes up with a successful connection every once and a while depending on time its been sitting doing nothing and the state of the receiver (whether it was on or off).
Haven't figured out any real pattern yet.
kevin
After a fair bit of messing around this is what i can get to consistantly happen...
I unload the Yamaha RX-V1500 driver
Power off the receiver
load the Yamaha RX-V1500 driver and get the following console output.
Communication with Receiver successful
...\Program Files\Promixis\Girder\luascript\JYamaha.lua:80: attempt to perform arithmetic on a nil value
stack traceback:
...\Program Files\Promixis\Girder\luascript\JYamaha.lua:80: in function `handleData'
...\Program Files\Promixis\Girder\luascript\JYamaha.lua:38: in function <...\Program Files\Promixis\Girder\luascript\JYamaha.lua:34>
if I then power up the receiver the console output can vary. Most of the time it is a dump of the receiver setting and sometimes hardly anything at all no matter how many times I power up and down the receiver.
When it dumps out the receiver setting I can immediately press buttons on the remote and get appropriate console logs. If I just leave everything for awhile the console output stops when I press buttons on the remote. This is the tail end of the console log when it stops working ...
Received Display Report String
Tuner Frequency: 94.5
Data received:---303601---
Got Generic Report
Data received:---303C01---
Got Generic Report
Serial Error (CallLua, Code=288): attempt to call a number value
stack traceback:
Seems to me something is jamming up somewhere in a buffer of something. (Thats my technically professional diagnostics ... lol) I'm hoping someone can maybe help me figure out whats going wrong.
thanks,
kevin
Have you tried the Yamaha receiver manager. That should help you prove if your connection is good etc, and that the problem lies only with Girder, and not with several factors.
Hey Kevin,
it'd be great if you try what Dan suggests just in order to make sure your serial cable and serial port is working correctly.
Also, I made a couple of changes in the JYamaha.lua script attached below. If you could please try it exactly the way you described in your last post and post the output you get this time. I'm interested in whether it always craps up on 303C01, if so this little fix should work around that. I'm surprised you get this though, the script really shouldn't bother.
Honestly it feels like something is really weird though. The init string you receive should definitely be longer than the one you get, AND it's supposed to start with something similar to R1077....
Feels like this is timeout issues or something to me.
I'll get back with an updated serial file a little later, please try this meanwhile.
Cheers,
Jens
\"Video games don\'t affect kids. I mean, if Pac Man affected us as kids, we\'d all run around in darkened rooms, munching pills and listen to repetitive music.\" - Kristian Wilson, CEO of Nintendo, 1989
You guys are awsome!
I have tried the Yamaha receiver manager and it appears to work perfectly. I'll try jens new JYamaha.lua and get back to you today with the results.
I had this thought that maybe the difference is because my receiver is made for the North American market and yours are European. Although I'm just guessing that your not in North America. When I run the Yamaha receiver manager in Asyncronous mode it asks me to choose a tuner region. So there is obviously some difference in the receivers. ... just a thought.
thank you,
Kevin
here's the results with the different JYamaha.lua script ...
Communication with Receiver successful
...\Program Files\Promixis\Girder\luascript\JYamaha.lua:81: attempt to perform arithmetic on a nil value
stack traceback:
...\Program Files\Promixis\Girder\luascript\JYamaha.lua:81: in function `handleData'
...\Program Files\Promixis\Girder\luascript\JYamaha.lua:38: in function <...\Program Files\Promixis\Girder\luascript\JYamaha.lua:34>
*** Turned on Power ***
Data received:---300001---
Got Generic Report
Data received:---102001---
Got Generic Report
Power
Sending: All On to Yamaha.Power
Data received:---R0177F8A@E019000120505092771713140100101000000010 20011002828282828282828282800000014140000000410511 0000011120100000282828282828282828285077000021129---
Sending: -26.5 to Yamaha.MasterVolume
Sending: 146 to Yamaha.Vol
Sending: -40 to Yamaha.Zone2Volume
Sending: 7ch Stereo to Yamaha.Program
OSD: Short
Sending: Short to Yamaha.OSD
Sleep: Off
Sending: Off to Yamaha.Sleep
Tuner Page: A
Sending: A to Yamaha.TunerPage
Power: All On
Sending: All On to Yamaha.Power
Input: Tuner
Sending: Tuner to Yamaha.Input
SP Relay A: On
Sending: On to Yamaha.SPRelayA
SP Relay B: Off
Sending: Off to Yamaha.SPRelayB
Playback: Analog
Sending: Analog to Yamaha.Playback
Input Mode: Analog Only
Sending: Analog Only to Yamaha.InputMode
EX/ES: Off
Sending: Off to Yamaha.EXES
Mute: Off
Sending: Off to Yamaha.Mute
RED dts: Release
Sending: Release to Yamaha.REDdts
Zone2 Input: DVD
Sending: DVD to Yamaha.Zone2Input
Zone2 Mute: Off
Sending: Off to Yamaha.Zone2Mute
Dts 96/24: Off
Sending: Off to Yamaha.DTS9624
Tuner Tuned: Not Tuned
Sending: Not Tuned to Yamaha.TunerTuned
Tuner No: 2
Sending: 2 to Yamaha.TunerNo
Fs: Analog
Sending: Analog to Yamaha.Fs
Thr/Bypass: Off
Sending: Off to Yamaha.ThrBypass
Data received:---301501---
Got Generic Report
Tuner Tuned
Sending: Tuned to Yamaha.TunerTuned
Data received:---00 94.5 ---
Received Display Report String
Tuner Frequency: 94.5
Sending: 94.5 to Yamaha.TunerFreq
Data received:---303601---
Got Generic Report
Data received:---303C01---
Got Generic Report
DC2 Trigger Output
Sending: On to Yamaha.DC2TriggerOutput