this is my code for serial communication using 8051 iam trying to send letter B on serial port but iam not getting any thig on heperterminal though all setting are ok .so not getting what the problem is.
ORG 000H MOV TMOD,#20H MOV TH1,#0FAH MOV SCON,#50H SETB TR1 MOV A,#'B' ACALL DELAY A_1: MOV SBUF,A H_1: JNB TI, H_1 CLR TI SJMP A_1 DELAY: MOV R0,#255 L1: DJNZ R0,L1 MOV R1,#255 L2: DJNZ R1,L2 RET end
"Such an eengineer is likely to have to spend a significant amount of time explainging why data sheets, product overviews etc are using the above constructs."
That is a false assumption - Re: likely, significant
"Thereby, such an engineer will have a hard time actually engineering."
Therefore, this is a false conclusion.
Training on such details should normally be done when the team is initially built - It should not be needed latterly.
A common word for this is induction.
You can only call an assumption false if you have the proof.
Without proof, you can only claim it to be an unlikely assumption.
Point taken - But there again, you can only claim a statement is true if you have the proof. Until that time it is a theory.
I think you're assumption is incorrect.
My reason - In our team, we DO have induction courses that show how documents, code (and comments) are expected to be done.
In general, team members DO follow the guidelines.
One very important rule we follow is: It is not so important which style the team use, but it is important that everyone is consistent.
"...you can only claim a statement is true if you have the proof. Until that time it is a theory."
Point taken, but that is why i wrote "Such an eengineer is likely to have to spend a significant amount..." Clumsilly, I unintentionally managed to loose the "likely" word in my second sentence.
In Sweden, it is very, very common to talk about an IC circuit. I have at a number of times responded with "Oh, you mean an IC?" just to either see a deer in the headlight, or hear a "yeah". A couple of minutes later, that same "IC circuit" phrase is used again.
Because of this, I have a lot of indication that it is very hard to break bad habits. Upgrading corrections from hints to company policy would be thought of as putting the energy at the wrong things. An R&D unit is better off making sure that the code is testable, maintainable, matching the customer requirements, ...
So, a good engineer can find a large number of areas where the pay-off is better.
"I think you're (sic) assumption is incorrect."
Clearly your induction classes don't include the proper use of apostrophe's (sic)...
;-)
Clearly your induction classes don't include the proper use of apostrophe's
That's normally one I'm quite careful of.
Whoops - Silly me!
"you can only claim a statement is true if you have the proof."
No.
You can claim anything you like - it's getting other people to believe you that tends to require the proof...!
"That's normally one I'm quite careful of."
Or should that be, "That's normally one of which I'm quite careful" ?
Or not?!
Wow, you're good!
For years now, I've been described as fussy, pedantic and having various other similar traits.
I can see now that I am just an amateur ;-)