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 - cafedumonde

Pages: [1] 2 3 4
1

Phenigma,

Thanks for the reply. Follow ups are as follows:

1. How do I turn off auto configure for mythfrontend? Is there a wiki reference?

2. I found another webcam, which is a Cisco branded camera, though it exactly looks like one of the later  Logitech models. It is working.

3. I am happy to create an issue in gitlab. How do I do it?

CDM

2

Looking up the camera model number on the Logitech support site, it is a QuickCam Pro 3000. Again, I had this working under 810.

Thanks,

CDM

3
Installation issues / 14.04 Installation - More Minor Issues
« on: Today at 12:58:01 am »

My 14.04 Installation has proven to be very usable in spite of some persistent minor issues. In each case I have reviewed the wiki as well as explored the installation in order to troubleshoot. I hope that I am not posting too much; my intention is to ask the community only were I am unable to flush out solutions on my own. I completely accept that LMCE is a project rather than a product, and that figuring things out is part of the fun. Solutions and clues equally welcome in response to my questions.

My current issues are as follows:

1. Mythfrontend does not save settings. I have changed a few things in the front end, in particular the scaling of the video image as negative percents. These parameters are not saved, even when I exit the frontend setup gracefully.

2. Cannot install a Logitech Quickcam. There is a wiki page for this here:

http://wiki.linuxmce.org/index.php/Logitech_QuickCam_Sphere

I followed the instructions, substituting "**PWC Camera Drivers" for "PWC Camera Drivers" in the instructions. Only the ** version appeared in the dropdown when building the device template. The motion wrapper seems to work fine: I get a grey square with some text overlayed when I choose the camera in the Security scenario. The LED on the camera does not illuminate, as it did when I have this same camera connected to my old 810 installation. I think this means that the camera driver is not working.

3. The system has still not discovered my Denon 2307 receiver over RS-232. The discovery script does not seem to be running. How can I initiate it? As indicated by Phenigma in an earlier post, there is a question about the syntax in the discovery script, assuming that I can get the script to run again.

Thanks,

CDM


4
Installation issues / Re: Does the WebDT 366 work with 1404?
« on: August 17, 2016, 03:29:15 am »

That did it. I just daisy-chained another access point to a port on my 802.11n router which is configured as an access point on the internal network. Its great to have all of my old gear back in action. Thanks.

CDM

5
Installation issues / Re: Denon Receiver Control over Ethernet
« on: August 17, 2016, 01:35:22 am »

Phenegma,

Please follow up on your comment regarding $?. Please check the file for this script in your installation. I did not change this.

After many days, the detection script has not run. Is there a way to trigger?

CDM

6
Installation issues / Does the WebDT 366 work with 1404?
« on: August 14, 2016, 03:55:11 pm »

I have a WebDT 366 loaded with the webpad orbiter image, previously associated with my old 810 system. It has not been used in years. I have revived it but it is not seen by my new 1404 installation. Following the instructions on the wiki, I have updated the wireless settings but still no luck. Questions are:

1. Should this work?
2. Is there an updated version of the image that should work?
3. Following the link on the wiki, the image is no longer posted. Is it still available?
4. What are suggested next steps?

Currently, the pad is charged, boots the old image without errors and stops with the LMCE splash screen and an X Windows cursor that responds to the touch pad.

Thanks,

CDM

7
Installation issues / Re: Denon Receiver Control over Ethernet
« on: August 13, 2016, 09:32:22 pm »

More progress but still no prize...

I modified the Denon detection script /usr/pluto/pnp/20_DenonReceiver.sh to create a tool for testing the detection. I found that it only works intermittently on my machine. The detection depends on the contents of "$?" in the script after sending a command over the serial port to the Denon.

The test script, DenonPNPTest.sh

Code: [Select]

#!/bin/bash                                                                                                                             

echo "Denon Detection script queue $2"
echo "Arg1=$1 Arg2=$2 Arg3=$3 Arg4=$4"
/usr/pluto/bin/TestSerialPort -p $3 -P N81 -b 9600 -t "PWSTANDBY\r\s500mPWON\r" -i 1 -s "MON\r"
if [[ "$?" -ne 0 ]]; then
echo "It's not a Denon Receiver Resp=$?"
# /usr/pluto/bin/MessageSend dcerouter -r 0 $1 1 806 224 $2 13 "$4" 44 0                                                               
else
echo "It is a Denon Receiver Resp=$?"
# /usr/pluto/bin/MessageSend dcerouter -r 0 $1 1 806 224 $2 13 "$4" 44 71                                                               
fi


 And the output of several runs, with lines added in between for readability....

