Forum Update - Announcement about May 10th, 2018 update and your password.

Newhaven + Matrix Orbital Display with On-board FTDI FT81X Embedded Video Engine

13»

Comments

  • RaymanRayman Posts: 8,532
    edited July 4 Vote Up0Vote Down
    With some quick changes, can now control two 7" LCDs from one SPI bus.
    Getting really close to being done now...

    Prop Info and Apps: http://www.rayslogic.com/
  • What’s an example of needing to LCDs at the same time. I assume since you’re putting this much effort into it that you have an application where you need controls on one screen graphics on another right
  • RaymanRayman Posts: 8,532
    edited July 4 Vote Up0Vote Down
    I'm making a box with 4 touchscreens… Two 7", one 4.3" and one 3.5".

    Box will control two High Voltage Power Supplies. The 7" screens will show details for each supply. 4.3" will show overview. 3.5" will have some buttons (TBD).

    Going to have two SPI busses with 2 screens on each...
    Prop Info and Apps: http://www.rayslogic.com/
  • Nice job I'd like to tryout one of these New Haven's but they are a little pricey 7" $80-$90 range
  • Are you going to take a crack at LVDS
  • How are you using the same SPI bus for multiple EVE2. Are they ID’d?
  • RaymanRayman Posts: 8,532
    edited July 4 Vote Up0Vote Down
    Currently, each display has it's own chip select and power down pins.
    They have interrupt pins too, but I'm not using them because polling looks to be just fine...
    It's the individual CS pins that lets them share the SPI bus.
    I could actually put all 4 displays on one SPI bus...

    LVDS? Maybe when Prop2 comes out...
    I don't have to worry about budget for this particular project...


    Prop Info and Apps: http://www.rayslogic.com/
  • jmgjmg Posts: 11,507
    Rayman wrote: »
    Currently, each display has it's own chip select and power down pins.
    They have interrupt pins too, but I'm not using them because polling looks to be just fine...
    It's the individual CS pins that lets them share the SPI bus.
    I could actually put all 4 displays on one SPI bus...

    I'm not clear here - The picture appears to show one board, and 2 ribbon cables (parallel RGB ?) to LCDs , or are there 2 x EVE2s on that board ?
    Is this one EVE2 per display, or can you work 2 displays from one EVE2 ?
  • An EVE2 is built on the back of each LCD.
  • RaymanRayman Posts: 8,532
    edited July 4 Vote Up0Vote Down
    Think I have it now :) This version demonstrates controls on two independent screens on a single SPI bus.



    I've also made it so that image upload can go to both screens at the same time.
    Want to make it fast to get a splash screen on both screens...


    Prop Info and Apps: http://www.rayslogic.com/
  • Just got this working on a Matrix Orbital 5" LCD (kindly donated to the cause).
    Only had to give it the pixel timings for this particular display. No changes to the driver itself.

    I did have to make a little adapter to go from my IDC header to the FFC connector on the Matrix Orbital display.
    At first, I thought I had the pinout reversed on my FFC connector. Well, I did for regular ffc cable with exposed metal on the same sides.
    But then I noticed that the Matrix Orbital FFC cable has exposed metal on opposite sides on opposite ends of the cable.
    That lets you use the same connector and pinout.
    If I was a little smarter, I would have realized this before spending 3 hours making a 18-pin ffc connector with top contacts work...

    Anyway, this 5" display is kinda nice as it has the full 800x480 resolution.

    The attached example is meant for a single display, not the dual display test from last time...

    Prop Info and Apps: http://www.rayslogic.com/
  • Looks really cool, Ray. Once you start refining code you'd probably do this, anyway -- just a reminder to save a few lines.
    pub start(pSettings, sck, miso, mosi, csn, intn, pdn) | i, j
    
      longmove(@DispWidth, pSettings, 15)
      longmove(@pin_sck, @sck, 6)
    
      { other start code }
    
    Jon McPhalen
    Hollywood, CA
    It's Jon or JonnyMac -- please do not call me Jonny.
  • RaymanRayman Posts: 8,532
    edited July 15 Vote Up0Vote Down
    That's a good idea. This driver is not particularly optimized yet...

    I think I just got the Matrix Orbital 3.8" display working.
    This one is interesting, it's an extra-widescreen format.
    It's 480 pixels wide but only 116 or 117 pixels tall.

    The visible screen spans y locations from about 10 to 125, i.e., top left corner is (0,10) instead of (0,0).
    Maybe I could tweak the display settings to fix that, it might be VSync0 that sets the offset...


    This screen format is interesting...
    Prop Info and Apps: http://www.rayslogic.com/
  • Are you seeing any advantage/differences from the NH and MO products.
  • Well, it's good to have options!

    I haven't done a complete comparison.
    But, the main differences seem to be in the connecting cable and how the screens attach.

    If space is a huge concern then the 0.5mm pitch ffc cable on MO screens is small.
    Otherwise, NH has a IDC and larger pitch FFC cable option.
    I'm using IDC in my big project because they are in a giant box with lots of space and I can make my own IDC cables.

    The MO screens have sticky tape on the back to attach whereas NH has mounting holes.
    Sticky tape is probably easier but maybe mounting holes is more robust.
    MO has bezels but NH does not.

    Most MO screens don't need separate backlight power, they just get it from the 3.3 logic power whereas I think you need to connect backlight power on NH screens. Also, it's better to use 5V for backlight on NH screens as it's more efficient than 3.3 V. The MO efficiency at 3.3V is much better.

    NH is open source hardware, so maybe you could make your own version, perhaps with a prop onboard :)

    NH has several options for each size like daylight readable, premium, low cost. MO has some screen sizes that NH doesn't have.

    So, there are some differences...
    Prop Info and Apps: http://www.rayslogic.com/
Sign In or Register to comment.