IT WORKS!!!
-
:Atlantys does the Crazily-Happy Dance: :jig: :jig: :jig: :jig: (I might as well just throw in a few more) :jig: :jig: :jig: :jig: Our fourth-year design project, the Mother of all projects at our school, and hell that spans 3 terms, FINALLY works now. :insert super-smiley: We got the last bit of code to work today. Now, it's just the major documentation X| X| X| and, of course, the presentation. Fortunetaly, that's not my job :-D: I was assigned the job of "software guy", and they other 3 were in charge of the hardware and docs. We designed an RDS (i think it's popular in Europe, but not really in NA) receiver that would sync, decode, and display the data on a PIC18 board. Sure, there are a few sites out there where people have done the already, and it's not exactly the most complex thing in the world, but it was a b*tch for us, so we're just happy it works and *we* got it to work. :-D Especially since this was my first foray into real assembly programming (we had a course on it, but that was just simple things). My groupmates know that I like to code when I can (who doesn't!?), but in their hardware-oriented minds, all software coders are the same. Since I know C++, therefore, I know all programming languages. It was a losing battle to explain that I can't just 'pick up assembly and do the project' in 2 days. Oh well, I struggled and struggled, but now IT WORKS!!! I'm just sitting here, grinning that we actually got it *done*. Especially after two of my group mates decided that they wanted to go away this week and leave the 'Get It To Work' part of the project to me. :mad: They all owe some :beer::beer::beer: I apologize to anyone who has no idea what I'm talking about. In short: I'm happy now. So, come rejoice in a few :beer:s with me! :-D:-D They didn't understand what they were doing. [Tombstone of the human race]
-
:Atlantys does the Crazily-Happy Dance: :jig: :jig: :jig: :jig: (I might as well just throw in a few more) :jig: :jig: :jig: :jig: Our fourth-year design project, the Mother of all projects at our school, and hell that spans 3 terms, FINALLY works now. :insert super-smiley: We got the last bit of code to work today. Now, it's just the major documentation X| X| X| and, of course, the presentation. Fortunetaly, that's not my job :-D: I was assigned the job of "software guy", and they other 3 were in charge of the hardware and docs. We designed an RDS (i think it's popular in Europe, but not really in NA) receiver that would sync, decode, and display the data on a PIC18 board. Sure, there are a few sites out there where people have done the already, and it's not exactly the most complex thing in the world, but it was a b*tch for us, so we're just happy it works and *we* got it to work. :-D Especially since this was my first foray into real assembly programming (we had a course on it, but that was just simple things). My groupmates know that I like to code when I can (who doesn't!?), but in their hardware-oriented minds, all software coders are the same. Since I know C++, therefore, I know all programming languages. It was a losing battle to explain that I can't just 'pick up assembly and do the project' in 2 days. Oh well, I struggled and struggled, but now IT WORKS!!! I'm just sitting here, grinning that we actually got it *done*. Especially after two of my group mates decided that they wanted to go away this week and leave the 'Get It To Work' part of the project to me. :mad: They all owe some :beer::beer::beer: I apologize to anyone who has no idea what I'm talking about. In short: I'm happy now. So, come rejoice in a few :beer:s with me! :-D:-D They didn't understand what they were doing. [Tombstone of the human race]
Woohoo!! Congratulations! :-D I had to do that for uni last year. Mine was a DSP-based project that scanned an image of a bank note ($5, $10 etc) and had to recognise what it was. I was really happy when I got that to work, and ended up with a 88% recognition rate :-D. I used mostly C, but the time-critical stuff was all in assembly. I had to write a delay function that was accurate to the nearest microsecond :omg:, which caused a bit of agony for a while, but I got it working eventually :) You're lucky you had other people to help. I had to do the whole lot myself, but loved it :-D
Ryan
"Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"
-
Woohoo!! Congratulations! :-D I had to do that for uni last year. Mine was a DSP-based project that scanned an image of a bank note ($5, $10 etc) and had to recognise what it was. I was really happy when I got that to work, and ended up with a 88% recognition rate :-D. I used mostly C, but the time-critical stuff was all in assembly. I had to write a delay function that was accurate to the nearest microsecond :omg:, which caused a bit of agony for a while, but I got it working eventually :) You're lucky you had other people to help. I had to do the whole lot myself, but loved it :-D
Ryan
"Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"
Ryan Binns wrote: Congratulations! Thanks! :-D Ryan Binns wrote: I had to do the whole lot myself :omg::omg: If they had taught us ANYTHING about this topic at school (I know other school have courses that include RDS) then it would be been much easier. We learnt most of the RDS stuff from the standard (such dry reading) and from tech journals. Looking back at we did, I can see a single person doing this. But there was NO way *I* would have been able to do it in the time we had (<12 weeks), especially since we had labs and midterms in there, and I had to look for a job... It all came down to about 2 weeks of work. We spent about a month just getting the pre-project documentation done (A month! :wtf::wtf: ), conforming the insane (and other words I won't use, since my kid sister is looking over my shoulder) "guidelines"! Ryan Binns wrote: accurate to the nearest microsecond X| For us, every 842uS, 104bits of data get sent, and we have to process that and convert those bits encoded in the stream into ASCII values to be displayed on the LCD. That was a b*tch trying to get it to work in a time-critical environment. Writing it wasn't hard. Getting it to work in the time I needed it, was. X| I prefer to wear gloves when using it, but that's merely a matter of personal hygiene [Roger Wright on VB] Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning. [Rich Cook]
-
Ryan Binns wrote: Congratulations! Thanks! :-D Ryan Binns wrote: I had to do the whole lot myself :omg::omg: If they had taught us ANYTHING about this topic at school (I know other school have courses that include RDS) then it would be been much easier. We learnt most of the RDS stuff from the standard (such dry reading) and from tech journals. Looking back at we did, I can see a single person doing this. But there was NO way *I* would have been able to do it in the time we had (<12 weeks), especially since we had labs and midterms in there, and I had to look for a job... It all came down to about 2 weeks of work. We spent about a month just getting the pre-project documentation done (A month! :wtf::wtf: ), conforming the insane (and other words I won't use, since my kid sister is looking over my shoulder) "guidelines"! Ryan Binns wrote: accurate to the nearest microsecond X| For us, every 842uS, 104bits of data get sent, and we have to process that and convert those bits encoded in the stream into ASCII values to be displayed on the LCD. That was a b*tch trying to get it to work in a time-critical environment. Writing it wasn't hard. Getting it to work in the time I needed it, was. X| I prefer to wear gloves when using it, but that's merely a matter of personal hygiene [Roger Wright on VB] Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning. [Rich Cook]
Atlantys wrote: <12 weeks Aaah. I had a lot longer. I had the whole uni year to do it :) Atlantys wrote: Writing it wasn't hard. Getting it to work in the time I needed it, was Ditto :) But I got used to it in the end (I think I knew the entire instruction set by heart :~ )
Ryan
"Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"
-
:Atlantys does the Crazily-Happy Dance: :jig: :jig: :jig: :jig: (I might as well just throw in a few more) :jig: :jig: :jig: :jig: Our fourth-year design project, the Mother of all projects at our school, and hell that spans 3 terms, FINALLY works now. :insert super-smiley: We got the last bit of code to work today. Now, it's just the major documentation X| X| X| and, of course, the presentation. Fortunetaly, that's not my job :-D: I was assigned the job of "software guy", and they other 3 were in charge of the hardware and docs. We designed an RDS (i think it's popular in Europe, but not really in NA) receiver that would sync, decode, and display the data on a PIC18 board. Sure, there are a few sites out there where people have done the already, and it's not exactly the most complex thing in the world, but it was a b*tch for us, so we're just happy it works and *we* got it to work. :-D Especially since this was my first foray into real assembly programming (we had a course on it, but that was just simple things). My groupmates know that I like to code when I can (who doesn't!?), but in their hardware-oriented minds, all software coders are the same. Since I know C++, therefore, I know all programming languages. It was a losing battle to explain that I can't just 'pick up assembly and do the project' in 2 days. Oh well, I struggled and struggled, but now IT WORKS!!! I'm just sitting here, grinning that we actually got it *done*. Especially after two of my group mates decided that they wanted to go away this week and leave the 'Get It To Work' part of the project to me. :mad: They all owe some :beer::beer::beer: I apologize to anyone who has no idea what I'm talking about. In short: I'm happy now. So, come rejoice in a few :beer:s with me! :-D:-D They didn't understand what they were doing. [Tombstone of the human race]
-
:Atlantys does the Crazily-Happy Dance: :jig: :jig: :jig: :jig: (I might as well just throw in a few more) :jig: :jig: :jig: :jig: Our fourth-year design project, the Mother of all projects at our school, and hell that spans 3 terms, FINALLY works now. :insert super-smiley: We got the last bit of code to work today. Now, it's just the major documentation X| X| X| and, of course, the presentation. Fortunetaly, that's not my job :-D: I was assigned the job of "software guy", and they other 3 were in charge of the hardware and docs. We designed an RDS (i think it's popular in Europe, but not really in NA) receiver that would sync, decode, and display the data on a PIC18 board. Sure, there are a few sites out there where people have done the already, and it's not exactly the most complex thing in the world, but it was a b*tch for us, so we're just happy it works and *we* got it to work. :-D Especially since this was my first foray into real assembly programming (we had a course on it, but that was just simple things). My groupmates know that I like to code when I can (who doesn't!?), but in their hardware-oriented minds, all software coders are the same. Since I know C++, therefore, I know all programming languages. It was a losing battle to explain that I can't just 'pick up assembly and do the project' in 2 days. Oh well, I struggled and struggled, but now IT WORKS!!! I'm just sitting here, grinning that we actually got it *done*. Especially after two of my group mates decided that they wanted to go away this week and leave the 'Get It To Work' part of the project to me. :mad: They all owe some :beer::beer::beer: I apologize to anyone who has no idea what I'm talking about. In short: I'm happy now. So, come rejoice in a few :beer:s with me! :-D:-D They didn't understand what they were doing. [Tombstone of the human race]
Congratulations! <old_college_war_story> When I was in school, my lab partner and I had a devil of a time finishing a project. He designed the hardware, I designed the software. Finally, over one weekend, he finished building the hardware. Monday through Wednesday, we spent evenings debugging the hardware, and getting most of the software working. Thursday, I skipped classes, and worked all night getting the software finished. I got the project checked off by the professor around noon on Friday. (here's the good part) It just so happens that Friday was our annual 'May Daze' festival, which consisted of (1) beer, (2) loud music, (3) naked people, (4) more beer, etc. I knew Paul would be out there, so I went and found him and told him our project was checked off. He suggested we celebrate. Five hours later, after an indeterminate number of beers (and no sleep or food to speak of in over 24 hours), I was leaning out the door of my car in the school parking lot, puking my guts out. It was the best feeling in the world. We'd finally finished the hardest project we'd ever done. </old_college_war_story> :cool:
Software Zen:
delete this; -
Congratulations! <old_college_war_story> When I was in school, my lab partner and I had a devil of a time finishing a project. He designed the hardware, I designed the software. Finally, over one weekend, he finished building the hardware. Monday through Wednesday, we spent evenings debugging the hardware, and getting most of the software working. Thursday, I skipped classes, and worked all night getting the software finished. I got the project checked off by the professor around noon on Friday. (here's the good part) It just so happens that Friday was our annual 'May Daze' festival, which consisted of (1) beer, (2) loud music, (3) naked people, (4) more beer, etc. I knew Paul would be out there, so I went and found him and told him our project was checked off. He suggested we celebrate. Five hours later, after an indeterminate number of beers (and no sleep or food to speak of in over 24 hours), I was leaning out the door of my car in the school parking lot, puking my guts out. It was the best feeling in the world. We'd finally finished the hardest project we'd ever done. </old_college_war_story> :cool:
Software Zen:
delete this;Gary R. Wheeler wrote: I was leaning out the door of my car in the school parking lot, puking my guts out. It was the best feeling in the world Believe me, once we hand this thing in, I'll be downing much more than a few Mooseheads (:beer:). :-D I prefer to wear gloves when using it, but that's merely a matter of personal hygiene [Roger Wright on VB] Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning. [Rich Cook]
-
Ryan Binns wrote: Congratulations! Thanks! :-D Ryan Binns wrote: I had to do the whole lot myself :omg::omg: If they had taught us ANYTHING about this topic at school (I know other school have courses that include RDS) then it would be been much easier. We learnt most of the RDS stuff from the standard (such dry reading) and from tech journals. Looking back at we did, I can see a single person doing this. But there was NO way *I* would have been able to do it in the time we had (<12 weeks), especially since we had labs and midterms in there, and I had to look for a job... It all came down to about 2 weeks of work. We spent about a month just getting the pre-project documentation done (A month! :wtf::wtf: ), conforming the insane (and other words I won't use, since my kid sister is looking over my shoulder) "guidelines"! Ryan Binns wrote: accurate to the nearest microsecond X| For us, every 842uS, 104bits of data get sent, and we have to process that and convert those bits encoded in the stream into ASCII values to be displayed on the LCD. That was a b*tch trying to get it to work in a time-critical environment. Writing it wasn't hard. Getting it to work in the time I needed it, was. X| I prefer to wear gloves when using it, but that's merely a matter of personal hygiene [Roger Wright on VB] Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning. [Rich Cook]
I love hearing good old fashoned assembly language war stories :) My first EUREKA! was on an old 8-bit Atari 800. By trapping the vertical blank interrupt (when the TV electron beam was finished its sweep and moving back up to the top) you had some 20 6502 clock cycles to fool around with some register bits and I was able to get that old Atari 800 to display 256 colors at the same time.
I'm going to live forever or die trying!
-
:Atlantys does the Crazily-Happy Dance: :jig: :jig: :jig: :jig: (I might as well just throw in a few more) :jig: :jig: :jig: :jig: Our fourth-year design project, the Mother of all projects at our school, and hell that spans 3 terms, FINALLY works now. :insert super-smiley: We got the last bit of code to work today. Now, it's just the major documentation X| X| X| and, of course, the presentation. Fortunetaly, that's not my job :-D: I was assigned the job of "software guy", and they other 3 were in charge of the hardware and docs. We designed an RDS (i think it's popular in Europe, but not really in NA) receiver that would sync, decode, and display the data on a PIC18 board. Sure, there are a few sites out there where people have done the already, and it's not exactly the most complex thing in the world, but it was a b*tch for us, so we're just happy it works and *we* got it to work. :-D Especially since this was my first foray into real assembly programming (we had a course on it, but that was just simple things). My groupmates know that I like to code when I can (who doesn't!?), but in their hardware-oriented minds, all software coders are the same. Since I know C++, therefore, I know all programming languages. It was a losing battle to explain that I can't just 'pick up assembly and do the project' in 2 days. Oh well, I struggled and struggled, but now IT WORKS!!! I'm just sitting here, grinning that we actually got it *done*. Especially after two of my group mates decided that they wanted to go away this week and leave the 'Get It To Work' part of the project to me. :mad: They all owe some :beer::beer::beer: I apologize to anyone who has no idea what I'm talking about. In short: I'm happy now. So, come rejoice in a few :beer:s with me! :-D:-D They didn't understand what they were doing. [Tombstone of the human race]
Congratulations! I remember well the joy of seeing my first project work exactly as designed... There's nothing quite like that feeling.:-D
"The Lion shall lie down with the Lamb;
but the Lamb will not get much sleep..."
Lazarus Long