FOCUS Software Engineering is now part of proconX Modbus protocol stack and library   
Main  
FieldTalk Modbus   
Overview  
Documentation  
Evaluation  
Testimonials  
Platforms   
Windows  
Linux  
QNX  
Commercial Unix  
Java  
Delphi  
Product Details   
Visit our Webstore   
Features  
Requirements  
Licensing  
Support Plans  
Documentation   
General Description  
Module Description  
Class Hierarchy  
Modbus Background  
Examples  
Integration  
  
FieldTalk Modbus Master C++ Library  Library version 2.9.0
Installation and Source Code Compilation

Windows Platforms: Unpacking and Preparation

1. Download and save the zip archive into a project directory.

2. Uncompress the archive using unzip or another zip tool of your choice:

# unzip FT-MBMP-WIN-ALL.2.8.0.zip

The archive will create the following directory structure in your project directory:

myprj
|
+-+ fieldtalk
|
+-- doc
+-- include
+-- lib
+-- src
+-- samples
+-- Visual Studio

3. The library is ready to be used.

4. Optionally re-compile from source:

The Windows Editions do come with pre-compiled static libraries for Visual C++ and do not require compilation from source code. However there may be cases where re-compilation is desired.

To re-compile, open the Visual Studio\mbusmaster_win.vcxproj solution file with Visual Studio 2017. The project file will also work with older Visual Studio versions. The library will be compiled into one of the following sub-directories of your project directory:

Platform Library Directory
Windows 64-bit, Visual Studio 2017 lib\win\x64\Release
Windows 32-bit, Visual Studio 2017 lib\win\Win32\Release
Windows CE, Visual Studio 2005 or 2008 lib\wce\\Release

Linux, UNIX and QNX Platforms: Unpacking and Compiling the Source

1. Download and save the zipped tarball into your project directory.

2. Uncompress the zipped tarball using gzip:

# gunzip FT-MBMP-??-ALL.2.8.0.tar.gz

3. Untar the tarball

# tar xf FT-MBMP-??-ALL.2.8.0.tar

The tarball will create the following directory structure in your project directory:

myprj
|
+-+ fieldtalk
|
+-- doc
+-- include
+-- src
+-- samples

4. Compile the library from the source code. Enter the FieldTalk src directory and run make:

# cd fieldtalk/src
# make

Note: Previous versions used a shell script to build, this version now uses the make utility to build.

The make file tries to detect your host platform and executes the compiler and linker commands targeting the host platform. The compiler and linker configurations are contained in the platform make files in the makefiles folder.

To cross-compile, pass the basename of the cross-compilation make file as parameter:

# make arm-linux
# make qnx6-ppcle

The cross compilation make files can be found in the makefiles directory and you can add more by copying and editing the supplied files to match your toolchain setting.

5. The library will be compiled into one of the following platform specfic sub-directories:

Platform Library Directory
Linux lib/linux
QNX 6 lib/qnx6
QNX 4 lib/qnx4
Irix lib/irix
OSF1/True 64/Digital UNIX lib/osf
Solaris lib/solaris
HP-UX lib/hpux
IBM AIX lib/aix

Your directory structure looks now like:

myprj
|
+-+ fieldtalk
|
+-- doc
+-- src
+-- include
+-- samples
+-+ lib
|
+-- {platform} (exact name depends on platform)

6. The library is ready to be used.

Specific Platform Notes

QNX 4

In order to get proper control over Modebus timing, you have to adjust the system's clock rate. The standard ticksize is not suitable for Modbus RTU and needs to be adjusted. Configure the ticksize to be <= 1 ms.

VxWorks

There is no make file or script supplied for VxWorks because VxWorks applications and libraries are best compiled from the Tornado IDE.

To compile and link your applications against the FieldTalk library, add all the *.c and *.cpp files supplied in the src, src/hmlib/common, src/hmlib/posix4 and src/hmlib/vxworks to your project.

   Back | Top of page Info | Support | Contact | About   
Information in this document is subject to change without notice. Copyright © 2000-2018 proconX Pty Ltd (formerly FOCUS Software Engineering Pty Ltd). All rights reserved.
All product and brand names mentioned on this page may be trademarks or registered trademarks of their respective owners.