User Tools

Site Tools


wiki:en:ppedit

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
wiki:en:ppedit [2019/10/10 11:57]
admin
wiki:en:ppedit [2019/10/11 13:33] (current)
admin [REPETITIONS (LOOPS)]
Line 197: Line 197:
  
  
-You can read more about control codes in the section called ​"Formatted output" ​further on in this booklet.+You can read more about control codes in the section called ​[[wiki:​en:​ppedit#​formatted_output|Formatted output]] further on in this documentation.
  
    
Line 225: Line 225:
 It now remains to create the condition which will output code M66 the first time: It now remains to create the condition which will output code M66 the first time:
  
-''&​F25(” M66)''​+''​%%&F25(" ​M66")%%'' ​
  
 This means: //IF FLAG 25 IS NOT SET OUTPUT M66 AND SET FLAG 25.// This means: //IF FLAG 25 IS NOT SET OUTPUT M66 AND SET FLAG 25.//
Line 231: Line 231:
 The flag being zero (not set)  when we start the post processor the condition will be met the first time and since we use the &​character the flag will be set which will entail that the condition will not be met the next time. It now remains to insert the condition in the desired position in the macro for the change of tools. The flag being zero (not set)  when we start the post processor the condition will be met the first time and since we use the &​character the flag will be set which will entail that the condition will not be met the next time. It now remains to insert the condition in the desired position in the macro for the change of tools.
  
-''​M111 Makro for toolchange: M103 <​toolnr> ​” T#x M6” \ \\ +''​%%M111 Makro for toolchange: M103 <​toolnr> ​" ​T#x M6" ​%%'' ​\\ 
-&F25(” M66)''​+''​%%&F25(" ​M66")%%'' ​
  
 Notice that we use the   ​\-sign (backslash) to tell the post processor to go on reading the macro on the next line. Notice that we use the   ​\-sign (backslash) to tell the post processor to go on reading the macro on the next line.
Line 238: Line 238:
 We can also indicate what we want to happen if the condition is not met (OR ELSE). If we want to change the macro for the change of tools so that M66 is output at the first change of tools and M67 (notice that this example is not necessarily logical but only used to explain the functions of the language) is output at all subsequent changes of tools we must add a pair of brackets to be executed if the condition is not met. This is done like this: We can also indicate what we want to happen if the condition is not met (OR ELSE). If we want to change the macro for the change of tools so that M66 is output at the first change of tools and M67 (notice that this example is not necessarily logical but only used to explain the functions of the language) is output at all subsequent changes of tools we must add a pair of brackets to be executed if the condition is not met. This is done like this:
  
-''&​F25(” M66),(” M67)''​+''​%%&F25(" ​M66"),(" ​M67")%%'' ​
  
 This means: IF FLAG 25 IS NOT SET OUTPUT M66 OTHERWISE OUTPUT M67 AND SET THE FLAG. This means: IF FLAG 25 IS NOT SET OUTPUT M66 OTHERWISE OUTPUT M67 AND SET THE FLAG.
Line 244: Line 244:
 After all types of conditions we can print an alternative pair of brackets separately with a comma sign to be executed if the first pair of brackets was not executed. Those who know some BASIC would picture the above line like this: After all types of conditions we can print an alternative pair of brackets separately with a comma sign to be executed if the first pair of brackets was not executed. Those who know some BASIC would picture the above line like this:
  
-''​IF F25=0 THEN  +''​%%IF F25=0 THEN %%''​ \\ 
-  PRINT ” M66”  +''​%% ​ ​PRINT ​" ​M66" %%'' ​ 
-ELSE  +''​%%ELSE %%'' ​ 
-  PRINT ” M67”  +''​%% ​ ​PRINT ​" ​M67" %%'' ​ 
-END IF \\ +''​%%END IF %%'' ​\\ 
-F25=1 +''​%%F25=1%%''​  
-''​ +
- +
  
  
Line 280: Line 279:
 If we want a pair of brackets to be repeated controlled by a parameter we write: If we want a pair of brackets to be repeated controlled by a parameter we write:
  
-<​parameter> ​ *()+''​%%<​parameter> ​ *()%%''​
  
 which means that the contents of the brackets will be repeated as many times as the contents of the parameter. which means that the contents of the brackets will be repeated as many times as the contents of the parameter.
Line 286: Line 285:
 Instead of the name of a parameter we can write a calculation,​ a variable or an integer between the < and > signs. These will be created in the same way as a parameter of the post processor. See example below! Instead of the name of a parameter we can write a calculation,​ a variable or an integer between the < and > signs. These will be created in the same way as a parameter of the post processor. See example below!
  
-''<​10>​ \\ +''​%%<​10> ​%%'' ​\\ 
-<​5+toolnr>​ \\ +''​%%<​5+toolnr> ​%%'' ​\\ 
-<V1> \\ +''​%%<​V1> ​%%'' ​\\ 
-<​V1+toolnr>​ ''​ \\+''​%%<​V1+toolnr> ​%%''​ \\
  
 ==== Example ==== ==== Example ====
Line 478: Line 477:
  
 Before: \\ Before: \\
-''​M104 Set new X-pos              : &​V1<​ystopa>​("​ X#​x"​)''​+''​%%M104 Set new X-pos              : &​V1<​ystopa>​("​ X#x")%%''​
  
 After: \\ After: \\
-''​M104 Set new X-pos              : &​V1<​ystopa*2>​("​ X#​x"​)''​+''​%%M104 Set new X-pos              : &​V1<​ystopa*2>​("​ X#x")%%''​
  
 //- How do I get a decimal point after all numbers, even integers? My machine requires this otherwise the numbers will be interpreted as thousandths. //- How do I get a decimal point after all numbers, even integers? My machine requires this otherwise the numbers will be interpreted as thousandths.
Line 491: Line 490:
  
 Before: \\ Before: \\
-''​M104 Set new X-pos              : &​V1<​xstopa>​("​ X#x") \\ +''​%%M104 Set new X-pos              : &​V1<​xstopa>​("​ X#​x"​) ​%%'' ​\\ 
-M105 Set new Y-pos              : &​V2<​ystopa>​("​ Y#x") \\ +''​%%M105 Set new Y-pos              : &​V2<​ystopa>​("​ Y#​x"​) ​%%'' ​\\ 
-M106 Set new Z-pos              : &​V3<​zstopa>​("​ Z#x") ''​ \\+''​%%M106 Set new Z-pos              : &​V3<​zstopa>​("​ Z#​x"​) ​%%''​ \\
  
 After: \\ After: \\
-''​M104 Set new X-pos             : &​V1<​xstopa>​("​ X#​d0#​x"​) \\ +''​%%M104 Set new X-pos             : &​V1<​xstopa>​("​ X#​d0#​x"​) ​%%'' ​\\ 
-M105 Set new Y-pos             : &​V2<​ystopa>​("​ Y#​d0#​x"​) \\ +''​%%M105 Set new Y-pos             : &​V2<​ystopa>​("​ Y#​d0#​x"​) ​%%'' ​\\ 
-M106 Set new Z-pos             : &​V3<​zstopa>​("​ Z#​d0#​x"​) ''​ \\+''​%%M106 Set new Z-pos             : &​V3<​zstopa>​("​ Z#​d0#​x"​) ​%%''​ \\
  
 It could be that coordinate values are written out in several places in the post processor and then you will have to find these and enter the code #d0 there too. It could be that coordinate values are written out in several places in the post processor and then you will have to find these and enter the code #d0 there too.
Line 508: Line 507:
 Change the macros M6-M9 from looking like this: Change the macros M6-M9 from looking like this:
  
-''​M6 Clockwise arc < than 180° \\ +''​%%M6 Clockwise arc < than 180° %%'' ​\\ 
-: M108 M103 " G02" M104 M105 <​xcenti>"​ I#x" <​ycenti>​\ ​   " J#x" M101 M109''​+''​%%: M108 M103 " G02" M104 M105 <​xcenti>"​ I#x" <​ycenti>​\ ​   " J#x" M101 M109 %%''​
  
-''​M7 Clockwise arc > than 180°:​ M6''​ \\+''​%%M7 Clockwise arc > than 180°: M6%%''​ \\
  
-''​M8 C.Clockwise arc < than 180° \\ +''​%%M8 C.Clockwise arc < than 180° %%'' ​\\ 
-: M108 M103 " G03" M104 M105 <​xcenti>"​ I#x" <​ycenti>​\ ​   " J#x" M101 M109 ''​\\+''​%%: M108 M103 " G03" M104 M105 <​xcenti>"​ I#x" <​ycenti>​\ ​   " J#x" M101 M109 %%''​\\
  
-''​M9 C.Clockwise arc > than 180°: M8 ''​+''​%%M9 C.Clockwise arc > than 180°:​ M8 ​%%''​
  
 To look like this: To look like this:
wiki/en/ppedit.1570701464.txt.gz · Last modified: 2019/10/10 11:57 by admin