Python dnp3 #19
Open
Python dnp3 #19
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 30 commits
May 31, 2012 12:15
Remove several warnings printed when running swig by renaming the relevant functions to ones that are compatible with Java. Started working on porting the VTO interfaces to be Swig compatible. (Swig prefers "static const" over "const static.")
Linux and Windows handle case sensitivity differently. Namely, the former thinks that "dnp3test" and "DNP3Test" are different, while the latter believes that they are (mistakenly) the same. Since we generate binaries that match directories in a case insensitive manner (dnp3test->DNP3Test and testset->TestSet), simply adding 'dnp3test' and 'testset' to the .gitignore causes the source code directories with the "same" name to also be ignored. This isn't what we want, so the trick is to tell git to ignore the binaries but include the directories. We do this using the "negate" operator and the "directory-slash" suffix. These rules are at the top of the .gitignore so that all the other rules (like ignoring object files, swap files, etc.) behave like one would expect.
Thanks to William Sember for catching the non-thread-safe code generated by Swig. http://matt.eifelle.com/2007/11/23/enabling-thread-support-in-swig-and-python/
Conflicts: .gitignore
Support for 'make -j X' (where X is the number of parallel build threads to execute) now works properly for the Java Swig bindings.
Link local connections do not work. You need to bind to a global or loopback address.
Helps with backwards compatibility of existing testset XML files
Moved the ConvertMode() function to being owned by the XmlToConfig class
Moved the ConvertMode() function to being owned by the XmlToConfig class
For a master stack in testset, enabling time sync support was hardcoded to 'true'. This prevented testing with testset where time sync needs to be disabled on the master stack. Now we read the property and feed it into the master stack configuration struct properly.
…roup When multiple events are queued up for an object group, where the events themselves are part of different DNP3 classes (1/2/3), the iterator loop in ResponseContext::LoadEvents<T>() was causing a 0-length object group to be added to the APDU. ResponseContext::IterateIndexed<T>() appears to be writing everything in one iteration. The iterator loop needs to be bound on both the queue size _and_ whether any elements are remaining.
Historically, a Slave would reset its Time IIN bit each time the stack when down. This could cause extra traffic that isn't desired, so we now give the application control. The default behavior has been maintained.
is generated from. This enables the application to create a new slave stack and to properly bind it to the correct physical layer.
the outstation receives a READ request while waiting for an unsolicited confirm when it should abort any retries
Basic process flow:
Dependencies -- once per compile machine
----------------------------------------
sudo apt-get install -y \
dh-make devscripts dh-autoreconf \
libboost-all-dev \
oracle-java7-installer \
swig
Common variables used below
---------------------------
export PN="opendnp3"
export PV="1.1.2"
export P="${PN}-${PV}"
export ORIG_TARBALL="${PN}_${PV}.orig.tar.gz"
Step 1 - create the .orig.tar.gz file
-------------------------------------
git clone github:sentient-energy/dnp3.git ${P}
rm -rf ${P}/debian/ ${P}/.git
tar cfz ${ORIG_TARBALL} ${P}
rm -rf ${P}
Step 2 - create the DEB(s)
--------------------------
git clone github:sentient-energy/dnp3.git ${P}
cd ${P}
debuild -uc -us
Step 3 - get the DEB(s)
-----------------------
cd ..
ls -la *.deb
handle error if host name failed to be resolved.
If no value is specified, the default will be used.
buffer size. If no value is specified, the default will be used.
through a IIN write.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.