Brandon Bayer

Forum Replies Created

Viewing 30 posts - 61 through 90 (of 183 total)
1 2 3 4 5 6 7
  • Author
    Posts
  • November 25, 2015 at 11:13 am in reply to: Always receiving failed CRC and failed MIC packages #10139
    Brandon Bayer
    Blocked

    Eduardo,

    Ok, then it probably was a lease related issue. Do node list to see if it’s still in the db. I think you can remove them with node remove.

    -Brandon

    November 25, 2015 at 9:55 am in reply to: mDotlib Roadmap #10137
    Brandon Bayer
    Blocked

    Hey Jean,

    Your best bet for getting a rough roadmap is to open a support case.

    -Brandon

    November 25, 2015 at 9:43 am in reply to: LoRa message between Conduits? #10136
    Brandon Bayer
    Blocked

    Furrukh,

    It’s currently not possible to send lora packets between Conduits.

    -Brandon

    November 25, 2015 at 9:42 am in reply to: Documentation of SNR/RSSI stats? #10135
    Brandon Bayer
    Blocked

    Hey Mark,

    If you are getting 4 values back, then you are using it correctly. They will all be zero until you do an OTA join or, if doing manual join, until the mDot receives a packet from the server.

    -Brandon

    November 25, 2015 at 9:39 am in reply to: mosquitto_pub question #10134
    Brandon Bayer
    Blocked

    Eduardo,

    Look at the transmit section of this page:

    Conduit mLinux: LoRa Communication

    As noted there,

    The packet must be in JSON format and the data must be Base64 encoded

    -Brandon

    November 25, 2015 at 9:36 am in reply to: Always receiving failed CRC and failed MIC packages #10132
    Brandon Bayer
    Blocked

    Eduardo,

    When you changed the device address, did you do the node add command again?

    I suspect your address lease expired. After network["leasetime"] in lora-network-server.conf (minutes), the node will be purged from the DB. If the device then transmits again, the server will reject it because the address lease has expired.

    -Brandon

    • This reply was modified 9 years, 4 months ago by Brandon Bayer.
    November 24, 2015 at 7:23 am in reply to: How to upload mbed firmware to mDot #10114
    Brandon Bayer
    Blocked

    Jean,

    Ok, then I can’t think of any more obvious reasons it wouldn’t work. I suggest opening a support case (and link to this thread) for possibly more debugging or UDK replacement.

    -Brandon

    November 23, 2015 at 8:16 am in reply to: How to upload mbed firmware to mDot #10109
    Brandon Bayer
    Blocked

    Jean,

    Ok it sounds like your setup is good. Does your mDot have the programming header installed?
    mDot header

    -Brandon

    November 23, 2015 at 7:50 am in reply to: How to upload mbed firmware to mDot #10107
    Brandon Bayer
    Blocked

    Jean,

    Hmm, this is definitely not normal behavior. Is the blue PWR LED on the UDK lit?

    Have you tried a different USB port? Cable? Different computer?
    Some people have had issues where the corporate computer settings blocked USB drives, and they had to flash the mDot using a virtual machine.

    -Brandon

    November 23, 2015 at 7:43 am in reply to: Offline SDK build problems #10106
    Brandon Bayer
    Blocked

    Ah, good catch Neil. I’ve add a bit to that wiki page to hopefully clarify this for the next person.

    -Brandon

    November 20, 2015 at 1:29 pm in reply to: mDot EVB Docs? #10090
    Brandon Bayer
    Blocked

    Jose,

    I suggest checking out this page which shows how to view all AT Commands:

    AT Command Getting Started Guide

    You can also download a developer guide from this page:
    http://www.multitech.net/developer/products/multiconnect-mdot/

    And the frequency band cannot be changed (from 915 to 868 or vice versa).

    -Brandon

    November 20, 2015 at 8:13 am in reply to: Offline SDK build problems #10087
    Brandon Bayer
    Blocked

    Neil,

    So we are wondering if this is related to Windows 10. Everything you are doing looks correct and are the same commands we use to build on Windows 7. Do you have a Windows 7 pc to try or could you install it in a virtual machine?

    -Brandon

    November 20, 2015 at 7:39 am in reply to: Connecting to Node RED #10086
    Brandon Bayer
    Blocked

    Sean,

    It will be software only!

    -Brandon

    November 19, 2015 at 4:29 pm in reply to: Connecting to Node RED #10078
    Brandon Bayer
    Blocked

    Jim,

    Ah, that is interesting. I did a quick search and it looks like this is a known issue with Express 3 which is used by the Conduit’s version of Node-RED but is fixed in Express 4. The Node-RED upgrade won’t be in the next Conduit version to be released within a month or two (Node-RED v0.11.1), but we’ll try to get NR 0.12.0 or later in the next release after that.

    -Brandon

    November 19, 2015 at 3:14 pm in reply to: mDot EVB Docs? #10072
    Brandon Bayer
    Blocked

    Jim,

    Since it is only sampling, your best path is to create a support case where you’ll be connected to the folks who can answer your EVB questions as they may not be checking these forums 🙂

    -Brandon

    November 19, 2015 at 3:12 pm in reply to: Offline SDK build problems #10071
    Brandon Bayer
    Blocked

    Neil,

    Try using the full path to the source and build directories.

    -Brandon

    November 19, 2015 at 2:42 pm in reply to: I can receive SMS messages but I can not send SMS messages #10066
    Brandon Bayer
    Blocked

    Furrukh,

    Ok, cool! Yes, you can manually delete those files if you wish.

    -Brandon

    November 19, 2015 at 1:59 pm in reply to: I can receive SMS messages but I can not send SMS messages #10064
    Brandon Bayer
    Blocked

    Furrukh,

    This sounds like a bug fix we did that’ll be in the next firmware version. The bug didn’t allow sending an sms with a zero in it. Likely your inject node is sending a timestamp through the sms node (which overrides the sms node payload setting).

    Try changing the inject node to use a string without zero’s.

    -Brandon

    November 18, 2015 at 1:51 pm in reply to: LoRa Range problems #10044
    Brandon Bayer
    Blocked

    Jose,

    Those results only indicate something isn’t configured correctly. It doesn’t mean you have bad hardware. Go ahead and open a support case and someone will help you get things set up.

    -Brandon

    November 18, 2015 at 9:27 am in reply to: I can receive SMS messages but I can not send SMS messages #10040
    Brandon Bayer
    Blocked

    Furrukh,

    What sms content you are trying to send?

    Try sending an sms from the linux command line to rule out Node-RED interface issues. To do this, ssh into the Conduit using the same credentials as the web GUI and run this command:
    sms -vd /dev/modem_at1 send 8881231234 but replace the phone number with your own cell phone. That will open the vi editor where you can press i, type a message, press esc, then type :wq to close vim and send the message.

    Paste the output here.

    -Brandon

    November 18, 2015 at 9:13 am in reply to: LoRa Range problems #10039
    Brandon Bayer
    Blocked

    Wojtek,

    Yep, those numbers look good!

    -Brandon

    November 18, 2015 at 9:10 am in reply to: mDot EVB Docs? #10038
    Brandon Bayer
    Blocked

    Jim,

    A thorough EVB developer guide is coming soon. I do apologize for the product being released without proper documentation.

    -Brandon

    November 17, 2015 at 2:12 pm in reply to: failed to join the network #10017
    Brandon Bayer
    Blocked

    Jose,

    Alright, let’s just have you go ahead and create a support case which will make it easier to help you and send files back and forth. Use the same login information as for these forums and in the case, describe as much as possible. Put what you have tried, what works, what doesn’t, etc. Also include either the Conduit configuration files or screenshots.

    Thanks!

    -Brandon

    November 16, 2015 at 8:33 am in reply to: failed to join the network #10013
    Brandon Bayer
    Blocked

    Jose,

    Ok, so we still need to see either a screenshot of your Conduit lora configuration or post a copy of /var/config/db.json

    -Brandon

    November 13, 2015 at 1:49 pm in reply to: failed to join the network #10007
    Brandon Bayer
    Blocked

    What version of Conduit firmware do you have?

    November 13, 2015 at 11:20 am in reply to: failed to join the network #10003
    Brandon Bayer
    Blocked

    Jose,

    If you can issue AT commands to the mDot, your UDK is powered properly.

    Please post the output of the AT&V command from the mDot as well as a screenshot of your Conduit’s Lora configuration.

    -Brandon

    November 11, 2015 at 2:53 pm in reply to: LoRa Range problems #9937
    Brandon Bayer
    Blocked

    Jose,

    Have you established mDot to Conduit communications and vice versa? The Conduit will only transmit after downstream data is queued for a mDot and a packet is received from that mDot.

    -Brandon

    November 11, 2015 at 10:09 am in reply to: AEP-Specific Configuration Support for 85 sq. Miles #9896
    Brandon Bayer
    Blocked

    Patrick,

    I can put you in touch with our sales engineers. Are you wanting all the Conduits to be on the same LoRa network? Are you planning on using a public network like http://thethingsnetwork.org/ or do you want to have a private network?

    -Brandon

    November 10, 2015 at 11:33 am in reply to: Conduit no longer responding serial login on device port #9883
    Brandon Bayer
    Blocked

    Jonathan,

    Use the U-boot instructions on the second half of this page:

    Flashing mLinux Firmware

    -Brandon

    November 10, 2015 at 9:49 am in reply to: Twitter on NodeRED Fails #9881
    Brandon Bayer
    Blocked

    Patrick,

    When I first tried to do this, I got the same error. I then set the Conduit time to be the correct time and timezone, rebooted, and now it works properly.

    -Brandon

  • Author
    Posts
Viewing 30 posts - 61 through 90 (of 183 total)
1 2 3 4 5 6 7