Code: [Select]

root@dcerouter:/usr/pluto/pnp# ./DenonPNPTest.sh foo foo /dev/ttyS5 foo
Denon Detection script queue foo
Arg1=foo Arg2=foo Arg3=/dev/ttyS5 Arg4=foo
It's not a Denon Receiver Resp=!!0

root@dcerouter:/usr/pluto/pnp# !!
./DenonPNPTest.sh foo foo /dev/ttyS5 foo
Denon Detection script queue foo
Arg1=foo Arg2=foo Arg3=/dev/ttyS5 Arg4=foo
PWSTANDBY\rZMOFF\rZ2OFF\rPWON\rZMON\rZ2ON\r
It is a Denon Receiver Resp=1

root@dcerouter:/usr/pluto/pnp# !!
./DenonPNPTest.sh foo foo /dev/ttyS5 foo
Denon Detection script queue foo
Arg1=foo Arg2=foo Arg3=/dev/ttyS5 Arg4=foo
It's not a Denon Receiver Resp=0

root@dcerouter:/usr/pluto/pnp# !!
./DenonPNPTest.sh foo foo /dev/ttyS5 foo
Denon Detection script queue foo
Arg1=foo Arg2=foo Arg3=/dev/ttyS5 Arg4=foo
It's not a Denon Receiver Resp=0

root@dcerouter:/usr/pluto/pnp# !!
./DenonPNPTest.sh foo foo /dev/ttyS5 foo
Denon Detection script queue foo
Arg1=foo Arg2=foo Arg3=/dev/ttyS5 Arg4=foo
It's not a Denon Receiver Resp=0

root@dcerouter:/usr/pluto/pnp#


Could it be that the command is somehow taking too long to populate "$?"  ???

I am not a bash scripter but could I just capture the string returned directly from the serial port test and decide the detection on that? It is frustrating that "$?" does not work reliably given that it is a standard bash scripting feature.

Feedback from developers would be appreciated. Thanks.

CDM

8
Installation issues / Re: Denon Receiver Control over Ethernet
« on: August 13, 2016, 04:13:21 pm »
Posde,

It looks like LMCE has registered the serial ports. Looking in WebAdmin HOME > MyDevices > CORE , the Available Serial Ports box shows both ports and one that I think is my USB UIRT:

/dev/ttyS4,/dev/ttyS5,pci0000:00/0000:00:1d.0+1.2

Does reloading the router trigger detection? Is there a log file I can look at?

--------------------------

Updating the post...

I tried to connect to the port again using minicom. LMCE is running, with a video paused. I get the fiollowing when trying to connect to /dev/ttyS5..

Code: [Select]

Device /dev/ttyS5 is locked.
root@dcerouter:~# ls -la /dev/ttyS5
crw-rw---- 1 root dialout 4, 69 Aug 13 07:46 /dev/ttyS5
root@dcerouter:~#


Not sure if this is good or bad. Does this mean that LMCE has locked the port? Otherwise could this be a file permission issue and LMCE is locked out? Again, an LMCE log file might give a clue.

CDM

9
Installation issues / Re: Denon Receiver Control over Ethernet
« on: August 13, 2016, 02:58:21 pm »

More success but no prize just yet....

I found the detection script which appears to be /usr/pluto/pnp/20_DenonReceiver.sh

Looking at the script, I modified the detection command in order to run from the command line:

Code: [Select]

/usr/pluto/bin/TestSerialPort -p /dev/ttyS5 -P N81 -b 9600 -t "PWSTANDBY\r\s500mPWON\r" -i 1 -s "MON\r"


This works!!! The receiver power cycles as expected.

I now know the following:

1. the serial ports on the PCI card work
2. the serial interface on the receiver works
3. they are communicating in both directions
4. LMCE has a detection script for the Denon over RS-232

However, AVWizard does not seem to trigger this script. Is there another way to trigger? Will it trigger automatically if I wait long enough?

CDM



10
Installation issues / Re: Denon Receiver Control over Ethernet
« on: August 13, 2016, 02:21:15 pm »

I have had some success this morning. I have tested both serial ports using minicom, connecting them to each other and passing characters both ways with two terminal sessions. Connecting one port to the receiver, I am also able to see status change reports when I press buttons on the ir remote. So, I know which serial port I am on and I know that it is working. I am also receiving characters from the AVR-2307. However, typed characters are not echoed and the receiver does not respond to commands.

