Navigation

    • Register
    • Login
    • OpenHardware.io
    • Categories
    • Recent
    • Tags
    • Popular
    1. Home
    2. n1ck1355
    3. Posts
    • Profile
    • Following
    • Followers
    • Topics
    • Posts
    • Best
    • Groups

    Posts made by n1ck1355

    • RE: Battery powered PIR

      Hi 🙂
      does anyone know where i actually find the FT531IA? on aliexpress there are only FT531EA with output of 2.5V 😞

      posted in Hardware
      n1ck1355
      n1ck1355
    • RE: Is it worth building accurate sensors?

      what? a simple ds18b20 (only temp sensor) cost <1$..
      i belive that the sensors with hum are also not quite expenive

      posted in Hardware
      n1ck1355
      n1ck1355
    • RE: Mi-Light controller for Mysensors

      @Nca78 :

      did you have success with thw NRF boards connecting?

      posted in My Project
      n1ck1355
      n1ck1355
    • RE: Mi-Light controller for Mysensors

      Thank you @ted 🙂
      i already played with it and can turn the bulbs on/off. i will play around with your
      information to make the other funktions work.

      But what i see is that you cannot e.g. dim the bulbs softly from say 100% to 20% cause
      that would be more commands behind each other. But the node must reset itself after
      each command by calling _Begin() and that takes some time..
      any suggestions to resolve that?

      posted in My Project
      n1ck1355
      n1ck1355
    • RE: Mi-Light controller for Mysensors

      that's really great 🙂 Thanks!

      posted in My Project
      n1ck1355
      n1ck1355
    • RE: Mi-Light controller for Mysensors

      @ted are you there and can get a hint please? 🙂

      posted in My Project
      n1ck1355
      n1ck1355
    • RE: Mi-Light controller for Mysensors

      @Jason-Brunk
      unfortunately i havnt got my own milight bulbs but for what i've seen on the
      reverse engineered protocol page the payload must be something like
      "07B0F2EA359001B9ACF9" for all on or
      "07B0F2EA7D910FD4EC72" for green

      or the part "07B0F2EA" must be the ID so the payload
      is somethink like "359001B9ACF9" for all on and
      "7D910FD4EC72" for green

      posted in My Project
      n1ck1355
      n1ck1355
    • RE: MYSBootloader 1.3 pre-release & MYSController 1.0.0beta

      @Mickey :
      It's the same problem i've posted about 4 months ago here.. i also cant run sketches i've uploaded via serial..
      i hope it is solved with a new release...maybe the final already @tekka?

      posted in Development
      n1ck1355
      n1ck1355
    • RE: MYSBootloader 1.3 pre-release & MYSController 1.0.0beta

      any news about 1.3 final release?

      posted in Development
      n1ck1355
      n1ck1355
    • RE: MYSBootloader 1.3 pre-release & MYSController 1.0.0beta

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

      posted in Development
      n1ck1355
      n1ck1355
    • RE: MYSBootloader 1.3 pre-release & MYSController 1.0.0beta

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

      posted in Development
      n1ck1355
      n1ck1355
    • RE: MYSBootloader 1.3 pre-release & MYSController 1.0.0beta

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

      posted in Development
      n1ck1355
      n1ck1355
    • RE: MYSBootloader 1.3 pre-release & MYSController 1.0.0beta

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

      posted in Development
      n1ck1355
      n1ck1355
    • RE: MYSBootloader 1.3 pre-release & MYSController 1.0.0beta

      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.

      posted in Development
      n1ck1355
      n1ck1355
    • RE: MYSBootloader 1.3 pre-release & MYSController 1.0.0beta

      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 😉

      posted in Development
      n1ck1355
      n1ck1355
    • RE: no connection with GatewayW5100MQTTClient

      ok i got it.. i don't know why but i reuploaded the sketch und bam...it works 🙂

      posted in Troubleshooting
      n1ck1355
      n1ck1355
    • no connection with GatewayW5100MQTTClient

      Hi Folks, glad to be here 🙂

      I have a problem with the Connection of the WZ5100 Ethernet Module and the
      GatewayW5100MQTTClient example sketch from the devel branch.
      I use the NRF24L01+ Radio Module.
      As I understood it is not necessary to change the myconfig.h or the example sketch to use softspi as it's on by default? Nor
      it is necessary to define a MAC cause it is by default deadbeeffeed?
      I tried it for one run and then used the original myconfig.h without modifications.
      Another Question: the Pins 14,15,16 for the SOFTSPI are the analog pins on the ATMega? caouse on an Arduino Uno there aren't digital pins beyond 13.

      I'm using a seperate ATMega328 with 8Mhz Clock and 3.3VCC and wired it according to
      http://www.mysensors.org/build/ethernet_gateway where i used the pin mapping from here:
      http://www.jameco.com/Jameco/workshop/JamecoBuilds/arduinocircuit_fig12.jpg. Sketch compiles fine on Arduino 1.6.7. But Serial Output gives:

      0;255;3;0;9;Starting gateway (RNNGA-, 2.0.0-beta)
      0;255;3;0;9;Radio init successful.
      0;255;3;0;9;Init complete, id=0, parent=0, distance=0
      0;255;3;0;9;Attempting MQTT connection...
      0;255;3;0;9;Attempting MQTT connection...
      0;255;3;0;9;Attempting MQTT connection...
      0;255;3;0;9;Attempting MQTT connection...
      0;255;3;0;9;Attempting MQTT connection...
      0;255;3;0;9;Attempting MQTT connection...

      next i checked all wires, remove mysensors library and redownloaded and installed it again. Compiled and uploaded -> no change.
      then i deinstalled the library and also the Arduino IDE and installed IDE version 1.6.5 and installed mysensors devel library again.
      compied and uploaded -> no change..

      then i realized that on the WZ5100 board the only leds tx, power and sometimes another (i don't remember which) blinks.
      so i changed the overall VCC to 5V and a voltageregulator to 3.3V before the Radio. now the WZ5100 comes up with almost all leds and i got also a link. but still no connection to MQTT broker nor a overall network connection

      so i'm off...has anyone a clue? it would really nice 😉

      btw: can the WZ5100 module powered from 3.3V?

      posted in Troubleshooting
      n1ck1355
      n1ck1355