cupoftea
Advanced Member level 5
Hi,
I dont think i have ever worked on a project where the software engineers didnt endlessly blame the PCB and layout, noise etc, for problems with their comms channels...and hence the reason for their software not working.....
Is there not a "comms channel byte correspondance procedure" to proove beyond doubt that its the hardware thats messing up the software? (ie, messing it up by changing the bits of the bytes due to noise)
Surely all that needs to be done is have a microcontroller on one board, transmit a byte to a micro on the other board...then that micro transmit the byte back, (the byte that it 'thought' it received).....then do this 100000 times.......if every byte sent, correpsonds to every byte received...than that surely confirms that noise in the comms cables is not the problem? (and vice versa)
Why is this not done? why is this not a standard procedure? or is it?
I dont think i have ever worked on a project where the software engineers didnt endlessly blame the PCB and layout, noise etc, for problems with their comms channels...and hence the reason for their software not working.....
Is there not a "comms channel byte correspondance procedure" to proove beyond doubt that its the hardware thats messing up the software? (ie, messing it up by changing the bits of the bytes due to noise)
Surely all that needs to be done is have a microcontroller on one board, transmit a byte to a micro on the other board...then that micro transmit the byte back, (the byte that it 'thought' it received).....then do this 100000 times.......if every byte sent, correpsonds to every byte received...than that surely confirms that noise in the comms cables is not the problem? (and vice versa)
Why is this not done? why is this not a standard procedure? or is it?