Baud rate for noble diagnosis software
Discussion
I think you'll find that the Baud Rate is set by the app, not via windows. If you check the app you'll notice you any only select which COM: port to use; you can't select the baud, which therefore implies that it sets it ( which of course it would have it ).
Also, if you had to set it via Windows control panel then logically you would also have to set:
7 or 8 data bits
1 or 2 stop bits
odd or even parity
Also, if you had to set it via Windows control panel then logically you would also have to set:
7 or 8 data bits
1 or 2 stop bits
odd or even parity
Briefly;
Several parameters are used in relation to serial comms :
a) Baud Rate ; i.e. bits per second, including the start bit, stop bit(s) and parity bit.
9600 is the most common speed, 19.2k or 4800 the next.
b) Start bit; signals the start of transmission, this is almost always one bit, but can be two
c) Stop bits(s) ; normally one bit is used to mark the end of transmission of the byte ( sometimes 2 are used on very old equipment )
d) Parity bit; either odd, even or none. When a byte of data is transmitted, the number of high bits is counted and a further parity bit is appended so that the number of high bits is either always odd, always even or not used. This acts as a crude, but reasonable error check on the data transmission
That covers settings, but there are also electrical connections to consider. For RS232, you have a transmit line and a receive line at TTL levels ( 0-5V ). But, you also have other control signals which may or may not be used. The most common are RTS ( ready to send ) and CTS ( clear to send ). These act as handshaking controls between the two devices. The configuration of these also changes depending on whether the devices are DCE or DTE ( data carrier equipment or data terminal equipment ). Pins 2 & 3 are for data ( transmit and receive ) on a 9 pin connection, pins 7 & 8 are CTS and RTS ( these are sometimes configured but then linked at the master device ). Then you need a 0V reference, which is pin 5. There are others as well, but these are generally not used.
So, that's a very quick lesson on serial comms. The point I'm making is that back in old days of serial comms ( with devices using UART chips to communicate ), all these things had to be set correctly, otherwise comms would not work. But, now we have USB, all this stuff pretty much goes out of the window and is not applicable. That's great for devices which use USB, but not great for devices which use conventional serial, such as, in our case, the ECU.
Now, you can buy USB to serial converters which attempt to replicate as much of the above as they can. But, some do it better than others, some don't.
Further, the parameters in the ECU ( baud rate, parity etc ) are fixed, so it makes sense that in the Noble ECU software you have no options to change them, that's why you can't. The application changes them for you ( normally, it would set them once at start up ). If you start fiddling around with them in Windows then it's even more likely that things wont work. Also, if the app changes them, it's highly likely that if you use windows to check what they are, that windows will not report them correctly anyway so looking in windows control panel is a waste of time.
So, to conclude; if you are using a serial to USB converter then dont be at all surprised if it dont work !
Several parameters are used in relation to serial comms :
a) Baud Rate ; i.e. bits per second, including the start bit, stop bit(s) and parity bit.
9600 is the most common speed, 19.2k or 4800 the next.
b) Start bit; signals the start of transmission, this is almost always one bit, but can be two
c) Stop bits(s) ; normally one bit is used to mark the end of transmission of the byte ( sometimes 2 are used on very old equipment )
d) Parity bit; either odd, even or none. When a byte of data is transmitted, the number of high bits is counted and a further parity bit is appended so that the number of high bits is either always odd, always even or not used. This acts as a crude, but reasonable error check on the data transmission
That covers settings, but there are also electrical connections to consider. For RS232, you have a transmit line and a receive line at TTL levels ( 0-5V ). But, you also have other control signals which may or may not be used. The most common are RTS ( ready to send ) and CTS ( clear to send ). These act as handshaking controls between the two devices. The configuration of these also changes depending on whether the devices are DCE or DTE ( data carrier equipment or data terminal equipment ). Pins 2 & 3 are for data ( transmit and receive ) on a 9 pin connection, pins 7 & 8 are CTS and RTS ( these are sometimes configured but then linked at the master device ). Then you need a 0V reference, which is pin 5. There are others as well, but these are generally not used.
So, that's a very quick lesson on serial comms. The point I'm making is that back in old days of serial comms ( with devices using UART chips to communicate ), all these things had to be set correctly, otherwise comms would not work. But, now we have USB, all this stuff pretty much goes out of the window and is not applicable. That's great for devices which use USB, but not great for devices which use conventional serial, such as, in our case, the ECU.
Now, you can buy USB to serial converters which attempt to replicate as much of the above as they can. But, some do it better than others, some don't.
Further, the parameters in the ECU ( baud rate, parity etc ) are fixed, so it makes sense that in the Noble ECU software you have no options to change them, that's why you can't. The application changes them for you ( normally, it would set them once at start up ). If you start fiddling around with them in Windows then it's even more likely that things wont work. Also, if the app changes them, it's highly likely that if you use windows to check what they are, that windows will not report them correctly anyway so looking in windows control panel is a waste of time.
So, to conclude; if you are using a serial to USB converter then dont be at all surprised if it dont work !
I can see the ecu as it always operates for about the first 5 seconds of plugging it in to my computer. When i say it freezes i mean the data on the screen freezes. Not the program as it still operating but everything just remains the same. If i blip the throttle it is not shown.
Cheers snuffy, so you don't think it'll be worth messing around then?
Cheers snuffy, so you don't think it'll be worth messing around then?
noble1978 said:
I can see the ecu as it always operates for about the first 5 seconds of plugging it in to my computer. When i say it freezes i mean the data on the screen freezes. Not the program as it still operating but everything just remains the same. If i blip the throttle it is not shown.
Cheers snuffy, so you don't think it'll be worth messing around then?
I'm sorry if that came over as a bit of a lecture, it's just that serial comms used to be my thing a few years ago for work and I got carried away typing !Cheers snuffy, so you don't think it'll be worth messing around then?
Your best bet is to try another USB/Serial adapter.
snuffy said:
ThatPhilBrettGuy said:
snuffy said:
Your best bet is to try another USB/Serial adapter.
Or even better, if the laptop has a PCMCIA slot a card based one.http://www.brainboxes.com/product/pcmcia/PM-132.as...
Gassing Station | Noble | Top of Page | What's New | My Stuff