Windows GUI/Controller for MySensors
-
@niccodemi I just was able to upload the bootloader using the files provided by @siklosi posted here http://forum.mysensors.org/topic/2319/how-to-make-complie-mysbootloader/7. The difference is I used a USBASP (V2.0) instead of an UNO. It worked the first time uploading the blink sketch!! It was a pain getting the USBASP to work on Windows 8.1 but after I got the driver installed (and the wiring connections correct) it worked great. I haven't uploaded any sensor sketches yet but hopefully I'll have time to play with it soon.
-
Hi, download link for MYSController is broken. Error on attempt to download. thank you
-
Hi, download link for MYSController is broken. Error on attempt to download. thank you
-
@balloonguy Not on my side. Please try again.
@tekka thanks for the quick response - i have tried the {http://goo.gl/9DCWNo} with no luck, all i get is a "this page is not available" message. I have tried with different browsers and different pc's - still the same response.
BTW- Merry Christmas. -
@tekka thanks for the quick response - i have tried the {http://goo.gl/9DCWNo} with no luck, all i get is a "this page is not available" message. I have tried with different browsers and different pc's - still the same response.
BTW- Merry Christmas.@balloonguy just tried this link. Everything is working, MYSController.zip file with md5 checksum dfe98f9e7ed6e1c3d5c418a862c23ee0 is downloaded.
-
Hi @tekka
When editing/adding items to the firmware_config.csv file, what should go in the types column? Could you please explain it?
Thanks,
@drock1985 said:
When editing/adding items to the firmware_config.csv file, w
The type field is intended for defining a FW type, e.g. a node with a DHT humidity/temperature sensor may be FW type 1, whereas a node with a different sensor FW type 2 and so on...
-
Now that I have sensors that have the correct bootloader I have been able to upload firmware a few times. But now that I have made changed to the sketch and copied the new hex file over I even bumped the version tag in the file. I can't get it to flash. Nothing I do makes it upload the new code? Thoughts?
-
Now that I have sensors that have the correct bootloader I have been able to upload firmware a few times. But now that I have made changed to the sketch and copied the new hex file over I even bumped the version tag in the file. I can't get it to flash. Nothing I do makes it upload the new code? Thoughts?
-
Now that I have sensors that have the correct bootloader I have been able to upload firmware a few times. But now that I have made changed to the sketch and copied the new hex file over I even bumped the version tag in the file. I can't get it to flash. Nothing I do makes it upload the new code? Thoughts?
-
Yes I can reboot the node. trying to upload dallastemp to it.
-
Yes I can reboot the node. trying to upload dallastemp to it.
-
Its turned on in MySensors.h and reuploaded
-
Bootloader on the sensors is the one from your firmware directory. on the GW its the standard arduino one... do I need yours on the GW?
@p0lar No, GW should have normal (i.e. Arduino) bootloader. However, without DEBUG output it's gonna be hard to diagnose what's wrong - can you double-check your settings and re-upload the GW sketch just to be on the safe side.
Also, I'd like to see the log during a manual reset (not remote reboot) of your node. -
Hi @tekka,
tried now some evenings to change node-id / clear the eeprom. No luck. FW update works always. After reading the bootloader code I expected myscontroller to send a invalid fwrequestresponse packet with special crc for the bootloader commands. Never showed up in the log.
Myscontroller .282 on Win xp and msbootloader 1.1 on nano. 47uF on nrf. No transmission errors.Any ideas where to look next ? Maybe .278 will do the trick ?
Thanks for your efforts ,
stebra -
Hi @tekka,
tried now some evenings to change node-id / clear the eeprom. No luck. FW update works always. After reading the bootloader code I expected myscontroller to send a invalid fwrequestresponse packet with special crc for the bootloader commands. Never showed up in the log.
Myscontroller .282 on Win xp and msbootloader 1.1 on nano. 47uF on nrf. No transmission errors.Any ideas where to look next ? Maybe .278 will do the trick ?
Thanks for your efforts ,
stebra -
MySensors_20160110-115615_stebra.log
hi tekka,
here is the log. Contains:
[2016-01-10 12:02:26.390 Info] INFO *** Logging START *** // stebra : succesful reboot of node 6 via myscontroller
[2016-01-10 12:02:59.000 Info] INFO *** Logging START *** // stebra : succesful FW update of node 6 via myscontroller
[2016-01-10 12:05:35.109 Info] INFO *** Logging START *** // stebra : ID reassign attempt of node 6 to node 12 via myscontroller
[2016-01-10 12:05:48.328 Info] INFO Send FW info to node 6: type=1E, version=1, blocks=0x0448, CRC=0xA87A // here the behaviour is unexpected for me[2016-01-10 12:06:37.437 Info] INFO *** Logging START *** // stebra: Clear eeprom attempt on node 6
[2016-01-10 12:06:44.812 Info] INFO Send FW info to node 6: type=1E, version=1, blocks=0x0448, CRC=0xA87A // here the behaviour is unexpected for methank you for having a look..