Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Problem reboot with robotank
#1
    Hello Rob ! It’s been several times, robotank reboot Alone. I can’t see on Log « reboot manually »
But when restart, the dc port stay off. It’s unfortunate because all my material no restart. 
When i stop rpi my materials work because i plug relay normaly Closed (when there is no currant on command my materials work)
A try to restart rpi manuelly, when it stop, dc port work but when robotank Goes into services dc port stop. My dc port are settled on inverted. Robotank do not remember dc port settings.
Do you have an idea ?

It has been working since march but it’s been 2-3 reboot this last month
Reply to top
#2
Hi, thanks for reporting this and sorry it happened. At this time whenever the controller is started up it'll be logged as a manual reboot so a little hard to determine what caused it. I just did a quick look and the reboot function is only run when updating or changing sensor ports to control DS18B20. I'm guessing it's nothing to do with a power outage? Now a days people don't have clocks to know if power went out.

Not sure if I understand correctly, after you reboot the controller you need to go back into settings and set the "inverted" option again before it will work correctly?
Reply to top
#3
Hi, there was another reboot this night. It’s only robotank. No reboot rpi. It’s not a power outage. No,the settings option ´inverted’ stay well. Just the control buttons are ´off’, not green. I just have to press all the buttons to turn the devices back on. Ato is ok. everything has been working fine since 3 month.
When robotank reboot,it doesn’t go through the page auto logout, direct control page.
I will try to disable sensor ports to control DS18B20, the probe may be faulty.(the displayed temperature looks correct). excuse me for my english. Thanks for your help
Reply to top
#4
Very strange, am I correct there are two separate issues?

1. When the controller reboots the DC ports aren't going in the correct mode? Even if the controller didn't auto reboot this would still be a problem on a manual reboot?
2. After 3 months the controller is now randomly rebooting, after it reboots it does start up again but you then run into problem 1 with the DC ports?

I forgot to mentioned about the log, the ATO custom rule to turn off the pump runs a lot and I don't see any entries saying it turned on, has that always been the case?

For the reboot it's sounding like the program is crashing, if that happens the Pi service file will attempt to start the program again after 3 seconds which would explain why it comes back online. Can you think of any changes you might have made just before this started happening? I'm thinking a variable is receiving bad or unexpected data which could crash the program.

Can you run the program in a manual mode so we can see if it is crashing. Run the following 3 commands in the Pi SSH terminal. Take note that if you close the SSH terminal or it loses connection the program will stop running.

sudo systemctl stop robotank.service

cd /var/www/html/cpp

sudo ./robotank

After the 3rd command you'll see a bunch of startup data load and the program should be running. If it crashes the SSH terminal will likely says "segmentation fault".
Reply to top
#5
hi rob, yes when the controller reboots the DC ports aren't going in the correct mode. i don't change anything.
after 3 commands :

startupI2C --------------------------------
i2cTotalProbes          = 1
i2cTotalPca9685        = 1
i2cTotalSaved          = 5
i2cID[a]            = 2
i2cDeviceTypeID[a]  = 2
i2cDriverID[a]      = 3
i2cDecAddress[a]    = 64
i2cEnabled[a]      = 1

i2cID[a]            = 3
i2cDeviceTypeID[a]  = 0
i2cDriverID[a]      = 1
i2cDecAddress[a]    = 87
i2cEnabled[a]      = 0

i2cID[a]            = 4
i2cDeviceTypeID[a]  = 1
i2cDriverID[a]      = 1
i2cDecAddress[a]    = 99
i2cEnabled[a]      = 1

i2cID[a]            = 5
i2cDeviceTypeID[a]  = 0
i2cDriverID[a]      = 4
i2cDecAddress[a]    = 104
i2cEnabled[a]      = 1

i2cID[a]            = 1
i2cDeviceTypeID[a]  = 0
i2cDriverID[a]      = 1
i2cDecAddress[a]    = 112
i2cEnabled[a]      = 0

Scanning I2C BUS -

startupRTC --------------------------------
rtcAddress      = 104
rtcEnabled      = 1
timeFormat      = 0
RTC Found            = 104

-currentMillisTime  - 1658330937000
-midnightMillis    - 1658268000000
-nextMidnightMillis - 1658354400000
currentWeekday      - 3
-currentMillisTime  - 1658330937000

startupController-------------------------
prevControllerVersion      - 0
controllerVersion          - 0

startupEmails------------------------------
emailEnabled---------- 0
smtpServer------------ smtp.office365.com
smtpPort-------------- 587
smtpUser--------------
adminEmail------------ tutuss@free.fr
recipient1------------ tutuss@free.fr
recipient2------------
recipient2Enabled----- 0
recipient3------------
recipient3Enabled----- 0
----------------------------------------

startupPCA9685 --------------------------------
pca9685TotalPins        = 16
pca9685totalEnabled    = 1
pca9685I2Cfile    = 7
pca9685Address    = 64
pca9685DriverID    = 3

input            = !▒▒▒▒
input            =
input            = !
input            =
frequency              = 524296

startupACoutlets------------------------------
gpio AC outlet - 6 - 10 - 2 - 1
gpio AC outlet - 19 - 23 - 2 - 0
gpio AC outlet - 21 - 25 - 2 - 0
gpio AC outlet - 10 - 14 - 2 - 0
gpio AC outlet - 18 - 22 - 2 - 0
gpio AC outlet - 5 - 9 - 2 - 0
gpio AC outlet - 11 - 15 - 2 - 0
outletTotal------- 7
----------------------------------------

