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.

Topics - bdevlin

Pages: [1]
I upgraded the latest gw110app firmware and I am now experiencing max 24-48 hours responsiveness before it crashes. I downgraded to the prior version and the problem persisted, so I upgraded again and I still have the same problem. Logging to usb would be helpful for us to get you debug info. My gateway is now totally unstable and I have no idea how to fix it. I have uses .5/1/2 amp power supplies with no apparent difference regarding this issue. Please advise.

Every column that is solid red indicates when the gateway stops relaying mqtt from all of my devices. It is then also unresponsive (not even visible) in mc-Studio.

[ Guests cannot view attachments ]

mc-Gateway / beacondata API
« on: November 06, 2017, 12:48:17 pm »
Is there an api for reading the beacondata directly from the gateway? My thought is if the beacondata is extremely low power, I can extend battery life on modules by using beacondata instead of Lplan.Publish. Clearly an API exists as mc-Studio can read beacons. How do you plan to expose this API to us? I prefer python. Or what if we could program the gateway to publish beacondata to an mqtt server?


mc-Studio / Variables for shared event timing
« on: July 08, 2017, 12:28:21 pm »
Looking to do something like this. Possible?

Class mqtt_json
    Shared interval As Byte = 5
    Shared span As String = "Minutes"
    Shared Event json_payload_mqtt() RaiseEvent Every interval span
            Do Stuff
End Event
End Class

Finally upgraded everything to 9.615.

Trying to connect to my devices (MC-110s in this case) responds with "gateway did not react on connect request". Then disconnects the gateway.

Devices on latest firmware. Gateway on app and firmware 9.615

Basically, I can't even upload new code to my devices now.

Please advise.

mc-Things General Discussion / TimeStamps
« on: April 12, 2017, 01:37:07 pm »
Does anyone have a GetTime() functions of sorts. Perhaps we can use the various cloud time servers. I don't know how to do it though. I know I can just stamp the data as it streams into my MQTT server, but I am just toying with a few options.


mc-Studio / Device.Uid
« on: April 05, 2017, 06:26:19 pm »
Device.Uid does not seem to be available in the IDE. I want to create a generic script for a standard task across 5 units and update code in one place. With the Uid , I can simply cross join a lookup table for data visualization. Uid is not available though.

16.34. Device Structure Inherits Object
Shared Function BatteryVoltage() As Short
Shared Function GarbageCollection() As Integer
Shared Function MemoryAvailable() As Integer
Shared Sub OpampEnable(enable As Boolean)
Shared Function TempDie() As Float
Shared Sub TempSensorEnable(enable As Boolean)
Shared Function Uid() As Integer
Shared Function Uptime() As Integer
Shared Function GetTimeSpan() As Integer

mc-Things General Discussion / Access old firmwares
« on: April 02, 2017, 11:24:41 pm »
I updated my gateway to the latest software and firmware 06-367 and 0.7-421.

The gateway no longer accepts messages from my modules scripts at all, so my entire test scenario is now broken. I am using the latest mc-Studio 0.7-906, and the gateway can connect, but will not detect devices for programming at all. I have one device sitting directly on top of the gateway. The beacons do show for all modules in range. Very frustrating. Any tips or an archive of old soft/firmwares please.

I have four active modules working reasonably well before this update.


mc-Studio / Frequent crashes with mc-studio
« on: January 06, 2017, 10:51:09 pm »
This app constantly crashes. 2 days ago I re-installed, rebooted... it still crashed. I manually removed everything from the windows install directory and my appdata . Then it worked, but broke my apps. I have them all in text so it was just copy/paste. Maybe implement a send error details to mc-things option so you guys can debug.

Any advice? You can see it's the latest firmware. Basically it's impossible to set up the MQTT details as per the video tutorial.

Pages: [1]