Accelerometer | ADC | ADXL | Adxl20 | AVR | BasicStamp | BX-35 | BX28 | BX35 | COM3 | Compiler | Downloader | EEPROM | Electromagnet | GetADC | GP2D1 | GPS | I2C | IDE | Keypad | LCD | LCD+ | MIDI | Motors | Multitasking | Netmedia | Networking | PCB | PID | PlaySound | PWM | Relays | RTC | Servo | ShiftOut | SitePlayer | SPI | Stack | Timer | USB

HI

Not sure if this is the right place but here it goes:

I'm trying to expand the capabilities for the wired remote control for
an Archos Multimedia Jukebox (JBM20). The main unit (juskebox) talks
to the remote via two wires (a PIC16LF627). One of the cables connects
to the hardware TX (haven´t found the other yet). I want´t to steal
some of the data with the basicx and forward it to a bigger LCD (also
send some commands to the host unit)

I have had a look at the signal transmitted with an oscilloscope and
definetly there's something going. The problem is how can I find the
type of communications? I2C, SPI, RS232... the cable lenght is about
40cm so I would think serial comms but... so far I haven´t been able
to make sense on any of the data.

Has someone got experience in something similar?

Thanks

Ed
	

(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )

You will need to find the other wire to get a sure answer.
   
  If it is a ground wire, then you have serial (possibly 1Wire ?) comms.
   
  If ground was implied, and the second is a clock, it could be I2C.
  If it is not a clock, could be two way serial.

  SPI requires a MOSI, MISO, CLK, and /CS.  Too many wires.
   
  If it is serial (which seems likely), you can always use the BasicX's InputCapture
command to figure out the baud rate.  
   
  Thad
  
Ed <esteyezz@este...> wrote:
    <snip>
   
  The main unit (juskebox) talks to the remote via two wires (a PIC16LF627). One of the
cables connects
to the hardware TX (haven´t found the other yet). I want´t to steal some of the data with
the basicx and forward it to a bigger LCD 
   
  <snip>
   
  type of communications? I2C, SPI, RS232...
   
  <snip>
	---------------------------------
	[Non-text portions of this message have been removed]
	

(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )

Ed,

I was thinking about doing the same thing ... ok sort of, I was planning on
creating an IRDA interface to the JBM20 to a Palm PDA. Controlling and
displaying the JBM20 from the PDA.

Shoot me an email!

Keith

-----Original Message-----
From: basicx@basi... [mailto:basicx@basi...]On Behalf Of
Ed
Sent: Wednesday, March 08, 2006 2:57 PM
To: basicx@basi...
Subject: [BasicX] uC comms decoding
	HI

Not sure if this is the right place but here it goes:

I'm trying to expand the capabilities for the wired remote control for
an Archos Multimedia Jukebox (JBM20). The main unit (juskebox) talks
to the remote via two wires (a PIC16LF627). One of the cables connects
to the hardware TX (haven´t found the other yet). I want´t to steal
some of the data with the basicx and forward it to a bigger LCD (also
send some commands to the host unit)

I have had a look at the signal transmitted with an oscilloscope and
definetly there's something going. The problem is how can I find the
type of communications? I2C, SPI, RS232... the cable lenght is about
40cm so I would think serial comms but... so far I haven´t been able
to make sense on any of the data.

Has someone got experience in something similar?

Thanks

Ed
	Yahoo! Groups Links
	

(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )

Hi

Yes, there're two wires plus ground. the signal I see with the oscope
doesn't look like a clock, it seems much more like streams of data
(they look pretty much like serial).

I didn't thought about inputcapture, good idea!! 

will update my results

Thanks

Ed

