Search found 20 matches
- 20 January 2022, 10:35
- Forum: CAPE-OPEN Binary Interop Architecture
- Topic: Optional Port in COBIA unit operation
- Replies: 7
- Views: 18076
Re: Optional Port in COBIA unit operation
Thank you for the great tips. I have a much better idea now for the different ways I can have my implementation.
- 18 January 2022, 06:05
- Forum: CAPE-OPEN Binary Interop Architecture
- Topic: Optional Port in COBIA unit operation
- Replies: 7
- Views: 18076
Re: Optional Port in COBIA unit operation
Here is a sample of a collection template implementing ICapeIdentification and ICapeCollection which similar to the sdk documentation: #pragma once #include <COBIA.h> using namespace COBIA; template <typename MyCollectionItem> class MyCollection : public CapeOpenObject<MyCollection<MyCollectionItem>...
- 15 January 2022, 17:38
- Forum: CAPE-OPEN Binary Interop Architecture
- Topic: Optional Port in COBIA unit operation
- Replies: 7
- Views: 18076
Re: Optional Port in COBIA unit operation
I am curious if there is an alternative way to create a collection class with my_port_class as a collection Item. If I use my_port_classPtr instead of CAPEOPEN_1_2::CapeUnitPort I always get the following build error: Error C2039 'outputArgument': is not a member of 'COBIA::CapeOpenObjectSmartPointe...
- 28 December 2021, 16:10
- Forum: CAPE-OPEN Binary Interop Architecture
- Topic: Optional Port in COBIA unit operation
- Replies: 7
- Views: 18076
Re: Optional Port in COBIA unit operation
Thank you once again for your guidance. I have sucessfuly implemented and validated primary and optional streams by casting CapeUnitPort to my MaterialPort class as you suggested.
- 27 December 2021, 16:29
- Forum: CAPE-OPEN Binary Interop Architecture
- Topic: Optional Port in COBIA unit operation
- Replies: 7
- Views: 18076
Optional Port in COBIA unit operation
I am trying to implement optional ports in COBIA unit operation and I have some doubts about the best way to do so. Assuming a simple mixer unit operation with MaterialPort class implementing the Unit Port (and identification) interface. Let's say I add additional members and/or additional methods, ...
- 01 November 2021, 13:41
- Forum: Unit Operations
- Topic: Error getting single phase heatCapacityCp
- Replies: 2
- Views: 6569
Re: Error getting single phase heatCapacityCp
Turns out I overlooked this step indeed. Thanks as usual for great support and tips. Working as intended now.
- 31 October 2021, 12:23
- Forum: Unit Operations
- Topic: Error getting single phase heatCapacityCp
- Replies: 2
- Views: 6569
Error getting single phase heatCapacityCp
Greetings, I am trying to get heatCapacityCp for calculation method in COBIA unit operation but getting the following error: CAPE-OPEN error, caused by: in ICapeThermoMaterial::GetSinglePhaseProp of 'feed': no values set for heatCapacityCp, phase Vapor, CalcType mixture (2x) Here is a sample code: C...
- 12 September 2021, 11:40
- Forum: Unit Operations
- Topic: Implementing reaction interface on a COBIA Unit
- Replies: 4
- Views: 9696
Re: Implementing reaction interface on a COBIA Unit
Thanks as always for your reply. Is there a timeline for the Reactions 1.1 specifications and integration into COBIA?
- 10 September 2021, 12:53
- Forum: Unit Operations
- Topic: Implementing reaction interface on a COBIA Unit
- Replies: 4
- Views: 9696
Implementing reaction interface on a COBIA Unit
Greetings Dr Jasper and fellow developers,
I could nit find the Chemical Reactions interface specifications consistent with Thermo 1.1 or any mention to the interfaces in COBIA reference documents. Is it not possible yet to develop a reactor unit using COBIA SDK?
I could nit find the Chemical Reactions interface specifications consistent with Thermo 1.1 or any mention to the interfaces in COBIA reference documents. Is it not possible yet to develop a reactor unit using COBIA SDK?
- 09 August 2021, 08:28
- Forum: Unit Operations
- Topic: COBIA EnergyPort Class
- Replies: 5
- Views: 9845
Re: COBIA EnergyPort Class
Thank you once again for the clarification. The energy stream now exposes all the parameters just as it does with the built-in heater (at least it appears so). I can now comfortably move on to practise with more complicated units. https://user-images.githubusercontent.com/80135041/128679766-4597a3c9...