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

Pages: [1]
1
YamppLink / Re: YL Crashes on loading playlist
« on: 07.07.2006 at 01:53:44 »
Hi Mic,

It seems to be files that are MPEG 1 Layer 1 instead of Layer 3 that cause the issue.. Also 320kbps files seem to do it. It would be good if YL showed an error instead of just crashing out..

2
YamppLink / YL Crashes on loading playlist
« on: 06.07.2006 at 14:51:53 »
Hi,

When I Load certain m3u playlist files YL just seems to exit withouth any warning or error. I am using 0.926a. I have checked the log file but no luck.. any ideas?

Cheers

Martin

3
Software / Artist List in Y3
« on: 16.05.2006 at 11:33:53 »
Hi all,

I have been reading some of the past posts about getting the Y3 to show a list of artists in alphabetic order ( in much the same way as a list of playlists at present). Has anyone actualy done this using the YADL filesystem items shown below.

Code: [Select]
u16      next_artist;         /* pointer into songbase to (alphabetically) next title of this artist or new artist */
u16      next_artist_grouped; /* pointer into songbase to (alphabetically) next artist in unique(grouped) list */
u16      next_title;          /* pointer into songbase to (alphabetically) next song  */

In an ideal world I would like 'Browse Artists' and 'Browse Playlists' to be included in the menu. Has anyone got any pointers?

Thanks in advance.

Martin.

4
YamppLink / Question about Playlists
« on: 11.05.2006 at 12:14:58 »
Hi all,

I want to know if you have two playlists that reference the same file, will the file be transfered and stored on the disk twice? i.e. once for each playlist it exists in?

Martin

5
Hardware / Re: Y3/USB IR Remote Problems!
« on: 11.05.2006 at 10:35:20 »
Im on 1.53.

With the changes above it all seems to work fine and shows up as NEC80. I sometimes find the next disc button doesnt work if you press it to long. I suspect this is due to a double tap as this button sends repeat commands like the volume button.

Cheers
Martin.

6
Hardware / Re: Y3/USB IR Remote Problems!
« on: 11.05.2006 at 00:56:21 »
Looking at the protocols it seems almost identical to the NEC format.

I took captures of the IR receiver output on a DSO to see exactly what is going on. I also compared this to a RC-5 remote and the results are very different. A few of the kenwoods buttons are listed below and the binary/hex they produce

Src Button:  10011101 01100010 11001000 00110111
                  9D           62            C8           37

Att Button:  10011101 01100010 01101000 10010111
                  9D           62            68            97

So it seems the first 16 bits are device and second 16 bits are command.

I then had a look at the code in the control.c file. Having identified 'u16 get_rec80(u08 std)' as the area most of this takes place I stepped through it. Here are the changes I had to make:


Code: [Select]
for (i = 0; i < ((std == 0) ? 48 : 31); i++)    // changed from 32
Changing the number of iterations in the loop meant the loop didn't drop out using the return(). This stopped it defaulting the RC-5 and allowed it to show up as NEC. Maybe it has to be 31 instead of 32 as the first bit has already occoured before the loop has started??

Code: [Select]
else
{
if( i == 22)                                // changed from 15
code.bytes.high = tmp;
if( i == 30)                                // changed from 31
code.bytes.low = tmp;
}

The changes to this area make's sure the hex data shown when selecting what function each button will do is correct. I had these set at 14 and 30 but that meant I was seeing the 2nd and 4th byte in the value not the 3rd and 4th.

So all seems to work well now with the Kenwood remote. Anyone have any ideas why the NEC code wouldnt work in the same way??

Cheers

Martin

7
Software / Re: Y3 Software Structure
« on: 11.05.2006 at 00:36:36 »
 :) Thanks nilrog that clears things up a little.

8
Software / Y3 Software Structure
« on: 10.05.2006 at 13:22:54 »
Hi all,

I am pretty new to the Yampp software and just had a few questions about the flow and how it is compiled.

