Intermediate files for debugging with dump.cps

[componentscience]

Hello Community,

Looking for some clarification on using intermediate files for debugging with dump.cps, which for Fusion 360, we understand to be the equivalent of code.cps with HSM (2-43). It is stated that an intermediate file can be used as input for debugging (2-43).

How is the intermediate file used as input for debugging in Fusion 360? How and when is the file fed into Fusion? How is the intermediate file used for debugging if the post is not selected during posting in the post dialogue (dump.cps is selected instead)?

[bernard5BABD · Accepted solution]

I certainly don't have all the answers to your questions, as I am learning myself, but it seems to me there is some confusion in your question. Dump.cps does NOT generate an intermediate file for debugging. It does generate a dump of data a post-processor can get from Fusion. Something like this:

-1: onMachine()
  Post Engine Version = 4.5834.0
  Program Name = BG-Dump
  Program Comment = 
-1: onOpen()
0: onParameter('product-id', 'fusion360')
1: onParameter('generated-by', 'Fusion 360 CAM 2.0.12376')
2: onParameter('generated-at', 'lundi 14 février 2022 14:06:07')
3: onParameter('hostname', 'PC-64-BERNARD-LaPoste')
4: onParameter('username', 'bgros')
5: onParameter('document-path', 'P_M10_3_E4 3 Axes Seulement v4')
6: onParameter('document-id', 'ef26dddd-075b-487e-8d6c-a1cbf20f160a')
7: onParameter('model-version', '9b07e016-403f-4faf-9ff0-38381e710881')
9: onParameter('leads-supported', 1)
10: onParameter('job-description', 'Usinage Dessus generation dump code')
11: onParameter('machine-id', '1')
12: onParameter('machine-config', '<?xml version="1.0" encoding="UTF-16" standalone="no" ?><machine xmlns="http://www.hsmworks.com/xml/2009/machine" version="1.0"><vendor>Roeders</vendor><model>V2</model><description>Roeders 5 axis</description><machining jet="no" milling="yes" turning="no" wire="no"/><tooling maximumToolDiameter="0mm" maximumToolLength="0mm" maximumToolWeight="0kg" numberOfTools="100" toolChanger="yes" toolPreload="yes"/><machiningTime ratio="1" toolChangeTime="15s"/><coolant options="FLOOD"/><capabilities workOffsets="100"/><spindle axis="0 0 1"/><post><postProcessor>user://roeders rms6-BforCure_R4.cps</postProcessor><setupSheet></setupSheet></post><simulation retractOnIndexing="yes" shortestAngularRotation="yes" wcs="0mm 0mm 0mm"/><multiAxis adjust="yes" angle="10deg" cone="3deg" feedrateMethod="fpm" linearizationTolerance="0.04mm" method="linearize rotary" reconfigure="no" tolerance="0.04mm" virtualToolTip="no"/><axis id="Y" link="head" range="-82mm 212mm" tcp="no"/><axis id="Z" link="head" range="-210mm 0mm" tcp="no"/><axis id="X" link="table" range="-210mm 100mm" tcp="no"/><axis actuator="rotational" axis="1 0 0" coordinate="Y" id="U" link="table" maximumFeed="21600deg/min" offset="-239mm 0mm 68mm" range="-30deg 115deg" tcp="yes"/><axis actuator="rotational" axis="0 0 1" coordinate="Z" cyclic="yes" id="V" link="table" maximumFeed="21600deg/min" offset="0mm 0mm -6mm" range="-360deg 360deg" tcp="yes"/></machine>')
13: onParameter('stock-type', 'box')
15: onParameter('stock', '((-60.9368, -43.125, 0), (60.9368, 43.125, 40.15))')
17: onParameter('stock-lower-x', -60.9367513459481)
19: onParameter('stock-lower-y', -43.12500000000001)
21: onParameter('stock-lower-z', 0)
23: onParameter('stock-upper-x', 60.9367513459481)
25: onParameter('stock-upper-y', 43.12500000000001)
27: onParameter('stock-upper-z', 40.15)
29: onParameter('part-lower-x', -59.9367513459481)
31: onParameter('part-lower-y', -42.12500000000001)
33: onParameter('part-lower-z', 0)
35: onParameter('part-upper-x', 59.9367513459481)
37: onParameter('part-upper-y', 42.12500000000001)
39: onParameter('part-upper-z', 39.15)
44: onParameter('notes', '')

To generate an intermediary file for debugging, you have to download and use "export CNC file to vs code.cps".  Once you have processed your test part with it, you will have a CNC file with a single line, looking like this

Success, your CNC file "BG-Export2VSC.cnc" is now located in "C:\Users\bgros\.vscode\extensions\Autodesk.hsm-post-processor-3.5.5\res\CNC files\Custom" and you can select it in VS Code.

then, in VSCode, you should be able to load your CNC debug file by clicking twice on it there

Hope this help,

Bernard

[componentscience]

@bernard5BABD 

Thank you. We understood dump.cps for Fusion to be the equivalent of code.cps for HSM, but may have misunderstood this and the process as well. This will be revisited and the forum-post will be updated accordingly.

Best

[componentscience]

@bernard5BABDyou are correct, thank you for the clarification. We confused the intermediate file (2-43) with the concept of an intermediate toolpath (1-1), and believed dump.cps or code.cps were responsible for its creation.

Best