Shop OBEX P1 Docs P2 Docs Learn Events
Video Overlay - Page 2 — Parallax Forums

Video Overlay

2»

Comments

  • TimmooreTimmoore Posts: 1,031
    edited 2009-07-03 06:59
    Looking at the driver on hitt and the overlay driver in your test zip file they have different pins configured. The driver in the test zip file assumes pin 0, 1, etc. The one on hitts website uses different pins, you want make sure your hardware matches the code.
  • propwellpropwell Posts: 87
    edited 2009-07-03 07:15
    thanks for your help! But where are they defined in the code? I can't find the lines! Or is it at the DAT-Part OverlayASM?

    OverlayASM   MOV _screenAddr, par
                                  MOV _syncPinMask, #1
                                  MOV _videoPinMask, #2
                                 MOV -genPinMask, #4
    
    


    that's the one from my zip-file! How can i read it from these lines which pins that are? #1=0, #2=1, and #4=2 :?

    And i've got the HITT_Video_Overlay_018, but there is nothing like that!
    Ok. My hardware is connected like that, so i assume that my Test-Zip wouldn't work for me! Can i redefine the Pins in my Test-File?

    Man i'm so confused :S In the attachment is the schematics how i exactly have it connected, now i'm only looking for a piece of code that i could use, without all this GPS-Stuff. I'm never sure if there could not probably be an error in this part of code!

    Thanks to you all!
    631 x 662 - 23K
  • TimmooreTimmoore Posts: 1,031
    edited 2009-07-03 07:40
    There is a couple of places I can see in the driver

    OverlayAsm    MOV _screenAddr,par      ' Get address of screen memory
                  MOV _syncPinMask,#1      ' Sync is on pin P0
                  MOV _videoPinMask,#2     ' Output is on pin P1
                  MOV _genPinMask,#4       ' Output is on pin P2
    
                  ' Setup cnta to use video hardware
                  MOVI ctra,#%000001_111   ' Video PLL x16
                  MOV frqa,VideoFreq       ' Set dot clock to 5.818182 MHz
    
                  ' Setup VSU (initially off)  
                  MOVI vcfg,#%0_00_0_0_0_000 ' Generation off
                  MOVS vcfg,#%0000_0010    ' Use only pin 1 for output
                  MOVD vcfg,#0             ' Use pin group 0  
    
    


    The 1st you found, the 3 lines setting the masks, 1, 2, 4 which are pins 0,1,2
    The 2nd is the last 2 lines above which is setting the video config - the last line is saying a pin group - which is 0-7,8-15,16-23,24-31, the 2nd to last line is giving the pin mask within the group, so in the above code group 0 (0-7), then pin 1 within the group.
  • propwellpropwell Posts: 87
    edited 2009-07-03 07:52
    oh yeah, i got it! Is that all i have to change for getting my test-zip working?

    OverlayAsm    MOV _screenAddr,par      ' Get address of screen memory
                  MOV _syncPinMask,#1      ' Sync is on pin P0
                  MOV _videoPinMask,#2     ' Output is on pin P1
                  MOV _genPinMask,#4       ' Output is on pin P2
    
                  ' Setup cnta to use video hardware
                  MOVI ctra,#%000001_111   ' Video PLL x16
                  MOV frqa,VideoFreq       ' Set dot clock to 5.818182 MHz
    
                  ' Setup VSU (initially off)  
                  MOVI vcfg,#%0_00_0_0_0_000 ' Generation off
                  MOVS vcfg,#%0000_0010    ' Use only pin 1 for output
                  MOVD vcfg,#4             ' Use pin group 0
    


    Ok so for my schematics, i use pin group 2 (16-29), but which pin is the one for the line
    MOVS vcfg,#%0000_0010    ' Use only pin 1 for output
    


    ?

    and how about these lines. I thin _syncPinMask should be Pin22, which is #4194304 am i right? Looks a bit stupid.
    And what are these other masks? Actuallly, i've got something like 4 output-pins (16-19).
    MOV _syncPinMask,#1      ' Sync is on pin P0
                  MOV _videoPinMask,#2     ' Output is on pin P1
                  MOV _genPinMask,#4       ' Output is on pin P2
    



    thanks for your help timmoore, but i'm not yet getting the point !
  • TimmooreTimmoore Posts: 1,031
    edited 2009-07-03 17:19
    There is the equalivalent in the other driver but its done differently
    This is the vcfg config
                  MOVI vcfg,#%0_00_0_0_0_000 ' Generation off
                  MOVS vcfg,#%0000_1100    ' Use pin P18,P19 (2&3 of group 2) for output
                  MOVD vcfg,#2             ' Use pin group 2 (P16-P23)  
    
    


    Using pins 16 and above, the bit mask will be greater than $1ff so it can't be done as an argument to the pasm instruction, so they are defined in variables at the end.
    _syncPinMask             LONG %0000_0000_1000_0000_0000_0000_0000_0000 ' Sync output from EL1883 IC P23 (22)
    _videoPinMask            LONG %0000_0000_0000_1100_0000_0000_0000_0000 ' Video output from propeller (~470Ohm) P18,P196yhn 2 
    _videoSinkPin            LONG %0000_0000_0000_0100_0000_0000_0000_0000 ' Video Sink (darken) pin mask P18
    _genPinsMask             LONG %0000_0000_0000_0011_0000_0000_0000_0000 ' Mask for both generation pins P16,P17
    _genPinSyncMask          LONG %0000_0000_0000_0010_0000_0000_0000_0000 ' Mask for generation sync pin P17
    
    


    So there isn't the instructions needed to set the variables, since they are set in the source file.
    Is there a reason why you couldn't use the driver from terry hitt rather than trying to modify the other driver? The trouble I see is the 2 drivers you different wiring. So to use the driver you are currently using, yo either need to change the wiring or work out the changes to map to the wiring you have. The schematic you show is correct for the version 18 driver but the driver in you zip file is version 12 which has a different schematic at the top.
    I think you need to make sure the schematic and driver match.
  • Ole Man EarlOle Man Earl Posts: 262
    edited 2009-07-03 18:05
    First, you need video input to generate a vertical sync pulse from the lm1881 (lm1883) into p0 of the prop in my case. The video in goes to pin 2 on the ln1881 via a .1 mfd cap used to generate the vertical sync pulse out on pin 1 of the lm1881 who's output goes to p0 of the prop.

    I have my video in/out connected together directly.
    The .1 mfd cap goes from this in/out connection to pin 2 on the lm1881 (or 1883)
    Pin 1 of the lm1881 to P0 of the prop via a 1k series resister unless you use the lm1883 a 3v part, then connect directly
    Then I have a 470 ohm resister from P1 of the prop to the in/out video connector.

    I use "HITT_Video_Overlay_012" for the overlay video on my autopilot.
    I don't think I modified it buy just in case, here is the one I use
  • Phil Pilgrim (PhiPi)Phil Pilgrim (PhiPi) Posts: 23,514
    edited 2009-07-03 19:08
    Hey Earl,

    Just to clarify: pin 1 of the LM1881 is the composite sync (CSYNC) output and is, in fact, the correct pin to use. I think there was some confusion in earlier posts about which sync output to feed the Prop. While it may be possible to use the vertical sync (VSYNC, pin 3), one would probably begin to lose line synchronnization before the field ended and the next VSYNC came along.

    -Phil
  • propwellpropwell Posts: 87
    edited 2009-07-06 09:05
    Hey Phil, Earl and Timmoore,

    thank you very much for your help! Today i tried to adapt the Version 12 (Pins 0-4) to the wiring of version 18 (16,17,18,19,23.. which i use).
    My video-signal (PAL from cam) is shown very good, so that part works [noparse];)[/noparse] But there's still no overlay!
    In the attachment is the program i adapted.

    I'm not sure about the following lines:
    OverlayAsm    MOV _screenAddr,par      ' Get address of screen memory
                  MOV _syncPinMask,#%1000_0000      ' Sync is on pin P23
                  MOV _videoPinMask,#%0000_0100     ' Output is on pin P18
                  MOV _genPinMask,#%0000_1000       ' Output is on pin P19
    


    i know that #%1000_0000 is not 23, but i'm not able to change it to 23, because the error Timmoore mentioned.
    So there is this part of code at the end of my file:
    _syncPinMask             LONG %0000_0000_1000_0000_0000_0000_0000_0000             ' Sync output from EL1883 IC
    _videoPinMask            LONG %0000_0000_0000_1100_0000_0000_0000_0000             ' Video output from propeller (~470Ohm)
    _genPinMask              LONG %0000_0000_0000_0010_0000_0000_0000_0000             ' Sync gen output from propeller (~1K)
    


    I adapted the Pins, but am not sure if this is right. And also: do i have to remove the top-instruction?!? (think it's twice then?)
    also, in Version18, there are the following lines:
    _videoSinkPin            LONG %0000_0000_0000_0100_0000_0000_0000_0000 ' Video Sink (darken) pin mask P18
    _genPinsMask             LONG %0000_0000_0000_0011_0000_0000_0000_0000 ' Mask for both generation pins P16,P17
    _genPinSyncMask          LONG %0000_0000_0000_0010_0000_0000_0000_0000 ' Mask for generation sync pin P17
    


    They don't appear in the Version12!

    I'm very confused about which parts of the drivers i have to use! But i feel like being close to the solution, thanks to you!

    Thank you very much!!
  • TimmooreTimmoore Posts: 1,031
    edited 2009-07-06 17:41
    You want to remove the mov_syncPinMask,.. lines. The variable is initialized to the value you have at the end of the file. The mov instruction is overwriting this value which isn't what you want. Just deleting the line means the variable is set to the value you need. Try commenting out the 3 mov ...Mask,... lines.
  • TharkunTharkun Posts: 67
    edited 2009-07-06 19:20
    propwell said...


    My video-signal (PAL from cam) is shown very good, so that part works [noparse];)[/noparse] But there's still no overlay!

    Hi propwell,

    i think the HITToverlay-version 1.2 doesn't run with PAL, it's only for NTSC, try using HITT_Video_Overlay_017(018).spin
    (or switch you CAM to NTSC output)

    here is a good example with HITT_Video_Overlay_017.spin and source:

    http://forums.parallax.com/forums/default.aspx?f=25&m=202781&g=263040#m263040

    regards from Germany
  • propwellpropwell Posts: 87
    edited 2009-07-06 21:04
    @Timmoore: thanks, do you think this could be the problem?

    @tharkun: hm well, changig to NTSC doesn't work for me, what a petty. Is it possible to change the 017 or 018 to PAL or why do you propose that? In your posted link it is also an NTSC-Cam used!

    I'd be glad to change my existing file to PAL and to "working" [noparse];)[/noparse]

    Thank you everybody,
    Max
  • propwellpropwell Posts: 87
    edited 2009-07-14 17:56
    hey together,

    i now used the programcode of the Propeller_On_Screen_Drone, the HITT-Version 17.
    I can find there several lines with PAL written in it:

    _palModeAddr             RES 1             ' Address of PAL_Mode variable
    _palModeValue            RES 1            ' Hold value in PAL_Mode variable 0=NTSC; 1=PAL generation
    



    in the code there are many points where the palModeValue appears, but i don't know where to change the PAL_Mode variable to 1, instead of 0?

    Can please someone help me?

    Thank you all very much!

    [noparse]:edit:[/noparse] i added the whole project in the attachment. I tried to delete everything that hasn't anything to do with the Overlay ( Like the GPS and the accerometer...)
    When i let it run, i get a flickering white line running repeatently from top to bottom, taking about 1,5 seconds. the source-video seems to be ok!
    man, i feel to be so close, but i can't find where i have to switch it to PAL!

    Post Edited (propwell) : 7/15/2009 10:59:06 AM GMT
  • shanghai_foolshanghai_fool Posts: 149
    edited 2012-01-01 01:42
    Hey,

    It been a long time since I was on here but
    http://orzparts.com/index.php?main_page=product_info&cPath=28&products_id=1243&gclid=CLutrfHCrq0CFQVvhwod_0WqlA
    has the MAX7456 listed for $7.20 now.
    I'm still looking for an easy to use driver.
    I'm building a dual prop system and just need to offload the video. The props have enough to do.
    PS. I measured 85ma current draw.
Sign In or Register to comment.