Differences

This shows you the differences between two versions of the page.

--- packet:bpq [2024/05/16 09:01] – g7taj
+++ packet:bpq [2025/04/13 11:43] (current) – m0lte
@@ Line 12: / Line 12: @@
 Here are some miscellaneous hints and tips on BPQ configuration.
+==== Showing up on the Maps ====
+There are at least 2 different maps you can configure your BPQ system to appear on, the primary BPQ map at [[http://nodemap.g8bpq.net:81/]], and the live connectivity map at [[https://nodes.ukpacketradio.network/packet-network-map.html]].
+In both cases you will need to set these in the root of bpq32.cfg:
+<code>
+LOCATOR=<Lat/Lon GPS coordinates, or Maidenhead grid square>
+MAPCOMMENT=<Briefly describe node>
+</code>
+To appear on the live connectivity map as well (recommended), also set:
+<code>
+EnableM0LTEMap=1
+</code>
+The ID of your ports will also show up as a port description, and you can add more specific information about each port by adding M0LTEMapInfo in the port section which can help the map system, and other software built to read it's data, better understand your port. This is in the format:
+<code>
+M0LTEMapInfo=<RF|PrivateNet|Internet|Other>,<DIAL+modem centre freq|freq_mhz>,<modulation>,<baudrate>,<bitrate>,<Access|Backbone|Mixed|Other>
+</code>
+The DIAL+freq format is used if you are setting the frequency with rigcontrol. 40m slot one would be DIAL+850.
+Example port configuration:
+<code>
+PORT
+  PORTNUM=1
+  ID=432.625 9600 GFSK IL2P+CRC
+  M0LTEMapInfo=RF,432.625,GFSK,9600,9600,Mixed
+  ..... other port config ...
+ENDPORT
+</code>
 ==== 'NODE' and node 'HELP' commands ====
@@ Line 39: / Line 77: @@
 ==== Enable Logging ====
-Sometimes you just NEED a log; but be aware that SD cards do not really like to many writes. ( [[packet:bpq_logging_reduction|packet:bpq_logging_reduction]])
+Sometimes you just NEED a log; but be aware that SD cards do not really like to many writes. ( [[packet:bpq_logging_reduction|packet:bpq_logging_reduction]] )
@@ Line 144: / Line 182: @@
 ===== REST API =====
-BPQ has a simple and evolving HTTP REST API.
+Details here: [[packet:bpq-api|BPQ APIs]]
-It is used though the HTTPPORT (in this example is port 9122)
-endpoints: (note older versions were prefixed with 'get' (except request_token)
-<code>
-/api/request_token
-/api/ports
-/api/nodes
-/api/users
-/api/info
-/api/links
-/api/mheardport/<port#>
-</code>
-Requested like so:
-<code>curl 127.0.0.1:9122/api/request_token</code>
-Output:
-<code>{"access_token":"OSTWFHSGAPKZWMZORFEFWOFIHMOZUMJK", "expires_in":3600, "scope":"create"}</code>
-Example of MH for Port 1: ( >ver 6.0.24.33 )
-<code>curl 127.0.0.1:9122/api/mheardport?1 -H "Authorization: Bearer OSTWFHSGAPKZWMZORFEFWOFIHMOZUMJK"</code>
-Output:
-<code>{"callSign": "G7TAJ-15", "port": "1", "packets": 10, "lastHeard": "2024-3-6 17:14:01"  },
-{"callSign": "G7TAJ", "port": "1", "packets": 5, "lastHeard": "2024-3-3 15:46:07"  }</code>
 ===== Events =====
 BPQ can fire an executable on certain events.
@@ Line 246: / Line 256: @@
 See [[packet:linbpq_monitoring|Monitoring LinBPQ through SNMP]]
+===== BPQ Web Monitor =====
+Watch the packet racket in your web browser!
+See [[packet:bpqmonweb|Setting up Tom 2E0JJI's bpqmonweb project]]
+===== Credentials =====
+The password at the top of bpq32.cfg is only use for authenicating access to the node over rf commections, using the node PASSWORD command.
+Webmail uses the password in the BBS User config. The management part of the Web interface uses USER records from the Telnetserver config.
+===== Building from source =====
+Requires ''libjansson-dev'', ''libpaho-mqtt-dev''