Code is unstable without BLYNK_PRINT

I created code to run my greenhouse, using a Sparkfun Redboard (UNO clone), CC3000, and Blynk. I am running Blynk 2.8.3 on an iPhone, over the cloud (I’ll start a local RPi server soon). My code reads three DHT22 temp sensors and runs a fan, misters, and a couple of irrigation systems. My Blynk code has a history graph with the temperature, allows full control over the greenhouse systems, and sends tweets when the temperature goes outside of limits. It runs beautifully with the exception of one minor weirdness.

The Arduino code immediately goes unstable unless I have BLYNK_PRINT Serial and Serial.begin activated. If I comment them out, the code hangs. I’ve also tried activating BLYNK_NO_BUILTIN because all I use are virtual pins, and BLYNK_NO_FLOAT because I only transmit integers. This also hangs the code.

Turning the Serial commands on only costs me 3% SRAM, so its not a big deal. But it may become important as I upgrade and tweak the code in the future. So - what gives? Its like it won’t work unless it can sit there muttering to itself.

Cheers,
Q_Mech

Hello. As I know this is common issue with CC3000. Replacing it with more reliable hardware will solve your problem.

Hm. Got any suggestions on the best hardware to use?

Hmm, that sounds like me :wink:

@q_mech Not sure how this would relate to the need for the serial communication, but apparently power is a known issue with the CC3000… needs external power to the hardware, not just the USB.

@Dmitriy is the need for BLYNK_PRINT a specific issue with the CC3000? Or are you just recommending something better because the CC3000 has other issues to begin with?

I ask because since I currently must use USB link with my Arduinos (yes, I know… get something better… in time, but can’t right now :stuck_out_tongue: )… anyhow, I also have to disable BLYNK_PRINT to connect via USB Link. And I do seem to have many strange issues concerning stability that I have yet to track down.

I have to ENABLE the BLYNK_PRINT option to get it to run, not disable. That’s what I find confusing.

I have updated the firmware on my CC3000. I’ll see if that helps. Right now I have it all up and running again but didn’t play with the BLYNK_PRINT toggle.