MYSBootloader 1.3 pre-release & MYSController 1.0.0beta
-
I have to ask again: GatewayW5100MQTTClient or the old Broker Gateway?
I am not able to connect to my GatewayW5100MQTTClient on port 1883 or 5003 with MYSController 1.0.0beta.
The gateway is in working condition with openHAB. -
-
Hello @ all :)
first thx to tekka for the great job :)
as the release notes say with the mysbootloader 1.3pre one can use the serial upload.
is its usable via the arduino ide? Because i can upload a sketch but it seems not to start.also as rollercontainer asked is the myscontroller application usable via the old broker or with the new clientmqtt gateway?
Would be nice if there are some instructions how to use ;) -
Hello @ all :)
first thx to tekka for the great job :)
as the release notes say with the mysbootloader 1.3pre one can use the serial upload.
is its usable via the arduino ide? Because i can upload a sketch but it seems not to start.also as rollercontainer asked is the myscontroller application usable via the old broker or with the new clientmqtt gateway?
Would be nice if there are some instructions how to use ;)@n1ck1355 @rollercontainer MYSController does not support MQTT (at the moment), but have a look at MyController.org. Please provide more details regarding your issue with MYSBootloader 1.3pre.
-
thx tekka for clearing this :)
for my bootloader problem:
i burned the 1.3mysbootloader with the 8mhz config successfully from the arduino dev ide.
then i uploaded a little test sketch like this without errors:void setup() { Serial.begin(57600); Serial.println("Setup Start"); } void loop() { }but there is no output on the serial monitor. it lookes like the bootloader didn't start the sketch.
-
I try to add new hex file in MYSController 1.0 but after clicking "reload repo", it tells me 2107-15-31 is not a valid date specification. I don't have the ability to select firmware after this. And after a reboot the "reload repo" is garyed.
Arduino ide 1.6.7
csv :Type,Name,Version,File,Comments 10,Blink,1,Blink.ino.hex,blinking example 20,TimeReporter,1,TimeReporter.ino.hex,TimeReporter demo 30,SenseBender,1,SensebenderMicro.ino.hex,Sensebender microAnother 'bug". It always ask me to download a "new" version ... I install it but ask me again (1.0 beta)
I think this issue is related to the last arduino IDE version. -
I try to add new hex file in MYSController 1.0 but after clicking "reload repo", it tells me 2107-15-31 is not a valid date specification. I don't have the ability to select firmware after this. And after a reboot the "reload repo" is garyed.
Arduino ide 1.6.7
csv :Type,Name,Version,File,Comments 10,Blink,1,Blink.ino.hex,blinking example 20,TimeReporter,1,TimeReporter.ino.hex,TimeReporter demo 30,SenseBender,1,SensebenderMicro.ino.hex,Sensebender microAnother 'bug". It always ask me to download a "new" version ... I install it but ask me again (1.0 beta)
I think this issue is related to the last arduino IDE version. -
thx tekka for clearing this :)
for my bootloader problem:
i burned the 1.3mysbootloader with the 8mhz config successfully from the arduino dev ide.
then i uploaded a little test sketch like this without errors:void setup() { Serial.begin(57600); Serial.println("Setup Start"); } void loop() { }but there is no output on the serial monitor. it lookes like the bootloader didn't start the sketch.
-
Hi, i like OTA Update :-)
How it is possible to change the Cannel from 76 to 105?
-
@rollercontainer said:
@Takero https://github.com/mysensors/Arduino/blob/development/libraries/MySensors/MyConfig.h#L387
Yes, i know what, but this is not there I am looking for.
The Autor wrote:
Attached bootloader file, compiled with these settings:nRF24 (Channel 76, base address 0xA8A8E1FC00, data rate 250kbs)
115200 baud (16Mhz) or 57600 (8Mhz)I want a Bootloader file with Channel 105.
-
@rollercontainer said:
@Takero https://github.com/mysensors/Arduino/blob/development/libraries/MySensors/MyConfig.h#L387
Yes, i know what, but this is not there I am looking for.
The Autor wrote:
Attached bootloader file, compiled with these settings:nRF24 (Channel 76, base address 0xA8A8E1FC00, data rate 250kbs)
115200 baud (16Mhz) or 57600 (8Mhz)I want a Bootloader file with Channel 105.
sorry, you are right. Since the source isnt yet available, you cant compile your custom bootloader. So, thats a no.
-
@tekka here is the log output:
05.04.16 21:51:34 STARTUP Initialize message logging 05.04.16 21:51:34 STARTUP 1.0.0 (build 3312) 05.04.16 21:51:34 STARTUP FPC 3.0.0 / Lazarus 1.6 05.04.16 21:51:34 STARTUP still under development :) tekka 2016 05.04.16 21:51:34 STARTUP Load INI file... 05.04.16 21:51:34 STARTUP INI version NA 05.04.16 21:52:08 INFO Connected to 192.168.0.101:5003 05.04.16 21:52:23 RX 2;255;3;0;15;0100 05.04.16 21:52:23 NODE New node discovered, node id=2 05.04.16 21:52:23 CHILD New child discovered, node id=2, child id=internal 05.04.16 21:52:30 RX 2;255;4;0;0;FFFFFFFF0800077E0102 05.04.16 21:52:30 DEBUG Undefined firmware/type for node=2 05.04.16 21:52:30 INFO BL version=258 05.04.16 21:52:30 INFO No FW assigned 05.04.16 21:52:36 RX 2;255;4;0;0;FFFFFFFF0800077E0102 05.04.16 21:52:36 DEBUG Undefined firmware/type for node=2 05.04.16 21:52:36 INFO BL version=258 05.04.16 21:52:36 INFO No FW assigned 05.04.16 21:52:43 RX 2;255;4;0;0;FFFFFFFF0800077E0102 05.04.16 21:52:43 DEBUG Undefined firmware/type for node=2 05.04.16 21:52:43 INFO BL version=258 05.04.16 21:52:43 INFO No FW assigned 05.04.16 21:53:00 RX 2;255;3;0;15;0100 05.04.16 21:53:07 RX 2;255;4;0;0;FFFFFFFF0800077E0102 05.04.16 21:53:07 DEBUG Undefined firmware/type for node=2 05.04.16 21:53:07 INFO BL version=258 05.04.16 21:53:07 INFO No FW assigned 05.04.16 21:53:14 RX 2;255;4;0;0;FFFFFFFF0800077E0102 05.04.16 21:53:14 DEBUG Undefined firmware/type for node=2 05.04.16 21:53:14 INFO BL version=258 05.04.16 21:53:14 INFO No FW assigned 05.04.16 21:53:21 RX 2;255;4;0;0;FFFFFFFF0800077E0102 05.04.16 21:53:21 DEBUG Undefined firmware/type for node=2 05.04.16 21:53:21 INFO BL version=258 05.04.16 21:53:21 INFO No FW assigned 05.04.16 21:53:38 RX 2;255;3;0;15;0100 05.04.16 21:53:45 RX 2;255;4;0;0;FFFFFFFF0800077E0102 05.04.16 21:53:45 DEBUG Undefined firmware/type for node=2 05.04.16 21:53:45 INFO BL version=258 05.04.16 21:53:45 INFO No FW assigned 05.04.16 21:53:52 RX 2;255;4;0;0;FFFFFFFF0800077E0102 05.04.16 21:53:52 DEBUG Undefined firmware/type for node=2 05.04.16 21:53:52 INFO BL version=258 05.04.16 21:53:52 INFO No FW assigned 05.04.16 21:53:58 RX 2;255;4;0;0;FFFFFFFF0800077E0102 05.04.16 21:53:58 DEBUG Undefined firmware/type for node=2 05.04.16 21:53:58 INFO BL version=258 05.04.16 21:53:58 INFO No FW assigned 05.04.16 21:54:16 RX 2;255;3;0;15;0100 05.04.16 21:54:23 RX 2;255;4;0;0;FFFFFFFF0800077E0102 05.04.16 21:54:23 DEBUG Undefined firmware/type for node=2 05.04.16 21:54:23 INFO BL version=258 05.04.16 21:54:23 INFO No FW assigned 05.04.16 21:54:29 RX 2;255;4;0;0;FFFFFFFF0800077E0102 05.04.16 21:54:29 DEBUG Undefined firmware/type for node=2 05.04.16 21:54:29 INFO BL version=258 05.04.16 21:54:29 INFO No FW assigned 05.04.16 21:54:36 RX 2;255;4;0;0;FFFFFFFF0800077E0102 05.04.16 21:54:36 DEBUG Undefined firmware/type for node=2 05.04.16 21:54:36 INFO BL version=258 05.04.16 21:54:36 INFO No FW assigned 05.04.16 21:54:54 RX 2;255;3;0;15;0100 05.04.16 21:55:01 RX 2;255;4;0;0;FFFFFFFF0800077E0102 05.04.16 21:55:01 DEBUG Undefined firmware/type for node=2 05.04.16 21:55:01 INFO BL version=258 05.04.16 21:55:01 INFO No FW assigned 05.04.16 21:55:07 RX 2;255;4;0;0;FFFFFFFF0800077E0102 05.04.16 21:55:07 DEBUG Undefined firmware/type for node=2 05.04.16 21:55:07 INFO BL version=258 05.04.16 21:55:07 INFO No FW assigned 05.04.16 21:55:14 RX 2;255;4;0;0;FFFFFFFF0800077E0102 05.04.16 21:55:14 DEBUG Undefined firmware/type for node=2 05.04.16 21:55:14 INFO BL version=258 05.04.16 21:55:14 INFO No FW assigned 05.04.16 21:55:32 RX 2;255;3;0;15;0100 05.04.16 21:55:38 RX 2;255;4;0;0;FFFFFFFF0800077E0102 05.04.16 21:55:38 DEBUG Undefined firmware/type for node=2 05.04.16 21:55:38 INFO BL version=258 05.04.16 21:55:38 INFO No FW assigned 05.04.16 21:55:45 RX 2;255;4;0;0;FFFFFFFF0800077E0102 05.04.16 21:55:45 DEBUG Undefined firmware/type for node=2 05.04.16 21:55:45 INFO BL version=258 05.04.16 21:55:45 INFO No FW assigned 05.04.16 21:55:52 RX 2;255;4;0;0;FFFFFFFF0800077E0102 05.04.16 21:55:52 DEBUG Undefined firmware/type for node=2 05.04.16 21:55:52 INFO BL version=258 05.04.16 21:55:52 INFO No FW assigned 05.04.16 21:56:10 RX 2;255;3;0;15;0100 05.04.16 21:56:16 RX 2;255;4;0;0;FFFFFFFF0800077E0102 05.04.16 21:56:16 DEBUG Undefined firmware/type for node=2 05.04.16 21:56:16 INFO BL version=258 05.04.16 21:56:16 INFO No FW assigned 05.04.16 21:56:23 RX 2;255;4;0;0;FFFFFFFF0800077E0102 05.04.16 21:56:23 DEBUG Undefined firmware/type for node=2 05.04.16 21:56:23 INFO BL version=258 05.04.16 21:56:23 INFO No FW assigned 05.04.16 21:56:30 RX 2;255;4;0;0;FFFFFFFF0800077E0102 05.04.16 21:56:30 DEBUG Undefined firmware/type for node=2 05.04.16 21:56:30 INFO BL version=258 05.04.16 21:56:30 INFO No FW assigned 05.04.16 21:56:47 RX 2;255;3;0;15;0100 05.04.16 21:56:54 RX 2;255;4;0;0;FFFFFFFF0800077E0102 05.04.16 21:56:54 DEBUG Undefined firmware/type for node=2 05.04.16 21:56:54 INFO BL version=258 05.04.16 21:56:54 INFO No FW assigned 05.04.16 21:57:01 RX 2;255;4;0;0;FFFFFFFF0800077E0102 05.04.16 21:57:01 DEBUG Undefined firmware/type for node=2 05.04.16 21:57:01 INFO BL version=258 05.04.16 21:57:01 INFO No FW assigned 05.04.16 21:57:07 RX 2;255;4;0;0;FFFFFFFF0800077E0102 05.04.16 21:57:07 DEBUG Undefined firmware/type for node=2 05.04.16 21:57:07 INFO BL version=258 05.04.16 21:57:07 INFO No FW assigned 05.04.16 21:57:25 RX 2;255;3;0;15;0100 05.04.16 21:57:32 RX 2;255;4;0;0;FFFFFFFF0800077E0102 05.04.16 21:57:32 DEBUG Undefined firmware/type for node=2 05.04.16 21:57:32 INFO BL version=258 05.04.16 21:57:32 INFO No FW assigned 05.04.16 21:57:39 RX 2;255;4;0;0;FFFFFFFF0800077E0102 05.04.16 21:57:39 DEBUG Undefined firmware/type for node=2 05.04.16 21:57:39 INFO BL version=258 05.04.16 21:57:39 INFO No FW assigned 05.04.16 21:57:45 RX 2;255;4;0;0;FFFFFFFF0800077E0102 05.04.16 21:57:45 DEBUG Undefined firmware/type for node=2 05.04.16 21:57:45 INFO BL version=258 05.04.16 21:57:45 INFO No FW assigned 05.04.16 21:58:03 RX 2;255;3;0;15;0100 05.04.16 21:58:10 RX 2;255;4;0;0;FFFFFFFF0800077E0102 05.04.16 21:58:10 DEBUG Undefined firmware/type for node=2 05.04.16 21:58:10 INFO BL version=258 05.04.16 21:58:10 INFO No FW assigned 05.04.16 21:58:16 RX 2;255;4;0;0;FFFFFFFF0800077E0102 05.04.16 21:58:16 DEBUG Undefined firmware/type for node=2 05.04.16 21:58:16 INFO BL version=258 05.04.16 21:58:16 INFO No FW assigned 05.04.16 21:58:23 RX 2;255;4;0;0;FFFFFFFF0800077E0102 05.04.16 21:58:23 DEBUG Undefined firmware/type for node=2 05.04.16 21:58:23 INFO BL version=258 05.04.16 21:58:23 INFO No FW assigned 05.04.16 21:58:41 RX 2;255;3;0;15;0100 05.04.16 21:58:45 USER Debug=FALSE 05.04.16 21:58:45 INFO *** Logging STOP *** 05.04.16 21:58:47 RX 2;255;4;0;0;FFFFFFFF0800077E0102 05.04.16 21:58:47 DEBUG Undefined firmware/type for node=2 05.04.16 21:58:47 INFO BL version=258 05.04.16 21:58:47 INFO No FW assigned 05.04.16 21:58:54 RX 2;255;4;0;0;FFFFFFFF0800077E0102 05.04.16 21:58:54 DEBUG Undefined firmware/type for node=2 05.04.16 21:58:54 INFO BL version=258 05.04.16 21:58:54 INFO No FW assigned 05.04.16 21:59:01 RX 2;255;4;0;0;FFFFFFFF0800077E0102 05.04.16 21:59:01 DEBUG Undefined firmware/type for node=2 05.04.16 21:59:01 INFO BL version=258 05.04.16 21:59:01 INFO No FW assignedhope it helps finding out whats wrong ;)
-