@tbowmo said:
I am using exactly that example sketch in my own serial gateway, with 3 empty functions. And it works!
Really? In both directions? You can send from puTTY and the Serial Gateway displays it --AND-- the Serial Gateway sends stuff and puTTY displays it?
That's why I wrote above "code that you can see working on your PC?"
@mfalkvidd said:
- Don't place ads
Seriously? What is that supposed to mean? Are you suggesting I am posting ads about puTTY?
Watching my posts? Seriously, that's great as maybe you can offer some actual help rather than lazy rhetoric.
That's about as "nice" as I can be when I am getting no actual help, just vilification.
IF I am dogin it wrong then PLEASE show me how it should be done.
We appear to be on a merry go round to beat the messenger at each pass. You people need to READ my posts and respond to what I write, not just chest-thump.
I have PC controller software that I have written (professional programmer for 40-years, so I have a few ideas on how things work) and it accesses the Nano via the USB-Serial connection. It sends commands to the network of Smart-Nodes and receives information from the network of Nodes.
It is very much like MySensors but a lot less complicated than MySensors as it is designed to do just one job for one network with a half dozen specific and very-smart Nodes. By Smart-Nodes I mean every Node will keep actively controlling the A/C, heating etc if the power goes out as it frequently does out here in the boonies.
It is working almost perfectly with the RF24network libraries, but after six or so days the network becomes unreliable with occasional data packets not being sent. I have tracked it down to within the RF24network but I do not want to spend days or weeks hunting down the problems and thought I would use MySensors for the networking as I had previously used 1.5 very successfully
I feel it is a waste of any more time as NO ONE has yet shown me how to make the example work WITH 2.) Bear in mind I WROTE ABOVE it worked OK with 1.5 AND the basic Arduino Serial.
Thank you all so much for all that wonderful help.
@tbowmo I have no idea why you mention the W5100 when I am asking about passing data between the PC and Arduino via Serial.
@Anticimex I do not expect that kind of support, I do expect an "example" to actually example something.
The example does NOT handle the Serial to and from the serial port of the PC as it stands. I obviously need to have more in that Serial Gateway than three empty functions. AND YES, I read up on the subject including a few posts here as I mentioned in the OP but nothing seems to get data passing in both directions.
Instead of rhetoric back at me, what about offering up some example code that you can see working on your PC?. I just need a very basic example using puTTY that works in both directions.
Thank you.
@tbowmo said:
You use serial GW, and also handle serial input yourself?
Using several Arduino Nano by the way and nRF24LO1.
In the absence of any instructions for using Serial at all in v2, I am left to guessing how to proceed. I researched here a few days back and questions on Serial gateway for v2 is pretty much ignored.
I ONLY handled serial myself as I could not find any reference to using the Serial Gateway in Examples. It is an appalling "Example" when it has three empty functions. How an Earth can anyone say that code below is an example of anything?
How does it send data via serial to the attached PC?
How does it receive data via serial from the attached PC?
#include <SPI.h>
#include <MySensors.h>
void setup() {
// Setup locally attached sensors
}
void presentation() {
// Present locally attached sensors
}
void loop() {
// Send locally attached sensor data here
}
@AndErn said:
Using the Example SerialGateway like this...
testing here = *nbvbnvbv>
junk nbvbnvbv>
junk bvbnvbv>As you can see characters are getting lost.
How can I work around this
So, no one knows or no one cares. Can't make up my mind as to which it is.
I guess not enough people use the Serial interface for the Dev's to care even to comment. {sigh}
I tested MySensors 1.5 and it seems all OK, so I guess it is a failure of progress.
@Yveaux said:
@AndErn Nope, pipe has nothing to do with channel number.
A different channel number means a different frequency. Channel pipes are all on the same frequency.
OK, thanks, I didn't realize that. In my RF24 setup I am defining the Channel to use in all nodes the Channel so it should be OK then.
I will seek out how to define the Channel for MySensors and stay well away from RF24.
@Yveaux said:
@AndErn run mysensors on a different channel than your existing network and you should be just fine!
Ummmm, thanks, I think...
But in my OP I said, "RF24network uses all 6-Pipes of the RF24" so as I understand it all available "channels" of the radios are taken.
Using the Example SerialGateway like this...
// Enable debug prints to serial monitor
//#define MY_DEBUG
// Enable and select radio type attached
//#define MY_RADIO_NRF24
//#define MY_RADIO_RFM69
// Set LOW transmit power level as default, if you have an amplified NRF-module and
// power your radio separately with a good regulator you can turn up PA level.
//#define MY_RF24_PA_LEVEL RF24_PA_LOW
// Enable serial gateway
#define MY_GATEWAY_SERIAL
// Define a lower baud rate for Arduino's running on 8 MHz (Arduino Pro Mini 3.3V & SenseBender)
//#if F_CPU == 8000000L
//#define MY_BAUD_RATE 38400
//#endif
// Flash leds on rx/tx/err
//#define MY_LEDS_BLINKING_FEATURE
// Set blinking period
//#define MY_DEFAULT_LED_BLINK_PERIOD 300
// Inverses the behavior of leds
//#define MY_WITH_LEDS_BLINKING_INVERSE
// Enable inclusion mode
//#define MY_INCLUSION_MODE_FEATURE
// Enable Inclusion mode button on gateway
//#define MY_INCLUSION_BUTTON_FEATURE
// Inverses behavior of inclusion button (if using external pullup)
//#define MY_INCLUSION_BUTTON_EXTERNAL_PULLUP
// Set inclusion mode duration (in seconds)
//#define MY_INCLUSION_MODE_DURATION 60
// Digital pin used for inclusion mode button
//#define MY_INCLUSION_MODE_BUTTON_PIN 3
// Uncomment to override default HW configurations
//#define MY_DEFAULT_ERR_LED_PIN 4 // Error led pin
//#define MY_DEFAULT_RX_LED_PIN 6 // Receive led pin
//#define MY_DEFAULT_TX_LED_PIN 5 // the PCB, on board LED
#include <SPI.h>
#include <MySensors.h>
void setup() {
// Setup locally attached sensors
}
void presentation() {
// Present locally attached sensors
}
void loop() {
// Send locally attached sensor data here
}
void serialEvent()
{ while (Serial.available())
{ String tStr = Serial.readString();
if (tStr.charAt(0) == '*')
{ Serial.print(" testing here = ");
Serial.print(tStr);
Serial.println(">");
} else
{ Serial.print("junk ");
Serial.print(tStr);
Serial.println(">");
}
}
}
When I send stuff *nbvbnvbv via the Arduino Terminal or my own Serial software I get this...
testing here = *nbvbnvbv>
junk bvbnvbv>
testing here = *nbvbnvbv>
testing here = *nbvbnvbv>
testing here = *nbvbnvbv>
junk nbvbnvbv>
testing here = *nbvbnvbv>
junk nbvbnvbv>
testing here = *nbvbnvbv>
testing here = *nbvbnvbv>
junk nbvbnvbv>
junk bvbnvbv>
As you can see characters are getting lost. If I use the Arduino basic sketch and add the serialEvent to it, I never get dropped characters. I assume MySensors is off checking other stuff and misses the incoming Serial stream.
How can I work around this as I need that '*' as the first character to signify a control string.
How can I give the Serial the first bite at the cherry, always?
I currently have a working network (all using Nano) using RF24 library and my own node software etc. I am having reliability issues after running continuously for 6 or 7 days and I have narrowed it down to the RF24network library.
I have spent way too long trying to resolve the problem and I'd like to try using MySensors but need to keep the current system going as it is working fine as long as I keep an eye on the nodes and reboot as needed.
Can I run Mysensors nRF24 SerialGateway plus an nRF24 test node without affecting the current RF24network? RF24nework uses all 6-Pipes of the RF24, so not sure if this is possible. I can't shut down the RF24network as it is controlling our A/C and while it IS a dry-heat, we still need the A/C running. 