colinbourassa
Adding update/fix to 11.0.0?
Hi, I have no idea about programming, but I do own a TVR and have been using RoverGauge - though I have reverted to the previous version because of the issue that the latest upload aims to fix. I have no idea how to apply the fix - I have so far just copied the new batch of files into the main folder that houses the app, but it's made no difference. Clearly I'm not doing it right...
Not sure if it makes any difference that I'm running a Windows virtual machine on my MacBook Pro?
Can you help please?
If you extract the .zip file containing the new version into a folder, it should have everything needed to run. There is no need to extract it into the existing RoverGauge folder. However, if you do choose to extract into an existing folder, you need to ensure that you are actually overwriting the older rovergauge.exe.
There should be no issue with running in a virtual machine, as long as the virtual machine makes the USB serial device available to the guest OS.
There are two things to note about this latest published release (11.0):
- It was migrated from the Qt5 framework to Qt6. This newer version of Qt does not support Windows 7, so this build of RoverGauge will not run on Windows 7 machines. I plan to revert to Qt5 for subsequent releases.
- There is a bug in this release that prevents the display of the tune/revision ID information.
Hi Colin,
Thank you for the update, I see you've posted v11.1.0, so I will install that on my system later - brilliant, thank you!
And for my next trick, to try to track down a stalling issue on my TVR!
All the best, and thank you for providing this resource
Paul
On 26.10.2023 5:29 pm, Colin Bourassa wrote:
If you extract the .zip file containing the new version into a folder, it should have everything needed to run. There is no need to extract it into the existing RoverGauge folder. However, if you do choose to extract into an existing folder, you need to ensure that you are actually overwriting the older rovergauge.exe.
There should be no issue with running in a virtual machine, as long as the virtual machine makes the USB serial device available to the guest OS.
There are two things to note about this latest published release (11.0):
- It was migrated from the Qt5 framework to Qt6. This newer version of Qt does not support Windows 7, so this build of RoverGauge will not run on Windows 7 machines. I plan to revert to Qt5 for subsequent releases.
- There is a bug in this release that prevents the display of the tune/revision ID information.
-- Reply to this email directly, view it on GitHub [1], or unsubscribe [2]. You are receiving this because you authored the thread.Message ID: @.***>
Links:
[1] https://github.com/colinbourassa/rovergauge/issues/23#issuecomment-1781457150 [2] https://github.com/notifications/unsubscribe-auth/BDQXXVGD3VBCCT5YS62MG3LYBKFXJAVCNFSM6AAAAAA6PT7IZ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBRGQ2TOMJVGA
Finally downloaded the new version, will try to test it later.
One detail (and this is the designer in me), you'd got the interface looking smart in 11.0.0, but 11.1.0 doesn't look as pretty!
Not sure if that relates to the Qt5 or Qt6 framework, or whether it can be smartened.
Not critical of course.
Hi Colin, I just connected to the car, engine running, and the Tune/ID remains blank.
Do I need to do anything else (like drive the car whilst connected) to draw that info?
I haven't been able to reproduce either of these problems with 11.1.0, although my Windows testing is limited to Windows 10. (I've run it both in VirtualBox and bare metal.)
Do you see the incorrect font size with older versions that were using Qt5, i.e. RoverGauge 0.10.7? I guess I'm trying to determine if it's a Qt5 problem or something to do with your configuration of Windows. None of the code for drawing those widgets has changed in this repository.
The missing tune ID / revision number is particularly strange, as this is always requested during the normal connection sequence.
Hi Colin, Apologies for the delayed response! I saw the same font size issue on 0.10.7, it only worked properly on 11.0.0 I will do a proper run with it soon, just haven't had the chance recently, then will report what happens with 11.1.0, especially the tune ID. I also have no idea what my Windows configuration is, I haven't touched it, and as a Mac user I'm not sure I'd know where to look anyway. I'll come back to you
First off - @colinbourassa wow! cant thank you enough for the detailed work you have done here and on the top sharing it with us all - God bless!
I have done many interior updates on my RRC'91 and my last step is to have a digital instument/cluster. i was searching for a cluster that i can just buy and connect but i was unable to find anything that works with 14CUX.
I have downloaded the source code.,.. its already doing most of the work but i think for most of us, we are interested in a digital dash as well. Perhaps 2 screens: Screen1: when the car turns On; Screen 1 is a instrument cluster that looks like a OEM but in a much nicer way, Screen2: The current diagnostic screen that you already have.
RPi, Python, and a screen is needed to get started. I am on it.... will be back soon! thank you again for this GREAT work and i hope 'we' all can contribute more to this contribution!
@colinbourassa Update from my end, I transferred to a PC laptop (put a new battery in my son's old machine), and it works well now. Not sure if it's a glitch in the virtual machine world, but everything is happier now I've taken that layer away.
The only difference I'm seeing is the way the log is recorded - I have captured a log on separate journeys in the same day, and the app records it all into the same file. Nothing is lost, but a log from a morning run is then added to later on a return journey. It starts a new file on a different day, but not just by disconnecting/connecting on the same day. As I said, nothing is lost, but it behaves differently from how it did on the Mac.
Paul
I hope you’re having a good holiday in Cypus.
RoverGauge starts a new log file name when you exit RoverGauge & restart RoverGauge not disconnecting and re-connecting and has always been like that including the latest 11.2 version. I’m therefore very surprised to hear your return journey was appended to your morning log, therefore please can you test exiting RoverGauge and restarting to see if the time in the log file name changes.
Did you hibernate the laptop without closing RoverGauge?
Message me when your back and we’ll go for a diff & CV joint test drive.
Cheers Steve
From: PaulGillam Sent: Wednesday, July 24, 2024 9:45 AM To: colinbourassa/rovergauge Cc: Subscribed Subject: Re: [colinbourassa/rovergauge] Adding update/fix to 11.0.0? (Issue #23)
@colinbourassa Update from my end, I transferred to a PC laptop (put a new battery in my son's old machine), and it works well now. Not sure if it's a glitch in the virtual machine world, but everything is happier now I've taken that layer away.
The only difference I'm seeing is the way the log is recorded - I have captured a log on separate journeys in the same day, and the app records it all into the same file. Nothing is lost, but a log from a morning run is then added to later on a return journey. It starts a new file on a different day, but not just by disconnecting/connecting on the same day. As I said, nothing is lost, but it behaves differently from how it did on the Mac.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.***>
