Topics created by Anduril

@Anticimex , @Anduril Thanks for this response @evb great job, here is an easy to understand summary for beginners like me. Thanks

@Anduril Well, its all opensource, so you are free to do whatever you want. Just remember that if you are starting to alter the behaviour and use of the security infrastructure, you could potentially compromise it for yourself and those that use your code.

thanks a lot

For this special application I use MyController. In the controller the string is displayed correctly, but in the serial monitor of the node I only see this distorted version (But sending them by sketch works, so it's not a problem of the serial monitor in general). I will ask at the MyController forum, maybe the dev can help.

@Anduril said in receiving numbers bigger than unsigned long: uint64_t value; send(Mymessage.set(&value, sizeof(value) );

@Anduril great that you found the problem. Thanks for sharing the solution, it might help someone else in the future.

@pansen something like that. The value overflows and then gets assigned.

ok so // Select soft/hardware signing method #define MY_SIGNING_SOFT //!< Software signing //#define MY_SIGNING_ATSHA204 //!< Hardware signing using ATSHA204A // SETTINGS FOR MY_SIGNING_SOFT #define MY_SIGNING_SOFT_RANDOMSEED_PIN A0 //!< Unconnected analog pin for random seed should give a good random signing.

here is my solution; add a new udev rules file for permissions: sudoedit /etc/udev/rules.d/50-usb-permissions.rules paste the following in our new rules file: (it gives all permission to any USB* and ACM* devices) KERNEL=="ttyUSB[0-9]*",MODE="0666" KERNEL=="ttyACM[0-9]*",MODE="0666" that's it. this will give you all the permissions to all usb devices on every boot. also you can reload udev instead of rebooting. udevadm control --reload-rules *** please note that this gives permissions to all USB* and ACM* devices. if you're concerned about security you can add the following so that only the mentioned device will be accessable: ATTRS{idVendor}=="XXXX", ATTRS{idProduct}=="YYYY" for example, in my case (output from dmesg): [ 2654.037338] usb 1-1: New USB device found, idVendor=1a86, idProduct=7523 [ 2654.037344] usb 1-1: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [ 2654.037347] usb 1-1: Product: USB2.0-Serial [ 2654.038531] usb 1-1: ch341-uart converter now attached to ttyUSB0 so, for me it's: ATTRS{idVendor}=="1a86", ATTRS{idProduct}=="7523"

@kduino you should go to "Manage palette" and search for mysensors. From there install node-red-contrib-mysensors or you could run npm install node-red-contrib-mysensors

No, you cannot.

Did you check RX and TX channels? My serial to usb converter has the labels already switched (so I have to connect Rx to Rx and Tx to Tx).

@Yveaux thats what I was thinking about. Thanks for confirming.

I found out some part via google, but still some trouble. Maybe someone can help: I have the SDA and SCL connected to GPIO9 and GPIO10 of my nodeMCU (labeled SD2 and SD3). When uploading my normal ESP8266OTA sketch everything works fine and gateway is running. I added the Wire.begin(9,10) at the beginning of setup to set the pins used for I2C. void setup() { Wire.begin(9, 10); //sensor.begin(); ArduinoOTA.onStart([]() { Serial.println("ArduinoOTA start"); }); ArduinoOTA.onEnd([]() { Serial.println("\nArduinoOTA end"); }); ArduinoOTA.onProgress([](unsigned int progress, unsigned int total) { Serial.printf("OTA Progress: %u%%\r", (progress / (total / 100))); }); ArduinoOTA.onError([](ota_error_t error) { Serial.printf("Error[%u]: ", error); if (error == OTA_AUTH_ERROR) Serial.println("Auth Failed"); else if (error == OTA_BEGIN_ERROR) Serial.println("Begin Failed"); else if (error == OTA_CONNECT_ERROR) Serial.println("Connect Failed"); else if (error == OTA_RECEIVE_ERROR) Serial.println("Receive Failed"); else if (error == OTA_END_ERROR) Serial.println("End Failed"); }); ArduinoOTA.begin(); Serial.println("Ready"); Serial.print("IP address: "); Serial.println(WiFi.localIP()); // if (!bmp.begin()) // { // Serial.println("Could not find a valid BMP085 sensor, check wiring!"); // while (1) {} // } //metric = getConfig().isMetric; But as soon as I enable the sensor.begin() or bmp.begin() it's not working anymore. I get resets with the following message in serial monitor: ×Åü1¤ñþ0;255;3;0;9;Starting gateway (RNNGE-, 2.0.0-beta) 0;255;3;0;9;Radio init successful. scandone state: 0 -> 2 (b0) state: 2 -> 3 (0) state: 3 -> 5 (10) add 0 aid 5 cnt connected with WiFi, channel 1 ip:192.168.38.19,mask:255.255.255.0,gw:192.168.38.1 .IP: 192.168.38.19 Ready IP address: 192.168.38.19 ü!m!„þæÊõþ0;255;3;0;9;Starting gateway (RNNGE-, 2.0.0-beta) When using the BMP085test example sketch from the library I get ets Jan 8 2013,rst cause:4, boot mode:(3,7) wdt reset load 0x4010f000, len 1264, room 16 tail 0 chksum 0x0f csum 0x0f ~ld Does anyone knows if that is a problem of incompatible library or any other hint how to solve?

@Anduril

I haven't tried it yet but this plugin for serial monitor over network looks nice https://github.com/esp8266/Arduino/issues/1360

I'm currently in the process of trying to figure out why one of my battery powered nodes isn't working very well with a newly purchased NRF24L01+PA+LNA module. I've shielded it as described in earlier posts. There is plenty of pure power in the batteries. Just as in the case for @pkjjneal it works well only if I'm touching the antenna with a finger. I decided to look inside the antenna: As you see above, it starts with an antenna cable that leads to a half wave dipole (where the antenna element is of about 1/4 wave length) and there is a "sleeve balun" going back over the cable . I can find no ground plane though. The problem that I can see is that the antenna length is 27 mm where it should optimally be 28.8 mm. Now, if I remove the antenna completely my node works quite well. At least better than if I use the original antenna unmodified. If I insert a wire (DIY antenna made by a paper clip) extending 121 mm out of the antenna sockets forming a full wave length antenna things work great. I also modified the original antenna so that the antenna element becomes 28.8 mm. It works a bit better but it's far from perfect and communication errors are shown in the log. As the final test, I added a nice ground plane to the original antenna and now it works really perfect! So what can I learn from this? My test rig is an EasyPCB powered with batteries. I'm quite sure that my NRF24L01+PA+LNA module used in another scenario, for example connected to a Arduino Nano fed by a FTDI connector could actually work. It's because it would create a different environment. The antenna will work in relation to what it's connected to, shielding the grounding, and surrounding objects. Capacitive and inductive reactances are involved in mysterious ways. Anyway. My conclusion is that the two original antennas I have are not working very good. They obviously have the wrong length just a little bit, and I'd say that the the way the antenna is constructed with the sleeve balun and no ground plane, doesn't seem to work well. At least not here. I'll do some more experimenting with making my own antennas. Starting with taking apart an original antenna is not so bad, I can solder anything (solderable) onto the cable. Cheers! From wikipedia: Sleeve balun At VHF frequencies, a sleeve balun can also be built to remove feeder radiation. Another narrow-band design is to use a λ/4 length of metal pipe. The coaxial cable is placed inside the pipe; at one end the braid is wired to the pipe while at the other end no connection is made to the pipe. The balanced end of this balun is at the end where no connection is made to the pipe. The λ/4 conductor acts as a transformer, converting the zero impedance at the short to the braid into an infinite impedance at the open end. This infinite impedance at the open end of the pipe prevents current flowing into the outer coax formed by the outside of the inner coax shield and the pipe, forcing the current to remain in the inside coax.

Sweet! Thanks for the feedback @Anduril .

Here is a recent example: http://forum.mysensors.org/topic/2286/experimenting-with-cheap-433mhz-gadgets

@Anduril said: ok, what is the behavior if there is no ACK coming back? Trying again for several times before discarding the message? How long is the timeout? We are discussing this topic in http://forum.mysensors.org/topic/2189/serial-api-noack-when-sending-with-ack-failed as well. Currently MySensors never resends any messages. You have to program it into your serial application by yourself. It would have to wait for an ACK message and send again, if it didn't come back within time. In the linked thread we are hoping to find a way for implementing this on the hardware of the gateway.

Ok Looked at the code earlier but couldn't find anything wrong.

thanks for the clarification. I'm not going to use the regulator at all, as I'm powering the whole setup with a HLK-PM01 (when it finally arrives).

How did you get it to work?? Could you write a noob tutorial on how it works with bootloaders and how to upload them? I've downloaded the mysensors1.5 zip file, but what are the next steps, how do i get it to show up in arduino sketch and after that what must i change and how do i upload it in my arduino??