Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - mikeybs

Pages: 1 ... 3 4 [5]
Users / Re: gc100 and rs232 control
« on: November 13, 2013, 07:11:35 am »
ok, I will do that

any advice on figuring out why the virtual serial port /dev/ttyS_38_0 is not working with the TestSerialPort command? 

Clearly the gc100 is working along with the serial cable since I am able to get feedback with the iTest.exe application.  How can I go about debugging the virtual serial port?  I would rather work on this problem first.  If I can't solve it there is no point in generating a template as I need to use my gc100 to control the receiver.  If I can't get the gc100 virtual serial port working I'd prefer to switch to IR control. 

I've got the gc100 using IR to successfully control both my TV and Verizon STB in this entertainment area.  I wanted to use RS232 for the receiver since it supports it, but if I can't get the gc100 to play nicely with the virtual serial port, then IR is my only option.

Users / Re: gc100 and rs232 control
« on: November 13, 2013, 06:55:27 am »
My best guess is that the problem lies with the virtual serial device /dev/ttyS_38_0

I am still at a loss as how to use the protocol sheet correctly...

When I put "11 00 00 00 03" into a hex translator ( it does not produce any text output

Can you give me one more example with the hex of a full command that would be sent to the receiver?  I think with that I would be able to generate the rest of them myself...

So the first part would have to be the ready message as described above, which the sheet says must come at the beginning of all communication.

What I have been working on is trying to get the receiver to switch to the HDMI 1 input.  On the protocol sheet in the Operation Commands table on page 14 that is listed as: 0784A

How do I incorporate that into the hex string I send?

I tried translating 0784A to hex: 30 37 38 34 41

and then adding that to the end of the ready command to create this hex string: "11 00 00 00 03 30 37 38 34 41"

I tested that with the iTest.exe application and it seemed to generate the same output as the ready command by itself.  The receiver did not change to the HDMI 1 input....

Users / Re: zwave dimmable light switches
« on: November 13, 2013, 05:44:51 am »
ok, I was able to work around it by adding in all my dimmable switches, then deleting the entire zwave interface, then letting linuxmce readd the zwave interface along with all the dimmable switches it has associated with it.  Now I have dimming controls on my orbiters for all the dimmable switches  :)

not a very elegant way of achieving the result though...

Maybe I'm missing something?

Users / Re: gc100 and rs232 control
« on: November 13, 2013, 05:39:59 am »
I was able to get feedback using the iTest.exe application from globalcache.

I used the application to connect to the Serial Port and then sent the Hex command string:  \11\00\00\00\03

I received a very long response just as you suggested I would :)

That is the first feedback I've gotten from the receiver via RS232 so thank you for helping me achieve that. 

Perhaps I messed something up in the TestSerialPort command?

should the output for it come right through on STDOUT, or do I have to specify a "-s Search String" or "-m message to log" to see some output?

Could this mean the issue is with the virtual serial port on the linuxmce core.... /dev/ttyS_38_0? 

Users / zwave dimmable light switches
« on: November 13, 2013, 05:12:45 am »
For some reason when I add a new zwave dimmable light switch, the orbiters only show on/off controls for the new switch instead of also showing the dimming controls (10% 30% 50% 70% 90%).  This has been happening to me with a fresh install of 1004.  Funny thing though, if I take the zwave usb stick from the existing install where the newly added dimmable light switches have on/off control, and plug it into a fresh 1004 install then all the dimmable light switches that I added on the previous installation show up and they all have their dimming controls on the orbiters.

I thought maybe I could workaround this by deleting the newly added switch and then letting linuxmce readd it for me (hopefully with the dimming controls), but that did not work.  It readded the switch, but still with only on/off controls.  The only way I have been able to get the dimming control into the orbiters is to take the zwave stick to a fresh install of linuxmce....

Users / Re: gc100 and rs232 control
« on: November 13, 2013, 05:04:49 am »
I attempted to run this as root:

/usr/pluto/bin/TestSerialPort -P N81 -t \11\00\00\00\03 -b 9600 -p /dev/ttyS_38_0

it hung for a few seconds and then completed, there was no output

On the gc-100 web interface, what should the serial port settings for "Flow Control" be?  "Hardware" or "None" are the options...  I tried it with both settings, neither produced any output

Users / Re: gc100 and rs232 control
« on: November 13, 2013, 02:18:16 am »
well I now have both an inline tester as well as a straight through serial cable and I am still unable to get things working.  According to the tester the signals are coming across the wire.

