Jump to content

TheRussian

Members
  • Content Count

    36
  • Joined

  • Last visited

  • Days Won

    1

TheRussian last won the day on May 25

TheRussian had the most liked content!

Community Reputation

1 Neutral

Recent Profile Visitors

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

  1. Hello guys, back to say that everything works good for me on the Kona Ev 64kWh with AutoPi. Only "issue" is that the consumption is over estimated, even when reading the live data from AutoPi: it's usually overestimate consumption of about 10% in a trip where I use 80% SOC. Basically I start from 100%, the trip predicted SOC at the end to be 20% and I finally end up with 30% SOC.
  2. I confirm full functionality of the script now, at least every 30 seconds if not more, good logging, good consumption estimation. Full marks for ABRP with Kona and AutoPi so far. ๐Ÿ‘‘
  3. Thanks Jason, I deactivated your sleep code and now everything works just fine. ๐Ÿ‘
  4. You mean I just need to comment this line? self.manage_sleep() Thanks!
  5. Jason, if I want to remove the additional sleep management that you have in your script, what lines should I remove? It seems like your script sees -0.0003kW (which is clearly a mis-reading, as there's nothing going on) and prevents AutoPi from going to sleep. I've already implemented a robust routine to schedule sleep in another script, so I would just like to remove this feature from your script, without breaking it obviously... ๐Ÿ˜… Is it enough to remove the following? # Manage sleep as the last thing in the script. self.manage_sleep() if self.scripts is not None:
  6. I've just tested it and it seems to work correctly now, updates every few seconds as expected. I'll do some more tests and report back with results! ๐Ÿ˜‰
  7. Here's the last working code: I would still love to get the new PIDs/feature you inserted in latest releases though (odometer, speed, kWh charged, etc.)... ๐Ÿ˜‡ LastWorkingScriptKonaEv.txt
  8. Well, I can send you the code that was actually working for me in the past, if you wish to look for the differences... ๐Ÿ˜… Anyway, I've just reset my AutoPi completely: now the behavior of your last script is that it's only triggered once every minute by the cronjob, so I can confirm that something is not working correctly with the script itself.
  9. The problem is that it's not even updating every 30 seconds, while more than once every 2 minutes... So I wonder if it's really related to that additional part of the script or something else... One more question: In the Kona the flag is_driving is always true except when is_charging is true, correct?
  10. Thanks for the guide, I may try this out later in the week. As of now, the current "Excecution script" has for sure some troubles (at least for me) as it doesn't update on 5 seconds basis during running (but it is basically run by the cronjob every minute), but it actually works fine when charging... I don't have a direct SSH access while running, do you have some other hints to debug or get extra debug data from the web interface?
  11. I'm trying to configure the script as a service, to see if it gets unstuck: can you write down all the AutoPi configuration steps you used for your test?
  12. I'm having a lot of troubles after updating to the new release, but it seems like it's not running at all in AutoPi, so there's nothing really wrong with the code itself: I'll try to figure that out and let you know asap...
  13. Ok, I'm testing the new one and let you know if it works better! ๐Ÿ˜…
  14. I think it has something to do with the is_driving calculation you did for the Kona: if you give me the specific command line to test, I can run it from the web interface while driving and let you know (unluckily I don't have a SSH connection setup while driving, but I can run the commands from the web terminal, no problem). My feeling is that is_driving is not working correctly, so the script runs on the cronjob basis instead, skipping some values when Mobile Data connection is not strong enough.
  15. Actually I have a pretty low number of loggers and just 5 scripts, all very slowly triggered, so I donโ€™t think this is the issue. I donโ€™t know if it is due to the addition of the speed obd query, but now ABRP script runs only once every couple of minutes when driving, while everything is normal during charging. I did a 32 km trip and only got 8 data points in ABRP, while all the data are recorded correctly in AutoPi... Do you have any idea how this is possible and what could cause this issue in your latest script?
×
×
  • Create New...