Under the 2nd part, the full wireless connection: What code should I put into the first radio setup? The one without the BME280. I don't want to set up a Gateway yet. Just want to receive weather from the "remote" node back to the "home" node via radio.
Thank You
I found the sketch I was looking for just a bit further the page.
But now a new problem. Running Serial Monitor at "home" end, I see nothing.
Running Serial Monitor at "sensor" end, I see: Transmitting at 915 Mhz...
SPI FlashMEM not found (is chip onboard?)
What does this mean? Is the Sparkfun Pro mini compatible with Moteino?
Pro mini is no Moteino, it is Arduino, different bootloader. But your question was, is A compatible with B. Well it depends, can be, but this are two different systems. One is just controller, other is controller with RF and flash(or without it). But sketch will run on both. Sensor is set to 915MHZ and you don't have flash on "sensor". Can't say what you have on "home" side of things nor how are "home" or "sensor" configured.
Understand. If I knew about your company a few weeks ago, I would have gotten started with Moteino. Simple Weather Node does work fine as a stand alone with your code and the other parts I mentioned. Thanks for reply.
Sorry, I keep answering myself!
At this time: Stand alone weather node 1st example and your code works fine with non-LowPowerLab parts.
Full wireless weather node 2nd example and your code for non-Gateway for each end setup does not.
Now I get on Serial Monitor from either end Transmitting at 915 Mhz...
SPI FlashMEM not found (is chip onboard?)
Before I got error just from sensor end. Found a problem and fixed.
So, is there a wiring problem I need to correct?
The message implies there is no SPIFlash MEM chip on the Moteino. If you have another board or did not get this option with your Moteino, ignore this message.
The FLASHMEM is for wireless programming and/or datalogging/data storage.
No, Moteino parts, only your software. It's not just the error message, I don't get any weather data from the BME280. No problem with the 1st example of Simple Weather Node. This example is stand alone, not involving wireless. My parts for sensor end: Pro mini, RFM69HCW, BME280. For local end: The same minus the BME280.
Software for local end (no Gateway) is the 3rd script you show for Simple Weather Node. For the BME280 end, the 1st script. I also notice no local node ID or Network ID. I added these lines. Still no work.
You mean "No Moteino parts, only your software." You're running code written for a Moteino on other hardware. You will need to work out whether this will work right down to the lowest hardware level, it'll include pinout differences, external hardware interfacing, default pin states etc.
My suggestion would be to draw the schematic of your hardware and compare directly to the Moteino, make the hardware as identical as possible using the same Moteino pin numbers where you can, and modify the Moteino code appropriately for any differences. For example the Moteino code is looking checking for a flash device, your hardware might have used that chip select pin for something else. The BME280 might be on different pins.
Mark.
Why does your code in the first part of the Simple Weather Node work perfectly as a stand alone example?
Your parts use Moteino and a Moteino Weather Shield. My parts use a Sparkfun Pro mini, and a Sparkfun RFM69HCW, and a BME280 all on a breadboard. Apparently the problem arises when I try to form a network with the other breadboard with same parts except the BME280. This setup uses the SPI and SPIFlash from your libraries. I guess these 2 libraries are for the Arduino environment and not for the LowPowerLab environment. I thought you guys would work together better. Not sure I want to buy any more stuff, for it's all for recreation to learn and not to meet a deadline. I guess LPL knows how to create good gotchas. Not so good for potential customers.
Quote from: donde on July 03, 2018, 04:18:37 PM
I guess LPL knows how to create good gotchas. Not so good for potential customers.
Not sure what the gotchas are, perky explained some significant differences and assumptions you might make. I would appreciate his contributon, in fact - THANKS PERKY and Luka for taking time out of your day to try to help donde.
I2C is the same across all platforms, just 2 pins. Pullups for I2c might be different on different boards but that should not be a worry at common I2C speeds.
As for the RFM69, please watch my latest video about RFM radios and how to use them, i refer more to the software part. That is SPI and requires a bit of care. I designed Moteino to work with RFM69 and other products I make including the BME280 breakouts and it ALWAYS works.
Unfortunately I don't always have the time and energies to try to figure out why other's
HARDWARE don't work with my
SOFTWARE. Ultimately without having detailed details about the boards, how you wire and program them, its just a guess/suggestion game. I don't know what SF is doing these days, but I remember lots and lots of threads and emails in the past about their RFM69 breakouts not working with various dev boards. I only believe it's reasonable for them makers to figure out why, fix it, and talk to their customers. When someone reports a piece of hardware I am making for a living to have a problem with a known working 3rd party library, I try to make it a priority and figure out why, maybe there's a hardware bug I must fix. That's the angle I look at it from. Let me know if you don't find that reasonable. Most customers tend to appreciate the effort that has gone into the already free libraries, to support the hardware I make, and at that point if they care about their time and path to success, perhaps decide to buy something that is known to work. Maybe that doesnt make sense for everyone every time but its what I perceive through feedback from lots of happy customers.
And FWIW I am using the SF library (a git fork) for the BME280 boards, so it should JUST work with their hardware right? ;)
I want to thank and appreciate all the participants to this conversation, at the very least for the
intention to help, but maybe not everyone sees it that way.