Recent Posts

Pages: [1] 2 3 ... 10
1
mc-Innovations / Translate acceleration in G's to textual states.
« Last post by Junkboy on July 09, 2018, 03:10:42 pm »
Hello community of McThings, I am developing a project, in which I am using a module Mc120, which currently transmits via MQTT the angles of inclination and the acceleration of all its axes, all this information is sent every 3 seconds, since it is Very fast, a battery that in "theory" should last up to 5 years lasts no more than 2 weeks.

What is currently done is to receive the acceleration and tilt of the device in an MQTT server, the information is analyzed to translate the states to a person for example "Walking" or "Running" etc.

What I want to do to save battery is the following:

I think to use the function:
accel.ConfigureMotionInterrupt (1.15, 20.0)

This would cause an interruption when there is an acceleration equal to or greater than 1.15G for more than 2 ms, this is just an example in practice those parameters would change.

The idea would be to set the parameters so that when there is some acceleration the device wakes up and knows that there is movement, then it would have to verify in which case it is.

In my personal experience I know a lot more about the C ++ language so I can imagine it in this way in C ++:

if (accel> = 1.15)
{
 state = ON;
}

if (accel> = 1.15 && accel <= 1.8)
{
 printf ("Walking"),
}
if (accel> = 1.81 && accel <= 2.2)
{
 printf ("Runing"),
}
if (accel <= 1.15)
{
 printf ("Stopped"),
}

With these conditions I seek to make instead of every 3 seconds send me the acceleration etc, better the device stays off until there is some acceleration and send me the message that is what you are doing, in the case of "Stopped" is only to put it because in reality if there is no acceleration greater than 1.15 will not turn on, that's the idea and in fact I also have to do some condition or something so that as long as it is lower than 1.15 send the message "Stopped" but. I do not want them to repeat either, that is if the current state is "Stopped" that sends it only once, if it starts to walk then it sends "Walking" but if it kept walking 15 minutes, do not send me that message again until it change of state

I hope to be explaining, the truth is a bit complicated programming in McStudio for me, but I would like to know if someone can help me to translate this to the language used in McStudio because for example I do not know how to put a conditional with intervals, in the case of "if (accel > = 1.15 && accel <= 1.8)" I do not know how to do it in McStudio, nor am I sure how to make the data not repeat.

I would really appreciate very much if someone could support me a little with this.

Beforehand thank you very much.
2
mc-Things General Discussion / Re: Help with the accelerometer (mcMod120)
« Last post by Junkboy on July 05, 2018, 04:38:06 pm »
Thank you Nick_W, that help me a lot, I will send you a message, check it out please :D!
3
MQTT / Re: mcStudio cannot find Gateway
« Last post by Nick_W on June 29, 2018, 01:10:38 pm »
Jeff,

Sounds like you have the wrong version of McStudio. there are two versions, the legacy version (0.9) and the McCloud version. What you need is the legacy version. get it from here https://www.mcthings.com/wp-content/uploads/files/mcStudio/mcStudio+ReleaseNotes.zip

What does help->about McStudio say?
4
mc-Things General Discussion / Re: Help with the accelerometer (mcMod120)
« Last post by Nick_W on June 29, 2018, 12:40:10 pm »
JunkBoy,

I have lots of examples and libraries for the accelerometer, check them out here https://github.com/NickWaterton/mcScript

