Reply With QuoteNice work.
Do we need to install each update? I assume we can jump from say 1.04 to 1.04 without any hassles?
Cheers,
Nova
Master
It was quite a struggle but with only minutes to spare on our last working day of 2011, but we did in fact manage to release our fifth upgrade for the Nanocom Evolutions BBS V1.04.
As well as sorting out the known problems with the Slabs ghost "pump line monitor fault", it is also more stable and improves further upon some freezing problems with Motronic etc.
It also re organizes the menuing a little to standardize layout between models, most notably to also incorporate full Range Rover P38 coverage.
Here are a few quick and basic demo video clips.
[ame=http://www.youtube.com/watch?v=RRG9aPJ1j4U&list=UUwsWXJr_piaJD9UKSVMXiIQ& index=4&feature=plcp]Nanocom Evolution II Range Rover P38 Menu - YouTube[/ame]
[ame=http://www.youtube.com/watch?v=9h5_CXHfkpQ&list=UUwsWXJr_piaJD9UKSVMXiIQ& index=3&feature=plcp]Nanocom Evolution II, Range Rover P38 EAS Diagnostic - YouTube[/ame]
[ame=http://www.youtube.com/watch?v=Vx1Ok1VZgLo&list=UUwsWXJr_piaJD9UKSVMXiIQ& index=2&feature=plcp]Nanocom Evolution II, Range Rover P38 Body Control - YouTube[/ame]
[ame=http://www.youtube.com/watch?v=ZpWbt6WU7EI&list=UUwsWXJr_piaJD9UKSVMXiIQ& index=1&feature=plcp]Nanocom Evolution II GEMS Engine Management - YouTube[/ame]
Merry Christmas to all and a happy and prosperous new year for all.
Master
SubscriberNice work.
Do we need to install each update? I assume we can jump from say 1.04 to 1.04 without any hassles?
Cheers,
Nova
Master
Hiya Nova
Cheers.
Yes you can just jump to the latest version and miss previous ones out
YarnMaster
...
Problem solved...
Wizard
Update applied no problem, and p38 beta codes entered... Thanks Colin!
Will hopefully have a chance to test this arvo and over the weekend.
Cheers, Paul.
My toys, projects and write-ups at PaulP38a.com
Master
Cheers Paul
I just got my own 98 GEMS P38 back yesterday after having my garage owning mate fit a set of Gen II air springs on it, and bought it home to do a bit of testing today, with it being a Bank Holiday here and perhaps some more over the weekend.
Wizard
Hi Colin - good news from me.
I plugged the Evo into Wifey's 2000 model P38 (Motronics 4.6) and it worked a treat. I took a bunch of photos at each Motronics screen and will post them to my project site and send you a link.
It also confirmed that her EAS has a dodgy Rear Left Height Sensor so I will either swap it out, or do the old left to right swap tomorrow.
I must say that I really like the EAS module on the Evo. I think I may have mentioned to yourself (or one of your staff) in the past that I find the EAS module on the MSV2 difficult to use as it is slow to respond and the screen layout is messy. The Evo version is fast and elegant... well done BBS team.
I then plugged the Evo in to my 1999 P38 (Motronics 4.0) and to my surprise nothing happened! Blank screen and no startup sound from the Evo. Now, I know that the OBDII port has constant power, so the Evo should power up when it is plugged in. I am wondering if the voltage on mine was a bit too low for the Evo (the car has been sat idle for a few days) as it woke up after the engine had been running for 10 seconds or so. Weird?
Both of my P38's will be getting some attention over the weekend (I hope) so will let you know what else I discover.
Cheers, Paul.
My toys, projects and write-ups at PaulP38a.com
Master
Hiya Paul
I guess that like me, you have grown pretty used to the only thing so fully capable on a P38 being the much more expensive MSV-2, and it really takes a bit of sinking in when you see all this capability now being provided on such a small and usable, low cost bit of hardware as the EVO truly is.
Thanks for the initial thumbs up, as you can now see for yourself me and my guys have put a lot of effort into this and although it might still need a few tweaks here and there, it is already proving it's worth.
Re your Black screen problem, you must have either had a bad power or earth connection, or a very low Battery voltage for the EVO to not even fire up at all.
It does have a SMPS that requires a minimum voltage of about 9V so you must have been below that. Still a very quick remedy though.
Cheers
Colin
YarnMaster
Hi Colin,
My problem wasn't actually solved - it's an intermittent bug.
The Nanocom menu item has a tendency to disappear. I've just powered up the Evo 2 and the Nanocom button is not displayed. Shutting down and restarting while attached to power adapter and the Nanocom is displayed.
It's happened a few times now. I'll try to see if I can identify a pattern to when this occurs.
cheers
Paul
Master
Hiya Paul
Thanks for your input.
I have not seen this happen myself but have heard of cases where text has errors in it etc.
It sounds like a graphic controller display problem to me, or more accurately command of the graphic controller from the Main Firmware controller
In the Evo, the graphics display controller is instructed what to display by the Main controller over the internal SPI bus. The Graphics controller has it's own flash library of graphics for drawing buttons and icons etc, but otherwise what buttons to draw and what text is to be displayed is passed to it over the SPI Bus. There are other things on the BUS, like the SD card and of course the Graphics controller also passes back information from the Touch screen too.
We have done some tweaks to speed up the Graphics display and improve general responsiveness and it may be that we have pushed this so far that you can now get very occasional graphics errors such as you describe.
But given the infrequency of this, and others not reporting the same problem, it could well be something local to you. Did you have an SD card inserted when this happens for example.
Perhaps this might help you identify any pattern and help us get to the bottom of this oddity.
Paul:
Can I ask you to specifically check your Motronic immobilization codes match between the Motronic and the BeCM
Cheers
Colin
Posting Permissions
| Search AULRO.com ONLY! |
Search All the Web! |
|---|
|
|
|
Bookmarks