Connecting the serial port to the terminal and running AVWizard, I also do not see any characters coming out of the port.

Is this device really plug & play? Is there a detection script? If so, where is it? Is there a way I can trigger it manually?

Also, if there is not a script, how can I add the device manually?

CDM

11
Installation issues / Re: Denon Receiver Control over Ethernet
« on: August 13, 2016, 03:16:36 am »

Phenegma & Community,

It turns out that my receiver is an AVR-2307, which does not support Ethernet or CEC. The only option is RS-232. I have connected the receiver to my hybrid using a PCI serial port card with two ports and a db-9 cable. I do not know the pinout of the cable though there are male and female connectors, matching the genders on the equipment.

The wiki page, which is old, describes that this is plug&play. Trying the setup wizard, it is not detected on either port.

Trying to add the receiver manually, I selected Wizard > AV Equipment > Add Device and picked the AVR/AVC (Ethernet) template. It shows two serial ports, ttyS4 and ttyS5. I am ASSUMING that these correspond to the two on my PCI card. I tried both but still no luck after running AVWizard again to assign the inputs. Sending the "off" command through the Admin tool also does not work.

My normal troubleshooting approach with serial devices is to set up a dumb terminal on one side of the connection, send commands, and see the responses. This is the path I'll go down barring any advice. For starters it would be good to know if the use null modem connectors is typically required. Also, are there linux config files to validate the /dev/tty entries associated with my PCI card?

Thanks,

CDM

12
Installation issues / Zoom & Aspect Controls In Xine Not Working
« on: August 12, 2016, 03:14:41 am »

When playing a video and selecting the Zoom & Aspect button, the UI correctly shows the options but they are not responsive when selected. I am thinking that this could be a bug.

CDM

13
Installation issues / Re: Video Quality & Sound with Intel Drivers
« on: August 12, 2016, 03:11:48 am »

All issues resolved:

1: Darkness was not specific to LMCE. I just adjusted the display controls.

2: Video tearing fixed by passing the TearFree option to the Intel driver as described in the thread.

3: The subtle distortion was indeed a function of the modeline timings. The standard ATSC timings caused the distortion. I switched to one known to work with Sony TVs.

4. Sound is working fine. My receiver was not setup correctly.

Thanks again for the feedback. System is working great for basic playback...now on to the next set of issues...

CDM

14
Installation issues / Re: Video Quality & Sound with Intel Drivers
« on: August 08, 2016, 01:36:32 am »

Thanks Phengma for the quick reply. 

The tearing problem is solved. I added the following to the "Device" section of xorg.conf:

Option "TearFree" "true"

Apparently this is an special option for the Intel driver. It is puzzling to wonder why someone would want tearing.

What is fbdev? Why would it be a better choice than the proprietary driver?

CDM

15
Installation issues / Video Quality & Sound with Intel Drivers
« on: August 08, 2016, 12:41:09 am »

I have just gotten my new 14.04 installation to drive my Sony CRT television at 1080i but still have a few issues.

LMCE is working fine. I ran the AVWizard to resize the UI and specified sound over HDMI. The UI comes up and seems just as it should.

I think I have problems at a few levels:

1. Video Content is Dark: Is there a gamma or brightness adjustment in Xine, Xwindows, or perhaps in the Intel driver? I just need to brighten things up a bit. Cranking the brightness on the TV adds detail to the dark areas but washes out the brighter ones.

2. Video Tearing: Tearing is apparent when the video content changes quickly. I expect this is a driver issue, though I specified the intel driver in my xorg.conf. I will try switching back to the "fbdev" driver. Does anyone know the difference? Any other ideas? My old system, with the GeForce 6200 looked way better.

3. Horizontal Distortion: There is a slight horizontal wiggle in the CRT scan that happens when bright content transitions through a few lines of video. One possibility is that I may need to tweak my modeline. I used the ATSC timings as a start but there seem to be many variations for 1080i. Another possibility is that my attempt to pass sound over HDMI is somehow screwing up the video.

4. Sound Not Working: Sound is not coming over HDMI. Just a loud static. Sound works great on the HDMI output of my cable box and I run it into the TV exactly the same way. I said "yes" to DTS in the AVWizard. Any links or tips on this?

Once again, any input would be appreciated.

Thanks,

CDM

Pages: [1] 2 3 4