Jump to content

PaulS

Members
  • Content Count

    20
  • Joined

  • Last visited

  • Days Won

    2

PaulS last won the day on September 26

PaulS had the most liked content!

Community Reputation

4 Neutral
  1. 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.
  2. 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.
  3. 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?
  4. 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.
  5. 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.
  6. That might be taking it a bit far.
  7. 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?
  8. 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
  9. 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.
  10. 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
  11. Isn;t that just a display filter? Some areas have so many low power AC charging points that it makes the map unreadable.
  12. Looks like it's back
  13. Description: I've noticed that when you put a charge rate into the waypoint settings (gear icon next to a waypoint), the charging rate is limited by your cars AC charge rate (In my case 11kW). It would be good to be able to say when it's a DC charger that's available at the location, so DC limits are applied instead. Use Case: When a DC charger is not on the map (e.g. it's too new, it's a private company's or it's public and hasn't been commissioned yet) it can be useful to add a DC charger via a waypoint. Currently only AC charging is possible.
  14. Description: It looks like all charger belonging to Polar (BP Chargemaster) are now missing from ABRP. Replication Steps: Go to Milton Keynes, UK in OpenChargeMap and be amazed how many rapid chargers they have Go to Milton Keynes, UK in ABRP and be amazed because all the chargers are missing. These used to exist. I'm sure, and they're missing from all around the UK, including one half a mile from my house which I KNOW used to be in ABRP. Attached are screenshots, just in case this is a temporary blip. I commented in another thread about this before I realise how big an issue this is. Polar are the biggest network in the UK by far.
  15. I've noticed something similar in the UK. Milton Keynes Coachway has disappeared off the M1. It think it normally linked to OpenChargeMap, which still has it as OCM-113525 <Edit Link>. It's an 8-stall rapid charger site on a major motorway, so it's rather useful.

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...