I have set the following command in contants.h   

Code: [Select]
#define LCD_TYPE 6 // 4x20 LCD
Does this mean that in the following code, the line 'Vlcd_wrdata(0xff << (8 - (i+1)/2))' is not compliled into the final binary or is it compiled but the process just skips it as its not lcd type 7 ?


Code: [Select]
#if(LCD_TYPE == 7)
Vlcd_wrdata(0xff << (8 - (i+1)/2));
 #else
Vlcd_wrdata((u08)(0xff << (8 - (i+1)/3)) >> 1);
 #endif

Also, what about the code below, does the code between '#else' and '#else //GRAPH_LCD'  get compiled if the Y3 is set to use and alphanumeric display. I guess my question is could i remove these lines to save space if I never plan to use a graphical LCD?


Code: [Select]
#ifndef GRAPH_LCD
u08 i,j; // volume indicator on alphanumeric LCD's

if(!usb_play)
{
Vlcd_command(0x40); // define of volume bar characters
j=8;
while(j--)
{
for (i = 0; i < 8; i++)
{
if (i >= j)
lcd_data1f();
else
lcd_data00();
}
}

// if(!info_flag)
// lcd_clrline(LCD_LINES - 1);
// else
Vlcd_gotoxy(0, LCD_LINES - 1);

  #if (LCD_LINE_LENGTH > 16)
Vlcd_progputs(PSTR("Volume "));
  #else
Vlcd_progputs(PSTR("Vol"));
  #endif
for (i=0; i < 8; i++) // write volume bar
{
if(MIN_VOLUME - v >= i * (VOL_STEP*(NUM_VOL_STEPS/8)))
Vlcd_putchar(i);
else
Vlcd_putchar(' ');
}
if (v < 20) Vlcd_putchar(' ');
if (v > 1)
Vlcd_putchar('-');
else
Vlcd_putchar(' ');
lprintf("%udB",v/2);
}

 #else //GRAPH_LCD

Thanks all for your help.

9
Hardware / Re: Y3/USB IR Remote Problems!
« on: 10.05.2006 at 13:07:51 »
I have done a little digging a found the kenwood remotes use the following format. Checks with the scope prove this is about right.

The Kenwood remote control is based on the Space-Coding scheme. It is a 32-bit code sent on a 39.2 kHz IR wave. The signal is started by a header which is pulse for 16T followed by a space for 8T where T is 550 us. Following the header is the address and the command which consists of logical zeros and logical ones. Logical ones are represented by a T pulse followed by a 3T space. Logical zeroes are represented by a T pulse followed by a T space. As long as the button is depressed this command will continue to repeat. When the button is released the remote sends a stop command represented by a 16T pulse followed by a 4T space followed by a T pulse. The space between each transmission is 95 ms.

Can anyone tell me if this would be difficult to implement in the control.c file on the Y3? Would there be enough room for the code or would some other options need to be removed from the build?

Thanks


10
Hardware / Y3/USB IR Remote Problems!
« on: 09.05.2006 at 11:19:32 »
Hi,

I am trying to get a kenwood IR remote control working with my Y3/USB. I have read many of the other topics on remotes but cant seem to get it working. I have managed to get it working with an old TV remote so I know the ir receiver on the Y3 is working fine.

Why I try to setup the Y3 with any of the kenwood remotes it is detected as RC-5. But then when it asks you to press the play button the hex code changes everytime. At first i wondered if some code hopping was being used but then I connected a DSO to the ir receiver and noticed the code doesnt change. It seems the Y3 is incorrectly detecting it as a RC-5 remote when it isnt.

Has anyone any ideas or anything that may help in getting the Y3 to work with these remotes. I would like to stay with these as I have 2 of the steering wheel and one card remote so replacing them would be expensive!

The remotes are the following: KCA-RC700 and KCA-RC6A

RC700:


RC6A:



Thanks in advance!

Pages: [1]