Dear Kanticha, I believe that NI Labview is the best data acquisition tool to meet your requirement for collecting velocity, voltage and current etc. as the web link http://www.ni.com/labview/. Hope this helps - Ning
Dear Kanticha, I believe that NI Labview is the best data acquisition tool to meet your requirement for collecting velocity, voltage and current etc. as the web link http://www.ni.com/labview/. Hope this helps - Ning
Yeah definitely, I once did an internship where I working on an engine control for hybrid electric vehicles - there we used a NI CompactRIO System with LabVIEW Software. It is pretty convenient to use and quite powerful.
Really NI labview is the best acquisition system for this purpose but it is also very expensive. You will need to purchase hardware and NI software. If you have any technical support in informatics, you can use the ARDUINO board to develop an embedded system with very little investment.
You need to provide a lot more information before anyone can provide a reasonable answer to your question. Are you measuring voltage and current? What are the resolution and full-scale range requirements? What sample rates do you need? How many channels? Can you mux the sampling, or does it have to be done simultaneously across two or more channels? What kind of system do you intend to connect this to: laptop with USB 2? PC Tower with PCIe? Ethernet? ISA? HPIB?
In addition to what Gregg said, the question comes up whether your vehicle inherently offers the possibility to access the data you're searching for.
My own electric vehicle has an EMUS battery management controller collecting all you ask for, so this could be an option as well.
It can collect data on instantaneous Current/Voltage/Temperature from the whole battery block as well as the individual cells, check the speed, acceleration and distance travelled.
I suppose any modern electric vehicle will have such a system, most likely not as a part accessible for everybody.
Would be worth trying to contact the vehicle manufacturer for this option.
Martin: the onboard systems like that used by Telsa motor drives privde the data you need via the CAN bus network. I believe someone has done the work to reverse engineer the protocol packets, so it should be simple enough to get at that using a tool like wireshark with a CAN interface card.
I love this little handy device for recording data:
http://www.ahlborn.com/getfile.php?1886.pdf
You can get all different kinds of sensors for this device and record everything at the same time. Basically there is no need to have a computer next to your test setup anymore. After the test is done it exports all the data directly into an excel and/or ascii file.
To check the available sensors use this list: http://www.ahlborn.com/Sensors.html
As suggested by the above authors, a NI system will probably be able to do what you want.
If you want to avoid coding in LabView, you can use Signal Express or Sound & Vibration Measurement Suite. http://www.ni.com/gate/gb/GB_EVALSVMEASSUITE/US . You then just have to plug in your NI hardware to get started with a measuerement.
If you want to log time signals only and make analysis elsewhere, you can settle for downloading the NI-daqmx drivers as these are free and allow single measurements using NI hardware.http://www.ni.com/download/ni-daqmx-14.2/5046/en/
The above will give you access to analog and digital signals but not to CAN or GPS data.
It might help to know exactly which electric vehicles you are trying to collect data from. If the vehicle is equipped with an OBD II connector, vehicle speed is broadcast using nonproprietary signalling and can be captured using any number of data acquisition systems. NiDAQ/Labview can certainly do this but there are also numerous systems that are designed specifically for acquiring OBD II or CAN-BUS data. This can go from simple touch-screen OBD monitoring systems such as the DashDAQ XL:
to high-speed data acquisition systems from Dearborn Group Technologies, National Instruments and others. If OBD data is fast enough and if you can find out the correct PIDs for voltage and current that are broadcast by the EMS, then one of the simpler systems will suffice.
Ask yourself how often you want to collect the data and then looking for a solution. The last suggestion is a "toy" for pseudo-tuning. Search for better design solutions NI. Binary signal from the GPS (command NEMA) also can register them using the LabVIEW platform.
The systems produced by DGT and comparable systems from other vendors are used for CAN-bus data acquisition by automobile manufacturers during vehicle EMS calibraton for both drivability, durability, NVH and emissions. They are also used by emissions compliance authorities in North America (EPA, EC). They are definitely not toys. Even more limited systems can acquire data at OBD II bus speeds without necessitating the intrusion of large, hardware rack-mounts within the vehicle interior and/or extensive labview programming and these are often useful for gathering data from a larger vehicle fleet where other hardware is either too intrusive or too cost prohibitive. We use all three types of these systems within our laboratory (1. custom built NI, 2. contractor purchased/programmed CAN-bus DAQ, 3. simple OBD scanner with touch interface) depending on the type of data we are collecting and the number of vehicles we are trying to access within our research programs. We even use a simple, cheap, pre--programmable PLC that is slightly larger than a flash drive for acquiring "saturation" levels of OBD data - i.e., instrumenting dozens of vehicles undergoing road testing simultaneously. The end use of the data will define the data acquisition system that is most appropriate to use.
If the only tool a person has is a hammer, then everything starts to look like a nail.
Kanticha, did not say for what purpose he wants to use the information. If you are just to "see" what happens to the vehicle while in motion your system - yes. But look at the test performed by dragging it aims to give the external characteristics of the engine, or indeed signals from the OBD connector to provide the necessary information has been appointed - eg. what about the ACX, slipping wheels rolling resistance? - look at in the publication: Jazar, Vehicle Dynamics. Theory and Application - Ch. 2 and 3. If you want to test the traction this information from the OBD connector can only support systems based on GPS and Corsyss Datron. I'm sorry but it is still not a tool for scientific and research. It is difficult to read minds Kantichy what she wants to achieve, although apparently think is the future of the nation (I do not know how well last thought fared in translation?). Or maybe you tested it in parallel with the system Datron or profesionalnym based GPS system - external characteristics, moose test etc .... I am I did it. Once again, what she wants to?
Thirty years back ,I developed, 8085 based modules to collect data, and store in sequential memory locations for I+,I- and Izero, along with data of hot spot temperature, diff. current etc. hence simple microprocessor module, using interrupt routine using ADC, or microcontroller could solved your problem economically, refer my papers.