Re: New to Lab view! Need some Help.
"Actually this is only first part of my project in which i should be able to create a vehicle file using two different data base and should be able to save it as *.vcf. (you are right dialog box must produce a file named abc.VCF) first data base only contain messages in hex format and second data base only contain names of the modules in hex as wel.please see attached files above. Answer to your first question is that I do not need to keep database in MS Notepad files. You are quite right, I want the user to be presented with a list of messages but in the sub file, which is drawn from database1. At the later stage user is going to use this file to send the messages. nodes data means names of the modules e.g. power window, seat control, etc. these two do not have any direct relationship.we are going to select messages and nodes then save them as vehicle file for them to be used at later stage in the application. my phone number is 07949940740. if you need more information. thank you for your help."
Re: New to Lab view! Need some Help.
--8014094.1076335774371.JavaMail.quiq.tekken Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit here is the attachment of the of the message data base and node database. I have attached all of node and few commands of message database, as it is very big. --8014094.1076335774371.JavaMail.quiq.tekken Content-Type: text/plain; name=NODESDATABASE.txt Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=NODESDATABASE.txt Content-Description: NODE DATA BASE 10 PCM "POWERTRAIN CONTROL MODULE" 12 TCU "THROTTLE CONTROL UNIT 28 ABS "ANTI-LOCK BRAKING SYSTEM CONTROL MODULE" 2A EPB "ELECTRIC PARK BRAKE" 39 ADCM "ADAPTIVE DAMPING CONTROL MODULE" 50 REM "REAR ELECTRONIC MODULE" 52 GEM "GENERIC ELECTRONIC MODULE" 54 BPM "BODY PROCESSOR MODULE" 4A SLM "SECURITY & LOCKING MODULE" 60 IC "INSTRUMENT CLUSTER" 61 MC "MESSAGE CENTRE" 68 NAV "NAVIGATION CONTROL MODULE" 80 ACM "AUDIO CONTROL MODULE" 91 VEMS "VEHICLE EMERGENCY MESSAGING SYSTEM" 92 VACM "VOICE ACTIVATED CONTROL MODULE" 98 DATC "DUAL AIR TEMPERATURE CONTROL MODULE" 9B DGSM "DUAL GAS SENSOR MODULE" A0 DDM "DRIVERS DOOR MODULE" A2 DSM "DRIVERS SEAT MODULE" A4 PDM "PASSENGERS DOOR MODULE" A6 PSM "PASSENGERS SEAT MODULE" A8 DRDM "DRIVERS REAR DOOR MODULE" AC PRDM "PASSENGERS REAR DOOR MODULE" C3 SCL "STEERING COLUMN LOCK MODULE" F0 J10 "JEST TOOL #10" F1 J1 "JEST TOOL #1" F2 J2 "JEST TOOL #2" F3 J3 "JEST TOOL #3" F4 J4 "JEST TOOL #4" F5 J5 "JEST TOOL #5" F6 J6 "JEST TOOL #6" F7 J7 "JEST TOOL #7" F8 J8 "JEST TOOL #8" F9 J9 "JEST TOOL #9" --8014094.1076335774371.JavaMail.quiq.tekken Content-Type: text/plain; name=MESSAGEDATABASE.txt Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=MESSAGEDATABASE.txt Content-Description: MESSAGE DATA BASE All Courtesy Lamp are Off (Stat),41,DF,01,00 All Courtesy Lamp are On (Stat),41,DF,81,00 All Courtesy Lamp Switch Active,41,DF,A1,00 All Courtesy Lamp Switch Inactive,41,DF,21,00 ALL Door Lock Command - Lock(ed),41,C4,81,00 ALL Door Lock Command - Unlock(ed),41,C4,01,00 ALL Door Lock Motor Enable (cmd) Dis(d),41,C4,10,00 All Front Fog Lamps Off (cmd),41,DA,09,08 All Front Fog Lamps On (cmd),41,DA,89,08 All Front Fog Lamps are Off (stat),41,DB,09,08 All Front Fog Lamps are On (stat),41,DB,89,08 ALL Front High Beam Lamps Off (cmd),41,DA,06,08 ALL Front High Beam Lamps On (cmd),41,DA,86,08 ALL Front High Beam Lamps are off (stat),41,DB,06,08 ALL Front High Beam Lamps are On (stat),41,DB,86,08 ALL Headlamps Off (cmd),41,DA,01,00 ALL Headlamps On (cmd),41,DA,81,00 ALL Headlamps are Off (Stat),41,DB,01,00 ALL Headlamps are On (Stat),41,DB,81,00 ALL Park Lamps Off (cmd),41,DA,04,00 ALL Park Lamps On (cmd),41,DA,84,00 All Rear Brake Lamps Off (cmd),41,DA,03,38 All Rear Brake Lamps On (cmd),41,DA,83,38 All Rear Fog Lamps Off (cmd),41,DA,09,38 All Rear Fog Lamps On (cmd),41,DA,89,38 All Rear Fog Lamps are Off (stat),41,DB,09,38 All Rear Fog Lamp are On (Stat),41,DB,89,38 All Rear Park Lamps Off (cmd),41,DA,04,38 All Rear Park Lamps On (cmd),41,DA,84,38 --8014094.1076335774371.JavaMail.quiq.tekken--
Re: New to Lab view! Need some Help.
Actually this is only first part of my project in which i should be able to create a vehicle file using two different data base and should be able to save it as *.vcf. (you are right dialog box must produce a file named abc.VCF) first data base only contain messages in hex format and second data base only contain names of the modules in hex as wel.At the moment I am not able to attach these files because of some fault.But I can do that tommrrow. Answer to your first question is that I do not need to keep database in MS Notepad files. You are quite right, I want the user to be presented with a list of messages but in the sub file, which is drawn from database1. At the later stage user is going to use this file to send the messages. nodes data means names of the modules e.g. power window, seat control, etc. these two do not have any direct relationship.we are going to select messages and nodes then save them as vehicle file for them to be used at later stage in the application. my phone number is 07949940740. if you need more information. thank you for your help.
Re: New to Lab view! Need some Help.
I am rather new myself but have suggestion. Can he talk to M.S. Access files via ActiveX. I have not worked directly with LabView database files but have experience posting and drawing data from Excel files and Access. This seems to be a more viable option. Rebuttal? Seth jcrooke <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > I can help you get started with your project, but first, please, > provide more information. Do you have to keep your database in MS > Notepad files, or can you create datalog files in LabvIEW to serve as > your databases. Things are much easier for you if you can work > directly with LabvIEW data structures, which are saved into datalog > files with full retention of the data types. Reading, scanning, > sorting, and all of those sorts of activities are much easier when > working directly with LabVIEW data structures. You could then create > a special routine that parses your data into any structure you wish > for the benefit of other users. > > I am not very familiar with common database structures. I build > databases as I have mentioned above, using LabVIEW datalog files. It > may not be as efficient as a true "database" structure, but unless you > are talking about large amounts of data distributed over various > servers, I would think that the datalog file would suffice. > > Please, define the relational characteristics of these databases. > Does database1(message data) just contain lists of messages within a > matrix of lookup parameters? What is node data? Is this also just a > list of identifiers or strings? I beg your pardon, but I need you to > describe your task in more generic programming terms, a lower level > than the database structure. Once we get beyond this initial > communication gap, I can help you. > > You said, "in my application I need to have a dialog box with the > VEHICLE.VCF extention." I need a more careful explanation of this. > Do you mean that your dialog box must produce a file named > VEHICLE.VCF? Do you mean that your dialog box is a file dialog that > filters candidate files by the .VCF extension? > > You said, "database1(message data) this needs to have few massages > chosen from the main database1 and should be able to save them in > background." It sounds like you want the user to be presented with a > list of messages, which you have drawn from database1. You want the > user to be able to select an arbitrary number of these messages and > save them to a file? > > I will stop here. If you still need help, please, try to be more > specific. It is hard to design the entire application from this brief > description. Perhaps you should pick a single task and ask how that > one task might be accomplished. We could proceed from there.
Re: New to Lab view! Need some Help.
I can help you get started with your project, but first, please, provide more information. Do you have to keep your database in MS Notepad files, or can you create datalog files in LabvIEW to serve as your databases. Things are much easier for you if you can work directly with LabvIEW data structures, which are saved into datalog files with full retention of the data types. Reading, scanning, sorting, and all of those sorts of activities are much easier when working directly with LabVIEW data structures. You could then create a special routine that parses your data into any structure you wish for the benefit of other users. I am not very familiar with common database structures. I build databases as I have mentioned above, using LabVIEW datalog files. It may not be as efficient as a true "database" structure, but unless you are talking about large amounts of data distributed over various servers, I would think that the datalog file would suffice. Please, define the relational characteristics of these databases. Does database1(message data) just contain lists of messages within a matrix of lookup parameters? What is node data? Is this also just a list of identifiers or strings? I beg your pardon, but I need you to describe your task in more generic programming terms, a lower level than the database structure. Once we get beyond this initial communication gap, I can help you. You said, "in my application I need to have a dialog box with the VEHICLE.VCF extention." I need a more careful explanation of this. Do you mean that your dialog box must produce a file named VEHICLE.VCF? Do you mean that your dialog box is a file dialog that filters candidate files by the .VCF extension? You said, "database1(message data) this needs to have few massages chosen from the main database1 and should be able to save them in background." It sounds like you want the user to be presented with a list of messages, which you have drawn from database1. You want the user to be able to select an arbitrary number of these messages and save them to a file? I will stop here. If you still need help, please, try to be more specific. It is hard to design the entire application from this brief description. Perhaps you should pick a single task and ask how that one task might be accomplished. We could proceed from there.
