Jump to content

PaulS

Members
  • Content Count

    33
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by PaulS

  1. If anyone has Torque Pro (I don't) and wants to give things a try, here's an initialisation sequence I've extracted from Deep OBD. "AT D\nAT E0\nAT PP 2C OFF\nAT SH 6F1\nAT CF 600\nAT CM 700\nAT PB C0 01\nAT SPB\nAT AT0\nAT ST FF\nAT AL\nAT H1\nAT S0\nAT L0\n" I can't be sure it'll work for Torque, but I now have Deep OBD working and can log data to SD card. @Jason (ABRP) is there any way to use off-line data logs?
  2. It's not there (yet, hopefully).
  3. Go to an IONITY charger and click on it. You'll get the same menu again.
  4. Description: In the same way that we currently have preferences about which networks to use, I would like to see a preference to use sites that have more than one appropriate (CCS, Chademo, Tesla) charger. Use Case: In the process of planning a cross-Europe trip in a CCS car, I found that a lot of the stop were at sites with only one CCS connector. As it's an area I'm not familiar with I'd feel a lot more comfortable if it was preferring larger sites so that a failure is less likely to be catastrophic. Maybe this is something you can switch on in the settings, or maybe just have a static weighting based on the number of chargers at a site.
  5. I think it's a problem with how the data is being imported for them. It effects a couple of networks where OpenChargeMap is importing their data from the Department for Transport database. I theory, going on to Open Charge Map and marking them as "Status: Operational" should make them start to appear. That said, I've done it with one near me and it's not changed yet (on OCM).
  6. Looks like everything on the Geniepoint network is marked as "Status: Unknown" in Opencharge map. This is because they've been imported from the Department for Transport database rather than being from the network provider. I think this is true for Engenie as well. There's a large number of rapid chargers in this state in the UK. I can understand these being filtered out, but it does leave some holes in certain areas like Cornwall. Screenshot of OCM with CCS chargers with uknown status highlighted.
  7. Ok, so any chance you'll share the initialisation sequence. Then we could look at using Torque to send live data.
  8. Click on one of their chargers and select "Prefer or avoid Smatrics chargers". Choose "Never use" and re-route.
  9. PaulS

    Save calculated route

    As a work around, you can hit the share button and open the route in google maps. As long as you've got less than about 10 stops it sends everything over as calculated.
  10. Tesla CCS is only usable by Teslas. Don't worry too much about pre-selecting which chargers to use. The whole point is that ABRP chooses the chargers that get you there quickest. If a quick stop at a lower speed charger saves you a big diversion for a high speed charger it can work out quicker.
  11. Oooh. I quite like the look of the vector maps.
  12. Where? Did you mean to have a link?
  13. I was trying to get ABRP to plan a trip around Scotland following the route of the North Coast 500. Now obviously it's a scenic route, so it's needed quite a few waypoints to get it to follow it, but it's doing some very strange things. https://abetterrouteplanner.com/?plan_uuid=f987e61f-8ffd-406b-b467-a765ee12f160 Specifically On the section between Durness and Drumbeg, it drives past the turning for Drumbeg (at about 80% SoC, as it just charged), on to Ullapool and charges at Latheron Lane, then doubles back on itself to go to Drumbeg reaching the turning at around 60% SoC. It's done an extra 60 miles to lose 20%. It does something similar between Applecross (Where I've manually charged at a campsite) and Loch Dughaill, making a diversion to a charger only to get back to where it was 10% lower. It seems to be something to do with it not thinking it'll be able to make the next charger, as planning the section by itself will give the route I'm after, but take it back to the last charger and the weirdness appears. What's going on?
  14. PaulS

    ABRP 3.8 Release Notes

    I think I've found something odd on 3.8. https://abetterrouteplanner.com/?plan_uuid=2e3571dd-bbc5-4327-90f6-aaeaa98d0caa The first alternative route has a 70-80 segment coming up as 1 mile long. I was wondering how it managed to do the journey 90minutes quicker that the other alternatives.
  15. PaulS

    IOS & Android App ?

    ...and I think they've entirely missed the point of systems like What 3 Words - That being to make the transmission of locations robust when done verbally. You call emergency services and they ask you where you are. "I'm at VS8Q+T5"..."Sorry was that a B or a V?" "I'm at Battery..Horse..Staple"..."Right we're on our way" For us, the equivalent is calling up customer services for a charger.
  16. I've just started using ABRP as an in-car tool rather than just a planning app, and I'm finding it rather difficult to use. I'm wondering if we can have a discussion about improving it. I expect some of this comes from the difference of using it on a large built-in interface (e.g. Tesla) vs a phone or tablet, so maybe these features want to be optional or selected on the user-agent string? Generally I'm finding the interface too busy and cluttered, and I need to be too precise to use it in a moving car. It takes too much attention away from the road, so I wanted to feedback what I think could be done to simplify things and make it safer to use. All of the changes I'm talking about are in reference to driving. I'm not seeing a need to change things for planning. A realise that might mean defining a "driving GUI" which doesn't really exist yet, as what we have is a small modification on the planning results page. I should preface this with saying I'm using Firefox on Android. Maybe some of these are Firefox-isms. Full screen - Screen real estate is at a premium, yet I've got the address bar locked at the top. It's not going to disappear because that only happens when you scroll down a page which doesn't apply here. I've seen some web-apps go full screen. Could ABRP do this when on the move? Map scale - The default scale seems to be to show the whole trip. This is useful when planning, but isn't very useful when driving as you can't see detail when approaching a charging stop. Could we auto-scale to show the car and the next charging stop? Then as you approach a stop you're getting more and more detailed information about how to find it. The Itinerary aka the top drawer - I personally don't think this needs to be available after planning, but certainly should auto-hide once moving. Buttons - I think it would be good to reassess which buttons are needed and when. I'm finding certain buttons are in the way and some I have to go digging for. The '?' button - It needs to die, at least whilst we're on the move. On a smaller screen it just takes over the whole display, and has lots of hot links which will take you off round the web as you're trying to get rid of it. Zoom buttons - I'm finding pinch to zoom is awful on the web app because it doesn't work if you hit a UI element by accident (e.g. the charger information bubbles). Couple this with trying to do it whilst keeping your eyes on the road, generally because you're approaching the area where you need to find a charger and so need to change lanes to come off the motorway or something. Generally auto-zooming would get rid of most of the need, but a quick tap to zoom in/out would generally be easier. So can we move them out of the dock during driving? Back arrow - Returning to the planner is a pretty devastating thing to hit by accident whilst driving. Can we make this less prominent? Battery adjustment - I like the functionality, but invariably when I'm trying to nudge the battery level up or down I end up selecting the value text in-between the two buttons and getting caught up in cut and paste menus. Is there something that can be done to make all text unselect-able? Maybe make the hot spot for each button overlap onto the text? Night mode - Can we automate it based on local time? User preference if you like. Then lose the button. Centre on car - Make it a "return to default view" button which appears only when user isn't on the default view? Slow charger filter - Only useful for planning? Hide whilst driving. These changes would mean that we're left with only the two zoom buttons most of the time, and a return to default view some of the time. No expandable dock necessary. All of these are my opinions only, so please understand this is all said in a spirit of making ABRP a better tool. I realise there may be good arguments against any of them (including developer time). Thoughts? Alternative suggestions? Developer feedback?
  17. So, I'm trying to have a go at this. First thing is trying to work out what to get to connect to the car. I too have been doing various bits of research, and found some schematics for the wiring inside the i3. So, the OBD connector has two protocols on it. There's the DCAN bus, , and Ethernet. The K+DCAN cable allows access to DCAN and K-Line buses (K-Line isn't connected on the i3 I think). The ENET cables allow you to talk TCP-IP. Most things I see about coding the car talk about using the ENET cable, but Bimmercode just seems to use DCAN I think. Second thing is that the OBD connector connects to the BDC (Body Domain Controller). It then connects over the PT-CAN bus to the EDME (Electrical Digital Motor Electronics), and that connects over the PT-CAN2 bus over to the SME (Supply Machine Electronics - The box that sits in the battery tray). OBDII Port <---DCAN---> BDC <---PT-CAN---> EDME <---PT-CAN2---> SME That matches the diagram you've posted. There's no guarantee that the CAN messages from the SME that we want are forwarded from the PT-CAN2 bus, through the EDME, to the BDC, and then onto the DCAN bus on the OBD port. We are a few levels deep here. One thing that's working for us is that the instrument cluster is on the PT-CAN bus, so the charge level updates should be on that bus, and that's just one step away. I'm waiting for my cables to turn up, and then I'll start doing some experiments.
  18. PaulS

    IONITY

    It might consider them, but if there's a faster alternative it will use that. It's not going to select a 50kW charger if there's a 150kW one available.
  19. That might be taking it a bit far.
  20. Yep, that's exactly what I ended up doing. Trouble is that doesn't give me the fastest method of getting back. It'll stop there for a full charge, rather than just the charge necessary to get to the next rapid charger. Really what I'm wanting to calculate is how long I need to be there at the slow charger. Thanks for the clarification on the "Car Charger" box. Could this not be part of the car database?
  21. I'm trying to plan a route where I'm going to be picking up a car, and I have no idea how much charge will be in it. So I've entered 10% as my starting charge, and ticked the "Level 2" box with 3.5kW in the associated box (Is this minimum charge point capacity, or the size of the charger installed on the car?). What I was expecting was that the router would find somewhere local to get enough charge to get to a rapid charger, but it appears to be ignoring low power chargers and failing. Am I setting it up wrong? Some local chargers exist within a few miles, so I don't know why it isn't using them. https://abetterrouteplanner.com/?plan_uuid=6b1b6714-686a-46d3-9a33-a5acb3b38721
  22. Seems to work great for my use case. I'm getting better solutions now that I'm filter out what I don't want, vs. preferring a few that I do. It's giving the tool more options.
  23. I'd say that when I have a network I don't want to use... I'm absolute about it. It's either not available to me, or I don't trust it to be working so I'm not going to make a plan with it. For a network that I want to use, it's more of a preference. I'm a member so get good prices, or something like that. It's not critical I use it, I'd just prefer to. So for me, having preferred network is fine as it is, but excluding networks should be a hard rule. I guess where we ending up is the "Prefer this network" button. becoming a "Set network preference" button, behind which you can select from a few positive and negative options. Use only this Network Prefer this Network I don't care Avoid this Network Never use this Network
  24. Isn;t that just a display filter? Some areas have so many low power AC charging points that it makes the map unreadable.

Contact Us

Bo - Lead Developer and Tesla owner: bo@abetterrouteplanner.com

Jason - New Car Models, Developer and Bolt owner : jason@abetterrouteplanner.com

Idreams - Forums Administrator, Forums Developer and Tesla owner : idreams@abetterrouteplanner.com

×
×
  • Create New...