splash error HCRTAR (what does it mean?)

Hello,

I tried to generate Iso in the design module using our in-house macros but after several extractions an error will occur on pdms console...

ERROR in SPLASH routine HCRTAR Area: 'NULL SPLASH AREA' Error:19 TMA too many areas <> 127>

At first, I thought it was because of the number of loops but there is no definite number of pipes to where this error will occur.
I was wondering if you guys have encountered same error and already fixed it. Would you mind sharing it with us??? :embaressed_smile:

Anyways is it alright to produce Iso in Design module? Is there any side effects?or maybe this error is one.. (I hope not...)..

Thanks....

I have not seen any errors with isometrics run in Design (Isodraftmode). I do believe that sometimes the files in the PDMSUSER directory needs to be cleaned up.

I've seen these errors sometimes. They are related to your LAN connection. Happens when the server connection was lost or intermittently appearing / disappearing.

Last week I received a splash error.....here are the circumstances........

I needed to replace a structural joint detail with another created on a different structure.  I could have updated my joint....but to save time....I copied the joint from the different structure and qualified the components.  Once I was satified,  I deleted my joint and replaced it with the new joint.  All heirarchy changes were made to match as closely as possible with the existing format. I had an existing draft drawing of the old joint already created.  All seemed fine  when I opened the existing draft drawing excepted for some missalignment of glabs,slabs and dimensions. Next I navigated to a view to perform a graphics design update.  To my suprise....my dimensions, glabs, slabs and btext elements dissapeared.  The new joint detail varied enough to disconnect with existing draft elements.  So I quit out of the draft session and reloaded a new draft session. I then began the process of goin to each view to re-attach all the existing draft elements.  All seem to be working fine....then in the middle of the process my draft drawing locked up and notified me of a splash error.  I quit out of the draft session and reloaded a draft session....however.....the splash error became a road block.....no matter how many time I reloaded a session......I was locked up with a splash error........

finally....I requested help from our PDMS adminstrator....He said oh this has happened before......all I needed to do was DATAL out a file of the existing draft file in question and reload.  To my surprise.....it worked.  Some of the existing draft elements that I had not re-attached had dissapeared....however....at least I was able to save some without starting over.

In the series of events you have described.
The DB Refs is another reason for disappearance of GLABs and SLABs.

1. When you modify the element in design the db ref remains the same and attributes change.

2. But when you do Delete Old >> Create New instead of modify and rename it, looks good in design but not in draft.

3. Draft remembers the design by DB Ref and not by the names we assign in design and hierarchy.

I'm not good when it comes to handling draft but this is what I remember from past assignments.

I have not seen any errors with isometrics run in Design (Isodraftmode). I do believe that sometimes the files in the PDMSUSER directory needs to be cleaned up.

I beleive this to be true....the solution for a re-ocurring splash error was solved by taking the existing draft file and creating a DATAL OUT file and reloading back into draft........circumstances described in my previous post.

I think Splash error occurs when you do some things that requires memory allocation, as far as I noticed. Some users will have error after 103rd ISO extraction on PDMS Design. It makes me more suspicious that PDMS doesn't release memory well but, it's only a theory though.
Thanks guys..

Well that is why in some companies the Iso's are run in TTY mode which does not display graphics which need updating after every iso run.

Well that is why in some companies the Iso's are run in TTY mode which does not display graphics which need updating after every iso run.

I see, this is also the kind of advice I received from AVEVA. Anyway, I tried to make it run in TTY mode and so far it run smoothly as I wanted. Hopefully it won't disappoint me.
Thanks by the way at least I have a testimony that some companies are using this. :_: