I have found the MSC Exo-6 report utility to be very helpful over the last several years since it came out in 2012. It still seems to work fine with all versions up to and including 2017. But it crashes when I try to open an f06 file from version 2018. I wonder what in the 2018 f06 file could have broken this very valuable tool.
Also, I have been using your other report writer called F06_Reader that is distributed with the 2017 version. That tool works fine for the 2017 version but always seems to crash with the 2018 version.
Do you have any reporting tool that works with version 2018?
Hi Don. So I just took some time and figured out what the problem is with the old exo-6 reader and why it stopped working after nastran 2017 was released. So now I have exo-6 working fine. The fix requires a change to the log file and also to the f04 file. The main reason that exo-6 reader stopped working with version 2017 and later is that the log file and f06 file stopped reporting memory in words and started reporting in MB. So once I figured that out, I just needed to make minor changes to my log and f04 files to get the exo-6 reader to work.
If I had a million dollars I would give it to MSC so you could find a programmer to fix the old exo-6 reader program and get it to work with memory in units of MB instead of words. it would probably be a quick and easy fix that would make the exo-6 program usable with all new versions of Nastran.
Why not provide working exo-6 and f06 reader programs to your customers so they can pick the best tool for their needs? I think that would fall under the category of providing excellent customer service, don't you. I hope to see the available for download soon.
Also, could you provide the source code for those tools if nobody at MSC or Hexagon has the time to fix them and maintain them?
Hi Don. So I just took some time and figured out what the problem is with the old exo-6 reader and why it stopped working after nastran 2017 was released. So now I have exo-6 working fine. The fix requires a change to the log file and also to the f04 file. The main reason that exo-6 reader stopped working with version 2017 and later is that the log file and f06 file stopped reporting memory in words and started reporting in MB. So once I figured that out, I just needed to make minor changes to my log and f04 files to get the exo-6 reader to work.
If I had a million dollars I would give it to MSC so you could find a programmer to fix the old exo-6 reader program and get it to work with memory in units of MB instead of words. it would probably be a quick and easy fix that would make the exo-6 program usable with all new versions of Nastran.
Why not provide working exo-6 and f06 reader programs to your customers so they can pick the best tool for their needs? I think that would fall under the category of providing excellent customer service, don't you. I hope to see the available for download soon.
Also, could you provide the source code for those tools if nobody at MSC or Hexagon has the time to fix them and maintain them?