I would like to see the G11 module added as a device to connect with via internet through IQAN ANALYZE similar to how RUN and DESIGN currently have the option. This would be a very useful tool for diagnosing issues in the field for customers that have the G11 but do not have a CAN sniffer available.
The G11 has been a very useful tool for me and i would like to see its capabilities expanded.
When using a modern monitor the menus and text is very small in analyze compared to design, almost unreadable without magnifying glass.
Here is a picture with them side by side for comparison:
Is there any way to change the scaling?
Windows 11 Pro
It would be very helpful to add additional export file formats such as .blf or .mdf to allow for a capture to be logged by a field tech or customer that already has IQANanalyze, which then can be imported into more powerful software for detailed review.
This would allow for custom decoders and increase usability for people that are not as familiar with hex for diagnostics
It would be useful if the CANopen decoder included some common LSS commands for example change state, node id and bitrate.
Here is an example log with some comments:
Can anyone help me get this information into my system? This is the information i can see in IQAN Analyse, can anyone tell me how to 'decode' this and extract the information inside a module inside IQAN Design please?
Specifically its the highlighted bits of information i need insed my program.
It doesn't look like J1939, it looks like 11 bit identifiers, and all the ID:s look like the CANopen defaults.
IQANanalyze, switch decoder from J1939 to either Generic or CANopen.
I was using IQANAnalyze to trace the J1939 communication between my MD3 and a pump that it was controlling. I recorded the data for 5 minutes, then stopped the recording, and saved the .izbx log file.
Eventually, I was asked to get a graph of the flow coming out of the pump over that period, to help diagnose an issue we were having. The flow is transmitted on 2 bytes of one of the CAN messages. I was able to, pretty quickly, export the log file as a text file, then import that into excel, sort the data by PGN, select the PGN that had my information, add the pertinent bytes together to get the actual reading, and graph the result against time. The whole process took me a bit of time and googling, but I got the graph I needed.
However, I believe it would be more convenient if part of the IQAN suite that already has graphing capability could import the log file created by IQANAnalyze, and the user could select a parameter to graph based on PGN, length, and offset. Or, if the graphing capability could be pulled into IQANAnalyze itself, along with a modest ability to produce trendlines of averages, modeled on that of Excel.
I think this could be done with minimal programming investment, and would make logging information much more legible.
Customer support service by UserEcho