PXML

PXML

jesper.gustavsson
Explorer Explorer
2,764 Views
11 Replies
Message 1 of 12

PXML

jesper.gustavsson
Explorer
Explorer

Hi,

 

Is it possible to export the PXML with project number and element mark, based on parameters in the Revit project?

 

Many thanks

 

@teodorb 

0 Likes
2,765 Views
11 Replies
Replies (11)
Message 2 of 12

jeremytammik
Autodesk
Autodesk

I searched the Internet for PXML and am so far unable to guess what you mean by that.

 



Jeremy Tammik
Developer Technical Services
Autodesk Developer Network, ADN Open
The Building Coder

0 Likes
Message 3 of 12

jeremytammik
Autodesk
Autodesk

By the way, is this a Revit API issue, or an end user question?

 

Are you doing anything programmatically yourself, or just using the standard Revit user interface?

 

If you are not doing anything programmatically, this is not the best place to ask such a question.

 

Please note that this discussion forum is dedicated to programming Revit using the Revit API.

 

Therefore, you cannot expect an answer to a question such as yours relating to product usage or end user support issues here.

 

You should try one of the non-API Revit product support discussion forums instead for that:

 

https://forums.autodesk.com/t5/revit-api-forum/this-forum-is-for-revit-api-programming-questions-not...

 

The people there are much better equipped to answer your question than us programming nerds.

 

If you are doing it programmatically, please be aware that the Revit API hardly ever supports any functionality that is not also available in the user interface.

 

Please be aware that the Revit API generally only supports functionality that is also available in the user interface.

 

Therefore, if the UI does not support this, the API will probably not do so either.

 

So, it will always help to research the optimal manual approach to a solution first, before attacking the task programmatically.

 

I hope this clarifies.

 

Thank you for your cooperation and understanding.

 

Best regards,

 

Jeremy

 



Jeremy Tammik
Developer Technical Services
Autodesk Developer Network, ADN Open
The Building Coder

0 Likes
Message 4 of 12

teodorb
Autodesk
Autodesk

Hi @jesper.gustavsson,

You can use the parameters for PXML in the Configuration. Would you need additional parameters than the ones available there? For the mark number, is the ProdNo parameter enough?

Kind regards,

Bogdan Teodorescu



Bogdan Teodorescu

Product Owner
0 Likes
Message 5 of 12

jesper.gustavsson
Explorer
Explorer

Hi @teodorb and @jeremytammik,

I want to achieve a PXML similar to the "old.png".

It doesn't have to be exactly the same, but the red text is the parameters that I want to change/set.

 

Thanks and best regards,

Jesper

0 Likes
Message 6 of 12

jesper.gustavsson
Explorer
Explorer

I tested to set a value on the ProdNo parameter, but it didn't appear in the PXML file. When I change the header in the file it works with the machine's software, but I only get a list of all the rebars. I need to export more information so I know which project and element mark the rebar belongs to.

 

Best regards, 

Jesper

0 Likes
Message 7 of 12

teodorb
Autodesk
Autodesk

Hi @jesper.gustavsson ,

We would like to learn more about your needs. Would it be possible to contact you in private?

 

Thank you,

Bogdan Teodorescu



Bogdan Teodorescu

Product Owner
0 Likes
Message 8 of 12

Zengwa
Community Visitor
Community Visitor

Hi Jasper,

How is revit in precast?

0 Likes
Message 9 of 12

KE-engineering
Contributor
Contributor

Hi @teodorb , 

I am currently in contact with Progress Group (the developer of the PXML format), and they have indicated that the Revit PXML export is missing certain information — in our case, the <Pos> field. Without this information, it is not possible to correctly interpret the rebar data in BFW (www.lic.nl), which is widely used in the rebar industry. Tekla does export the <Pos> field but that's not what we want.

 

Would it be possible to get in touch? I would greatly appreciate your help with this issue. I have also received example files from Progress Group that clearly illustrate the problem.

0 Likes
Message 10 of 12

KE-engineering
Contributor
Contributor

Hi Jeremy,
I know this is an old post but the Precast pxml export is a big problem. The export lacks of crucial information (Revit ElementId which has to be in the <Bar> field. It also misses the <POS> field. But I can program to fill that when the bars ElementIds are exported.

Is there anyway you can help me (and a lot of other engineers working in the precast industry) with this? I really really don't want to switch to Tekla which does a good pxml export.

Regards,

Dennis

0 Likes
Message 11 of 12

ctm_mka
Collaborator
Collaborator

@KE-engineeringJeremy is retired, so not sure he's going to answer here, that being said, three things. First, make an ideas post to fix this. Three, file a support request as this does seem like an oversight. Three, if you into actual programming (you know, what the API forum is about) the PXML file that ive seen in these posts is just an xml file with certain nodes. Which means you could absolutely modify/create it yourself using C#.

0 Likes
Message 12 of 12

KE-engineering
Contributor
Contributor

Hello Conor,

Thank you for your response. I wasn’t aware that Jeremy had retired.

The PXML file is indeed just a standard XML file, and I am currently working on developing the necessary Python code. However, transforming a reinforcement cage into a position that a PXML import program can interpret correctly is not straightforward.

The precast CAM export handles this perfectly, but the ElementId is missing in the <Bar> field. This appears to be a Revit bug. If this ID were included, anyone would be able to write their own code to easily enrich the PXML file.

Kind regards,

Dennis

0 Likes