SAE Data Acquisition (SAEDAQ)
Contents
1. 17 Appendix B Amulet CommunicCat10ns aa 18 20 Appendix C Amulet lol ee pa WCAG WARS OAZA 21 26 Appendix D Final Microcontroller Coding 1 11112 maa 27 36 SAEDAQ 3 Page Introduction Racing and technology have been partnered together for several decades They have a mutual relationship in which technology helps the car run faster and more efficiently and racing helps expedite the rate of new and better technologies Any driver will tell you that just a few seconds shaved off of their race time can mean the difference between winning and losing a race and that the process of analyzing data taken from their car in a practice run can lead to tweaks and improvements on the car s systems This could be all that 1s needed to give a driver the edge he needs to beat the competition Nowhere in professional racing does one see a driver failing to take advantage of as much technology as they can in order to acquire more data about their cars This project has been attempted in past years but has never been able to develop a fully integrated working system where the next step would be to combine it with the SAE Formula Car Although some concepts have been duplicated from previous years the majority of the hardware and software decisions have been of our own design in order to achieve the goals we had set for our project SAEDAQ 4 Page Hish Level System Block Diagram2. ewitch to ADCZ ADMUX 6 OxFO ADMUX _BV MUXI jelse if sensor 2 sensor U grabs the current value oil temp ADCH convert to the proper ascii transmission values of the ADC byte value oll temp Ll to ascil oll temp gt gt 12 amp Ox0EF oil temp 10 to ascii O11 temp gt gt 89 0x0B oil temp 01 to ascii o1l temp gt gt 4 amp OxOF SAEDAQ 32 Page Oll Temp 00 to 49111011 temp Ux0F 7 switch t ADCO ADMUX 6 OxFO0 ADMUX _BV MUX0 USART1 UDRE vect interrupt for when the UDRO transmit buffer is empty ISR USART1 UDRE vect LE arr Size UCSR1B amp 247 stop transmitter G O Pu F transmit a Li i art Size 4 Iq ISR USART1 RX vect receiver interrupt NOTE In order to function properly the UDR byte must always be read E from in this interrupt otherwise the interrupt will instantly 24 interrupt again upon exiting if UDR1 17 ready 1 int main void DDRC OxFF enable PORTE as an output DDRF 0x00 enable PORTF as an input DDRA OxFF enable PORTA as an output DDRE OxFF kkkkkkkkkkkkkkkkkkkkkkkkkkk ADC SETUP kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk set ref value to Vcc left adjust output to use only ADCH ADMUX BV REFSO _BV ADLAR switch to ADCO ADMUX amp OxFO0 enable AtoD converter start conversion setup free running mode to contiuously update va
3. r r r transm it 39 0 transmit 40 1 jelsel transmit 39 g transmit 40 0 if oil temp gt oil temp max r transmit 44 0 transmit 40 7177 jelsef transmit 44 0 transmit 45 let s if mph gt mph max transmit 49 90 transmite 50 gt 1 gt jelsel transmit 49 p transmrt l50 u if rpm gt max_rpm transmit 54 transmit 55 1 jelsef transmit 54 0 transmiE 55 r r r r r r r stay on default 31 Page ir coolant Lemp gt coolant max Pressire gt pressure max oil temp gt oil temp max mph mph max rpm max rpm jump to warning screen transmit 59 36 transmit 60 58 jelsel jump to default screen transmrt 59 32 transmit 60 62 UCSRIB BV TXEN enable transmitter ADC conversion complete interrupt flag ISR ADC Vect 4 1 sensor 0 1 sensor l grabs the current value coolant temp ADCH convert to the proper ascii transmission values of the ADC byte value gool IL CO ascii Coolant temp 2 gt 2 7 cool 0 tO asclr coolant temp amp Ox0F Jawiteh to ADCI ADMUX 6 OxFO0 ADMUX BV MUX1 jelse if sensor l sensor 2 grabs the current value pressure ADCH convert to the proper ascii transmission values of the ADC byte value pressure LO ascil pressure gt gt 4 pressure 0 TO asell pressure Ux0F 7
4. Figure 5 1 shows a high level system block diagram of our system Analog and digital sensors send data acquired from the formula car to the microcontroller The microcontroller s software processes and formats both the analog and digital data to be sent via RS 232 to the Amulet display for on car viewing as well as the Aerocomm wireless boards The touchscreen displays the real time data with appropriate warning screens to tell the user if any of the values go out of their designated safety range A second wireless board receives the data sent by the microcontroller where it is logged and viewed in real time via a laptop equipped with LabVIEW Wireless board receiver N Wireless board Wireless gt transmitter y 4 Ww Sensors from N Microcontroller formula car N Touch screen Laptop display Figure 5 1 High Level System Block Diagram Microcontroller Written using C code the Mavric IIB development board Figure 6 1 uses the Atmel Atmegal28 microcontroller and processes the analog and digital sensors located on the car The oil temperature oil pressure and coolant temperature are measured with the microcontroller s A D converter These values are scaled into a single byte value with a reference voltage range of 0 2 56 VDC The RPM and wheel speed MPH are measured counting TTL pulses coming from the sensors The values are sent to the Aerocomm wireless board and the LCD touch screen for transmission
5. dag data l2 pressure 1 dag datald pressure 9 oil temp daq data 4 oil temp 11 dag data 5 oi1l temp 10 dag data 6 011 temp 01 dag data 7 011 temp 00 wheel speed daq data 8 mph 11 dag detel9l mph 107 daq data 10 mph 01 dag dartaLLcrjemph 00 RPM dag dertahbt2l rpmsm Ll dag dartall5lerpm 10 daq data 14 rpm 01 daq data 15 rpm 00 reenable UDRIEO interrupt UCSR B BV UDRIEO 7 if ready 1 if display time 5 SAEDAQ display time 0 i 0 start up transmission array position counter byte O coolant temp eka COOL 17 transmit 4 cool 0 byte 1 oil pressure CLAIM EL pressure 15 cxanemite 9 pressure W fword 0 oil temp teansm c LLl gt 01L temp LL transmit 14 oil temp 10 Lronsmrcllo ceorl TEMP 01 vcransmiciIle sorl teme 007 30 Page Screen SGEES SAEDAQ word 1 transmit transmit transmit 2 2 2 transmit 2 Ka KA 1 MA word 2 RPM JR transmit transmit transmit transmit 7 transmit transmit transmit transmit AS FA FA 27 28 29 EE 21 28 29 301 Ka KA KA MA wheel speed 0 mph 11 L emph 107 2 mph 01 3 mph 00 mph 11 mph 10 mph 01 mph 00 rpm 11 rpm 10 rom 01 rpm 00 if coolant temp coolant max jump to warning byte 5 transmit 34 0 4 transmit 35 i jelsel byte 5 Etransmit 34 0 transmit 35 if pressure gt pressure max
6. 1 wheel speed 214 0 2 0 0 0 0 word 2 engine speed 213 0 5 0 D byte 5 coolant temp warning flag 213 0 6 0 0 byte 6 oil pressure warning flag 213 0 77 0 0 byte 7 oil temp warning flag 8 wheel speed warning flag 213 0 8 0 0 byte 213 0 9 0 0 byte 9 engine speed warning flag 160 2 0 32 62 Jupp to screen lOl send XOFF for end of transmission Figure 20 1 Amulet String Packet An ASCII table has been provided to help users convert what the values are in software coding This ASCII table 1s shown in Figure 20 2 Dec Hx Oct Char Dec Hx Oct Html Chr Dec Hx Oct Html Chr Dec Hx Oct Html Chr O 0 000 NUL null 32 20 040 32 Space 64 40 100 64 B 96 60 140 96 l 1 001 50H start of heading 33 21 04 337 65 41 10 65 A 97 61 141 97 a 2 2 002 STX start of text 34 22 042 34 66 42 102 66 B 98 62 142 98 b 3 3 003 ETX end o text 35 23 043 35 67 43 103 67 C 99 63 143 99 c 4 4 004 EOT end of transmission 36 24 044 6836 68 44 104 68 D 100 64 144 100 d 5 5 005 ENQ enquiry 37 25 045 37 69 45 105 69 E 101 65 145 101 e 6 6 006 ACK acknowledge 38 26 046 30 amp 70 46 106 70 F 102 66 146 102 f 7 7 007 BEL bell 39 27 047 39 7l 47 107 71 G 103 67 147 103 d 8 8 010 BS backspace 40 28 050 40 72 48 110 72 H 104 68 150 104 h 9 9 011 TAB
7. Figure 16 2 a Click the Find Ports button and select the according COM port that the USB is connected to Set the baud rate to 57600 parity to None Handshaking to None data bits to 8 and stop bits to 1 b Make sure that all of the checkboxes in the options tab are checked c Select the appropriate product AC4790 Click on the configure tab this menu shown in Figure 16 1 a For loading the provided EEPROM file proceed to part e For fresh programming proceed to the next part b Click on the Read Radio button at bottom right of the program The EEPROM file should load into the Radio Interface and Radio RF boxes c Change the Interface Baud to 9600 or whatever baud rate you are using d Set the RF packet size ours transmission was 12 bytes so we used 0x0C Proceed to part f e Click on the Load File button and select the location of the file f Click on the Write Radio button If it programs correctly a message should tell the user that 1t programmed correctly The transceivers are now set up to transmit data packet to each other In order to re read or correct programming on the newly programmed chips the baud rate under PC Settings must be changed to the baud rate that was programmed to the chip s EEPROM file If you cannot fully read the antenna s EEPROM after programming repeat steps 3 8 The Range Test tab of the program lets you test null data packets to make s
8. equal THEN function s ELSE function s NAMES string gt One of the earlier widgets that I played around with was the radio button the GEMstudio user s manual gives the definition A Radio Button is a labeled round button used to make a single selection from several options To set a radio button click on either the button or the adjacent label AlI radio buttons that have the same groupName are considered part of a radio button group Only one radio button within a group can be set at any one time When a radio button is selected its function s are called with the argument being the intrinsic value of the radio button Each radio button can invoke its own href function or set of functions The radio button can be set up with other radio buttons so only one can be pressed at a time Right clicking either the widget or its name in the drop down menu on the left SAEDAQ 22 Page opens a dropdown menu Click add remove parameters to open the menu Checking and unchecking the boxes will add remove properties on that individual widget s menu For example say you want a radio button to be a red button when not pressed grayed out when being pressed and then green after it is pressed You would go into the widget s menu and make sure emptyImage trackinglmage and fulllmage were checked The next step would be to then click the plus box next to the individual parameters and add the JPG to the respected parameter Note that if you
9. going on Knowing that the driver will not have his eyes glued to the touchscreen and that there will be plenty of distractions on the race course at any given time we chose numeric fields to display the data in the largest most visible font that could be made Figure 7 1 shows the two states that the touchscreen can be in The first is when there are no warnings and the second for when there 1s a warning due to a sensor going out of spec The contrast between the light blue and red background as well as the inverted colors of the numeric field that goes out of spec are implemented to attempt to catch the driver s attention should they not be looking at the screen at that time 211 Figure 7 1 Final Touchscreen Design The communications between the touchscreen and the microcontroller were not hard to work out because we were able to directly put the data from the microcontroller into the internal RAM of the touchscreen via RS 232 The numeric fields which are coded to take data from specific addresses in the internal RAM then display the data See Appendix D for specifics about the coding process SAEDAQ 7 Page LabVIEW User Interface LabVIEW is a graphical programming language used industry wide for data acquisition and processing control systems and system monitoring In this project LabVIEW provides a graphical user interface for an off track team to monitor the performance of the car Along with displaying the data in real t
10. horizontal tab 4 29 05 s 4l 73 49 111 73 I 105 69 151 105 i 10 A 012 LF NL line feed new line 42 2A 052 42 74 44 112 74 J 106 6A 152 8106 j 11 B 013 YT vertical tab 43 2B 053 43 75 4B 113 75 K 107 6B 153 8107 K 12 C 014 FF NP form feed new page 44 2C 054 44 76 4C 114 76 L 108 6C 154 108 1 13 D 015 CR carriage return 45 2D 055 45 77 ap 115 77 M 109 6D 155 109 m 14 E 016 50 shift out 46 E 056 46 78 4E 116 76 N 110 6E 156 110 n l5 FOL NI shift in 47 2F 057 497 79 4F 117 79 O lll 6F 157 111 o l6 10 020 DLE data link escape 48 30 060 46 0 80 50 120 950 P 112 70 160 112 p 17 11 021 DC1 device control 1 49 31 06 49 1 81 51 121 81 Q 113 71 161 e ll3 d 18 12 022 DC2 device control 2 50 32 062 50 2 82 52 122 02 R 114 72 162 s 114 E 19 13 023 DC3 device control 3 51 33 063 51 3 83 53 123 83 5 1115 73 163 115 3 20 14 024 DC4 device control 4 52 34 064 52 4 84 54 124 54 T 116 74 164 116 t 21 15 025 NAK negative acknowledge 53 35 065 amp 53 5 85 55 125 85 U 117 75 165 117 u 22 l6 026 SYN synchronous idle 54 36 066 54 6 86 56 126 56 V 118 76 166 1186 v 23 17 027 ETB end of trans block 55 37 067 amp 55 7 87 57 127 07 W 119 77 167 amp 119 w 24 18 030 CAN cancel 56 38 070 56 8 88 58 130 58 X 120 78 170 s 120 X 25 19 0
11. same readings were successfully transmitted wirelessly to a PC with the LabVIEW user interface installed LabVIEW updated in real time as well as logged the data to an Excel file specified by the user The overall goal of our project was achieved by being able to take car measurements and by sending those measurements to separate user interfaces for displaying and logging without data loss or mismatched values SAEDAQ 14 Page Appendix A Aerocomm Tutorial The initial setup of the Aerocomm chips was very easy to do The Aerocomm kit comes with two development boards for programming and initializing the AC 4790 transceivers To program the transceivers press the reset button on the development board while it 1s still powered This sets the transceiver to factory default settings so the user can know what baud rate the transceiver is set at l 2 gt U id 10 11 Power on development board Make sure that the AC 4790 1s plugged into the board Press the reset button on the development to make sure the antenna is at factory default settings Make sure that the development board s header cables are all set on the correct values TTL Radio USB Enable 3 3V Radio Normal Evaluation Select the correct power source The most efficient setting 1s to use the external power source The USB can still be plugged in without any problems with this setting Open AerocommOEM exe Select the PC Settings tab this menu shown in
12. use an image with a JPEG extension the compiler will generate an error You need to use an image with JPG Amulet document widgetName buttonDown Amulet document widgetName buttonUp Amulet document widgetName clearCanvas Amulet document widgetName disappear Amulet document widgetName forceHit Amulet document widgetName forceRefresh Amulet document widgetName forceUpdate Amulet document widgetName inverseRegionColor Amulet document widgetName inverseStringColor Amulet document widgetName nextEntry Amulet document widgetName normalRegionColor Amulet document widgetName normalStringColor Amulet document widgetName previousEntry SAEDAQ The named Function Custom Button Widget will appear as if t is currently being touched The named Function Custom Button Widget will appear as if it is currently NOT being touched The named Scribble Dynamic Image Widget clears its canvas including any background images The named widget will clear itself from the LCD f itis a View Widget it will also stop updating The named Control Widget will act as if it was hit The named View Image Sequence Widget will paint the image at the next update even if the incoming value is the same as the current state Useful if an anchor is used around an Image Sequence Widget The named View Widget will act as if it s update rate time was activated Allows for asynchronous updating The named
13. 31 EM end of medium 57 39 071 57 9 89 59 131 89 Y 121 79 171 6 121 Y 26 14 032 SUB substitute 58 3A 072 50 90 5A 132 90 Z l22 74 172 s 1l22 Z 27 1B 033 ESC escape 59 3B 073 6659 91 5B 133 91 123 7B 173 123 28 lC 034 FS file separator 60 3C 074 60 lt 92 5C 134 92 124 7C 174 124 29 ID 035 GS group separator 61 3D O75 61 93 5D 135 93 l25 7D 175 125 30 1E 036 R3 record separator 62 3E 076 amp 62 gt 94 SE 136 94 126 7E 176 126 31 1F 037 US wit separator 63 3F 077 amp 63 95 SF 137 95 127 7F 177 8127 DEL Figure 20 2 ASCII Table SAEDAQ 20 Page Appendix D Amulet Tutorial You can find all the information below and more at Amulet s website at www amulettechnologies com From there a video can be watched that gives a very basic but somewhat helpful example at www amulettechnologies com videos html Clicking the Help Documentation link off the main page brings you to a webpage with several useful links Most important is the USER S GUIDE GEM studio link and the PROGRAMMER S GUIDE GEMcompiler link The former link is where the bulk of the information needed to understand GEMstudio is When you open GEM studio clicking the first menu button will open the project configuration Make sure that the LCD size 1s 480x272 which is the size of the touchscreen we have currently In the Communications tab you can set the protocol ty
14. 7 1 LabVIEW Backpanel 17 Page SAEDAQ Appendix C Amulet Communications Amulet Communications Tutorial In order to communicate with the Amulet screen the RS 232 communication needs to be understood There are two ways to communicate with the Amulet ASCII and CRC For our application we chose the CRC protocol using XON XOFF Unlike the CRC protocol this protocol was simple and did not reguire multi byte handshaking In order to Work in this function the Amulet must be set to slave no response mode In this setting the Amulet only receives the byte packet commands but does not send any information packets back to its sender In the XON XOFF protocol the microcontroller sends its full packet of commands It ends each transmission with the XOFF command 0x13 The Amulet interprets data in the order that it was received When it reaches the last value in the data packet XOFF command it sends the XON command to the microcontroller which tells the microcontroller that the receive buffer 15 empty and ready for receiving again This description is shown in Figure 18 1 If the XON XOFF procedure was not used the Amulet could possibly result in a loss of data since the receive buffer is not cyclic Send Set XON 0x11h Data received Figure 18 1 Amulet Data Packet Transmission using XON XOFF Now that the concept of sending data has been explained example coding of specific Amulet CRC protocol commands will be shown Figure 19 1 sh
15. SAE Data Acquisition SAEDAQ Project Final Report By Caleb Davison George Kontos 8 Phil Jacher Advisor Professor Steven Gutschlag May 7 2011 Abstract The goals for this project are to implement a data acquisition system for the formula racecar built by Bradley University s Society of Automotive Engineers Sensors will be installed on the car to collect data for oil temperature oil pressure coolant temperature RPM and wheel speed A microcontroller will convert the data to digital signals and organize it to be sent out That data will be displayed on an LCD screen mounted to the car dashboard and also wirelessly transmitted to an off track laptop The LCD and the laptop will concurrently display the data in real time The laptop will also have a feature that will save and store the data for further analysis SAEDAQ 2 Page Table of Contents MC OCU CH OT A E E a 4 High Level System Block Di 387311 u a 5 Mieroeontr ller ns daan AO Ali 5 6 AGLOCOMM Wireless BONOAN nA ANA TANA AA AA 6 Touchsereen Display a eine 7 Lab VIEW User Terrace a AA NANANA NANA 8 11 Measurement DISDIA nun 8 GA usina nee 9 10 Data Plotted Versus Teaser 10 BAAROSECIUN Ge ait ete PET 11 Measurement SCMSOLS sad a a 11 14 Temperature and Pressure issue een ea 11 13 MA a A RA ee 13 AA 13 14 Results and Analysis A A O E 14 Appendices Appendix A Aerocomm Tutorial aa 15 16 Appendix B LabVIEW Backpanel
16. The calculation of the checksum is explained below The jump to page example 1s shown in Figure 19 2 Save byte value OxFE to internal RAM address 0x01 0xA0 0x02 CC Page 7 MSB Pabe LSB Checksum Opcode Internal RAM address Internal RAM value Figure 19 2 Sending Jump to Page Function To calculate the checksum the first four bytes must be added together X 0x40 0x02 0x01 0x03 0x46 The sum of X and the checksum values must make the least significant byte equal 0x00 Therefore checksum 0x100 0x46 0x5 A Check to prove that the value for the checksum is correct 0x46 0x54 0x0100 lt The checksum is correct since the MSB is equal to zero SAEDAQ 19 Page The string from the final microcontroller coding is shown in Figure 20 1 to help visualize the multiple bytes that are being sent to the Amulet in one single data packet transmission Bytes 0 1 words 0 2 and bytes 5 9 are all saved to their assigned internal RAM locations Bytes 5 9 are the warning bytes to tell the Amulet to invert the colors on the display The jump to screen command is then sent which tells the display to be on either the normal screen or the red warning screen The last byte sent is the XOFF command volatile unsigned char transmit 21 35 T0 T4 T01 17 0 ve DO coolant temp 213 0 1 0 Dt J7 byte ll pressure 214 0T ADYT TT 107 TOT T T mora o DLL temo 214 0 1 0 0 Kr T T 7 word
17. and display Below are the performance specifications A timer on the microcontroller counts the pulses from both the rpm and mph sensors The TTL pulses are sampled every 100 ms e The microcontroller uses the A D converter on the Mavric IIB to sample the coolant temperature oil temperature and oil pressure The total sampling time for the three values being recorded is 312 us The microcontroller sends the real time data to both the LCD and wireless antenna every 500ms The final coding for the microcontroller can be seen in Appendix A The documentation on the programming progress is shown in Appendix B SAEDAQ 5 Page Figure 6 1 Mavric IIb Microcontroller Board Aerocomm Wireless Boards The project started with the Chipcon CC12500 DK development board using the TI CC2400 wireless transceivers Figure 6 1 However after much time attempting to set up and interface the wireless there was not enough documentation on how to set up these antennas The TI tech support was not helpful in getting it to function properly and only suggested to buy their newer version of the antenna After much research and troubleshooting we decided to move to another antenna We switched to the Aerocomm AC 4790 transceivers Figure 6 2 These chips were much easier to set up and only took about one full lab day s worth of research to get them to function properly The Aerocomm chip transmits at 9600 baud on a 900 MHz chipset The values are received i
18. deled as current sources in Figure 12 1 our sensor measurement circuit Figure 12 1 Sensor Measurement Circuit The A D resolution on the microcontroller was set to 0 2 56 V since at the sensor output of 20mA the voltage across the load would be 2 4 V Table 12 1 shows the temperature data corresponding to the A D value A D Res 2 56 255 Sensor uC Bit Temperature 48 49 50 S1 S2 53 54 Table 12 1 A D Temperature Data Curve fitting analysis was used to find a software calculation for uC bit number to temperature However the formula that was generated contained decimal point SAEDAQ 12 Page arithmetic which would be inefficient The solution was to use a software lookup table because there was enough memory The curve fitting plot is shown in Figure 13 1 Temperature vs A D Value 2 3 E 2 AID Value Figure 13 1 Temperature vs A D value curve Note The pressure sensor modeling was conducted in the same manner with similar results A software lookup table was used as well Wheel Speed The wheel speed sensor MT 190 was not implemented into the project because we did not have a proper set up for it However the MT 190 was purchased because it is a Hall Effect sensor which eliminates the problem of dirt and grime interfering with the signal as with a laser tachometer Hall Effect sensors have a magnet attached to the end of it which outputs a signal when a metal
19. e settings UBRROH baudrate gt gt 8 UBRR L baudrate arr size 1 sizeof daq data sizeof daq data 0 fenable the transmitter and receiver UCSROB _ BV TXEN JE _BV RXEN set frame format G bit UCSROC BV UCSZ01 BV UCSZ00 enables UDREO interrupt UCSROB BV UDRIEO SAEDAQ 34 Page enables receiver interrupt UCSROB BV RXCIEO enables transmitter interrupt UCSROB BV TXENO kkkkkkkkkkkkkkkkkkkkkkkkkk RS 232 UARTI SETUP kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk set baud rate to 9600 unsigned int baudrate 103 see page 197 for baud rate settings UBRR1H baudrate gt gt 8 UBRRIL baudrate Z enable the transmitter and receiver UCSR1B _ BV TXEN _ BV RXEN set frame format 8 bit UCSRIC _BV UCSZ11 _BV UCSZ10 enables UDRE1 interrupt UCSR1B BV UDRIE1 enables receiver interrupt UCSR1B BV RXCIE1 enables transmitter interrupt UCSROB BV TXEN1 air Size 8120085 transmit sizeat transm 2 0 kkkkkkkkkkkkkkkkkkkkkkkkkkkkk EXC INC 1 kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk Located at PORTDL set external interrupts 1 as rising edge generation incl TESTO 10501 20505 EICRA BV ISC11 BV TSCLO 5 Enable External Interrupt 0 and 1 EIMSK BV INT1 kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk xkkkkkkkx Enables ALL Interrupts SREG 0x80 endless loop wh
20. e pulses in a set time frame The values are outputted to the Amulet screen and LabVIEW 7 include lt avr io h gt include lt inttypes h gt include lt avr interrupt h gt iumeti n header declarations int to ascii int val LED screen variables volatile unsigned int arr size 0 volatile unsigned char ready 1 volatile unsigned char i O max warning values Volatile unsigned char coolant max 2007 volatile unsigned char pressure max 200 volatile unsigned int oil temp max 200 volatile unsigned int mph max 190 volatile unsigned int Max rpm 120007 volatile Unsigned in pe time U volatile unsigned char j 0 volatile unsigned Int arr size 1 07 transmit buffer string volatile unsigned char transmit 213 0 0 0 0 byte 0 coolant temp 213 0T FILE TOT TOT bytell pressure ATA ET ATO POT UB word 0 mul tenp 214 0 1 0 0 0 0 word 1 wheel speed 214 0 2 Dr D T T TOT 7Z7wOrd 2 engine speed 213 0 5 0 0 7 7byte 5 coolant temo warning flag 213 0 6 0 0 7 bhvte 6 oil pressure warning flag SAEDAQ 27 Page 213 0 7 0 0 byte 7 213 0 8 0 0 byte 8 213 0 9 0 0 byte 9 160 2 0 32 62 jump to screen 19 send XOFF for end of transmission LabVIEW String volatile unsigned char dag dataj time to updat the display value volatile unsigned int display time d
21. eclare ADC storage value volatile unsigned char sensor Coolant Temp Values volatile unsigned char volatile unsigned char volatile unsigned char 77011 Pressure Values volatile volatile volatile unsigned unsigned unsigned Oil Temp Values volatile volatile volatile volatile volatile unsigned unsigned unsigned unsigned unsigned MPH Values volatile volatile volatile volatile volatile unsigned unsigned unsigned unsigned unsigned RPM Values volatile volatile volatile volatile volatile SAEDAQ unsigned unsigned unsigned unsigned unsigned char char char int char char char char DE coolant temp cool 1 cool U pressure pressure pressure LL tenp oil temp Old Temp oil temp oil temp int mph 0 char char char char mph 11 mph 10 mph OI mph 00 int rpm 0 char char char char rom LL rpm 10 rpm OL rpm 00 07 3 r Uf Xs uo er D oe 11 01 00 SAFE Or r VET s r SF s r VT s COT s Os r e gt r Y 0 Y Y 0 Y Y 0 Y Y 0 Y Y 0 Y DOES 07 07 gt r s r Ts POT s V Ts Or 4 4 4 4 4 r r 4 r RER KO Y Y 0 Y Y 0 Y Y 0 011 temp warning flag wheel speed warning flag engine speed warning flag Y Y Y Y 0 0 Y Y Y Y 0 0 Y Y Y Y 0 4 O 4 in increments of the time
22. en Port TCP IP Port Ports Port Status Unavailable Port ow gt Baud Rate 9600 r Parity None recommended y Handshaking None Data Bits E Stop Bits h Port2 Settings Enabled Options V Save Settings on Exit JV Readivvrite with AT Commands Y Use Auto BaudiPort lv Auto Archive EEPROM Settings Product Product ac4790 y USB COM Port Find Open Port C TCP IP Port Ports Close Port Port Status Unavailable Port ow y Baud Rate 900 Parity None recommended y Handshaking None Data Bits e y Stop Bits h Port1 Unavailable RTS Port1 High CTS Port1 High Port2 Unavailable Interface Baud 9600 Calc Baud RTS Port2 High px PC Settings Radio RF Radio Features Auto Config Full Duplex Auto Channel DES Enable Auto Destination IV Broadcast Unicast Only SLock SLock1 RTS Enable 485 DERE Protocol Status Parity Mode Probe Mode Probe Report Transmit API Receive API Send Data Complete 14 4 Jarchive Window gt l Save to File Print Write Radio Read Radio RTS Port2 High CTS Port2 High E PC Settings CTS Port2 High Communications idle Figure 16 2 PC Settings SAEDAQ 16 Page LabVIEW Backpanel Appendix B RPM vs Time Oil 4 p Jua mf ta mf tm WARNING 280 WARNING te AE Figure 1
23. ile 1 f if update 1 update 0 coolant temp clan 0 Cool 17 transmacllleeool OF oil pressure trapsmitl2lepressure 1 Lrensmitlol lepressure U oil temp SAEDAQ 35 Page transiit 4l 01l temp 11 transmait 5 9eo021l temp 10 transmitloleonl temp 01 transmitl eonl temp 00 wheel speed LtransmitLls mph Ll transmict i9 emph 10 trapnsmitllOlemph Ul transmit ll emph 00 REM transmitll2 erpm 117 transmitlla erpm 107 transmit l4 erpm 0217 transmib ll5 erpm 00 end main statement TO ASCTT this function converts a 4 bit value into its proper hexadecimal value into ASCII in order to be transmitted to the Amulet using ASCII protocol AM to ast int Val switch val case 0 val 0 SAEDAQ Case case Case case Cans Case Case Case case break qs val 1 break 24 vel tzts break 32 val 1T3 break 4 val 4 break 9 val 2 5 break 6 val 6 break 7 val 2 7 break 8 valetsts break ga 36 Page Gase case Case Cans case Gase val etets break 10 val tA s break 11 val B break 12 pala break 13 val D break 14 Val E break 1 23 val r break return val SAEDAQ r r 4 37 Page
24. ime the LabVIEW program plots the data versus time and logs the data to an Excel file specified by the user Figure 8 1 shows the user interface VISA resource name Baud Rate Stop Bits Parity L PPP Y a COMI gt 0 9600 J 1 J 10 Data Bits flow control n n LOG DATA Ja r None A 4 Engine RPM Speed MPH 4000 6000 8000 40 50 60 2000 10000 30 70 80 13000 Temperature Oil Pressure Coolant Oil 260 300 76 211 250 200 E 200 150 z WARNING 150 WARNING i wil 50 50 0 DE Velocity vs Time 80 60 40 velocity MPH 20 Or RO OJ OL L L LA 83 100 125 150 175 200 233 Time Oil Pressure vs Time 1505 125 pan e e 1 Oil Presure psi Lu TT BO TO CET 69 100 125 150 175 200 219 Time RPM vs Time 13000 Sample 12000 Times sec 2 ae Velocity ra 8000 0 25 a A 6000 RPM 5 0 25 4000 4 i Pressure 2000 10 25 A 0 1 LG 1 SON AL 1 LISA Ji et l el m M 1 PANUT 1 JV SM 1 LI 4 Temperature 86 100 125 150 175 200 236 1 A i 710 25 Time 2 Coolant Oil Temp vs Time 250 Coolant PANA 225 o MA 200 5 175 m p 150 a 5 125 100 75 50 prrrr T OTO TEKNO tern PRT pisay 107 120 140 160 180 200 211 Time Figure 8 1 LabVIEW User Interface Measurement Display The same measurements that are seen by the driver in the Formula One car are seen by an off track team The data is updated in real time once it is wirelessl
25. ing help M Clear parsing ASCII representation 00000000000 Bin and ASCII Byte Big Endian Motorola Separator s i Figure 9 3 I O Assistant Parse Settings Data Plotted Versus Time The right portion of our user interface displays the data acquired for wheel speed engine RPM oil pressure oil temperature and coolant temperature over the time of a race The unique feature of these displays is that the user can change the sampling time intervals For example the speed data can be updated every second while the pressure data can be updated every minute This feature is able to be implemented because of LabVIEW parallel computing programming structure While traditional programming languages such as C execute lines of code sequentially LabVIEW uses structures similar to functions and loops which execute independent of each other Figure 10 1 shows an example of this in the Back Panel programming The structures are two separate while loops with wait for ms functions block Velocity vs Time z Speed MPH URE Velocity BP Pressure Figure 10 1 Back Panel programming of the data versus time displays SAEDAQ 10 Page Data Log Feature The final feature of the LabVIEW interface is that the data being sent to it can be logged into an Excel spreadsheet file The save feature is the same as any other Windows application where the user can specify the file name and director
26. is passed by it This piece of metal could be a bolt attached to the wheel The MT 190W has the following specifications e Operating Distance 0 25 max gap Speed Range 1 99 999 RPM Power Required 5VDC Output Signal TTL 0 5 VDC e 8foot cable 2 long Engine RPM The sensor purchased to measure engine RPM was the ACI Hall Effect current sensor pictured in Figure 14 1 The goal was to run the engine ignition coil through the sensor to sense when the coil fires These pulses could be counted and sampled over a certain time interval to measure engine RPM This was not implemented because we could not get an ignition coil for testing SAEDAQ 13 Page Figure 14 1 ACI Hall Effect Sensor The ACI sensor has the following specifications e Sensor Power induced from monitored conductor e Output 0 5 VDC e Amperage Ranges 0 250 Amps Operating Frequency 50 600 Hz Results and Analysis Project milestones were assigned as follows e George LabVIEW user interface sensor measurements Phil Touchscreen LCD programming wireless chips Caleb Microcontroller programming interfacing wireless chips Each of us worked separately on our respected milestones Once completed each milestone was added to the overall project to work together The microcontroller successfully recorded simulated pressure temperature and speed readings at a specific rate and sent those readings to the LCD where it was properly displayed The
27. lues enable AtoD interrupts SAEDAQ 33 Page set prescaler to 128 ADCSRA BV ADEN BV ADSC BV ADFR BV ADIE BV ADP52 _BV ADPS1 BV ADPS0 kkkkkkkkkkkkkkkkkkkkkkkkkkk Timer 1 SETUP kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk sets the compare time to 0 1 sec in hexadecimal value when using prescaling 1 64 OCRIA 0x61AT7 set this bit to clear the timer on compare match pg 135 TCCRIB BV WGM12 sets this bit to enable timer 1 interrupt TIMSK BV OCIEIA start timer sets the clock to 1 64 prescaling and turns timer on pg 137 TCCRIB amp BV CS12 makes sure the CS12 bit is cleared TCCRIB BV CS11 TCCRIB BV CS10 kkkkkkkkkkkkkkkkkkkkkkkkkkk Timer 2 SETUP kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk l8 bit counter sets the clock to use an external clock source using pin T2 pin T2 is located on PORTD7 TCCR2 BV CS22 TCCR2 BV CS21 TCCR2 BV CS20 kkkkkkkkkkkkkkkkkkkkkkkkkkk Timer 3 SETUP KK IK kc k ck kk kk ck ck ck k ck kk kk k ck ck ck ck k ck kk kk kk 16 bit counter sets the clock to use an external clock source using pin T3 pin T2 is located on PORTE6 TCCR3A BV CS32 TCCR3A BV CS31 TCCR3A BV CS30 initialize counter to zero TCNT3H Q TCNT3L 0 KKK KK KK KKK KK KK KK KK KKK KK KK RS 2 32 UART I SETUP kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk set baud rate to 9600 unsigned int baudrate 103 see page 197 for baud rat
28. n a 12 byte data packet that is transmitted every 500 ms The data received from the antenna is attached to a laptop where LabVIEW parses and uses the date for live view analysis peg an o o Figure 6 1 Chipcon CC2400 Figure 6 2 Aerocomm AC 4790 SAEDAQ 6 Page Touchscreen Display The touchscreen display was an essential part of the system because it gives the driver data in real time This is essential for the integrity of the car and the driver in that the driver will be able to monitor the vitals of the car If a problem with one of the systems does arise the driver will be aware of it and will be able to take appropriate actions such as pulling over or making other minor adjustments The touchscreen used for this project was the Amulet STK 480272C LCD touchscreen It is made by Amulet Technologies and came as a packaged deal with GEMstudio which is a drag and drop GUI design tool GEMstudio is a powerful tool that allows for a wide variety of control and object widgets to be designed and implemented into a project It is based off of HTML called uHTML which uses less memory and allows for easy GUI programming The goal of the design for the touchscreen was to make the data as well as when the warnings popped up as visible as possible Previous projects might not have made this as efficient as possible with lower quality screens and designs or scales and gauges that are too small for the driver to easily see what is
29. nted to make a static image disappear on a button press and the image s name was image the code you would put in the function button s href would be SAEDAQ 21 Page Amulet document image disappear To add multiple commands to one widget separate with a comma disapear Amulet document Logic functions functions called based on timer events 1f then else statements and initializing internal RAM variables that are tied to the page and not a specific widget are to be put in the META refresh The META refresh 1s found in page functions under the project tab in GEMstudio In my design I wanted a if statement that would check for a specific byte to be set and when that byte is set invert the colors of a corresponding widget The byte would be set by the microcontroller which would send it over RS 232 when the situation called for the byte being set The code in the META refresh is lt META HTTP EQUIV REFRESH CONTENT 0 01 IF Amulet InternalRAM byte 7 value E01 THEN Amulet document OilTemp inverseRegionColor NAME invoiltemp gt The code above says that every 01 seconds check if byte 7 in the internal RAM equals 1 Ifitis 1 invert the background color of the numeric field displaying oil temperature The general syntax 1s as follows lt META HTTP EQUIV REFRESH CONTENT updateRate delayRate IF function EQ GT LT NEQ value equals greater than less than does not
30. ows how to send a command for saving to the internal RAM of the Amulet Saving a CRC value to internal RAM involves three parts Opcode internal RAM address and the internal RAM value The Opcode is the single byte command telling the Amulet what bytes are going to be coming next and what to do with them In Figure 19 1 the OxD5 Opcode is telling the Amulet to program the byte received to the internal RAM The figure depicts what each byte value 1s by color coordination For further analysis the CRC commands that were not used on our project can be found on Amulet s tutorial website under the UART CRC Protocol section http www amulettechnologies com GEMhelp GEMcompiler Help htm SAEDAQ 18 Page Save byte value OxFE to internal RAM address 0x01 0x30 0x31 je K Save word value 0x02C9 to internal RAM address 0x00 2 Z ic B Internal RAM address Internal RAM value Figure 19 1 Sending Values to Internal RAM Unlike the CRC commands shown in Figure 19 1 the jump to screen function does not follow the normal CRC protocol Each Amulet page has its own two byte identifier address which is used for the jump to page function Unlike the CRC protocol the Opcode is two bytes long The jump to page function first sends the two byte command the page address starting with the most significant byte then the checksum The checksum 1s an algorithmic value that is used to make sure that the bytes before it were actual valid data
31. pe to ASCII or CRC For more information on the differences between the two protocols see the user s guide GEMstudio link The protocols for ASCII and CRC are on the left side The documentation given in the link was very helpful for understanding how these protocols work from both the touchscreen and the microcontroller s point of view A couple of notes about the sections that describe the widgets The font and font size can exceed the presets that the studio gives Instructions can be found below how to modify this The example code the guide gives where it starts each line with lt PARAM NAME gt doesn t have to be coded It is all part of GEMstudio s GUI and can be managed with the menus and not the code The only coding you are probably going to do when making a project is coding in the href parameter which links the control widgets with the object widgets and in the MET A refresh which can call functions for a specific page of your touchscreen For the href commands the general syntax is Amulet document widgetname method Widgetname is the user defined name for the called widget The default name for a widget is MyWidgetName For example the default name for a function button would be MyFuncButton Double click the MyFuncButton to change it to whatever you want The options for what the method function can be is in Appendix B of the user s guide which I have attached at the end of this document If you wa
32. r interrupt 28 Page external interrupt count value for rpm volatile unsigned char count 1 volatile unsigned char update 1 ISR USARTO UDRE vect interrupt for when the UDRO transmit buffer is empty ir arr size l i UCSROB s 247 stop transmitter UCSROB z 223 stop UDRO interrupt else Ir jl arr size 1 1 UDRO dag daral z Jo External Interrupt 1 PORTD1 LOR INIL vegt 4 count count 1 ISR TIMER1 COMPA vect interrupt for timing display Lime display tame 2 po Cine pe time Lo record mph into 8 bit counter mph TCNT2 TCNTA2 0 record engine rpm TOM count ADD RPM CONVERSION FORMULA HERE rpm rpm 48 END OF CONVERSION FORMULA jser counter back to zero count 03 convert mph to display on screen mph Il to ascii mph gt gt 12 0x0E mph 10 vo asciil mph gt gt 8 0 0B mph 01 to ascii mph gt gt 4 4 0x0F mph 00 to asci1 mph 6 Ox0F convert rpm to display on screen rpm 11 to ascil rpm gt gt 12 O0x0F rpm 10 To ascii rpm gt gt 8 0 0B tpm 01 to ascii rpm gt gt 4 amp OxOE rpm 00 to ascii rpm a 0x0E SAEDAQ 29 Page if pc time 5 allow transmission after one second El mode j e pj pe time 0 ZUCSR Y Y e a BY TXENO 2 enable transmitter OB update 1 f 6001 dag da dag da ant temp tapolceool 7 ta 1 2cool 0 oil pressure
33. the method name such as value or disappear The IF method for the named widget will change to m where m 1s the method name such as value or disappear The ONVAR UART method for the named widget will change to m where m 1s the method name such as Value The variable number used in the ONVAR of the named widget will change to x where x 1s the variable index used in the following variable types byte x word x or string x The named Widget will change its equal gt or It value to the byte value x The href UART method for the named widget will change to m where m is the UART method name such as Value The update rate for the named widget will change to if where fis a floating point number that represents the update rate in seconds The named widget will receive the intrinsic value of the calling widget where x is the intrinsic value The variable number used in the href of the named widget will change to x where x is the variable index used in the following variable types byte x word x or string x The named Widget will change its topleft x coordinate to the word value x The named Widget will change its topleft y coordinate to the word value x The named View Widget will start updating the displayed data The named View Widget will stop updating the displayed data The named widget will either start or stop 24 Page displaying in reverse video The named widget s text s
34. tring will either start or Amulet document widgetName toggleStringColor PET EE ve The named View Widget will either start or stop Amulet document widgetName toggleUpdating updating the displayed data 1 Regarding x For Control Widgets that have intrinsic values such as lists and sliders leave the argument field empty since the intrinsic value of the selection will be sent out META REFRESH tags and Function Custom Buttons should use x The range for x is 0 255 0x00 0xff for a BYTE 0 65535 0x00 Oxffff fora WORD and 250 character strings in double quotes for STRINGs 2 Regardingm When setMethod setOnVarMethod setOnVarUARTMethod or setUARTMethod is the IWC method the argument should be the name of the method you want to set 1 e disappear or byte value Notice when dealing with a method that relies on a type byte word or string you need to include the type separated by a dot and then the method 1 e word value instead of just the method by itself 3 Regarding f For Control Widgets that have intrinsic values such as lists and sliders leave the argument field empty since the intrinsic value of the selection will be sent out META REFRESH tags and Function Custom Buttons should use f Like the regular updateRate use a floating point number to specify the update rate in seconds Range for f is 0 655 35 4 Regarding setX and setY These methods should most always be preceded by a disappear method and follo
35. ure that your settings are valid To transmit the data packets through RS 232 simply move the USB Enable header to the RS232 Enable header Once this is changed the user should be able to send their own data packets between boards This can be tested by hooking up the boards to two separate computers and typing a message through hyper terminal SAEDAQ 15 Page E AC4790 Configuration Test Utility Configure Radio Interface Interface Timeout RF Channel Number 0 Sensitivity Adjust B7 RF Packet Size Session Count 5 Max Power Full Power Stale Count Reload 140 Hex Random Backoff Packet time System ID Hex CTS On CTS Off Transmit Retries Broadcast Attempts Stop Bit Delay Info Center PAEROCOMM web www aerocomm com sales email sales aerocomm com technical support te ch supp orti aero comm com phone 913 492 2320 Mailing Address 11160 Thompson Avenue cron EEPROM GU View a ERO VIEW Port 1 Port 2 Port1 Unavailable Communications idle Radio Other 00 50 67 29 49 29 Destination 77 30 67 29 43 25 DES Key OD 1D 2D 3D 4D 5D 6D MAC Address 00 50 67 29 49 15 Firmware Version v 2 3 1 D O B 9 25 2006 Full Part Number amp C4790 200A TTL 01 Pairing Show Defaut Compare ee f RTS Port1 High Port2 Unavailable Figure 16 1 Configure Settings E AC4790 Configuration Test Utility Port1 Settings USB COM Port Find Op
36. wed by a reappear method The setting of the x and y coordinates are independent of the removal of the widget in the old coordinates and the displaying in the new coordinates Below 1s the code used in the page 2 the red screen META refresh which can be found by clicking on the Page Function tab lt META HTTP EQUIV REFRESH CONTENT 0 01 IF Amulet InternalRAM byte 7 value EQ 1 THEN Amulet document Oil Temp inverseRegionColor NAME invoiltemp gt lt META HTTP EQUIV REFRESH CONTENT 0 01 IF Amulet InternalRAM byte 6 value EQ 1 THEN Amulet document OilPress inverseRegionColor NAME invOilPress gt lt META HTTP EQUIV REFRESH CONTENT 0 01 IF Amulet InternalRAM byte 5 value E01 THEN Amulet document Coolant inverseRegionColor NAME invCoolant gt lt META HTTP EQUIV REFRESH SAEDAQ 25 Page CONTENT 0 01 IF Amulet InternalRAM byte 8 value EQ 1 THEN Amulet document MPH inverseRegionColor NAME invmph gt lt META HTTP EQUIV REFRESH CONTENT 0 01 IF Amulet InternalRAM byte 9 value EQ 1 THEN Amulet document RPM inverseRegionColor NAME invrpm gt SAEDAQ 26 Page Appendix E Final Microcontroller Coding NOTE the final coding is also available on the final project CD to make viewing easier Caleb Davison Created 03 29 11 LabVIEW and touchscreen interfacing This program takes three different voltages from the ADC It also counts th
37. widget will display in reverse video The named widget s text string will display in reverse video The named List widget will move its highlighted bar down to the next entry Does not perform a hit on the new entry The named widget will display In normal video The named widget s text string will display in normal video The named List widget will move its highlighted bar up to the previous entry Does not perform a hit on the new entry 23 Page Amulet document widgetName reappear Amulet document widgetName reset Amulet document widgetName setMethod m Amulet document widgetName setOnVarMethod m 2 Amulet document widgetName setOnVarUARTMet hod m Amulet document widgetName setOnVarVariableNu mber x Amulet document widgetName setTrigger x Amulet document widgetName setUARTMethod m 2 Amulet document widgetName setUpdateRate f Amulet document widgetName setValue x Amulet document widgetName setV ariableNumber x y Amulet document widgetName setX x Amulet document widgetName setY x Amulet document widgetName startUpdating Amulet document widgetName stopUpdating Amulet document widgetName toggleRegionColor SAEDAQ The named widget will reappear on the LCD in its original location if it is a View Widget it will also start updating The named widget will initialize internal variables and re draw The href method for the named widget will change to m where m 1s
38. y it 1s to be saved in The file already comes with headers for the columns of data Once the data log button is pressed the LabVIEW program terminates Measurement Sensors The sensors purchased for this project were only modeled for measurement methods not implemented Temperature and Pressure The two temperature sensors TTD25N 20 shown in Figure 11 1 are for oil and coolant temperature with the following specifications e RTD resistive thermo device outputs a proportional response e 4 20mA output proportional to temperature e 10 36V operating voltage can be powered from car battery minimal power consumption e 1 4 MNPT sensor can thread straight into lines e 4 5 long ideal size Handles 20g s of vibration 50g s of shock The pressure sensor PTD25 20 shown in Figure 11 1 has following specifications e RTD resistive thermo device outputs a proportional response e 4 20mA output proportional to temperature e 9 6 to 32 VDC Operating Voltage e 1 4 MNPT sensor can thread straight into lines e About 3 long Handles 20g s of vibration 50g s of shock Figure 11 1 Temperature and Pressure Sensors SAEDAQ 11 Page In modeling the sensor output the max resistive load had to be calculated Equation 1 is from the sensor data sheet RLmax Vsupply 9 6 50 1 For this model Vsupply 12 V because that 1s the voltage of the car battery corresponding to a 120 ohm resistive load The sensors are mo
39. y transmitted Figure 8 2 shows the front panel of the user interface Engine RPM Speed MPH Oil Pressure SAEDAQ Coolant Oil 163 WARNING _ 1502 Figure 8 2 LabVIEW Front Panel WARNING 8 Page Communications The LabVIEW user interface receives data being sent to it via RS232 communication The front panel allows the user to change the communication settings port number baud rate data bits flow stop and parity bits For this specific project we used the following settings e Baud Rate 9600 e Data Bits 8 e Flow Control None e Stop Bits 1 e Parity 0 Figure 9 1 shows the communication control portion of the user interface in Figure 8 1 VISA resource name BaudRate Stop Bits Parity m Jo Hi o Data Bits flow control jJ 8 P None l Figure 9 1 Communication Controls The data being sent to the PC is handled with the Instrument I O Assistant The I O Assistant receives the data in packets and parses through it to pull out specific variables to display Figure 9 2 shows the I O Assistant programmed in the Back Panel of the LabVIEW interface Figure 9 3 shows the settings window for parsing through data in the I O Assistant VISA resource name instrument VO Assistant 1 04 VISA Baud Rate lli mp 1 T V324 eener Data Bits viet Parity viet Stoo Bits flow control Figure 9 2 I O Assistant Program SAEDAQ 9 Page sb Run this step Auto parse Pars
Download Pdf Manuals
Related Search