Hi,
This reminds me of a question I answered a few days ago:
Have a look at this, try somethings and then get back if you need more information!
Hi,
You are right, I forgot about that.
The problem I faced in answering the question, just I have with you, is that you don't tell how Y updates. That's why I gave all the ingredients to the solution, but couldn't provide the worryfree code.
Example 1:
X = Y * 10 (X is a function of Y) AND
Y = [1,2,3,4,5,6..] (a fixed set of values)
Then put both in the loop, update Y, update the document and export X.
Example 2:
X = Y * 10
Y = Manual input OR Area/param1*param2 (depending on all kinds of things which may not have direct parameterized input)
Then forget about the loop, make a TextParameter that you set to A1 and update after each iteration to A2, A3 etc.
So if you can tell me how you want to use it, then I can provide a code that suits your needs.
Hi,
First define a User Parameter Row_number=1 (first value)
Make an ilogic rule like this, should be straight forward:
'Define the excel columns A to D to write to: Cell_X1="A" & Row_number Cell_X2="B" & Row_number Cell_Y1="C" & Row_number Cell_Y2="D" & Row_number 'Write the values GoExcel.CellValues(File, "Blad1", "Cell_X1") = X_Afstand_1_Ruit GoExcel.CellValues(File, "Blad1", "Cell_X2") = X_Afstand_2_Ruit GoExcel.CellValues(File, "Blad1", "Cell_Y1") = Y_Afstand_1_Ruit GoExcel.CellValues(File, "Blad1", "Cell_Y2") = Y_Afstand_2_Ruit 'Update the rownumber such that next time you write to the next row Row_no=Row_no+1
Now when a variable in the rule changes, here X_Afstand for example, the rule is triggered so it writes the values to Excel.
To be honest I didn't test this, so there might be a small issue running it like this.
Let me know how it goes.
Hi,
I made some updates to the code. I realized there were some issues. In order for this to work make sure that the excel sheet behind "FILE" exists.
The Save and close commands are there such that you will be able to see the results whenever you want.
File="C:\Users\asiteur\Desktop\TESTEXCEL.xlsx"
'Define the excel columns A to D to write to:
Cell_X1="A" & Row_number
Cell_X2="B" & Row_number
Cell_Y1="C" & Row_number
Cell_Y2="D" & Row_number
MsgBox("Exporting data to: " + File + " Row number: " + CStr(Row_number))
'Write the values
GoExcel.CellValue(File, "Sheet1", Cell_X1) = X_Afstand_1_Ruit
GoExcel.CellValue(File, "Sheet1", Cell_X2) = X_Afstand_2_Ruit
GoExcel.CellValue(File, "Sheet1", Cell_Y1) = Y_Afstand_1_Ruit
GoExcel.CellValue(File, "Sheet1", Cell_Y2) = Y_Afstand_2_Ruit
GoExcel.Save
GoExcel.Close
'Update the rownumber such that next time you write to the next row
Row_number=Row_number+1
Hi,
It was never clear to me that you wanted to write the values to different excel files. Beaware btw that you are writing Y2 to Y1.xls in your script.
Well, you can define a list in iLogic (not a multivalue list because they are annoying) in which you document the steps. You could start with a 0 step such that the initial Afstand is also used.
myStepList={1,3,10}
Afstand=Afstand + myStepList(Row_no-1)
This example would add the step to "Afstand" and then keep adding (afstand= initial Afstand + 1+3+10). Put this is a separate rule which you surpress (such that it doesn't run automatically)
You could make an iLOgic form with a button that runs this rule.
Because Afstand makes changes to 'X1' etc that rule will be triggered
Hi,
You have a valid point there, it doesn't work as I would expect.
First when you do something like this add a document update within your loop:
InventorVb.DocumentUpdate()
Otherwise the parameters will only update after the last iteration.
But then still it doens't write the values properly.
I'm not sure why, but it does work when you get rid of all the Open, Save, and Close commands. (It makes you code 100 times faster too)
You can save and close at the end of the code to save the excelsheet once.
Best,
Alexander
No,
The update command updates the Inventor Document, it's the exact same thing as the yellow lightning button in the top menu in Inventor.
What you do now makes no sense ,you do an update after making no changes to the document, which is just a waste of time and coding.
Typically you need 1 update command per rule.
You only need to ask yourself, when do I need to update this document. Well probably, after the afstand=afstand+0.5 line, and BEFORE the construction of the Cell identifiers.
Hi,
Oke well there is a dozen of things that I don't understand why you are working like this.
First and probably most importantly: get the export to excel part of the rule in a separate rule. Now you trigger everything over and over again.
2) Then get the Open close and Save commands out as I said,
3) Put the document update in properly
Then if that doesn't work:
4) why have you linked the excelsheets? There is no need to do this and I would suspect it to do more wrong than right
Ultimately if you could make a screencast of what's happening that would 'boekdelen spreken' probably.
Best,
Alexander
Hi,
Thank you for taking the time to make the screencast.
Oke I understand your problem. I wasn't aware of this issue because the 'excel already open'-message doesn't appear on my system, that might be due to the version of excel you are running or a setting somewhere. Regardless you should be able to run your rule properly. For next time, whenever you add something to your code that wasn't asked or even advised against, explain clearly what made you do so.
What we are encountering here is a limitation to iLogic, in the sense that you cannot control the excel instance you open using these snippets. In a normal programcode you can use a handle on a program instance such that handleonexcel.close() would close this specific instance. Now what you are doing in excel is always closing the last openend.
Slowly we are getting to what I think is the issue: the first 'Open' command, because you open the excelsheet first and then the next statement ALSO opens the sheet. Then you only close the last one such that you get an enormous amount of warnings.
You should also reset your 'row_number' parameter sometimes otherewise you'll have to scroll more and more in your sheet.
So what I think you should do:
1) Strip the 'Open'commands out
2) LEAVE the close and save commands
For me (again) this works. If you have trouble doing it like this, I'm really running out of ideas on how to get this right.