Hope this helps.
5
MQTT / mcStudio cannot find Gateway
« Last post by Jeffsg605 on June 28, 2018, 03:08:09 pm »
I’m following this tutorial (http://help.ubidots.com/connect-your-devices/connect-the-mc-gateway-with-the-ubidots-mqtt-broker) and I’m stuck on step 3 “Connect the mc-Gateway to mc-Studio”.  My “Tools” menu does not have a “Devices” option.  I have a “View->Devices” option but there does not seem to be any way to connect to a gateway from there.  I also have a “Tools->Gateway Configuration” but cannot seem to get that to find my gateway. 

Any ideas?

Thanks in advance.
6
Hi Tomasu,

I understand your disappointment and frustration - There are many good reasons why we had to move to a new system and drop the legacy version such as:

- SECURITY - as you know, in IoT, security is a big ticket item (there are news reports everyday about hackers, etc). The older system, while a bit more 'open', does not include the security required for large-scale enterprise IoT solutions. As we are a business and focused mostly on B2B opportunities, this is a critical thing that we needed to address and as such, a system like mcCloud was necessary

- SCALABILITY - if you have used the legacy system for some time, you understand that it can be frustrating to update even 10 or 20 devices with new code or firmware as you had to physically touch/get close to the devices. Imagine trying to do this with 100 or 100,000 devices! mcCloud changes this and makes it SO MUCH easier to manage the devices at scale.

-VERSATILITY - Using mcCloud, you can now easily send information to multiple locations (like Azure, Losant, Ubidots, etc) from the cloud, instead of configuring your gateway to send the information to one location only. While this might be nice for a DIY person, it is not scalable for anytype of real IoT solution.

IMPROVEMENTS - Just like almost anything else, as technology gets better and new requirements need to be addressed, systems need to change. As such, we needed to move to the new system for all the above reasons and it allows us to continue to add new features and functions in the future.

Sorry to hear that you are going to move away from our platform. Hopefully the above gives you some understanding of why we we changed from legacy and why we can no longer support the old system.
Take care.

I think the most disappointing part is the increased closed-ness, the fact that this has been a problem for a while, theres no fix, and the only comment is "sorry, we're not supporting it anymore"

I get the whole running a business thing. It just doesn't seem like the product was particularly valued, nor are the customers.
7
Hi Tomasu,

I understand your disappointment and frustration - There are many good reasons why we had to move to a new system and drop the legacy version such as:

- SECURITY - as you know, in IoT, security is a big ticket item (there are news reports everyday about hackers, etc). The older system, while a bit more 'open', does not include the security required for large-scale enterprise IoT solutions. As we are a business and focused mostly on B2B opportunities, this is a critical thing that we needed to address and as such, a system like mcCloud was necessary

- SCALABILITY - if you have used the legacy system for some time, you understand that it can be frustrating to update even 10 or 20 devices with new code or firmware as you had to physically touch/get close to the devices. Imagine trying to do this with 100 or 100,000 devices! mcCloud changes this and makes it SO MUCH easier to manage the devices at scale.

-VERSATILITY - Using mcCloud, you can now easily send information to multiple locations (like Azure, Losant, Ubidots, etc) from the cloud, instead of configuring your gateway to send the information to one location only. While this might be nice for a DIY person, it is not scalable for anytype of real IoT solution.

IMPROVEMENTS - Just like almost anything else, as technology gets better and new requirements need to be addressed, systems need to change. As such, we needed to move to the new system for all the above reasons and it allows us to continue to add new features and functions in the future.

Sorry to hear that you are going to move away from our platform. Hopefully the above gives you some understanding of why we we changed from legacy and why we can no longer support the old system.
Take care.
8
Hi Everyone,
sorry that you are experiencing these issues - As mentioned in other posts, we are no longer supporting the older version of the system in the fact that we are not going to make changes or fix any potential bugs as we are focused on the new system (with mcCloud: https://www.mcthings.com/getting-started-mccloud/). NOTE - Older hardware such as the gateway110 and mcMod110's will not function on the new system (they dont have the technical requirements to access the new system) so to work with the new release, you will need to upgrade your equipment.
We are planning on a discounted offer to existing users and backers soon (it has been delayed due to some massive projects we are working on). If you do want to get more information, you can ask us here or email as at info@mcthings.com.

In regards to the issue, our recommendation would be to re-load the firmware for all your devices, make sure your modules have fresh batteries and, if you are having issues using WIFI, switch to Ethernet as for some of you, it appears to be more stable.

Hope that helps!

*sigh*

That's incredibly disappointing.

I'm not really interested in a more closed system, it's already bad enough that the current one was dropped so quickly with so many issues still present.

I'm sorry but I don't think I'll be able to support you guys in the future. I'm disappointed. I was happy to support you guys as a fellow albertan.
9
Hi Junkboy,

yes, you can insert a 'sleep' function into your code. Check out the attached mcScript guide (Also available on the website) and search through it for the function. I think i remember that it is discussed or displayed on page 23 (and other areas within the document).

The concept would be, to complete what you are asking below, is to raise an event every 60 minutes, insert the sleep function for a certain period of time (I believe the sleep function calculates time in milliseconds so you'll need to do some conversion). Should allow you to do what you are asking below.

Good luck!
10
Hi Everyone,
sorry that you are experiencing these issues - As mentioned in other posts, we are no longer supporting the older version of the system in the fact that we are not going to make changes or fix any potential bugs as we are focused on the new system (with mcCloud: https://www.mcthings.com/getting-started-mccloud/). NOTE - Older hardware such as the gateway110 and mcMod110's will not function on the new system (they dont have the technical requirements to access the new system) so to work with the new release, you will need to upgrade your equipment.
We are planning on a discounted offer to existing users and backers soon (it has been delayed due to some massive projects we are working on). If you do want to get more information, you can ask us here or email as at info@mcthings.com.

In regards to the issue, our recommendation would be to re-load the firmware for all your devices, make sure your modules have fresh batteries and, if you are having issues using WIFI, switch to Ethernet as for some of you, it appears to be more stable.

Hope that helps!
Pages: [1] 2 3 ... 10