--- In basicx@basi..., Thad Larson <highwayman_33402@...> wrote:
>
> You will need to find the other wire to get a sure answer.
>    
>   If it is a ground wire, then you have serial (possibly 1Wire ?) comms.
>    
>   If ground was implied, and the second is a clock, it could be I2C.
>   If it is not a clock, could be two way serial.
> 
>   SPI requires a MOSI, MISO, CLK, and /CS.  Too many wires.
>    
>   If it is serial (which seems likely), you can always use the
BasicX's InputCapture command to figure out the baud rate.  
>    
>   Thad
>   
> Ed <esteyezz@...> wrote:
>     <snip>
>    
>   The main unit (juskebox) talks to the remote via two wires (a
PIC16LF627). One of the cables connects
> to the hardware TX (haven´t found the other yet). I want´t to steal
some of the data with the basicx and forward it to a bigger LCD 
>    
>   <snip>
>    
>   type of communications? I2C, SPI, RS232...
>    
>   <snip>
> 
> 			
> ---------------------------------
>  
> 
> [Non-text portions of this message have been removed]
>
	

(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )

Found some more info. It is a TTL serial comms. No comes the hard
work, to make sense of the data.

Ed
	--- In basicx@basi..., "Keith McKibbin" <kmckibbin@...> wrote:
>
> Ed,
> 
> I was thinking about doing the same thing ... ok sort of, I was
planning on
> creating an IRDA interface to the JBM20 to a Palm PDA. Controlling and
> displaying the JBM20 from the PDA.
> 
> Shoot me an email!
> 
> Keith
> 
> -----Original Message-----
> From: basicx@basi... [mailto:basicx@basi...]On Behalf Of
> Ed
> Sent: Wednesday, March 08, 2006 2:57 PM
> To: basicx@basi...
> Subject: [BasicX] uC comms decoding
> 
> 
> HI
> 
> Not sure if this is the right place but here it goes:
> 
> I'm trying to expand the capabilities for the wired remote control for
> an Archos Multimedia Jukebox (JBM20). The main unit (juskebox) talks
> to the remote via two wires (a PIC16LF627). One of the cables connects
> to the hardware TX (haven´t found the other yet). I want´t to steal
> some of the data with the basicx and forward it to a bigger LCD (also
> send some commands to the host unit)
> 
> I have had a look at the signal transmitted with an oscilloscope and
> definetly there's something going. The problem is how can I find the
> type of communications? I2C, SPI, RS232... the cable lenght is about
> 40cm so I would think serial comms but... so far I haven´t been able
> to make sense on any of the data.
> 
> Has someone got experience in something similar?
> 
> Thanks
> 
> Ed
> 
> 
> 
> 
> 
> 
> 
> Yahoo! Groups Links
>
	

(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )

>Now comes the hard work, to make sense of the data.
> Ed
	That might not be as bad as you think.  Unless there is a specific
reason to do so, most hardware/software developers don't try to
re-invent the wheel with every new project.  I suspect that the serial
communications you are seeing is standard format.  

Try getting that TTL level signal into a PC serial port.  The easiest
and most reliable way would be to use a MAX232 level converter.  

Once you can do that, you can just keep listening and changing serial
port settings until you get something useful.  

There's always the chance that the format is completely proprietary,
but I believe that chance is very small.

-Don
	

(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )

I was thinking more using Basicx to listen in one of the pins and then
output whatever to the HW serial port, assuming that the info I'm
looking for (song's name, folders, etc) is in ASCII code.
	--- In basicx@basi..., "psyclopedia" <psyclopedia@...> wrote:
>
> >Now comes the hard work, to make sense of the data.
> > Ed
> 
> 
> That might not be as bad as you think.  Unless there is a specific
> reason to do so, most hardware/software developers don't try to
> re-invent the wheel with every new project.  I suspect that the serial
> communications you are seeing is standard format.  
> 
> Try getting that TTL level signal into a PC serial port.  The easiest
> and most reliable way would be to use a MAX232 level converter.  
> 
> Once you can do that, you can just keep listening and changing serial
> port settings until you get something useful.  
> 
> There's always the chance that the format is completely proprietary,
> but I believe that chance is very small.
> 
> -Don
>
	

(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )