DotBox-Google – Data not displaying correctly

Home Forums Conduit: AEP Model DotBox-Google – Data not displaying correctly

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #20735
    Greg Tuthill
    Participant

    Hi,
    I have installed the DotBox-Google app on my conduit AEP. I want to test sending GPS data from my MDot-Box to the app and view the data on the map web page.

    The MDot-box is in the default configuration and connects to the conduit OK. The GPS data displays correctly on the device, but is not being displayed on the map, or the evbmonitor web page. When i look at the CSV file on the AEP that this data is stored in, it does not look right. Most columns have a zero value, and “Lat” and “Long” have no value at all. GPS time and Date look Ok.

    I have tried the 0.1.0 and 0.2.0 versions.
    How can I work out why the data is not passing correctly?

    Is there a support contact for the Apps in the Device HQ store?

    #20737
    Steve Kovarik
    Moderator

    Hi Greg

    By default the MTDOT-BOX does not send data to the gateway,
    you will need a developer board to use the MTDOT-BOX in
    configuration mode and issue the commands at+data=1 and at&w
    as out lined at this link http://www.multitech.net/developer/software/dot-box-and-evb-software/configuration-mode/

    Also you will only be able to get a GPS lock outside with a clear view
    of the sky, and blinking LED 2 will go solid when a GPS lock is achieved.

    -Best Regards

    #20747
    Greg Tuthill
    Participant

    Thanks for your response,
    The MDOT-Box is sending data to the gateway ok. If i look at the debug output of the Lora packet in node-red, i see the data ok, for both Lora Survey and GPS survey:

    I think it is one of the subsequent nodes “parse EVB Packet” or “To csv” that is not passing the data correctly.

    Is there a moderator on here that helped develop the DotBox-Google app that can help?

    Debug LoRa Packet – LoRa survey
    ——————————————————————–
    8/22/2017, 8:32:07 AM[debug LoRa Packet][msg] : object{ “ack”: false, “adr”: false, “appeui”: “b2-64-01-e7-b7-11-aa-c6”, “chan”: 6, “cls”: 0, “codr”: “4/5”, “datr”: “SF9BW125”, “deveui”: “00-80-00-00-00-00-ee-d7”, “freq”: “903.5”, “lsnr”: “9”, “mhdr”: “4001000000000100”, “modu”: “LORA”, “opts”: “”, “port”: 1, “rfch”: 1, “rssi”: -17, “seqn”: 1, “size”: 20, “timestamp”: “2017-08-21T20:31:01.023130Z”, “tmst”: 2042596676, “payload”: [ 14, 1, 255, 15, 8, 6, 44, 94, 5, 0, 104, 11, 1, 171 ], “eui”: “00-80-00-00-00-00-ee-d7”, “_msgid”: “aa0a3a1c.55f5c8” }
    ——————————————————————–
    8/22/2017, 8:34:15 AM[debug LoRa Packet][msg] : object{ “ack”: false, “adr”: false, “appeui”: “b2-64-01-e7-b7-11-aa-c6”, “chan”: 4, “cls”: 0, “codr”: “4/5”, “datr”: “SF9BW125”, “deveui”: “00-80-00-00-00-00-ee-d7”, “freq”: “903.1”, “lsnr”: “11.8”, “mhdr”: “4001000000000300”, “modu”: “LORA”, “opts”: “”, “port”: 1, “rfch”: 1, “rssi”: -27, “seqn”: 3, “size”: 20, “timestamp”: “2017-08-21T20:33:10.354607Z”, “tmst”: 2171923196, “payload”: [ 14, 1, 255, 15, 8, 6, 43, 243, 5, 0, 27, 11, 1, 184 ], “eui”: “00-80-00-00-00-00-ee-d7”, “_msgid”: “b69c2b76.4963d8” }

    Debug LoRa Packet – GPS Survey – No GPS Lock
    ——————————————————————–
    [msg] : object{ “ack”: false, “adr”: false, “appeui”: “b2-64-01-e7-b7-11-aa-c6”, “chan”: 1, “cls”: 0, “codr”: “4/5”, “datr”: “SF10BW125”, “deveui”: “00-80-00-00-00-00-ee-d7”, “freq”: “902.5”, “lsnr”: “12”, “mhdr”: “4001000000000000”, “modu”: “LORA”, “opts”: “”, “port”: 1, “rfch”: 0, “rssi”: -19, “seqn”: 0, “size”: 16, “timestamp”: “2017-08-21T20:34:11.641029Z”, “tmst”: 2233209876, “payload”: [ 0, 28, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], “eui”: “00-80-00-00-00-00-ee-d7”, “_msgid”: “6525e952.9ada18” }
    ———————————————————————-

    Debug LoRa Packet – GPS Survey – With GPS Lock
    ——————————————————————–
    { “ack”: false, “adr”: false, “appeui”: “b2-64-01-e7-b7-11-aa-c6”, “chan”: 2, “cls”: 0, “codr”: “4/5”, “datr”: “SF10BW125”, “deveui”: “00-80-00-00-00-00-ee-d7”, “freq”: “902.7”, “lsnr”: “8.8”, “mhdr”: “4001000000003e00”, “modu”: “LORA”, “opts”: “”, “port”: 1, “rfch”: 0, “rssi”: -67, “seqn”: 62, “size”: 16, “timestamp”: “2017-08-21T20:40:33.642886Z”, “tmst”: 2615222284, “payload”: [ 0, 25, 0, 198, 155, 0, 135, 124, 225, 215, 182 ], “eui”: “00-80-00-00-00-00-ee-d7”, “_msgid”: “d9a331b2.265cd” }

    #20832
    Greg Tuthill
    Participant

    I have done some more troubleshooting on this.

    Does anyone have a function node that is able to format GPS data from the mDotBox? From either the GPS Survey Mode, or Lora Demo mode?

    What I am trying to achieve is:
    GPS Survey Data > Gateway > Formatted Data to send on to MQTT or API.

    The GPS to Gateway Message is fine and has payload data as expected
    http://www.multitech.net/developer/software/dot-box-and-evb-software/survey-gps/
    ——————————————————————————
    [LoRa EVB output][msg] : object
    { “ack”: false, “adr”: false, “appeui”: “b2-64-01-e7-b7-11-aa-c6”, “chan”: 7, “cls”: 0, “codr”: “4/5”, “datr”: “SF10BW125”, “deveui”: “00-80-00-00-00-00-ee-d7”, “freq”: “903.7”, “lsnr”: “10.5”, “mhdr”: “8001000000000600”, “modu”: “LORA”, “opts”: “”, “port”: 1, “rfch”: 1, “rssi”: -75, “seqn”: 6, “size”: 16, “timestamp”: “2017-08-26T22:42:08.876890Z”, “tmst”: 2240121388, “payload”: [ 0, 26, 0, 198, 156, 51, 244, 124, 225, 185, 187 ], “eui”: “00-80-00-00-00-00-ee-d7”, “_msgid”: “41198a3.fbee674” }
    ——————————————————————————
    The Format EVB Parser node does not seem to be interpreting the payload correctly.
    https://webfiles.multitech.com/mmm/EVBParserLatest.txt

    ——————————————————————————
    [Formatted EVB Data Output][msg] : object
    { “data_valid”: 0, “block_start”: 0, “temperature”: 0, “x_pos”: 0, “y_pos”: 0, “z_pos”: 0, “baro_pressure”: 0, “lux”: 0, “pkt_timer”: 0, “rf_pwr”: 0, “sf_val”: 10, “gateways”: 0, “margin_up”: 0, “rssi_dwn”: 0, “snr_dwn”: 0, “lat_deg”: 0, “lat_min”: 0, “long_deg”: 0, “long_min”: 0, “num_sats”: 0, “gps_status”: 0, “_msgid”: “41198a3.fbee674” }
    ——————————————————————————

    Reviewing the data packet format information, indicates that payload should include IDs for GPS data (0x15, 0x16, 0x19). This doesn’t appear to be the case.
    http://www.multitech.net/developer/software/dot-box-and-evb-software/data-packet-format/

    I appreciate that this only applies to “Lora Demo” mode , “single survey” and “survey sweep”. Here is an example in this mode WITH GPS lock. Still no GPS info in formatted output.

    ——————————————————————————
    [LoRa EVB output][msg] : object
    { “ack”: false, “adr”: false, “appeui”: “b2-64-01-e7-b7-11-aa-c6”, “chan”: 5, “cls”: 0, “codr”: “4/5”, “datr”: “SF9BW125”, “deveui”: “00-80-00-00-00-00-ee-d7”, “freq”: “903.3”, “lsnr”: “11.8”, “mhdr”: “4001000000000000”, “modu”: “LORA”, “opts”: “”, “port”: 1, “rfch”: 1, “rssi”: -79, “seqn”: 0, “size”: 20, “timestamp”: “2017-08-26T22:30:38.486345Z”, “tmst”: 1549717516, “payload”: [ 14, 0, 255, 15, 8, 6, 54, 51, 5, 5, 170, 11, 1, 193 ], “eui”: “00-80-00-00-00-00-ee-d7”, “_msgid”: “c1cffe55.3e3” }

    ——————————————————————————
    But the formatted output has no values for GPS:

    ——————————————————————————
    [Formatted EVB Data Output][msg] : object
    { “data_valid”: 0, “block_start”: 0, “temperature”: 28.0625, “x_pos”: 0, “y_pos”: -0.0625, “z_pos”: 0.9375, “baro_pressure”: 101772.75, “lux”: 348, “pkt_timer”: 0, “rf_pwr”: 0, “sf_val”: 9, “gateways”: 0, “margin_up”: 0, “rssi_dwn”: 0, “snr_dwn”: 0, “lat_deg”: 0, “lat_min”: 0, “long_deg”: 0, “long_min”: 0, “num_sats”: 0, “gps_status”: 0, “_msgid”: “c1cffe55.3e3” }
    ——————————————————————————

    So the question is:
    Does anyone have a function node that is able to format GPS data from the mDotBox? From either the GPS Survey Mode, or Lora Demo mode?

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.