Fix links in examples

Author: sirhcel

doc/examples/ev-charging.md

@@ -382,7 +382,7 @@ the charging process.
 ### End of Charging
 
 Creating a _Signed Turn-Off Snapshot_ ends the charging process by turning of
-the contactor and recoding the snapshot data. Again, [Snapshot Creation]() gives
+the contactor and recoding the snapshot data. Again, [Snapshot Creation](snapshots.md#snapshot-creation) gives
 the details about this procedure.
 
 
@@ -453,7 +453,7 @@ the _Signed Turn-On Snapshot_ taken at the start of charging:
       difference can be one least significant digit larger than the value for
       _RCR_ (shown in the display).
     - Again, there is no active power
-      ([_W_](../../bauer_bsm/bsm/models/smdx_64901.xml#L185) = 0 Wh) since
+      ([_W_](../../bauer_bsm/bsm/models/smdx_64901.xml#L201) = 0 Wh) since
       power delivery got cut before recording the snapshot data
 - Time and counters
     - The response counter

doc/examples/modbus-interface.md

@@ -141,7 +141,7 @@ describes the interpretation of standard data types.
 
 The BSM-WS36A provides several data as Binary Large Objects (BLOBs) - for
 example, its [public key](../../bauer_bsm/bsm/models/smdx_64900.xml#L31) and
-[snapshot signatures](../../bauer_bsm/bsm/models/smdx_64901.xml#L65).
+[snapshot signatures](../../bauer_bsm/bsm/models/smdx_64901.xml#L67).
 
 SunSpec does not define a data representation for BLOBs and so a proprietary
 [bsm\_blob](../../bauer_bsm/bsm/models/smdx_64902.xml) or a similar arrangement
@@ -154,7 +154,7 @@ representation is used. Either by the specialized BLOB model
 - [_BB_](../../bauer_bsm/bsm/models/smdx_64902.xml#L49) the actual number of
   bytes
 
-- [_B_](bauer_bsm/bsm/models/smdx_64902.xml#L53) a repeating block with a
+- [_B_](../../bauer_bsm/bsm/models/smdx_64902.xml#L53) a repeating block with a
   single register of this name forming the BLOB data area
 
 See [Signed Snapshots](snapshots.md) for an example.

doc/examples/ocmf.md

@@ -37,7 +37,7 @@ model instance afterwards.
 ## Snapshot Data in OCMF
 
 The OCMF representation includes
-[_Meta1_](../../../../bauer_bsm/bsm/models/smdx_64901.xml#L31) as customer
+[_Meta1_](../../bauer_bsm/bsm/models/smdx_64901.xml#L31) as customer
 identification data which needs to be set appropriately. The other metadata
 fields are ignored and will not appear in OCMF output.
 
@@ -206,17 +206,19 @@ uses an XML envelope.
 The XML envelope includes the OCMF data taken before starting and after
 terminating the charging process along with the public key used for signing.
 The format could be generated from a
-[template](../../bauer_bsm/bsm/client.py#L214) where the actual data gets
+[template](../../bauer_bsm/exporter/ocmf.py#L48) where the actual data gets
 inserted.
 
 
 ### Generating OCMF XML
 
-The [BSM Python support](../../bauer_bsm/bsm/client.py#L183) and the BSM Tool
-support the generation of OCMF XML data for _OCMF Signed Turn-On Snapshot_ and
-_OCMF Signed Turn-Off Snapshot_ when the corresponding snapshots have already
-been successfully created. To generate an OCMF XML envelope, invoke the BSM
-Tool as follows:
+The [BSM Python support](../../bauer_bsm/exporter/ocmf.py#L12) and the [BSM
+Tool](../../bauer_bsm/cli/bsmtool.py#L343) support the generation of OCMF XML
+data for the OCMF representation of a pair of already created snapshots (the
+switching snapshots _OCMF Signed Turn-On Snapshot_ and _OCMF Signed Turn-Off
+Snapshot_ or the non-switching _OCMF Signed Start Snapshot_ and _OCMF Signed
+End Snapshot_). To generate an OCMF XML envelope for the switching snapshots,
+invoke the BSM Tool as follows:
 
 - Create _Signed Turn-On Snapshot_
     ```

doc/examples/snapshots.md

@@ -40,13 +40,13 @@ consumption without switching an external contactor:
 ## Snapshot Creation
 
 A snapshot gets created by the writing to its status data point
-[_St_](../../bauer_bsm/bsm/models/smdx_64901.xml#L115) and polling this data
+[_St_](../../bauer_bsm/bsm/models/smdx_64901.xml#L131) and polling this data
 point afterwards its value indicates either a successful update or a failure.
 
 The procedure looks as follows:
 
-1. Write [_UPDATING_](../../bauer_bsm/bsm/models/smdx_64901.xml#L12) (2) to
-   [_St_](../../bauer_bsm/bsm/models/smdx_64901.xml#L115)
+1. Write [_UPDATING_](../../bauer_bsm/bsm/models/smdx_64901.xml#L14) (2) to
+   [_St_](../../bauer_bsm/bsm/models/smdx_64901.xml#L131)
 2. Read the value of _St_ with a timeout of 15 seconds
 3. If _St_ returns _UPDATING_ (2), continue with step 2
 4. If _St_ returns _VALID_ (0), the snapshot data is ready to be read
@@ -241,10 +241,10 @@ $ bsmtool dump 40521 254
 A snapshot records three data points related to power and energy:
 
 - The reference cumulative register
-  [_RCR_](bauer_bsm/bsm/models/smdx_64901.xml#L185) which counts the energy
+  [_RCR_](../../bauer_bsm/bsm/models/smdx_64901.xml#L185) which counts the energy
   consumption since it got reset during the creation of the last _Signed
   Turn-On Snapshot_
-- [_TotWhImp_](bauer_bsm/bsm/models/smdx_64901.xml#L193) counting the overall
+- [_TotWhImp_](../../bauer_bsm/bsm/models/smdx_64901.xml#L193) counting the overall
   energy consumption measured by the BSM-WS36A
 - And the actual real power consumption
   [_W_](../../bauer_bsm/bsm/models/smdx_64901.xml#L201)