Navigating through the CELUS Design Studio, users might occasionally encounter errors that can hinder the progress of their projects. The Error and Warnings Panel is designed to provide actionable feedback, helping users to identify and resolve issues within their design workflow. This article aims to clarify some common error messages encountered on the platform, offering guidance on how to address them effectively.
No matching CUBOs found for block {block number}, {block name}: Consider using alternative Specifications or Interfaces for the connections between Functional Blocks.
CUBOs are chosen for a functional block from our database with careful consideration given to their specifications and requirements of their ports. When the specifications are narrowly defined or there is a high number of connected links, the pool of CUBOs that satisfy these requirements may become limited. To resolve this issue, we recommend these strategies: broaden the specifications, choose a more generic functional block, reduce the number of links connected to the block, or consider removing the interface requirements for the links connected to the block.
No common interface: The Functional Blocks don't have a compatible interface.
This issue arises when the functional blocks could be resolved to CUBOs but lack a shared interface that is compatible. To resolve this issue, we recommend the following: broadening the specifications of the functional blocks connected to the link causing the issue, selecting a more generalised functional block. These strategies increase the pool of CUBOs, improving the chance of finding CUBOs that share a compatible interface. Additionally, the interface specification of the link causing the issue could be removed. If the link in question is not critical to the project, it may be beneficial to remove it entirely.
Infeasible connection: The connection could not be established due to the amount of connections.
This issue presents itself when CUBOs, while having compatible interfaces between them, cannot be connected due to the compatible interface used in another connection. To rectify this, interface specifications from the problematic link could be removed. Expanding the functional scope and specifications of the functional block could also be beneficial, as it increases the number of CUBOs that could be matched to the functional block. If the issue persists, consider removing the problematic link if it is not essential to the project.
CUBO is Locked: If the locked CUBO solution is no longer available in the Platform database, but you previously resolved the project, the Platform will display an error message stating: 'The CUBO solution for {block number} {block name} can no longer be connected to the rest of the project.
To address this issue, consider unlocking the CUBO™ in the results view and then re-resolving the project. Alternatively, loosening the specifications for the functional block or the configuration of the connecting links may be beneficial. This broadens the criteria, thus enhancing the likelihood of retaining the locked CUBO™ in the results.