Final assembly problem with Driveworks, message: "the index is outside the boundaries of the array"

3D Design Volume Model
1

Hello

As the title says, I have a problem with the final assembly of my project.

I have a main assembly made up of sub-assemblies. When I launch my form, DW drives SW and builds all the subassemblies first. I guess I'm not telling you anything.

So far everything is going well, no freezes or errors indicated by the autopilot. The time comes to open the complete assembly. It opens in SW with everything it has built beforehand + other elements that are in my base model and must be removed during the final assembly + manage the assembly functions.

Except that once opened, everything stops. When I go through autopilot, SW closes completely, it tries twice to continue the process but it comes across the same problem which is as indicated on autopilot "the index is outside the limits of the array". When I test in step by step (Test mode, Queued, interactive) it stops just after opening the assembly and there it puts in red "generate component map" and when you go over it "the index is outside the limit of the array".

In short, always the same message but no other information.

I have spotted configurations that cause this problem (because it is not systematic) and I have therefore done different tests on them. By generating the subassemblies one by one, there is never a problem, it is only during the final assembly. And I can' t isolate any subassembly or element that causes the error all the time. I always have a case that works.

Today I only know one thing, when I launch my project directly with Solidworks in the Driveworks module that is integrated into it, it works until the end while I get the error when going through Driveworks Admin or Autopilot.

The difference is that I have references that get lost on extrusion functions for example by going through SW while they go very well with DW.

Has anyone ever encountered this error message and/or had the same problem?

I suspect that what is stuck must be in my programming but I look for a needle in a haystack with no other information than this message.

Thank you for your help.

Sarah

 

2

Hello

I don't have driveworks but in programming, when we get this message, it's that we called an element that is not in a list or an array.

Check this point, maybe ask you for a component whose name is misspelled or an item in a collection with a wrong Id.

1 Like
3

Hello

Totally agree with Yves.T and without forgetting that the indexes start at 0 ...

1 Like
4

Hello

Thank you for your answers, I'll check all that.

5

Hello s.loue,

Is this problem still present?

If so, I advise you to turn to your SOLIDWORKS reseller for technical support, this problem will require a lot of additional information and direct assistance.

If they can't solve this problem, they will turn directly to DriveWorks technical support and we will take a look!

Sincerely,

Thomas

6

Hello

Thank you Thomas. This was already the case at the same time, I am in contact with my dealer. But it took a lot of time so I tried the forum.

Unfortunately, I haven't actually found the cause of the problem, but it seems that the new version of Driveworks has solved it.

This has led to new little problems that I didn't have before. But that's another story...

Thank you all

Sarah

7

Problem solved by changing the software version.

I will probably never know the cause...

Thank you