O20C1 Chip with SSD firmware.

I hate to suggest it, but they could always have it require the hall sensor to be installed, and use the magnet trick to trigger DFU mode to change the firmware.

I certainly don't know enough about what the firmware and hardware is capable of, but even if you managed to keep it from losing power too long as it passes over lane changers, if your car happens to land on a dead spot during a yellow flag, you wouldn't be able to say "only reset if power has been lost" either. Any number of button combinations from a controller could happen while driving the car, so you can't really use that to trigger programming mode.

If the chip can tell the difference between pure DC and the rectified AC, then maybe have it only go into programming mode when put on DC? But then people would have to have some kind of thing to put the car on with enough DC to wake up the chip and keep it alive while programming. A 9v battery can do this, but it would be awkward to hold in position while fiddling with the app.

I look forward to the results of the testing. If this were being used on an APB and RCS64, then you'd have to watch the screen to make sure you didn't take away a damage point, or mark yourself ready before you're actually ready. ;-)

Klitgaard said:

Hi MrF
Thanks for the suggestions.
Brake is our fuel filling trigger, so that will not be one to use. I will give LC a try, but I do think this is a bug that slot it should look at.

Click to expand...

Does it trigger as soon as you press the brake, or do you have to hold the brake to make it refuel? I was not suggesting to hold the button(s) down, but just to click them every few seconds.

Razamanaz said:

I’ve mentioned this a couple of times, and this little problem has actually celebrated its first birthday. But yes, it’s easy that things get lost in this forum, and I’m positive. We, the community, simply need to apply some modern software practices together with slot.it, and we’ll be alright. I’ve wanted to start that discussion for a while, but have been holding back in order for the dust to settle around the last firmware updates, and let the everyone involved in oXigen 4.0 to focus on that first.

Click to expand...

MrFlippant said:

I did find a couple other issues that I believe are app related, and reported those to slot.it, but I don't think those issues are related to this.

Click to expand...

What I mean with the above is that we need some proper issue tracking and release management in place. Simply something similar to what’s is available out-of-the-box in e.g. GitHub, i.e. public threads that are focused on issues, and release documentation that links to those issues when things get fixed.

I’m not saying that oXigen should go open-source, but could use an official GitHub account for the above, or simply a subsection to this section of the forum, and also document in the firmware .zip files and the app stores what have been changed.

Personally, I’ve a bit given up spending too much time on detailing issues I or other find and writing about them here, because I don’t get any response on them, and I don’t see others getting any response as well. But I’ve now realized that this section of the forum doesn’t work as I think it does. It’s NOT an official channel that gets monitored for issues in the oXigen products; it more occasionally/randomly works that way (but without any feedback). It also so hard to know what problems others already have reported, and if there’s any work-around to those problems (or if they already have been solved). I think some of the frustration we see come from this (in addition to having an issue, of course).

But I’m positive, I think this can be turned around. It would be good that have some simple feedback loop in place, some simple software practices, a bit more structure, and we should be in a better shape. It would of course be good to have that in place before oXigen 4.0, as there will be a lot of issues there, but I guess this need to be discussed and implemented after that release.

OK, this got me a bit more motivated again. I’ve been waiting for a new iOS app, I’ve always needed to use my wife’s Android phone to be able to change firmwares. But now that we have a new iOS version, it may be time to look at this again. It may take a couple of weeks, but I’ll play with the firmwares as you suggested, Greg, and see if that solves anything.