Differences between revisions 3 and 15 (spanning 12 versions)
⇤ ← Revision 3 as of 2008-02-26 20:18:45 →
Size: 1422
Editor: MichaelWetter
Comment:
← Revision 15 as of 2009-06-30 04:31:45 → ⇥
Size: 4473
Editor: MichaelWetter
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
#pragma section-numbers 2
Line 2: Line 3:
[[TableOfContents]]
Line 3: Line 5:
== Matlab does not compile (Windows only) ==
Under Windows, if the BCVTB is compiled using the Microsoft compiler, then
the Matlab libraries also need to be compiled with the Microsoft compiler.
Otherwise, the you may get a compilation error like:		 == Compilation problems ==
=== Error when compiling Ptolemy II (Windows only) ===
If running
Line 8: Line 10:
Writing library for establishBSDSocket.mexw32
c:\docume~1\mwetter\locals~1\temp\mex_ae679\simulinksocket.obj .text: undefined reference to '_establishclientsocket'
c:\docume~1\mwetter\locals~1\temp\mex_ae679\simulinksocket.obj .text: undefined reference to '_exchangewithsocket' 		make configPt
}}}
 or running

{{{
./configure && make fast install
}}}
 gives the following error

{{{
/bin/sh: -c: line 1: unexpected EOF while looking for matching `''
/bin/sh: -c: line 4: syntax error: unexpected end of file
}}}
then the source code is most likely with Unix line endings. Download the Windows source code from the Ptolemy web page.

=== Error when compiling MATLAB (Windows only) ===
Under Windows, if the BCVTB is compiled using the Microsoft compiler, then the MATLAB libraries also need to be compiled with the Microsoft compiler. If, however, the gcc compiler has been used when compiling the BCVTB, then the following compilation error may be obtained when compiling the MATLAB libraries:

{{{
Writing library for establishBSDSocket.mexw32
c:\docume~1\mwetter\locals~1\temp\mex_ae679\simulinksocket.obj .text: undefined reference to '_establishclientsocket'
c:\docume~1\mwetter\locals~1\temp\mex_ae679\simulinksocket.obj .text: undefined reference to '_exchangewithsocket'
Line 13: Line 34:
To fix this problem, open Matlab, run  To fix this problem, open Matlab, run
Line 19: Line 41:
=== Error when compiling MATLAB (Mac OS X with Matlab R2009a only) ===
Under Mac OS X, if the BCVTB is compiled in Matlab R2009a, the following error may occur:

{{{
Undefined symbols:
  "_mxGetM", referenced from:
      _mexFunction in establishBSDSocket.o
  "_mxGetN", referenced from:
      _mexFunction in establishBSDSocket.o
  "_mxIsNumeric", referenced from:
      _mexFunction in establishBSDSocket.o
  "_mxGetClassID", referenced from:
      _ssGetDTypeIdFromMxArray in establishBSDSocket.o
  "_mxCalloc", referenced from:
      __RegNumInputPortsCB in establishBSDSocket.o
      __RegNumOutputPortsCB in establishBSDSocket.o
      _mexFunction in establishBSDSocket.o
  "_mxGetPr", referenced from:
      _mexFunction in establishBSDSocket.o
  "_mxIsComplex", referenced from:
      _mexFunction in establishBSDSocket.o
  "_mxCreateDoubleMatrix_700", referenced from:
      _mexFunction in establishBSDSocket.o
ld: symbol(s) not found
collect2: ld returned 1 exit status
    mex: link of ' "establishBSDSocket.mexmaci"' failed.
??? Error using ==> mex at 218
Unable to complete successfully.
Error in ==> /Applications/MATLAB_R2009a.app/toolbox/simulink/simulink/+legacycode/@LCT/compile.p>compile at 261
Error in ==> /Applications/MATLAB_R2009a.app/toolbox/simulink/simulink/legacy_code.p>legacy_code at 91
Error in ==> compile at 58
    legacy_code('compile', def, ...
}}}
This problem is caused because the linker flags in Matlab changed in R2009a. To fix this problem, open the file {{{bcvtb/lib/simulink/compile.m}}} and remove the entry

{{{
-L/usr/lib
}}}
Then, recompile the file. This will be fixed in releases after version 0.1.1.
Line 20: Line 82:
The following steps typically help analyzing problems if a simulation program does not work as expected.
Line 21: Line 84:
If something goes wrong during the simulation,
check the files {{{utilSocket.log}}} and {{{utilClient.log}}}.
They contain log messages that may indicate the cause of the problem.
If these files do not exist, go to the directory {{{bcvtb/lib}}},
open the file {{{defines.h}}} and add the line		 === Check log files ===
If something goes wrong during the simulation, check the files {{{simulation.log}}}, {{{utilSocket.log}}} and {{{utilClient.log}}}. They contain log messages that may indicate the cause of the problem. If these files do not exist, go to the directory {{{bcvtb/lib}}}, open the file {{{defines.h}}} and add the line
Line 29: Line 90:
Then, from the directory {{{bcvtb/lib}}} compile the libraries using Then, from the directory {{{bcvtb/lib/util}}} compile the libraries using{{{
ant clean all
}}}
and rerun the simulation. Now the log files should be written to the directory from which you started the BCVTB.

=== Display program output ===
Depending on how simulation programs are called by the {{{Simulation}}} actor in Ptolemy, the console output written by the simulation program may not be visible. To see the console output, change the command line of the Ptolemy actor from
Line 31: Line 99:
make clean
make		  bash ./runClient.sh
Line 34: Line 101:
and rerun the simulation. Now the log files should be written to the
directory from which you started the BCVTB.		 to

{{{
 xterm -e bash ./runClient.sh
}}}
This will start a terminal that shows the output of the running simulation program which help analyzing what goes wrong, for example, when the simulation program terminates due to an error before connecting to the BCVTB.

Help

TableOfContents

1. Compilation problems

1.1. Error when compiling Ptolemy II (Windows only)

If running 

make configPt
  • or running 

./configure && make fast install
  • gives the following error 

/bin/sh: -c: line 1: unexpected EOF while looking for matching `''
/bin/sh: -c: line 4: syntax error: unexpected end of file

then the source code is most likely with Unix line endings. Download the Windows source code from the Ptolemy web page.

1.2. Error when compiling MATLAB (Windows only)

Under Windows, if the BCVTB is compiled using the Microsoft compiler, then the MATLAB libraries also need to be compiled with the Microsoft compiler. If, however, the gcc compiler has been used when compiling the BCVTB, then the following compilation error may be obtained when compiling the MATLAB libraries: