Cleaned up version

.gitignore

@@ -0,0 +1,161 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+.vscode/
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/#use-with-ide
+.pdm.toml
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/

README.md

@@ -4,19 +4,18 @@
 The GridAPPS-D DNP3 Master Service acts as a bridge between GridAPPS-D platform and DNP3 Masters. The service connects with the DNP3 Masters and collects binary and analog output. It then converts them to CIM compliant message and publishes on Field Interface Manager's output topic. This message can then be received by any GridAPPS-D complaint application. The service also subscribes to control commands coming from GridAPPS-D applications and forwards them to DNP3 Masters after conversion.
 
 ## Running the service
-By default the service runs with IEEE123 model using the configurations files in dnp3-master/service/config. For more see Config heading.
+By default the service runs with IEEE123 model using the configurations files in dnp3-master/service/config. For more see Config heading. The argument passed here is 'RTU1'. You can modify as per your RTU name.
 ```
  python3 start_service.py 'RTU1' 
 ```
 
 ## Workflow
-`Needs to he updated`
+
 
 1. Lookup device ip and port information in device_ip_port_config_all.json file.
 2. The SOEHandler in the master.py will handle the indexes to CIM MRID mapping and conversion.
 3. CIMProcessor in CIMPro.py will handle the Analog Output data transfer
-4. Add or delete Analog Input (AI) or Analog Output (AO) in IEEE123_RTAC_AI_AO.xlsx file according to your application
-5. Run Conversion_dict_IEEE123.py to generate both conversion_dict_master.json and model_line_dict_master.json
+4. Create your own conversion_dict_master.json, device_ip_port_config.json, measurement_dict_master.json, model_line_dict.json files based on the field device details. 
 6. Run start_service.py (Check IP adrees of outstation, Port number, DNP3 address)
 
 ## Config
@@ -57,3 +56,7 @@ Output: dnp3-master/config/converstion_dict_master.json
 
 Output: dnp3-master/config/measurement_dict_master.json
 
+**2. Conversion Scripts**
+
+1. If you have not loaded your model into blazegraph then create the json in config folder as per the device list. 
+