Hey guys, I'm not understanding how to pull a TP from a slot on Only the Width and another TP from the same slot on Only the Length...
Any ideas?
Any ideas?
↧
True Position on Only Length and Only Width of a Slot?
↧
Invalid insertion here warning
Greetings!!
CAD++ 2017R2, Build #1364 (Service Pack 10).
So I am trying to edit a true position dimension. The tolerance for the hole went from +/-.03" to .010". I hit F9, go to the advance tab and change the tolerance on the hole. I hit OK and the warning box "Invalid insertion here." Hmmm. That is a new one. So I exit out and go back to F9 and just change the tolerance on the front page instead of the advance tab. Click on OK, same thing. So, I delete the line and go to tolerance it again. Same thing.
What am I doing wrong? Has the demon raised it's ugly head? I also downloaded and ran the update yesterday and that could be the issue. I have edited and corrected issues with the true position dimensions before doing it as described above.
Scott
CAD++ 2017R2, Build #1364 (Service Pack 10).
So I am trying to edit a true position dimension. The tolerance for the hole went from +/-.03" to .010". I hit F9, go to the advance tab and change the tolerance on the hole. I hit OK and the warning box "Invalid insertion here." Hmmm. That is a new one. So I exit out and go back to F9 and just change the tolerance on the front page instead of the advance tab. Click on OK, same thing. So, I delete the line and go to tolerance it again. Same thing.
What am I doing wrong? Has the demon raised it's ugly head? I also downloaded and ran the update yesterday and that could be the issue. I have edited and corrected issues with the true position dimensions before doing it as described above.
Scott
↧
↧
What parts of the analog modules require a lower level matrix?
Hey everyone,
I'm new to the scanning aspect of the CMM world and I took the calibration course and know how to properly calibrate our probes, my question is about which part of the probe body requires a lower level matrix calibration? we us renishaw SP25M and alternate between a SM25-2 and SM25-1 for our different probes. Is it just the SP25M that requires a lower matrix cal or each of the modules?
I'm new to the scanning aspect of the CMM world and I took the calibration course and know how to properly calibrate our probes, my question is about which part of the probe body requires a lower level matrix calibration? we us renishaw SP25M and alternate between a SM25-2 and SM25-1 for our different probes. Is it just the SP25M that requires a lower matrix cal or each of the modules?
↧
Rotary table
is any one can help me for use of rotary table in PC DMIS offline mode? of totally new to this one
↧
Position / GD&T Fundamental Question
I have a question concerning the picture above. The feature of interest is the I.D. on the left.
It is my understanding that since the feature axis and Datum -B- axis are parallel, the callout to -B- in the FCF is simply perpendicularity. That being said, I am trying to determine where the GD&T theory dictates the Position differences should be obtained from. In other words, in the .010 FCF datums -B-, -C-, AND -F- are called out. Should the Position be calculated as (feature_x - C_x)^2 + (feature_y - F_y)^2 etc... or should it be (feature_x - C_x)^2 + (feature_y - C_y)^2 etc...?
I am assuming it is the first option: delta x from feature and C, delta y from feature and F; but I would like to understand whether this is correct or not..... and why.
Next, looking at the .006 FCF, only -B- and -C- are called out. If -B- is there for perpendicularity, then we are only measuring distance to -C-. Do we do this strictly in x (C/L)? Strictly in y? Or in both directions?
The math is not too much of an issue for me, it's really just the GD&T theory that's wiping me out.
Thank you.
↧
↧
Multiple run in Inspect
Hi,
I have searched in Inspect for the option to run multiple programs automatically, but did not find this. I am used to the Operator Interface which has this option and also the pallet run.
Is this something what Inspect is not able to do? And is it possible to create a form for each program where the operator can fill in the name, batchnumber etc..
I would like to have this form in Inspect instead in PC-DMIS, because the purpose is to fill in all the forms before the multiple run and then it measures all the products automatically without intervention of the operator.
I have searched in Inspect for the option to run multiple programs automatically, but did not find this. I am used to the Operator Interface which has this option and also the pallet run.
Is this something what Inspect is not able to do? And is it possible to create a form for each program where the operator can fill in the name, batchnumber etc..
I would like to have this form in Inspect instead in PC-DMIS, because the purpose is to fill in all the forms before the multiple run and then it measures all the products automatically without intervention of the operator.
↧
DMIS to Excel Auto Command
Hi Folks
I have searched the posts now for over a hour but with no success.
I don't often have to run multiple parts but today I have been asked to run 90 parts.
I was wondering if there is a way to use the PCD2Excel command to run automatically and the end of each run of program using the serial number as a 'unique' file name?
This is way above my job remit but would be very useful!
Thanks in Advance.
I have searched the posts now for over a hour but with no success.
I don't often have to run multiple parts but today I have been asked to run 90 parts.
I was wondering if there is a way to use the PCD2Excel command to run automatically and the end of each run of program using the serial number as a 'unique' file name?
This is way above my job remit but would be very useful!
Thanks in Advance.
↧
PCDMIS2018 report format
I just got PCDMIS 2018. I had a program written in PCDMIS 3.7mr2. I loaded it onto the new CMM & got the program to run fine but my .rtf file looks like it save right but when I open it the format is all screwed up. Anyone have this issue before? I am sure it is a easy fix but I dont have time to search through all the old posts.
↧
changing default alignment for FCF
Good morning,
does anyone know how to change the default output alignment from "Datum Reference Frame" to "Current alignment" when using FCF's?
thanks, Mike
does anyone know how to change the default output alignment from "Datum Reference Frame" to "Current alignment" when using FCF's?
thanks, Mike
↧
↧
Show Contact Parameters
Wondering if there is a quick and dirty way to turn the Show Contact Parameters on for a bunch of circles.
I have a bunch of old programs that someone else wrote that has them all turned off. I thought there was going to be a way to do this in later versions.
Thanks in advance.
Code:
2156_25P576=FEAT/CONTACT/CIRCLE/CIRCLE_ANALOG_SCAN_STRATEGY,CARTESIAN,IN,LEAST_SQR
THEO/<163.5,122,172>,<1,0,0>,25.476
ACTL/<167.246,-281.245,167.65>,<0.9999988,0.0006434,-0.001407>,25.474
TARG/<163.5,122,172>,<1,0,0>
START ANG=0,END ANG=360
ANGLE VEC=<0,0,-1>
DIRECTION=CCW
SHOW FEATURE PARAMETERS=NO
SHOW CONTACT PARAMETERS=NO
Thanks in advance.
↧
Testing string for special chars and replacing them.
Trying to figure out a good way to remove any special chars input by operators. What I cam up with is to load all the special chars in to an array then loop through the input string and recreate it with out the special char. Loop then increments to the next index of the special char array and repeats until complete.
Is there a better way?
How would you do this using a script that would take the sting from from the var, remove the special chars, reassign the var with the new string. I think this would be best in case there is a need to stop and restart the program.
Is there a better way?
How would you do this using a script that would take the sting from from the var, remove the special chars, reassign the var with the new string. I think this would be best in case there is a need to stop and restart the program.
Code:
ASSIGN/TEST_STRING="<//??a/b*/c\\/>1/2/|3/a?>"
ASSIGN/CHAR_ARRAY=ARRAY("/","\\","?","<",">","*","|",":")
ASSIGN/LOOP_COUNT=0
ASSIGN/W_COUNT=1
$$ NO,
______________________________
Start Loops
_______________________________
WHILE/W_COUNT==LEN(CHAR_ARRAY) OR W_COUNT<LEN(CHAR_ARRAY)
WHILE/INDEX(TEST_STRING,CHAR_ARRAY[W_COUNT])>0
ASSIGN/SPC_CHAR_INDEX=INDEX(TEST_STRING,CHAR_ARRAY[W_COUNT])
ASSIGN/STRINGTEMP=LEFT(TEST_STRING,SPC_CHAR_INDEX-1)
ASSIGN/TEST_STRING=STRINGTEMP+MID(TEST_STRING,SPC_CHAR_INDEX)
ASSIGN/LOOP_COUNT=LOOP_COUNT+1
END_WHILE/
ASSIGN/W_COUNT=W_COUNT+1
END_WHILE/
COMMENT/OPER,NO,FULL SCREEN=NO,AUTO-CONTINUE=NO,
TEST_STRING
"loop Count = " +LOOP_COUNT
↧
Flow control to calculate mmc control of slots
I have a problem with the if end if statement when the following code is run step by step after a break point it shows the correct numbers in the variables when you hover over them with the mouse pointer, but when you run the program in full or execute the program from cursor it gives the wrong numbers. The code is just to calculate mmc from the slot length, I am running pcdmis 2018 r2 offline, anybody got any ideas where I may be going wrong.
Code:
COMMENT/REPT,
***SLOT LENGTH***
COMMENT/REPT,
***BALLOONED DRAWING NUMBER 95.***
DIM DIST2= 2D DISTANCE FROM POINT AU_LPNT1 TO POINT AU_LPNT2 PAR TO XAXIS,NO_RADIUS UNITS=MM,$
GRAPH=OFF TEXT=OFF MULT=10.00 OUTPUT=BOTH
AX NOMINAL +TOL -TOL MEAS DEV OUTTOL
M 4.370 0.050 0.050 4.490 0.120 0.070 >
COMMENT/REPT,
********************************************************************
IF/DIST2.MEAS>4.42
GOTO/L1
L1 =LABEL/
ASSIGN/V1A=4.42
ASSIGN/V1=V1A
END_IF/
$$ NO,
******************************************************************
IF/DIST2.MEAS<4.32
GOTO/L2
L2 =LABEL/
ASSIGN/V2A=4.32
ASSIGN/V1=V2A
END_IF/
$$ NO,
******************************************************************v
$$ NO,
******************************************************************
ASSIGN/V5=V1-4.32
DIM LOC32= POSITION OF POINT AU_LPNT2 UNITS=MM ,$
GRAPH=OFF TEXT=OFF MULT=10.00 OUTPUT=BOTH FIT TO DATUMS=ON DEV PERPEN CENTERLINE=OFF DISPLAY=DIAMETER
AX NOMINAL +TOL -TOL BONUS MEAS DEV OUTTOL
PR 269.612 269.655 0.043
PA -0.002 -0.002 0.000
D1 522.675 0.035 0.035 0.035 522.675 CIRCLE DATUM_B_DIAM AT MMC
TP RFS 0.3+V5 0.000 0.085 0.085 0.000 #
END OF DIMENSION LOC32
COMMENT/REPT,
********************************************************************
↧
Scanning Setup with Readpoint
Hello everyone,
Lets start with the 'light' information:
Leitz: LSPX1H_T
Software: 2015.1
Mach: DEA 15.30.10
The machine allows me a good area in 'Y' to locate my part, it also has 12x slot locations that are put in at a nearly 40º angle to my -A- plane at 30º increments about -B-.
I am trying to get the proper combinations to allow the scanning to remain in the program and NOT drive me crazy when swapping between offline/online programming.
Here's what I do:
Locate the probe with readpoint, perform a quick DCC check to define where part is on table
Move probe to desired -C- location and have part physically rotated.
Perform 1 more quick DCC check to re-define where part is on table.
Now it is a FULL ABC pickup then off to measuring the unit.
All regular points work PERFECT to measure/evaluate, scanning on the other hand.....
When it gets to the point of scanning, production is having to CANCEL the run cycle and regenerate the scan path in order to complete the inspection. This is not acceptable as I'd like this program to be free of user intervention (run at offshift times). Trying to determine what should be my setup approach:
Current Scan parameters:
Exec Mode: Defined
Nominals Method: FindNoms
^This has been what I used to perform my scans and I am begining to think I need to swap them. Next Trial:
Exec Mode: Relearn
Nominals Method: Nominals
Online to Offline is really a seperate topic and I have a work around with it right now, but maybe some of you have already found a method that can be supplied.
Appreciate anyones help, I'm not used to scanning and it drives me BONKERS that scan parameters are not 'sticky' like auto/measured features!
Lets start with the 'light' information:
Leitz: LSPX1H_T
Software: 2015.1
Mach: DEA 15.30.10
The machine allows me a good area in 'Y' to locate my part, it also has 12x slot locations that are put in at a nearly 40º angle to my -A- plane at 30º increments about -B-.
I am trying to get the proper combinations to allow the scanning to remain in the program and NOT drive me crazy when swapping between offline/online programming.
Here's what I do:
Locate the probe with readpoint, perform a quick DCC check to define where part is on table
Move probe to desired -C- location and have part physically rotated.
Perform 1 more quick DCC check to re-define where part is on table.
Now it is a FULL ABC pickup then off to measuring the unit.
All regular points work PERFECT to measure/evaluate, scanning on the other hand.....
When it gets to the point of scanning, production is having to CANCEL the run cycle and regenerate the scan path in order to complete the inspection. This is not acceptable as I'd like this program to be free of user intervention (run at offshift times). Trying to determine what should be my setup approach:
Current Scan parameters:
Exec Mode: Defined
Nominals Method: FindNoms
^This has been what I used to perform my scans and I am begining to think I need to swap them. Next Trial:
Exec Mode: Relearn
Nominals Method: Nominals
Online to Offline is really a seperate topic and I have a work around with it right now, but maybe some of you have already found a method that can be supplied.
Appreciate anyones help, I'm not used to scanning and it drives me BONKERS that scan parameters are not 'sticky' like auto/measured features!
↧
↧
PC-DMIS 2018 R2 SP2 now available
Looks like the second service pack for 2018 R2 is good to go. Download it here: ftp://ftp.wilcoxassoc.com/PC-DMIS-Ve...18_R2/SP2/x64/
Here's the list of bug fixes for anyone who is interested:
• PCD-125813 - When the pointcloud is not well aligned to the CAD model, the resulting measured cross section (yellow polyline) may not be computed as expected and may produce the incorrect shape. By default, the PointcloudOperator CrossSectionCopCadCrossSectionDrivenByCad registry entry is set to 1. It is possible to obtain better results by changing the registry entry's value to 0 and recreating the cross section so that it uses this new setting. This alternative way to calculate COP/CAD cross sections could give better results when the medium distance between the cloud and the CAD model is relevant in the section zone, and the nominal section is strongly curved in this zone (distance is greater than 2 or 3 mm).
• PCD-128933 - Improved the logic to determine the appropriate tip when it is part of block for the copy and Paste With Pattern. It fixes the issue of the tip not patterned.
• PCD-135514 - Ring light intensity migration will now only be attempted for features where the top and bottom lights are not in use.
• PCD-138257 - Fixed an issue where PC-DMIS stopped working when executing a measurement routine that already contained extra instances of commands (extra instances of commands are created by executing the measurement routine with commands such as Loops, Goto, etc.).
• PCD-140115 - When a new patch scan is created, all points taken for previous patch scan are deleted so as to create patch scan at new location.
• PCD-140952 - Fixed an issue with the displayed datum bonus value when the datum was shifted to its limit.
• PCD-145264 - Fixed an issue for the Leica LMF interface AT960 tracker where PC-DMIS 2018 R2 Release Notes 2
• PCD-146159 - The trapeze that represents the working area of the laser sensor is no longer shown for features that are extracted from a COP command.
• PCD-146366, PCD-147443 - The auto wrist toggle got enabled when linear open scan commands were edited.
• PCD-146476 - Fixed an issue that caused the layout toolbar to always appear after a toolbar was customized.
• PCD-146494 - It is now again possible to execute directly-measured laser features offline.
• PCD-146558 - Fixed an issue where it wasn't possible to calculate the form error for laser cylinder features extracted from a COP command.
• PCD-147370 - Fixed an issue where the Mesh Colormap scale did not appear in the Graphic Display window and the Text and CAD, CAD Only, and CADOnly Landscape report templates.
• PCD-147567 - Fixed I++ errors for Technology Server 1.x in the self-centering code.
• PCD-147569 - ToolName (the name of the tip in the I++ server) has never been composed correctly for the purpose of scrolling in the measurement routine in the Edit window when LOADTIP is done sometimes.
• PCD-147666 - PC-DMIS I++ server has fixed readouts for DEA machine interface for manual CMMs.
• PCD-147697 - Fixed a rounding issue of the percentages shown on the pointcloud colormap scale. The colormap scale now uses the number of decimal places that are defined on the Dimension Display Precision command (Edit | Preferences | Setup | Dimension tab).
• PCD-148128 - Added support for "minus tolerances show negative" in the new XactMeasure dialog box.
• PCD-148163 - Fixed an issue for the Leica LMF interface AT-960 tracker where two "OK to insert probe" messages occurred when switching from a reflector CCR probe (after measuring a feature) to the LAS scanner. PC-DMIS 2018 R2 Release Notes 3
• PCD-149014 - Failed to restore the original string if the expression failed. It was saved in all uppercase letters, which was incorrect.
• PCD-149024 - For the Pointcloud Export function, the user can define the separator used for the XYZ export. In the PC-DMIS Settings Editor, in the PointcloudOperator section, use the ExportXYZSeparator registry entry. The default value is a space: " ". Examples of separators are ";" and ",". Type the separator without the quotation marks. If you type more than one character, only the first one is used.
• PCD-149051 - PC-DMIS considers "-" or "/" as a mathematical operation and tries to resolve the expression. This issue allows you to type drawing number in the Trace field menu and does not consider it as an expression, so that you can use - for entering drawing or part numbers. You can now enter the new value during execution.
• PCD-149075 - Fixed an issue where dimension IDs did not update when a different geometric tolerance was selected from the XactMeasure dialog box.
• PCD-149206 - Fixed temperature compensation V1 for Manual mode (this applies to I++, Zeiss, and other third-party machine interfaces).
• PCD-149332 - Fixed an issue where, at times, the Surface Colormap could not be reset from within the dialog box.
• PCD-149711 - Fixed scanning for the Zeiss direct machine interface.
• PCD-149950 - Display the Datum Definition dialog box when an additional datum is requested and isn't yet defined.
• PCD-149958 - Fixed a case where PC-DMIS could lock up while trying to cancel Optimize Path.
• PCD-150629 - Fixed an issue that prevented setting the Xact Measure Position nominal values from the dialog box.
Here's the list of bug fixes for anyone who is interested:
• PCD-125813 - When the pointcloud is not well aligned to the CAD model, the resulting measured cross section (yellow polyline) may not be computed as expected and may produce the incorrect shape. By default, the PointcloudOperator CrossSectionCopCadCrossSectionDrivenByCad registry entry is set to 1. It is possible to obtain better results by changing the registry entry's value to 0 and recreating the cross section so that it uses this new setting. This alternative way to calculate COP/CAD cross sections could give better results when the medium distance between the cloud and the CAD model is relevant in the section zone, and the nominal section is strongly curved in this zone (distance is greater than 2 or 3 mm).
• PCD-128933 - Improved the logic to determine the appropriate tip when it is part of block for the copy and Paste With Pattern. It fixes the issue of the tip not patterned.
• PCD-135514 - Ring light intensity migration will now only be attempted for features where the top and bottom lights are not in use.
• PCD-138257 - Fixed an issue where PC-DMIS stopped working when executing a measurement routine that already contained extra instances of commands (extra instances of commands are created by executing the measurement routine with commands such as Loops, Goto, etc.).
• PCD-140115 - When a new patch scan is created, all points taken for previous patch scan are deleted so as to create patch scan at new location.
• PCD-140952 - Fixed an issue with the displayed datum bonus value when the datum was shifted to its limit.
• PCD-145264 - Fixed an issue for the Leica LMF interface AT960 tracker where PC-DMIS 2018 R2 Release Notes 2
• PCD-146159 - The trapeze that represents the working area of the laser sensor is no longer shown for features that are extracted from a COP command.
• PCD-146366, PCD-147443 - The auto wrist toggle got enabled when linear open scan commands were edited.
• PCD-146476 - Fixed an issue that caused the layout toolbar to always appear after a toolbar was customized.
• PCD-146494 - It is now again possible to execute directly-measured laser features offline.
• PCD-146558 - Fixed an issue where it wasn't possible to calculate the form error for laser cylinder features extracted from a COP command.
• PCD-147370 - Fixed an issue where the Mesh Colormap scale did not appear in the Graphic Display window and the Text and CAD, CAD Only, and CADOnly Landscape report templates.
• PCD-147567 - Fixed I++ errors for Technology Server 1.x in the self-centering code.
• PCD-147569 - ToolName (the name of the tip in the I++ server) has never been composed correctly for the purpose of scrolling in the measurement routine in the Edit window when LOADTIP is done sometimes.
• PCD-147666 - PC-DMIS I++ server has fixed readouts for DEA machine interface for manual CMMs.
• PCD-147697 - Fixed a rounding issue of the percentages shown on the pointcloud colormap scale. The colormap scale now uses the number of decimal places that are defined on the Dimension Display Precision command (Edit | Preferences | Setup | Dimension tab).
• PCD-148128 - Added support for "minus tolerances show negative" in the new XactMeasure dialog box.
• PCD-148163 - Fixed an issue for the Leica LMF interface AT-960 tracker where two "OK to insert probe" messages occurred when switching from a reflector CCR probe (after measuring a feature) to the LAS scanner. PC-DMIS 2018 R2 Release Notes 3
• PCD-149014 - Failed to restore the original string if the expression failed. It was saved in all uppercase letters, which was incorrect.
• PCD-149024 - For the Pointcloud Export function, the user can define the separator used for the XYZ export. In the PC-DMIS Settings Editor, in the PointcloudOperator section, use the ExportXYZSeparator registry entry. The default value is a space: " ". Examples of separators are ";" and ",". Type the separator without the quotation marks. If you type more than one character, only the first one is used.
• PCD-149051 - PC-DMIS considers "-" or "/" as a mathematical operation and tries to resolve the expression. This issue allows you to type drawing number in the Trace field menu and does not consider it as an expression, so that you can use - for entering drawing or part numbers. You can now enter the new value during execution.
• PCD-149075 - Fixed an issue where dimension IDs did not update when a different geometric tolerance was selected from the XactMeasure dialog box.
• PCD-149206 - Fixed temperature compensation V1 for Manual mode (this applies to I++, Zeiss, and other third-party machine interfaces).
• PCD-149332 - Fixed an issue where, at times, the Surface Colormap could not be reset from within the dialog box.
• PCD-149711 - Fixed scanning for the Zeiss direct machine interface.
• PCD-149950 - Display the Datum Definition dialog box when an additional datum is requested and isn't yet defined.
• PCD-149958 - Fixed a case where PC-DMIS could lock up while trying to cancel Optimize Path.
• PCD-150629 - Fixed an issue that prevented setting the Xact Measure Position nominal values from the dialog box.
↧
Article 3
I need to add to my comment / report the text ** CV followed by the assign CAV created earlier. How do I add text followed by a variable in the comment / report command? The expected result is: ** CV 1, ** CV 2, ** CV 3, ... Note: The loop and count are already correct, I just need to hit the comment / report Thank you.
ASSIGN/CAV=COUNTER+1
ASSIGN/COUNTER=CAV
COMMENT/REPT,
CAV
↧
Text and Assign on Comment Report
I need to add to my comment / report the text ** CV followed by the assign CAV created earlier. How do I add text followed by a variable in the comment / report command? The expected result is: ** CV 1, ** CV 2, ** CV 3, ... Note: The loop and count are already correct, I just need to hit the comment / report Thank you.
ASSIGN/CAV=COUNTER+1
ASSIGN/COUNTER=CAV
COMMENT/REPT,
CAV
How do I add text before assign CAV?
ASSIGN/CAV=COUNTER+1
ASSIGN/COUNTER=CAV
COMMENT/REPT,
CAV
How do I add text before assign CAV?
↧
Constructed Circle
Hi All,
I am reporting a radius on a small part. The part is about 50mm long, the print reports a radius of 136. I measure five vector points and construct a circle, I then place the proper axis for my dimension. The nominal comes out fine, but the measured result is 11mm smaller than the nominal. There is no way this is that shy. I am using cad, the points do lay on the cad, two of the points are datums, I should check the deviations of each point, but I just cannot figure out why it's reporting 11mm shy, I would buy a less then a couple mm's. Trying to get a large radius on such a small distance seems questionable. I did look at the search files and found nothing that seems to help. I have adjusted as many of the filters as I could. Any help on getting an accurate result would be much appreciated. I cannot be the only one with this issue. I am using pcdmis 2018 r1 and the customer cad file
Thanks,
Odda
I am reporting a radius on a small part. The part is about 50mm long, the print reports a radius of 136. I measure five vector points and construct a circle, I then place the proper axis for my dimension. The nominal comes out fine, but the measured result is 11mm smaller than the nominal. There is no way this is that shy. I am using cad, the points do lay on the cad, two of the points are datums, I should check the deviations of each point, but I just cannot figure out why it's reporting 11mm shy, I would buy a less then a couple mm's. Trying to get a large radius on such a small distance seems questionable. I did look at the search files and found nothing that seems to help. I have adjusted as many of the filters as I could. Any help on getting an accurate result would be much appreciated. I cannot be the only one with this issue. I am using pcdmis 2018 r1 and the customer cad file
Thanks,
Odda
↧
↧
Construct line / rotation
Of all things... I'm having trouble constructing a proper line to lock rotation.
Please see attached.... ??
No matter what I do at which alignment / workplane the constructed lines come out very undesirable.
Ideas? I know it's got to be something simple I'm missing.. Forgot to draw it, but the 45 angled line is the tertiary datum.![Click image for larger version
Name: CONSTRUCT LINE.jpg
Views: 1
Size: 13.2 KB
ID: 438074]()
Please see attached.... ??
No matter what I do at which alignment / workplane the constructed lines come out very undesirable.
Ideas? I know it's got to be something simple I'm missing.. Forgot to draw it, but the 45 angled line is the tertiary datum.
↧
error : "m_pnca thread is not running"
Trying to help d_tox on this error ? (Romer ?)
Anyone has an idea ?
Anyone has an idea ?
↧
Equating an Alignment
Good morning everyone,
I have a question. Is it easier to equate an alignment or just simply start a new program for the underside of the part. I have read the help files on how to equate but it didn't work well with me. Maybe I did something wrong.
I have a question. Is it easier to equate an alignment or just simply start a new program for the underside of the part. I have read the help files on how to equate but it didn't work well with me. Maybe I did something wrong.
↧