Wired remote for Alpine


Closed Thread
Results 1 to 39 of 39

Hybrid View

  1. #1
    Join Date
    Dec 2008
    Location
    Ploiesti, ROMANIA
    Posts
    582


    Did you find this post helpful? Yes | No

    Default Re: Wired remote for Alpine

    Still no good news ... Cycle " for ...next" generate a "big" delay ?

  2. #2
    Join Date
    Aug 2008
    Location
    Portugal
    Posts
    240


    Did you find this post helpful? Yes | No

    Default Re: Wired remote for Alpine

    Hi fratello;

    I dind't read the hole thread, but are you trying to reproduce a IV remote control??
    If so, i see on your last post that your reproducing the pulses, but you are not using modulation, and you must use modulation when using IV. Probably 36Khz, or 38Khz, or 40Khz.
    Thanks and Regards;
    Gadelhas

  3. #3
    Join Date
    Oct 2005
    Location
    Sweden
    Posts
    3,612


    Did you find this post helpful? Yes | No

    Default Re: Wired remote for Alpine

    Hi,
    The actual FOR-NEXT construct will add some additional delay due to the fact that it is a jump isntruction and it has to make the comparison. Add to that the execution time of the LOOKUP instruction you're using. Why don't you just measure it and adjust the pulse constant so it matches the capture of the working remote?

    /Henrik.

  4. #4
    Join Date
    Dec 2008
    Location
    Ploiesti, ROMANIA
    Posts
    582


    Did you find this post helpful? Yes | No

    Default Re: Wired remote for Alpine

    Thanks !
    @Gadelhas : I try to build a wired-remote, not IR remote ; I use IR remote just for reading codes, but I intend to use wired - steering wheel - remote.
    @Henrik : Good ideea !!! I will try tomorrow to read MY signal ...by putting one LED to PIC output (?!)

  5. #5
    Join Date
    Dec 2008
    Location
    Ploiesti, ROMANIA
    Posts
    582


    Did you find this post helpful? Yes | No

    Default Re: Wired remote for Alpine

    I make reverse-engineering ... I put one IR-LED on output (driving by transistor) to see how the code work !
    And... surprise ! It's totally different by Proteus simulation and my whis !!!
    Despite I try to "PauseUs 560" the Pauseus, measured in IR_Scope, it's 202 to 208 us !

    I read this : "PAUSEUS assumes an oscillator frequency of 4MHz ;PAUSEUS 1000 ' Delay for 1 millisecond "
    It's not applicable on my code ?! Why ? I use an 4 MHz crystal , I define "XT_OSC" ... I really don't understand ...

  6. #6
    Join Date
    Oct 2005
    Location
    Sweden
    Posts
    3,612


    Did you find this post helpful? Yes | No

    Default Re: Wired remote for Alpine

    Hi,
    Are you sure that it is a 4Mhz and not a 10Mhz crystal?
    Do you have the correct capacitors inplace to load the crystal?

    Try something like
    Code:
    TRISC.0 = 0
    Main:
      PortC.0 = 1
      Pauseus 1000
      PortC.0 = 0
      Pauseus 1000
    Goto Main
    What's the frequency of the output signal?

    /Henrik.

  7. #7
    Join Date
    Dec 2008
    Location
    Ploiesti, ROMANIA
    Posts
    582


    Did you find this post helpful? Yes | No

    Default Re: Wired remote for Alpine

    Unfortunately, I dont have an oscilloscope ...I use just software tools, which are not so accurate !
    I capture the signal with OSCILLOSCOPE V1.40 and it's ok (measuring all pulses and pauses, dont know how accurate)...
    I am in big deadlock ! I don't know what else I can do.
    Attached Images Attached Images  

Members who have read this thread : 1

You do not have permission to view the list of names.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts