hi~~~

I'm running a case with CFX-4. I got an error message....

MAX. NO. OF INTER-BLOCK BOUNDARIES EXCEED PLEASE CORRECT AND RESUBMIT JOB THE CFX-4 SOLVER HAS BEEN STOPPED BY SUBROUTINE GLUE

What's the meaning of this error message ? Thank you for your help~~~

Devin

Devin,

This message happens most often when building the grid within the command file. There's a command set for the top of the command file that fell out of standard usage (you can still find it in the help files though).

>>CFX4
:>SET LIMITS

MAXIMUM NUMBER OF INTER BLOCK BOUNDARIES n

Set n to increase the maximum allowable. If the error message doesn't give you a clue as to how many were requested, start at say 200 and work your way up by 100's until the message goes away.

You'll probably run into some of the other limits as well, however, and will need to look these up whenthey occur

MAXIMUM NUMBER OF BLOCKS

MAXIMUM NUMBER OF PATCHES

TOTAL CHARACTER WORK SPACE

TOTAL REAL WORK SPACE

TOTAL INTEGER WORK SPACE

These all go under the >>SET LIMITS command.

Jeff

hi,Jeff~~

I've set Unmatched Boundaries in "run build". I set "BLKBDYSLIDING1" & "BLKBDYSLIDING2" on interface between stationary part and moving part.

When I set command, I got some error message, If I set--
:>GLUE PATCHES FIRST PATCH NAME 'BLKBDYSLIDING1' SECOND PATCH NAME 'BLKBDYSLIDING2'

The error is-- ERROR IN SUBROUTINE GLUE PATCH NAME BLKBDYSLIDING2 DOES NOT EXIST ERROR: MULTIPLE PATCHES ON MATCHED-GRID INTERFACE USING PATCH NAME 'BLKBDYSLIDING1' INTER-BLOCK BOUNDARY PATCHES FOR MATCHED-GRID INTERFACES SHOULD HAVE A UNIQUE NAME FOUND 1 ERRORS IN GLUE PATCHES INFORMATION PLEASE CORRECT AND RESUBMIT JOB THE CFX-4 SOLVER HAS BEEN STOPPED BY SUBROUTINE CHKIBB

If I set--
:>GLUE PATCHES FOR UNMATCHED GRIDS FIRST PATCH NAMES BLKBDYSLIDING1 SECOND PATCH NAMES BLKBDYSLIDING2

The error is-- ******************* ERROR ****************** THE FOLLOWING KEYWORD HAS NOT BEEN PROCESSED FIRST PATCH NAMES BLKBDYSLIDING1 ******************************************** ******************* ERROR ****************** THE FOLLOWING KEYWORD HAS NOT BEEN PROCESSED SECOND PATCH NAMES BLKBDYSLIDING2 ******************************************** ####> ERROR. NO PATCH NAMES GIVEN FOR FIRST SIDE OF UNMATCHED-GRID GLUE PATCH ####> ERROR. NO PATCH NAMES GIVEN FOR SECOND SIDE OF UNMATCHED-GRID GLUE PATCH THE CFX-4 SOLVER HAS BEEN STOPPED BY SUBROUTINE DEFGUM

Can you please give me some advice on this problem?

Best Regards, Devin

Use the GLUE PATCHES FOR UNMATCHED GRIDS command....

>>GLUE PATCHES FOR UNMATCHED GRIDS FIRST PATCH NAMES 'BLKBDYSLIDING1' SECOND PATCH NAMES 'BLKBDYSLIDING2'

....and don't forget to quote your patch names!!

Jeff

Hi,Jeff

I've created the unmatched boundaries "BLKBDYSLIDING1" and "BLKBDYSLIDING2" on the interface between stationary part and moving part in "run bulid". And I've quoted the patch names when use the GLUE PATCHES FOR UNMATCHED GRIDS command. But the error message is still emerge when I run SOLVER. The error is---ERROR: UNKNOWN PATCH NAME 'BLKBDYSLIDING2' HAS BEEN REFERENCED IN 'SECOND PATCH NAMES' OF '>> GLUE PATCHES FOR UNMATCHED GRID' 1 ERRORS DETECTED IN SUBROUTINE GUM PLEASE CORRECT AND RESUBMIT THE JOB THE CFX-4 SOLVER HAS BEEN STOPPED BY SUBROUTINE GUM .

Could you provide me with some advice? Thanks!!

Devin

Devin,

You're making progress if the only unrecognized patch is the second one. Look in your .geo file and make sure both patches are there and that you're spelling them correctly.

Jeff

hi,Jeff~~

WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWWWWWWWWWWWWWW FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFF SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS SSSSSSSSSSSSS SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS SSSSSSSSSSSSS AAAAAAAAAAAAAAAAAQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQ QQQQAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

I've created the unmatched boundaries "BLKBDYSLIDING1" and "BLKBDYSLIDING2" on the interface between stationary part and moving part in "run bulid". But I didn't find out the patch "BLKBDYSLIDING2" in .geo file. Why can I not find "BLKBDYSLIDING2"? Is it not right to creat "BLKBDYSLIDING2" on the surface of the conducting solid?(the moving part is a conducting solid, and the interface is between interblock and conducting solid) Thanks in advance!

(W:wall F:fluid S:conducting solid wiht a constant velocity A:adiabatic Q:constant heat flux)

Devin

AHA!

Sorry, you can't do that. Unmatched boundaries have to be between fluid cells. CFX-4 puts a wall patch at the surface of your conducting solid as an interface to the fluid and this is overwriting your BLKBDY patch.

Typical resolution is to put at least two fluid elements between the unmatched boundary and the wall. Just move it in a little.

Jeff

hi,Jeff

I've put two fluid elements between the unmatched boundary and the wall. But when I run SOLVE, there is no .dmp file produced. The .fo file says "ON UNMATCHED-GRID INTERFACES HAVE NO CONNECTED NEIGHBOUR" "POSSIBLY THE BLOCKS ON EITHER SIDE OF THE INTERFACE HAVE MOVED TOO FAR APART" "PLEASE CORRECT AND RESUBMIT JOB" "THE CFX-4 SOLVER HAS BEEN STOPPED BY SUBROUTINE CONNCT"

What's wrong with my case... Thanks!

Devin

Devin,

Read the message. It says your interfaces don't match up. Each side of an unmatched interface has to match the other exactly in terms of overall area. If it's a curved surface (as in a mixing tank analysis) the curvature has to match as well.

Cases can occur where, because of the courseness of the mesh, the curvature is not mapped close enough and the resulting interface gap exceeds the allowable tolerance. Refining the mesh usually corrects this.

Otherwise, I can't tell from here. Examine your surfaces to make sure the total surface area matches.

Jeff