Jump to content

vag

Members
  • Posts

    28
  • Joined

  • Last visited

Reputation

0 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi again, After having reinstalled the Autopi, there was also an update pushed out on 1st of October that I launched too. Since then, I made a trip of about 100 Km go & return without any issue. Hopefully, the problem was from the Autopi unstable state. Nevertheless, The problems that I had were during a longer trip (about 1000 km) and they started after about 300 km. So I need to check again when I'll have to drive far, but for the moment it operates without issues. Thank you.
  2. Hi, the Autopi was finally completely blocked and was not booting up. I had to reflash it from scratch. Now it works again, the debug=true is configured in the kwargs, but performing: sudo tail -f /var/log/salt/minion | grep ABRP doesn't outputs anything on the screen.
  3. Yes, I downloaded it at least 3 times and saved it in the Autopi, the restarted everything etc. The the result is still the same. The best that I could had lastly was to have it operating only randomly.
  4. I have a problem using that last version of the script: I installed it about 2 weeks ago and went for a trip of about 1000km. After 350Km it stopped updating. I restarted the Autopi etc and didn't worked back again except after a few days. Actually the script doesn't updates ABRP anymore, while other scripts on the Autopi operate very well, like previously. The same behavior happens on a friend's Kona that has the same config like me. I commented out the sleep line self.manage_sleep() but this didn't changed anything. Any idea of what this problem could be?
  5. Ok, I'll try that and let you know
  6. @Jason (ABRP) of course I can give a try. Is this included in the actual version of your script from here?: https://github.com/iternio/autopi-link/blob/master/my_abrp.py
  7. @Jason (ABRP) After the last AutoPi update from 27/05/2020, the script seems to work correctly, even during very short trips. This means that until now and after several tests, I didn't encountered the problem that we had before. The only thing that I noticed, is that from time to time, when the car is OFF, it shows the "charging" sign, while it is not powered to any charger. This is occasional. Maybe a badly interpreted state?
  8. The zombie state idea sounds like a good path to follow, especially because the AutoPi wakes up every 3 hours, as it is configured actually, so even without using the car, the ABRP script should have at least one update within this interval. But this is not the case.
  9. @Jason (ABRP) After having changed the pid, I can confirm you that it works on the Kona like before.
  10. @Jason (ABRP) Today i tried something to see if the AutoPi wakes-up well on the car power-on. For this I used a power-on trigger that sends me an e-mail when the system boots. So this morning I received it at 7:45, when I powered on the car which is normal. On the other side, the last update that I have on ABRP is dated from yesterday, at 21:17, which is the time when I powered off the car (yesterday). The above means that the AutoPi starts well when the car is ON and powers down correctly when the car is OFF. The script doesn't starts on the same time than the AutoPi. I hope this can help you.
  11. @Jason (ABRP) Thank you for this new version. I uploaded your new version to the car. The script works like previously and the delay is still there. For small distances with the car (about 2km in the city: taking approximately 5-6 minutes with the parking), it doesn't has the time to send the data to ABRP.
  12. Hello @TheRussian, It is indeed a bit too slow at the startup, I don't see exactly why, but the script works well. You need to let it work for a few days in order to better estimate if it works or not. Hopefully we'll find out why soon.
  13. Hi @TheRussian, In the attached picture you have everything you need to make the script work: Variable items that depend on your setup: Name: is the name of the job, put something that reminds you what that job does Function: This is the name of the script, as you saved it in "Advanced" -> "Custom Code" AutoPi screen/menu. The first part is the exact name that you setup in the custom code script creation (I have set my_abrp_iternio) and here you must add the ".tlm" part (at the end of the script's name) Kwargs: Your own token as you see it in my example (replace the xxxxxx...) and at the next line the Kona car_model, exactly like you see it here above. All the rest must be exactly like on the picture here above. You save the cron job and you synchronize it with the AutoPi. After a while, it should start to send data to ABRP. Sometimes, and I don't know the reason why, it takes a little long to start sending the data. But it definitely works.
  14. The AutoPi doesn't takes that long to boot and we can see this by checking its web interface after power on, for instance. So I don't think that the delay could come from that. Anyway, this would be of course a nice improvement, but the script works perfectly for the rest. All in all, having the online info uploaded for very short distances is not that necessary.
  15. Yes, the job is configured to run once every minute and only one job may run at a time. I have some more and positive info: I reality, it needs to run for a while in order to provide the data to ABRP. Because of the actual pandemic limitations, driving a car is only possible for very small distances and this was apparently not always enough to get the data. So I can confirm that the script definitely works, but we need to drive for a few Kms in order to have the results online. Thank you Jason 🙂
×
×
  • Create New...