04-21-2015 10:42 AM
Hello,
I'm looking for a way to log all traffic on a given port in VeriStand. Basically I'd like to assign a DBC file to that port and then simply log everything but I can't see a way to do this in VeriStand. I've tried the Raw frame logging and choosing the "log entire bus traffic" option but end up with just a single channel "Engine Timestamp". I'm currently using the embedded data logger but that requires me to have imported the frames I want to log and the DBC file is simply too big for VeriStand, it doesn't seem to be particularily efficient at adding additional CAN frames and to try and add the entire DBC file essentially locks up VeriStand. Any suggestions or something I've simply missed? Thanks.
04-21-2015 11:06 AM
What are you using to view the file when you only see the EngineTimestamp channel? Are you using DIAdem perhaps?
05-15-2015 12:29 PM
I was using DIAdem, however I have since solved this issue by creating a logger similar to the Embedded Data Logger but specifically for CAN signals so I can log to directly to MDF, ASC, etc without having to convert post process.
05-15-2015 12:39 PM - edited 05-15-2015 12:40 PM
Thanks for the update! If anyone else has the same question, the answer is that in order to extract the bus log information in the TDMS file, you should use the DIAdem Bus Log Converter tool. It is expected (though confusing) that the file looks mostly empty in the Data Portal until you use this tool to extract the information.
Also, this is a fantastic tutorial from a very bright engineer on how to correlate data from multiple sources, such as raw frame files, in DIAdem. Highly recommended reading. It also has some data on the bus log converter.
11-09-2015 02:34 AM
11-10-2015 01:06 PM
This help article is a good resource for configuring raw frame data logging. You should be able to add additional files you want to log to using this method. Finally, this article contains more detailed information on the effect of the trigger settings. I hope this helps.
11-11-2015 02:30 AM
11-11-2015 04:50 PM
Could you clarify are you using VeriStand at all? Your first message implied that you were using this environment, but your most recent message makes it seem like you might be using TestStand exclusively. Depending on whether you are managing things through VeriStand, or TestStand you will need a different solution. If you are in VeriStand I believe you could use Raw Frame Data Logging, but it would take a bit of research to get the exact configuration settings right. If you are using TestStand I would recommend developing a VI in LabVIEW that uses the XNET driver to log these frames and then calling it as a step. If you are calling VeriStand from TestStand then you would still configure raw frame data logging in your VeriStand system definition. Which of these situations are you dealing with?
11-12-2015 12:52 AM
11-13-2015 10:04 AM
What file format do you want the files to be saved as? As for moving the files over, you can set up a LabVIEW step to either WebDAV or FTP the files off of the target in order to make them available for analysis in windows. That, or depending on the type of analysis you want to do, you could write a custom device to do it on the Real-Time side. Though I would say the TestStand LabVIEW method would be much simpler than writing a custom device.