The video on the Plus is truly binary monochrome, not greyscale. Without separate sync data, however, you don't know exactly where the start of a frame is, nor where the start of a line is. Video does not possess a guarantee on the density of transitions, so if I have an all-white line of video, for example, there is no way of knowing where the actual pixel boundaries are. So, as I mentioned, unless the display interface possesses rather specialized circuitry, you will need to use more than just the video signal.
And although the video data is binary, you can't easily just "save it to a disk." Again, if I have 99 white pixels in a row, I can't easily distinguish that from 98 or 100 white pixels in a row. That's why you need sync. An alternative would be to oversample the data prior to writing to a disk. You could do the equivalent operation in the FPGA. That's an example of what I mean by "rather specialized circuitry" -- it's not the sort of thing that is normally part of an LCDisplay interface.
And that, in turn, is what makes the project challenging. You will need to figure out how to use the sync signals generated by the Plus.
And although the video data is binary, you can't easily just "save it to a disk." Again, if I have 99 white pixels in a row, I can't easily distinguish that from 98 or 100 white pixels in a row. That's why you need sync. An alternative would be to oversample the data prior to writing to a disk. You could do the equivalent operation in the FPGA. That's an example of what I mean by "rather specialized circuitry" -- it's not the sort of thing that is normally part of an LCDisplay interface.
And that, in turn, is what makes the project challenging. You will need to figure out how to use the sync signals generated by the Plus.