Posts: 42
Threads: 7
Likes Received: 6 in 6 posts
Likes Received: 6 in 6 posts
Reputation:
6
Joined: Dec 2015
Country:
Hi Rob
On my V2 controller after many trial, i managed to get it to 6.4
But on my V1 board I'm also getting the black screen
pi@raspberrypi:~ $ sudo systemctl stop robotank.service
pi@raspberrypi:~ $ cd /var/www/html/cpp
pi@raspberrypi:/var/www/html/cpp $ sudo ./robotank
./robotank: /lib/arm-linux-gnueabihf/libstdc++.so.6: version `GLIBCXX_3.4.26' not found (required by ./robotank)
pi@raspberrypi:/var/www/html/cpp $
Posts: 3,251
Threads: 90
Likes Received: 163 in 120 posts
Likes Received: 163 in 120 posts
Reputation:
184
Joined: Sep 2015
Country:
Hi Fred, another error I don't know about. At one point I had an SD card running an older version of operating system and when I copied the new c++ compiled file it wouldn't load, I had to recompile. Try that and see if it works, use the following four commands.
sudo systemctl stop robotank.service
cd /var/www/html/cpp
g++ -o robotank robotank.cpp `mysql_config --cflags --libs` -lpthread -lquickmail -lcurl
sudo ./robotank
Posts: 42
Threads: 7
Likes Received: 6 in 6 posts
Likes Received: 6 in 6 posts
Reputation:
6
Joined: Dec 2015
Country:
03-22-2022, 10:41 PM
(03-22-2022, 08:09 PM)Rob F Wrote: Hi Fred, another error I don't know about. At one point I had an SD card running an older version of operating system and when I copied the new c++ compiled file it wouldn't load, I had to recompile. Try that and see if it works, use the following four commands.
sudo systemctl stop robotank.service
cd /var/www/html/cpp
g++ -o robotank robotank.cpp `mysql_config --cflags --libs` -lpthread -lquickmail -lcurl
sudo ./robotank That did the trick. It working now
Posts: 3,251
Threads: 90
Likes Received: 163 in 120 posts
Likes Received: 163 in 120 posts
Reputation:
184
Joined: Sep 2015
Country:
Alright, good to know. Any chance you're running a Pi 4?
Posts: 3,251
Threads: 90
Likes Received: 163 in 120 posts
Likes Received: 163 in 120 posts
Reputation:
184
Joined: Sep 2015
Country:
(03-21-2022, 11:14 PM)loksik.lubos Wrote: I tried to reinstall and also without success
I think you may need to recompile the program, use the following four commands.
sudo systemctl stop robotank.service
cd /var/www/html/cpp
g++ -o robotank robotank.cpp `mysql_config --cflags --libs` -lpthread -lquickmail -lcurl
sudo ./robotank
Posts: 42
Threads: 7
Likes Received: 6 in 6 posts
Likes Received: 6 in 6 posts
Reputation:
6
Joined: Dec 2015
Country:
03-23-2022, 02:33 PM
(This post was last modified: 03-23-2022, 02:34 PM by fred73.)
(03-22-2022, 11:01 PM)Rob F Wrote: Alright, good to know. Any chance you're running a Pi 4?
The p4 board worked without much trouble but it's the PI3 that gave me some grief and the errors listed above
Posts: 107
Threads: 18
Likes Received: 15 in 14 posts
Likes Received: 15 in 14 posts
Reputation:
15
Joined: Nov 2019
Country:
so on 6 installation attempts it succeeded
Posts: 3,251
Threads: 90
Likes Received: 163 in 120 posts
Likes Received: 163 in 120 posts
Reputation:
184
Joined: Sep 2015
Country:
Sorry it's been so difficult, it's a learning curve for some of this. I think I know how the last update got screwed up. I had a fresh SD card with bullseye OS variant installed which is what I compiled the program with however previously I was using the Buster OS variant. The program needs to be compiled separately for each of these, I didn't realize that would be the case. I know most of you have Buster as previous updates went ok. So going forward I'm going to still with Buster as it's more reliable than bullseye. If anyone is running Bullseye you will have to reinstall OS using Buster otherwise this will always be a problem. For the initial install I'm going to look at using an image file instead so it's not a confusion.
Posts: 8
Threads: 0
Likes Received: 1 in 1 posts
Likes Received: 1 in 1 posts
Reputation:
1
Joined: Mar 2022
Country:
03-30-2022, 10:14 PM
(This post was last modified: 03-30-2022, 10:17 PM by zedron.)
I cant get 6.4 to work at all. I've tried to reinstall it multiple times, recompile based on above recommendations, reflash with Bullseye and Buster. Start with 6.3 then go to 6.4, start with 6.0 then go to 6.4. All get a black screen. Tried numerous browser, different devices to connect with.
The Update feature in the GUI for 6.3 doesn't seem to do anything either.
The one time I got 6.4 loaded was from a fresh install with a fresh flash but I couldn't change any settings. I went into settings, selected my board (v2) set my time format, temperature (even though I did this upon fist logon), software asked to reboot so I click yes and the window never went away. I manually refreshed and all the settings were back to what they were originally.
Looks like I am going back to Reef-Pi.
Code: Hello World
startupI2C --------------------------------
i2cTotalProbes = 0
i2cTotalPca9685 = 1
i2cTotalSaved = 2
i2cID[a] = 326
i2cDeviceTypeID[a] = 2
i2cDriverID[a] = 3
i2cDecAddress[a] = 64
i2cEnabled[a] = 1
i2cID[a] = 61
i2cDeviceTypeID[a] = 0
i2cDriverID[a] = 1
i2cDecAddress[a] = 112
i2cEnabled[a] = 0
Scanning I2C BUS -
startupRTC --------------------------------
rtcAddress = 0
rtcEnabled = 0
timeFormat = 0
RTC Not Found = 0
-currentMillisTime - 1648700169616
-midnightMillis - 1648699200000
-nextMidnightMillis - 1648785600000
currentWeekday - 4
-currentMillisTime - 1648700169616
startupController-------------------------
prevControllerVersion - 0
controllerVersion - 0
startupEmails------------------------------
emailEnabled---------- 0
smtpServer------------ smtp.office365.com
smtpPort-------------- 587
smtpUser--------------
adminEmail------------ xxxxxx@gmail.com
recipient1------------ xxxxxx@gmail.com
recipient2------------
recipient2Enabled----- 0
recipient3------------
recipient3Enabled----- 0
----------------------------------------
startupPCA9685 --------------------------------
pca9685TotalPins = 16
pca9685totalEnabled = 1
pca9685I2Cfile = 6
pca9685Address = 64
pca9685DriverID = 3
input = !▒▒▒▒
input =
input = !
input =
frequency = 524296
startupACoutlets------------------------------
outletTotal------- 0
----------------------------------------
startupDCports------------------------------
dcTotal------- 0
----------------------------------------
startupDosing------------------------------
dosePinID------------
doseDriverID---------
dosePin--------------
doseAmount-----------
doseReservoirRemain--
doseReservoirSize----
dosePumpRate---------
doseStirrer----------
doseCalibrateAmount--
doseRunTime----------
dosesRemaining-------
doseInterval---------
totalDosers------------ 0
----------------------------------------
startupDHT22------------------------------
dht22Count - 0
----------------------------------------
startupSensors------------------------------
sensorTotal - 0
----------------------------------------
startupProbes-----------------------
probesSaved - 0
probeCount - 0
startupProbes Complete-----------------------
readLightModes--------------------------------
totalLightModes - 0
totalChannels - 0
channelPinID -----
totalModesPerChannel
modeID ------------
modePinID -----------
modeEnd -------------
modeEndLevel --------
modeEnabled----------
readSchedules--------------------------------
totalSchedules - 0
scheduleID -----
scheduleName -----
scheduleTypeID -----
scheduleRuleID -----
schedulePinID -----
scheduleOffOn -----
scheduleStart -----
scheduleSun -----
scheduleMon -----
scheduleTue -----
scheduleWed -----
scheduleThu -----
scheduleFri -----
scheduleSat -----
scheduleRepeatDays --
scheduleEnabled -----
scheduleEmail -----
scheduleAlert -----
scheduleCreated -----
nextScheduleTimeStamp -
nextUpcomingSchedule - 0
nextUpcomingID - 0
startupRules------------------------------
totalRules ---------- 0
totalSensors -------- 0
totalEquipment ------ 0
ruleID ------------
ruleName ----------
typeID ------------
email ---------------
alert ---------------
enabled -------------
sensorRuleID --------
sensorPinID ---------
sensorAddress -------
sensorDataType ------
sensorValue ---------
sensorLessGreater ---
sensorStability -----
sensorLogic ---------
sensorPinTypeID -----
equipRuleID ---------
equipPinID ----------
equipPinTypeID ------
equipOffOn ----------
equipSwitchDelayMil -
equipNextDoseDelay --
----------------------------------------
supportID - 1294255670
startupComplete - 1
startupComplete - 499830
-currentMillisTime - 1648700169666
ds18b20Startup-------------------------
ds18b20Saved = 0
ds18b20Count = 1
Posts: 8
Threads: 0
Likes Received: 1 in 1 posts
Likes Received: 1 in 1 posts
Reputation:
1
Joined: Mar 2022
Country:
03-31-2022, 09:06 AM
(This post was last modified: 03-31-2022, 09:06 AM by zedron.)
Well, I decided to give it one more try this AM. I did a fresh install last night of 6.4 and still had the issues where nothing saved and was just acting weird. I investigated a little bit and saw there were errors related to the "quickmail" library. I went ahead and installed 6.4 again over the current install and like magic everything seems to be working now. PH probe, Temp sensors, float switches, and dosing pumps seem to be all working.
Posts: 3,251
Threads: 90
Likes Received: 163 in 120 posts
Likes Received: 163 in 120 posts
Reputation:
184
Joined: Sep 2015
Country:
Hi zedron, glad you got it running, sorry it's not so smooth yet. That quickmail error was something I just came across as well, I'm not sure why it decided to act up.
Make sure you test everything you plan to run and monitor it closely the first few days, everything is still in beta testing. It's working pretty good but could be some bugs still. I'm going to have a nice update this weekend or shortly after which includes basic logs so a person can verify any actions taken, that should help with the testing.
Thanks for giving it a whirl.
Posts: 8
Threads: 0
Likes Received: 1 in 1 posts
Likes Received: 1 in 1 posts
Reputation:
1
Joined: Mar 2022
Country:
Yeah no problem Rob. Always willing to try new stuff.
Schedules are not saving for me. Not sure why since there are no logs. I create a simple On schedule for a CO2, save. and nothing appears in the list of schedules. I checked the SQL database int he schedule table and its empty.
Posts: 3,251
Threads: 90
Likes Received: 163 in 120 posts
Likes Received: 163 in 120 posts
Reputation:
184
Joined: Sep 2015
Country:
I just did a test and experiencing same thing, I should have a solution in 10 minutes hopefully.
Posts: 3,251
Threads: 90
Likes Received: 163 in 120 posts
Likes Received: 163 in 120 posts
Reputation:
184
Joined: Sep 2015
Country:
Looks like I broke it when I added the RTC. Month changed from 1-12 to 0-11 so it was trying to add feb 31 as date created which obviously isn't valid. You installed at a perfect time, if it was mid month I wouldn't have realized and data would be wrong. Not serious but not good.
Anyways to fix open the /var/www/html/cpp/rtc.h file using Nano or whatever.
Go down to line 44 which should be this.
short rtc::getCurrentMonth() {return currentMonth;} // get currentMonth
Change that line to the following
short rtc::getCurrentMonth() {return currentMonth + 1;} // get currentMonth
Then recompile the code but first stop robotank.service.
sudo systemctl stop robotank.service
cd /var/www/html/cpp
g++ -o robotank robotank.cpp `mysql_config --cflags --libs` -lpthread -lquickmail -lcurl
sudo ./robotank or sudo systemctl stop robotank.service
Posts: 8
Threads: 0
Likes Received: 1 in 1 posts
Likes Received: 1 in 1 posts
Reputation:
1
Joined: Mar 2022
Country:
03-31-2022, 10:09 AM
(This post was last modified: 03-31-2022, 10:12 AM by zedron.)
That did the trick. The joys of beta testing.
Thanks.
-Will
EDIT: Once a schedule is created I am unable to edit it or delete it. The changes dont take effect.
Posts: 164
Threads: 12
Likes Received: 14 in 14 posts
Likes Received: 14 in 14 posts
Reputation:
14
Joined: Oct 2021
Country:
maybe even currentWeekday starts from 0 ?
Posts: 3,251
Threads: 90
Likes Received: 163 in 120 posts
Likes Received: 163 in 120 posts
Reputation:
184
Joined: Sep 2015
Country:
Hmmm, I'm able to edit and delete. What is the exact schedule you set?
Gandalf could try if your able to? I will have to look into the currentWeekday to make sure but that won't relate to this. That's only used once while calculating the next schedule so if wrong it would trigger different day then should.
Posts: 8
Threads: 0
Likes Received: 1 in 1 posts
Likes Received: 1 in 1 posts
Reputation:
1
Joined: Mar 2022
Country:
Everything stopped working again so I restarted the Pi and it came back. Controller icon was in the red and had the disconnected icon, date was December 1969, nothing saved. All sensors showed NaN values.
Posts: 3,251
Threads: 90
Likes Received: 163 in 120 posts
Likes Received: 163 in 120 posts
Reputation:
184
Joined: Sep 2015
Country:
Sounds like the program isn't starting, try recompiling the startup.cpp file.
sudo systemctl stop robotank.service
cd /var/www/html/cpp
g++ -o startup startup.cpp `mysql_config --cflags --libs`
Then power cycle the controller.
Posts: 8
Threads: 0
Likes Received: 1 in 1 posts
Likes Received: 1 in 1 posts
Reputation:
1
Joined: Mar 2022
Country:
Done.
Schedules dont seem to work, atleast with the AC outlet I am trying to control. I created a schedule to turn off my CO2 regulator and it didnt do anything. The AC port is in auto mode (no red dot). Same applies for turning it on via a schedule.
Both On and Off schedules were set for a time now to test and repeat every 1 day.
|