MYSBootloader 1.3 pre-release & MYSController 1.0.0beta

Fabien

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 micro

Another '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.

tekka

@Fabien Are you running MYSController on WINE? I updated a few things, please update to the most recent version of MYSController (build 3312, here or via update button) and post the log. Thanks.

tekka

@n1ck1355 Please enable logging in MYSController, reboot the node and post the log here after a few mins of recording.

Takero

Hi, i like OTA Update :-)

How it is possible to change the Cannel from 76 to 105?

rollercontainer

@Takero https://github.com/mysensors/Arduino/blob/development/libraries/MySensors/MyConfig.h#L387

Takero

@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

sorry, you are right. Since the source isnt yet available, you cant compile your custom bootloader. So, thats a no.

n1ck1355

@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 assigned

hope it helps finding out whats wrong ;)

Fabien

@tekka I try with build 3312 and working fine with wine
Now I'm looking for I_PRESENTATION. With 2.0 beta it doesn't seem to work. May I use smartSleep ?

Fabien

So after few test, wrks fine with I_PRESENTATION request and using smartSleep (with interrupts too).

n1ck1355

@tekka : do you have any clue whats wrong with my setup?

DrJeff

Does the gateway need the OTA firmware (flashed) written to it as well as the Nodes?

tekka

@n1ck1355 yes, probably there is a timing issue with serial uploads. Need to review the STK500 code. Can you confirm that OTA FW updates work fine?

tekka

@DrJeff No, only the nodes

DrJeff

@tekka Cool thanks, can I use Arduino as ISP to program bootloader?

tekka

@DrJeff Yep :)

DrJeff

@tekka , Time to try Thanks! :)

n1ck1355

@tekka yes ota fw updates works. Tried it with the Time fw

n1ck1355

@tekka i musst revert my previous post...
I've OTA uploaded the sketch from my first post:

void setup() {
  Serial.begin(57600);
  Serial.println("Setup Start");
}

void loop() {
}

and i connected the board over Serial with my computer. After uploading the sketch i did not noticed any output on the serial monitor in the Arduino IDE. Also checked the transfer rate.

However the time reporter firmware works fine.

siklosi

Is there a way to send ota firmware to node using some cli (python or...) script? I'm using MySensors with domoticz on RPi and when flashing new firmware I usually disconnect gw from rpi plug it into notebook and send fw using MYSController. If I could just disable gw in domoticz and send fw using some script it would be great until (if) domoticz gets support for ota fw.

MYSBootloader 1.3 pre-release & MYSController 1.0.0beta

29

11.7k

11.2k

113.1k