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-Gyver

Pages: [1]
mc-Dev Board / Re: UART console example not working on mcMod120
« on: July 31, 2017, 02:42:46 pm »
Hi rudydevolder,

One thing to take note is that Pin0 and Pin1 are also used for virtual gateway communication whereas wireless mcAir is disabled in replace for direct wire UART communication. This feature is enabled when mcStudio is running and mcMod120 does power on reset while on the dev board with pin0 and pin1 are connected.

There are 2 options you can do. you either have pin0 and pin1 disconnected when the device does power-on reset and reconnect them once you can see beacons from the mcMod120 on mcStudio OR you can use other pins and connect them thru jumper wires to the RXD and TXD pins on USB UART header.

mc-Gateway / Re: Cannot see the gateway in mcStudio
« on: June 07, 2017, 10:10:36 am »
Hi Cclr,

Sorry to hear you are having troubles updating the modules.

The mcOTA and the mcDongle work hand in hand to load up new firmware to the mcModules. Once you see "Ready" on the mcOTA it means that, mcOTA was able to talk to the mcDongle and is ready for more instructions. So, your drivers should be all good.

Details on update steps:
1. Start mcOTA and make sure it says "Ready". (again  :) ).
2. Click "Search Device". (This start continuous scans for bootloader beacons )
3. Power Cycle your mcModule by taking out the battery and putting it back in. (mcModules always boot in bootloader mode for 5seconds, once the 5sec elapsed it will go to its normal operation and will never go back to bootloader mode until another reboot).
4. Within the 5 seconds bootloader mode you should be able to see population of the Device Information window in the mcOTA. 
5. Click "Start Update" to begin updating the mcModules. Wait until it says "Firmware Update Done".

I hope this helps.

Best regards,

mc-Module / Re: Erased mcScript and module stopped working
« on: February 23, 2017, 12:19:42 pm »
Hi mcHome,

Do you happen to know the version number of the bootloader before you pressed erase mcScript?

Did the manual setting of parameters work?

The COM port settings are:
* Bits per second: 38400
* Data bits: 8
* Parity: None
* Stop bits: 1
* Flow control: None

BUT, those should have been automatically set when mcOTA starts and an "mcBoot" device has been found.

mc-Gateway / Re: unable to update firmware
« on: September 12, 2016, 09:38:28 am »
Try re-updating the gateway host with 0.7-410 again. Just ignore "binary file is incompatible with the device" hit OK to proceed. (This error appears because the bootloader is an intermediate state where it was interrupted in the middle of the update).

Make sure the gateway is in good range with the mc-Dongle.

mc-Gateway / Re: How I broke OTA update
« on: August 22, 2016, 10:16:58 am »
Hi Millennial,

First, we have to check if your device still has a working bootloader.
1. Power down mc-Gateway.
2. Launch mc-OTA (make sure it says "Ready").
3. Click "Search" on mc-OTA.
4. Power up mc-Gateway.

Let us know what you have on the "Device Information" window. Do not worry about "VM Firmware Version:NA" it will be updated later on once the bootloader has been successfully updated.

The bootloader needs to be updated to accommodate new features like the ability to erase a bad mc-Script.

New Version Releases / Updated User Guide for mc-OTA Updater v1.2.10
« on: August 17, 2016, 12:57:16 pm »
An update of the mc-OTA Updater User Guide is now available for download!

New Version Releases / Re: New version of mc-OTA available today!
« on: August 17, 2016, 12:53:09 pm »
Hi Riverrider,

Based on the snapshot that you have provided, the mc-OTA Updater have found the mc-Dongle automatically and there is no need to change the Port Number. The "Connect" button will only be activated if for some reason it cannot find an appropriate mc-Dongle.

Second, I could see you have cancelled the update because of an Incompatible device bootloader warning. There has been some changes on the bootloader to accommodate few more features like erasing mcScript. If you click Start Update it should be able to continue the update including the update of your device's bootloader.

mc-Gateway / Re: Multiple mcGateways
« on: August 08, 2016, 04:27:25 pm »
Hi Kristofferis,

The registration information is on the mcGateways. Firmware update on the module does not loose its registration on a certain gateway.

In the future version (probably in v0.8), It will be possible to pull out this information.

Critical update for gateway host processor has been released.
This fixes a beacon channel breach. Symptom includes excessive number of identical beacon messages in less than a second.

mc-Module / Re: Can't get gateway to connect to mcmodule
« on: July 06, 2016, 04:00:18 pm »
Did you power cycle the device? The module's bootloader will be active for 5 seconds after a power on reset. We can try it again by doing the following steps.
   1. Unplug power from mcMod110.
   2. Launch mc-OTA Updater and start “Search Device”. (without filtering)
   3. Supply power on mcMod110
   4. When the Device (mcMod110) is found, It’s info will be populated on the Device Information window and should be ready for starting the update.

For more information you can find the quick start guide here:

mc-Gateway / Re: Multiple mcGateways
« on: June 09, 2016, 09:02:58 am »
The modules are automatically registered to a gateway the first time you connect/debug to it using mc-Studio. It will only talk to that gateway until you decided to connect/debug the same module on another gateway. If a module is registered to 2 or more gateways, the gateway with the best wireless integrity wins and will have the opportunity to transact sensitive data i.e. MQTT Publish/Subscribe, IFTTT etc.

Module Beacons on the other hand are passive, One way, Unencrypted transmission. Which means all of the gateways that are in range(registered or unregistered) will be able to receive the data and relay it to the IP Network through UDP messages.

Pages: [1]