I am thinking that I am simply not generating the correct codes to send using the protocol sheet.  I am not sure what I am doing wrong.  In my previous post there is a link to the protocol sheet for my receiver.  I would really appreciate it if anyone could help me generate the correct commands for TestSerialPort, or the correct hex codes so that I can use the globalcache iTest.exe application to test.

The core groups of commands I am interested in are:

Power On
Stand By
Volume Up
Volume Down

If anyone could help me determine the correct TestSerialPort command for any one of those receiver commands it would be fantastic.

Users / Re: gc100 and rs232 control
« on: October 30, 2013, 03:40:43 am »
here is a link to the protocol sheet for my receiver/soundbar as well if it is of any help

Users / Re: gc100 and rs232 control
« on: October 30, 2013, 03:37:58 am »
I am pretty sure the cable I need is a null modem cable :(  So I guess I just ordered a cable for nothing.  Looking at this PDF:


it appears my receiver/soundbar requires a null modem cable.  The cable I am using is brand new, the link for it is in one of my previous posts in this thread.  So looks like I am back to the drawing board.  I guess I'll have to buy a tester to see if the signals are going through...

Users / Re: gc100 and rs232 control
« on: October 30, 2013, 12:43:01 am »
ok, I'll get a straight through cable and try that, if I still have issues I'll get the tester too, thanks for the advice

Users / Re: gc100 and rs232 control
« on: October 29, 2013, 11:58:25 pm »
I'm trying to use the globalcache itest.exe application to see if I can get it working that way...

still no luck

I am not sure I am doing the hex translation correctly.  The "Yahama RX Receivers RS232" "Group/Codeset" has IR commands that look like the following in it's A/V Properties:


The codes in my protocol sheet appear to be very similar... I am attempting to send what is listed in my protocol sheet as: "0787F"

The itest.exe application will accept either string literals or hex input, so I am trying to use the hex input...

I used a hex code translator to turn "0787F" into "30 37 38 37 46" and then I entered that into the hex input of itest.exe and the receiver does nothing.  I also tried these for the hex codes:

00 78 7F
00 07 08 07 0F

neither of those worked either

itest.exe does seem to successfully connect to the serial port of the gc100 though.

I am back to wondering if the cable is my problem, or if I am screwing up the hex format in some way....

Users / Re: gc100 and rs232 control
« on: October 29, 2013, 11:35:27 pm »
so I'm thinking this is the correct command:

/usr/pluto/bin/TestSerialPort -p /dev/ttyS_38_0 -t "\x00\x78\x7F" -b 9600 -P N81

but the receiver does nothing when I send it...

I am still wondering if maybe I have the wrong type of cable.  I am rs232 newbie, so not quite sure.  Here is the cable I am using...  I tried putting in an actual link, but the forum will not let me.


Users / Re: gc100 and rs232 control
« on: October 29, 2013, 10:40:41 pm »
yeah I've been trying to use the TestSerialPort utility to see if I can get a successful send that way.  I don't think I am writing my commands properly though, I'm not that familiar with serial port stuff...  I am not sure how to generate the correct transmit string.

I tried:

/usr/pluto/bin/TestSerialPort -p /dev/ttyS_38_0 -t 0787F -b 9800

I'm guessing that 0787F needs to be rewritten, can anyone assist in how to do that?

Users / gc100 and rs232 control
« on: October 29, 2013, 08:17:32 pm »
I am trying to control a yamaha YSP5100BL soundbar/receiver via rs232 with the gc100.  I have found the rs232 protocol sheet for the receiver on the yahama website.

I am running lmce1004.  The gc100 was autodetected and setup.  I am using the IR transmitters without an issue.  The serial port was created on the core as /dev/ttyS_38_0 and I have selected that in the receiver device data as the value of "COM Port on PC".  

I went to the gc100 web admin and set up the serial port as described in the yahama protocol sheet:
baud rate: 9600
flow control: hardware
parity: no

The cable I am using to connect the gc100 serial port to the receiver serial port is described as a "DB9 RS232 Serial Null Modem Cable".  Perhaps the cable is my issue?  

I initially chose the "Yahama RX Receivers RS232" as the "Group/Codeset", but it doesn't appear that those codes match up well with my receiver.  I have been attempting to replace the rs232 codes in the template with the ones in the protocol sheet I have.  I am not having any success with this though.  I have yet to successfully send any sort of command to the receiver.

Can anyone suggest what I should attempt next?

Is there any other information I can provide?

Pages: 1 ... 3 4 [5]