This sample shows how (large) string messages could be outsourced into the external eprom.
This would reduce the required cpu internal V-Memory space, which
is left for other program parts or made a smaller CPU size available.
Conditions
The SMS string messages should be outsorced to the external eprom
Each message should have a fixed lenght of 50 character, regardless how much are
actually used
(Otherwise offset calculation would become difficult, a future sample will show this)
The complete function should not take more then 100 bytes from the V-Memory space
Write messages
To store the string messages into the external eprom a dummy project is required.
The project must contain the string messages at DataBlock and the "Write_ext_Eprom" routine.
After excution the string messages are stored persistent on the external program.
The dummy project is only required to add or modify string messages on ext. eprom.
Data block
Read messages
The second project shows how the user program could look like. The "Read_ext_Eprom" routine, offset
calculation and user own application functions (send SMS) are placed into a own subroutine.
The subroutine could be called easily form any program location with the associated SMS message number.
Notice:
The different messages would be visible if you monitor VB300 (as string) with status chart.
The author makes no warranty, expressed or implied, with regard to this informations and/or software.
All implied warranties, including the warranties of merchantability and fitness
for a particular use, are hereby excluded. Under no circumstances shall the
author of this product or the author(s) of S7-200.net, be liable for any incidental or consequential damages,
nor for any damages. Attachments could contain viruses, the user is repsonsible to check the downloaded
files before using. The user has no claims, especialy not for error correction
or support.
Notice:
