Mike McNeil
Forum Replies Created
-
AuthorPosts
-
Mike McNeilModerator
Hello Brandon,
Please review the API documentation from the .net site:
The Appendix section has information dealing with SMS.
Hope this helps.
Regards,
MikeMike McNeilModeratorHello Dennis,
What version of mPower are you using?
Anything with 5.0.x and newer requires the ?token=xxx for security purposes.
Example: …/system/date?data={“date”:”08/24/2022″}&method=PUT?token=xx
If that doesn’t help please provide your API calls.
The time zone is found under sntp/timeZone.Regards,
MikeMike McNeilModeratorYou didn’t mention what specif model your MTCDT was, whether it’s an older LEU1 or a newer L4E1, etc… See previous link about downgrading notes.
Otherwise, here is a link to newer signed firmware:
http://www.multitech.net/developer/downloads/
Regards.Mike McNeilModeratorHello Gedas,
Specifically, what product do you have?
What is your reason for wanting to switch to unsigned or what version are you wanting to downgrade too?
Regards,
MikeApril 27, 2021 at 10:50 am in reply to: How to read SMS in the MultiConnect® rCell 100 Series #31768Mike McNeilModeratorHello Gabriel,
If using the GUI, please review the Software Guide:
https://www.multitech.com/documents/publications/software-guides/s000720–mPower-Edge-Intelligence-MTR-Software-Guide.pdf
If using the API, please review the API Reference:
http://www.multitech.net/developer/software/mtr-software/mtr-api-reference/
If using AT commands, please review the AT Command Guide based on your product:
Telit: https://www.multitech.com/documents/publications/reference-guides/Telit_ME910C1_AT_Commands_Guide_r9-1.pdf
Quectel: https://www.multitech.com/documents/publications/reference-guides/Quectel_EG9x_AT_Commands_Manual_V1.1.pdf
Please review the product page for specific model information:
https://www.multitech.com/brands/multiconnect-rcell-100-series
Regards,
MikeMike McNeilModeratorHello Fred,
Actually, I just tested this with a MTCDT and it did work, so you must have something else going on or a setup issue with your device?
– Did you fill in both Email and Username with your @gmail account?
– I used port 465.
– Are you using Cellular, Ethernet or WiFi as your WAN transport?
– If Cellular, do you have a valid SIM and are you getting Carrier?
– Are you using mPower 5.1.6 or mLinux 5.1.6?
– Can you go to Admin > Debug and ping http://www.google.com?
It may be best for you to create a Support Case if the above isn’t working for you.
Regards,
MikeMike McNeilModeratorHello Fred,
I believe gmail is considering the MTCDT device a less secure device and not allowing it access to the gmail server.
I would recommend modifying your gmail account to allow less secure devices/app. Another option may be to install a signed and/or secure certificate.
If you have further questions, feel free to create a case at:
https://support.multitech.com
Regards,
MikeMike McNeilModeratorHello Jonathan,
Starting at mPower version 5.1.0, administrators can modify the Password Complexity Rules to allow a Credit Mode where the administrator can allow passwords with a specific number of credits instead of the Default Mode.
Please review the Help from your device or from the Software Guide for your device. This would apply to MTCAP, MTCDT, MTCDTIP and MTR products.
Regards,
MikeNovember 3, 2020 at 2:11 pm in reply to: Conduit does not check-in to DeviceHQ when Cellular is disabled #31305Mike McNeilModeratorHello William,
Sounds like your DNS server went down or isn’t working?
Seems like this has been working for a while, but just started failing?
Check to make sure your DHCP server is providing DNS or you have configured for a DNS server in your eth0 configuration.
If that doesn’t work then I suggest opening a support case at support.multitech.com and provide all details and how your MTCDT is configured.
Regards,
MikeMike McNeilModeratorCustomer has created a Support Portal case regarding this issue.
Regards.Mike McNeilModeratorCustomer has created a Support Portal case regarding this issue.
Regards.Mike McNeilModeratorCustomer has created a Support Portal case regarding this issue.
Regards.Mike McNeilModeratorCustomer has created a Support Portal case regarding this issue.
Regards.Mike McNeilModeratorCustomer has created a Support Portal case regarding this issue.
Regards.Mike McNeilModeratorCustomer has created a Support Portal case regarding this issue.
Regards.Mike McNeilModeratorVersion 5.1.6 has increased security. Issuing sudo -s at your SSH or debug port with place the device with root permissions instead of admin and that should provide access. Your root password is the same as your administrator password.
Regards.Mike McNeilModeratorHello KrisA,
mPower version 5.1.6 should have very similar functionality to 1.7.4. Please open a support case at https://support.multitech.com with your exact CDT model, serial number and required functionality.
Regards,
MikeMike McNeilModeratorHello AlexB,
Those listed commands are for mLinux only.
When using AEP or mPower firmware, it is recommended to use the AEP/mPower GUI to change the APN. Suggested locations would be Cellular > Cellular Configuration or Administration > Debug Options > Radio Terminal.
If requiring command line, try the radio-cmd call to send commands directly to the radio. Keep in mind, this communication is directly to the radio.
Regards,
MikeMike McNeilModeratorHello Rock,
All FaxFinder support is now led by the new, dedicated FaxFinder team.
Please send all support inquiries to support@faxfinder.net or visit
https://support.faxfinder.net to visit their new portal.For more information on all the changes to FaxFinder and the new initiative, be sure to visit https://www.faxfinder.net or call 763-777-1124.
Regards,
MikeMike McNeilModeratorI would try the upload_config command. You can use https://192.168.2.1/api/help/command for more information.
Regards.Mike McNeilModeratorHello Robert,
The AEP 5.0.0 comes from factory and after a factory reset in Commissioning mode. The user has to create a new User and Pass, the admin/admin is not default anymore. The default IP is still 192.168.2.1.
Please refer to Chapter 2 of the Software Guide ( https://www.multitech.com/documents/publications/software-guides/s000727%20-%20mPower%20Edge%20Intelligence%20Conduit_AEP_software_guide.pdf ) for further information.
Refer to the following if using Curl:
http://www.multitech.net/developer/software/mtr-software/mtr-api-reference/rcell_api_appendix/Regards,
MikeMike McNeilModeratorHello,
Yes, the MTR does allow external API calls with a Public SIM.
What firmware version you are using?
What Carrier are you using?
What are the digits of the first octet of your dynamic IP?
Do you have HTTPS Via WAN enabled under Access Configuration?
For external pinging you would need to enable ICMP Respond to WAN under Access Configuration.
Keep in mind, both these procedures will accrue data on your cellular account.
Regards,
MikeMike McNeilModeratorHello,
Are you trying to use the MTR as a Serial Modem or what is your purpose for sending AT commands to the MTR? If not as a Serial Modem, please provide more details.
If trying to use the MTR as a Serial Modem, I would set to Serial Modem Mode. After save and restart, I would open your terminal program directly to the COM port provided by the USB adapter. For example, TeraTerm to COM1. Default settings are 115200 8N1, flow control shouldn’t matter for this initial testing. I would try to interactively communicate with the MTR. For example, issue
ati3 <CR> and receive
Telit
OK
ati4 <CR> and receive
LE910-xxx
OK
Once you know that’s working then that’s when you can work on your ‘echo’ing and ‘cat’ting. We need to first verify your serial setup is working.
Regards.Mike McNeilModeratorHello,
When the MTR is configured for Network Router mode, the serial port is typically used for Serial-IP traffic and displaying GPS coordinates.
If attempting to use the MTR as a Serial Modem, I would select the Serial Modem Mode setting from the Initial Setup Wizard.Regards,
MikeMike McNeilModeratorHello,
Your serial number shows you have a mLinux version of the Conduit but you mentioned web version in your post. Are you using mLinux or AEP?
Regards.Mike McNeilModeratorHello Benjamin,
Did you try the commands from this link?
http://www.multitech.net/developer/software/mlinux/using-mlinux/reset-mlinux-to-defaults/
Regards.Mike McNeilModeratorHello Benjamin,
What version of AEP are you using?
What procedure did you try that was blocked?
Did you try holding the reset button for more than 30 seconds?
Did you try going to Administration > Save/Restore > Reset to Factory Default in the GUI?
Have you tried “reset-defaults -hard”?
Regards.July 15, 2019 at 11:17 am in reply to: Conduit does not check-in to DeviceHQ when Cellular is disabled #28217Mike McNeilModeratorHello William,
The Conduits can still check into DHQ when Cellular is disabled, you will have to make sure you have Internet access using your Ethernet as WAN.
When the SIM card is not detected you will have to make sure your WAN failover is setup properly to have WAN access if one of your modes fail.
To test, in the CDT GUI, go to Administration > Debug Options and ping 8.8.8.8 on ANY Interface. Does it error, respond with 4 transmits and 4 receives or 4 transmits and 0 receives? Now try http://www.google.com? The behavior will help determine if you have Internet access or DNS issues.Regards.
Mike McNeilModeratorHello Steve,
I’m not aware of the exact capabilities or specifics concerning the MTR’s SMS API abilities. I would recommend you create a Support Case at https://support.multitech.com and we can try to get the proper people included on the case.
Regards,
MikeMike McNeilModeratorHello Steve,
“Does not fail if SMS is longer than 160 characters”
– If using the API to send SMS messages you do not receive the 400 error fail message because of the length limit. The message will sometimes send and truncate at 160 other times it will not send at all. Note: In the WebGUI the SMS truncates at 160 characters.“Has issues depending on location of spaces”
– This involves using the API for the SMS Commands function, the reboot, checkin, ping, etc … commands. For example, sending the SMS command “p<space><space>password<space>#reboot” through the API causes issues compared to the documented “p<space>password<space>#reboot”.You did not mention what version of MTR code you were using, but these issues have likely been in the firmware since the API SMS Commands were implemented in 3.4.5.
Regards,
Mike -
AuthorPosts