"Once every two weeks" is actually "quite frequently" for an individual research project. Your supervisor, probably, just noticed that more often than not you could not tell him much after just one week of work (very few students can, actually) and decided to listen to your "progress report" once in two weeks. If you are really doing your work and aren't just dragged by him through it, this shouldn't slow you down in any way and I bet 10 against 1 that if you get something interesting to tell him tomorrow, he will listen to you the day after tomorrow no matter how far the scheduled meeting date is.
The idea of operating from a "submission deadline" in an unfinished research project looks totally ridiculous to me. The whole difference between a research project and house cleaning is that you never know how much time you'll need for the former and whether you'll be able to pull it through at all. In my own work, the failure to success ratio is 9 to 1 and that is generally considered quite good. You have to learn that things take time and that you may fail completely when doing research. It is normal and there is no reason to freak out about that. Even in the case when you see the general way to do things and are certain that it must work, the "little details" may take forever.
You can request direct help now and then but the request should be not in the form "I just don't know what to do next..." but in the form "I've done this. Now, for the next step I would need something like this. Unfortunately there is this particular obstacle in the approach I am currently pursuing. Do you have an idea of how I can overcome it or I should try a different route altogether?". You supervisor may share the "bird's view" of the road with you (and it is sort of his duty) but to go around trees, to jump over brooks and to climb hills is your job unless you really face an impenetrable thicket, a fast deep river, or a steep mountain on your way). Telling you how to do every little thing every time is no fun for him and takes the most important part of the research experience away from you. Passing the routine work (like programming of a known algorithm) to others is a no-no at your current level. You may "outsource" your own work only when you can do it faster and better yourself, but there is yet another task at hand that nobody else can do at all. You may (and should) seek general information, but not ready solutions to your particular problems even if the latter are as trite as "Why does this stupid while loop stop one step earlier than it should?".
So, my general advice is to relax, to forget about all deadlines, and to proceed on your own and at your own pace however slow it may seem to you. Just don't stop altogether and give up unless you are ready to declare an official failure and quit completely.