Turn on suggestions

Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.

Showing results for

- Navigation
- Tecnomatix
- Forums
- Blogs
- Knowledge Bases
- Groups

- Siemens PLM Community
- Tecnomatix
- Plant Simulation
- Two Interesting details in 12.1

Options

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

09-22-2015 05:14 PM

- I found it a bit odd that method getcolYdim was created but getrowXdim wasn't. Meaning I would need to transpose all tables having data by rows.
- Debugger expressions seems to not work properly with formulas as shown in the next picture

cortega@interlatin.com.mx

+52 (81) 10801310

InterLatin S de RL de CV

+52 (81) 10801310

InterLatin S de RL de CV

Solved! Go to Solution.

4 REPLIES

Re: Two Interesting details in 12.1

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

09-23-2015 01:09 AM

Yeah, I found the first point odd too. Would make sense to add both.

For the second part, is the method formatted as a SimTalk 1.0 method? You need to convert it correctly to a SimTalk 2.0 method to use expressions in 12.1. It's been mentioned to be fixed in the coming patch.

So replace local with var, remove ; and remove is do end;.

Then add var before all the variables you had between is and do.

Replace the return value to use -> instead.

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

09-23-2015 03:25 AM - edited 09-23-2015 09:44 AM

Plant Simulation internally stores the contents of a table in a list of columns. Therefore Plant Simulation can find out the y-dimension of a column very fast. Computing the x-dimension of a row would be significantly slower (in case that there are many columns). I think this is the reason we implemented only 'getColumnYDim'.

If you really need a 'getRowXDim', please say so. We then might provide it in the next version.

As has already been said, it is a known bug that in version 12.1 the debugger cannot evaluate some expressions. We will fix this for the next maintenance pack.

_________________________________________________________________

Did you like the answer? Then click the Thumbs Up button.

Did the answer solve your problem? Then accept the answer as solution.

Did you like the answer? Then click the Thumbs Up button.

Did the answer solve your problem? Then accept the answer as solution.

Re: Two Interesting details in 12.1

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

09-23-2015 09:39 AM

Actually it was in a V2.0 method.

But the thing is in this case arithmetic formulas cannot be evaluated.

Anyway for me where interesting details... if the does't make sense incorporating a getrowXdim for performance reasons then its ok.

Good day

cortega@interlatin.com.mx

+52 (81) 10801310

InterLatin S de RL de CV

+52 (81) 10801310

InterLatin S de RL de CV

Re: Two Interesting details in 12.1

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

09-23-2015 09:53 AM

We are aware that the debugger expression problem exists in SimTalk 1.0 and 2.0. We have already fixed that problem for the next maintenance pack (that will probably be released in about 3 weeks from now).

As a workaround, you can enclose your expression in to_str().

For example the expression '1+2' is not working, but 'to_str(1+2)' is.

_________________________________________________________________

Did you like the answer? Then click the Thumbs Up button.

Did the answer solve your problem? Then accept the answer as solution.

Did you like the answer? Then click the Thumbs Up button.

Did the answer solve your problem? Then accept the answer as solution.

Follow Siemens PLM Software

© 2019 Siemens Product Lifecycle Management Software Inc