startupDCports------------------------------
gpio DC port - 39 - 15 - 3 - 0
dcTotal------- 1
----------------------------------------

startupDosing------------------------------
dosePinID------------
doseDriverID---------
dosePin--------------
doseAmount-----------
doseReservoirRemain--
doseReservoirSize----
dosePumpRate---------
doseStirrer----------
doseCalibrateAmount--
doseRunTime----------
dosesRemaining-------
doseInterval---------
totalDosers------------ 0
----------------------------------------

startupDHT22------------------------------
dht22Count    - 0
----------------------------------------

startupSensors------------------------------
gpio input    - 13 - 2 - 17 - 8
gpio input    - 23 - 2 - 27 - 8
sensorTotal        - 2
----------------------------------------

startupProbes-----------------------
probeAddressSaved      - 99
probeAddress            - 99
probesSaved            - 1
probeCount            - 1
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 ---------- 3
totalSensors -------- 3
totalEquipment ------ 3
ruleID  ------------ 1, 2, 5,
ruleName  ---------- ato start, ato stop, stop ecumeur,
typeID  ------------ 2, 2, 2,
email --------------- 0, 0, 0,
alert --------------- 0, 0, 0,
enabled ------------- 1, 1, 1,
sensorRuleID -------- 1, 2, 5,
sensorPinID --------- 23, 23, 13,
sensorAddress ------- , , ,
sensorDataType ------ 0, 0, 0,
sensorValue --------- 0, 1, 1,
sensorLessGreater --- 1, 0, 0,
sensorStability ----- 1, 1, 1,
sensorLogic --------- 0, 0, 0,
sensorPinTypeID ----- 8, 8, 8,
equipRuleID --------- 1, 2, 5,
equipPinID ---------- 39, 39, 18,
equipPinTypeID ------ 2, 2, 1,
equipOffOn ---------- 1, 0, 0,
equipSwitchDelayMil - 1, 1, 1,
equipNextDoseDelay -- 0, 0, 0,
----------------------------------------
supportID          - 685919447
startupComplete    - 1
startupComplete    - 195415839
-currentMillisTime  - 1658330937071



path = /var/www/html/chartData/p99.csv
data = 2022/07/20 17:28:58, 8.398000


ds18b20Startup-------------------------
address      = 012042ed7deb
searchID    = 4294967295
ds18b20Saved    = 1
ds18b20Count    = 1

the error seems to be dated july 4. the ato work well before but after july 4, ato turn off all the time
   

my ato
   

normal running. dc port are green and pump work. when reboot dc port become gray and stay off
   

i think a problem ato but it still work. i looked in the log months back, from time to time robotank reboot but the dc port going in the correct mode after. something must have happened
thanks for your attention


Attached Files Image(s)
   
Reply to top
#6
Hmm, very interesting, I've been thinking about this and wondering if maybe you have the RTC enabled and it's causing strange behavior. If you do have it enabled try disabling it.

Run those 3 commands again, after the 3rd command leave the SSH terminal open. New lines will appear as some actions occur, check on it occasionally to see if it crashes. The SSH terminal will show the following again if it does crash.

pi@robotank:/var/www/html/cpp $
Reply to top
#7
Hi rob ! After make your instruction, robotank seems to work. No reboot since yesterday. Ato work normaly. I don’t unplugged rtc for the moment

   

   

I don’t Know what happen
Reply to top
#8
Hmm, I don't know what to think. Have you been running the program via the SSH terminal or using the Pi service file to run it?

What I had you do didn't really do anything, I see in the log you put all outlets in manual mode then back to auto mode I wonder if that had something to do with it although the custom rule is DC port so doesn't really make sense. Make sure to monitor it closely.
Reply to top
#9
Hi Rob ! It’ s not working a long time. Not a reboot but ato start Again to works badly.
I use the ssh terminal for running the program. when i come back to the pi, it was blocked (red plugged) so i restart pi and back to auto mode and it work normally.
I don’t try to disable rtc, i will do it. You can see it was a problem at 00h33
   
Reply to top
#10
Yeah do disable the RTC, I was doing something a little wonky with milliseconds which could be the issue.

Can you use the SSH terminal again to run the program (make sure to stop the robotank.service first) and this time if it crashes (red plug) send a picture of the SSH terminal.
Reply to top
#11
Hi Rob ! I did several tests. I have two problems. Problem restart ac outlets and problem Ato
I unplugged rtc, no change. That’s not What’s Wrong.
 When raspberry is off, ac outlets stay « on » but when restart,ac outlets becomes « off ».

When i put rules Ato to « off » the log is normally. Not turn off every second
   
As you can see on my log, i put ac outlets, turn on and resume auto mode. But when i restart raspberry ac outlets is off.
Ato works but it displays unnatural.(turn off every second)
When i restart
   
My rules Ato
   
Reply to top
#12
Hi tutuss21, thanks for the details, I will see what I can find.
Reply to top


Possibly Related Threads…
Thread Author Replies Views Last Post
  Problem with 6.5 tutuss21 11 3,972 09-30-2022, 07:42 PM
Last Post: Rob F
  Problem with v6.4 tutuss21 8 3,661 03-25-2022, 09:36 PM
Last Post: Rob F
  Robotank V6 issues fred73 12 9,542 12-05-2021, 05:50 PM
Last Post: Rob F
  Robotank v6 - can not save any schedule kukulin 5 3,095 11-07-2021, 09:44 AM
Last Post: Rob F

Forum Jump:

Current time: 04-23-2024, 08:10 AM