Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - mc-Abe

Pages: 1 [2] 3 4 ... 12
16
This is missed in our documentation, I will make sure we update this and add an example but here is an explanation of what I think is happening with your code:

Due to FCC regulation, there are time limits on how often sigfox messages can be sent. Effectively, you can only send 2 messages within a 20-second window. The underlying sigfox stack on our device will take care of this timing. However what you need to ensure is that your sigfox message was accepted by the device to be queued for transmission. We have limited memory so this queue size is small. the Lplan.Sigfox() function actually returns whether the message was successfully accepted for transmission or not. I would suggest you change your call to this:

Code: [Select]
While Not Lplan.Sigfox(msg)
    Thread.Sleep(10000000)
End While

Note that this will cause your thread to sleep for 10 seconds if the message is not accepted and continue to do so until the message is accepted (Should never be more than 20s). Not sure if this will be alright in your application but you need to implement a mechanism like this to avoid losing your messages.

17
mc-Demo205 / Re: Sending GNSS data over Sigfox
« on: December 13, 2016, 11:00:02 am »
The data that you place in the message structure using AddFloat is in Little Endian Float format so 0xa2479b41 equates to 19.41 in float.

You can use a tool like this: https://gregstoll.dyndns.org/~gregstoll/floattohex/ to see the conversion. Note that you have to flip the bytes since the tool is expecting data in Big Endian. So use 0x419b47a2 when you use this tool.

Add float placed data in using Little Endian by default as it is the native format of the processor. You can use an overloaded version of AddFloat to place the data in, in Big Endian format if you prefer.

Also the Sigfox backend has the ability to parse bytes into meaningful data but you need to look at their documentation for that.

18
mc-Module / Re: DateTime issues
« on: November 14, 2016, 10:57:34 am »
I believe the description of this function is incorrect. The current DateTime instance will not be modified. The function returns a new DateTime instance that must be assigned to a new DateTime object.

19
mc-Module / Re: Getting reboots during interrupts
« on: November 14, 2016, 10:53:54 am »
I am glad to see that things are improving. We are aware of the random reboot issue and are working on it.

As for the publishing stopping, we found a big problem that was solved in version v0.7-417 of the Gateway Host Processor which was released on Nov 10th. Could you try this improved version to see if your results are better?

20
mc-Module / Re: Getting reboots during interrupts
« on: November 07, 2016, 10:17:11 am »
All the memory used in the scripts are managed memory so if you run out of that memory you will receive a run-time error. We had some more issues with the garbage collection process on the managed memory, I believe these have been resolved and a new version is going up today. Could you try this so we can rule out the garbage collection as a source of the problem.

If we still have problem then, we will look further into what might the cause be.

21
mc-Module / Re: Indexers How do they work?
« on: November 03, 2016, 11:41:24 am »
I have found the problem. Will be fixed in the next mcStudio release.

22
mc-Module / Re: Indexers How do they work?
« on: November 02, 2016, 01:32:40 pm »
How do you expect InsertAt to work? According to the documentation it inserts an element at the specified index. It shifts everything else. This seems to be consistent with my tests. Are you expecting InsertAt to overwrite the element at the given index?

23
mc-Module / Re: Indexers How do they work?
« on: November 02, 2016, 12:14:51 pm »
I will have a look at this and have a fix release soon.

24
mc-Module / Re: Modules stop publishing
« on: November 02, 2016, 12:12:58 pm »
The release note refers to receiving deliveries on the module. This would be messages that the module is receiving as a result of subscriptions.

We are aware of the publish issues, we will be working on a major overhaul to improve these issues. Expect something in the near future.

25
mc-Module / Re: Indexers How do they work?
« on: October 24, 2016, 11:49:22 am »
Haha! No problem Nick. That functionality is shared between both mcMod110 and mcMod120 so as you mentioned the problem is in both. We will release both versions simultaneously.

26
mc-Module / Re: Indexers How do they work?
« on: October 24, 2016, 10:53:06 am »
It appears there is an issue with the Remove function on lists. I think I have tracked it down. I will verify this further and we will release a new version of mcMod120 soon to address this and a few other issues.


27
mc-Dev Board / Re: MQTT on mc-Dev Board
« on: September 19, 2016, 11:11:27 pm »
You are correct, at the moment all communications are directed to mcStudio through the serial port while using the mc-Dev board. This will change in the future.

28
mc-Studio / Re: Can't config Gateway
« on: September 08, 2016, 08:49:06 pm »
I believe the error reporting changed and that is what you are noticing. The issue is around added configurations in the gateway that mcStudio is requesting but the gateway doesn't have yet since it is an older version. Please look on the forum for other posts regarding updating the gateway. If you have the older version of the bootloader on your gateway then you will need a USB stick with less than 100mA of current requirement. If you look at the gateway quickstart guide you should be able to figure out which version of the bootloader you have.

29
mc-Studio / Re: Can't config Gateway
« on: September 08, 2016, 02:07:47 pm »
This is most likely because your gateway application processor is running a very old version. Please update to the latest version.

30
mc-Module / Re: New module firmware 7-368 problem
« on: August 31, 2016, 05:24:57 pm »
Glad that this fixed it. Sorry about the bug. Sometimes quick turnarounds lead to a little less than ideal testing.

Pages: 1 [2] 3 4 ... 12