hexagon logo
Register Sign in
  • Replies 3 replies
  • Subscribers 10 subscribers
  • Views 83 views
  • Users 0 members are here
Options
Related

Import info from different part stages?

oddam
Is there a way to make a run chart in DP but import info from different part stages? Let me explain what we are doing, I am measuring a welded assembly at different stages to determine welding warpage at the final stage. First I measure the stampings, send the info to DP. Second, tact weld the stampings together, measure the same features if available, (the program has a different name), send info to DP. 3rd, weld the tact welded parts with the actual full weld, measure the parts again, send info to DP. 4th, Add any other parts that are welded on, measure the welded assy, send info to DP. If the assembly has a bushing added, which this does, measure the final assembly, send info to DP. I use the same point features through the entire process if they are available to measure. To make it easy to visually understand, using a run chart, the same feature point from each process and give simple info, like range, high / low readings, whatever helps take away the data overload. Can DP do something like this? Has anyone done this before? Any help would be appreciated.

Thanks,
Odda
  • Are you able to put the data into an Excel sheet or something and import from there?

    Personally I don't have DataPage, but I might as well post an idea Sunglasses
  • You would have to figure out some sort of work around. DataPage is just a GUI for a SQL database. Each file imported into the database creates a new folder with its own structure. The name of the program determines where it imports. So, XXX_stamp makes a file called XXX_stamp, and XXX_weld goes into XXX_weld. If you named the weld program XXX_stamp, it would transfer into the XXX_stamp file, but it would be all jacked up. It would show 2 transactions, and each would be null where the data didn't match up.

    I don't know how you would do this, short of making it all into 1 program somehow.
  • I sorta got it to work, sorta, but haven't had time to get it completely. If you use the same part name in both PC-Dmis programs, it will append the 2nd program data with a new time stamp (leaving a large area of white space which is what I want to fix). On this part, all we are doing on this part is recording ranges so it's not critical that we maintain part traceability between side A and B.
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement