[superwofy]

I spent most of my time fixing APIX2. However, since I've had to order a new panel for that
screen, I decided to look into making this ID3 screen I have here work with my NBTevo_Y23236I on HW2.3.

It's actually quite simple. It seems that HUJacintoStage1 now enforces voltage monitoring. The developers were kind enough to add a flag that disables said enforcement. All that has to be done is to create a file:

On the Jacinto side (serial/telnet/ssh):

PHP Code:

touch /var/opt/sys/APIX_VMON_OFF && \
sleep 5 && OnOffDSICommander appreset 


Alternatively from OMAP:

PHP Code:

on -f hu-jacinto touch /var/opt/sys/APIX_VMON_OFF && \
sleep 5 && OnOffDSICommander appreset 


After this the screen should turn on. After clearing DTCs, CID errors should not return.

Tested with HU 6829104 on NBTevo_Y23236I and CID 9252004.

Code:

               <partIdentification>
                    <processClass>HWEL</processClass>
                    <id>000022E4</id>
                    <mainVersion>001</mainVersion>
                    <subVersion>002</subVersion>
                    <patchVersion>003</patchVersion>
                </partIdentification>
                <partIdentification>
                    <processClass>CAFD</processClass>
                    <id>00001EF6</id>
                    <mainVersion>006</mainVersion>
                    <subVersion>064</subVersion>
                    <patchVersion>013</patchVersion>
                </partIdentification>
                <partIdentification>
                    <processClass>BTLD</processClass>
                    <id>00001FFD</id>
                    <mainVersion>007</mainVersion>
                    <subVersion>049</subVersion>
                    <patchVersion>001</patchVersion>
                </partIdentification>
                <partIdentification>
                    <processClass>SWFL</processClass>
                    <id>00002718</id>
                    <mainVersion>007</mainVersion>
                    <subVersion>049</subVersion>
                    <patchVersion>001</patchVersion>
                </partIdentification>
                <partIdentification>
                    <processClass>SWFL</processClass>
                    <id>00002719</id>
                    <mainVersion>007</mainVersion>
                    <subVersion>049</subVersion>
                    <patchVersion>001</patchVersion>
                </partIdentification>
                <partIdentification>
                    <processClass>SWFL</processClass>
                    <id>0000271A</id>
                    <mainVersion>007</mainVersion>
                    <subVersion>049</subVersion>
                    <patchVersion>001</patchVersion>
                </partIdentification>
                <partIdentification>
                    <processClass>SWFL</processClass>
                    <id>0000271C</id>
                    <mainVersion>007</mainVersion>
                    <subVersion>049</subVersion>
                    <patchVersion>001</patchVersion>
                </partIdentification>
                <partIdentification>
                    <processClass>SWFL</processClass>
                    <id>0000271E</id>
                    <mainVersion>007</mainVersion>
                    <subVersion>049</subVersion>
                    <patchVersion>001</patchVersion>
                </partIdentification>
                <partIdentification>
                    <processClass>SWFL</processClass>
                    <id>0000271F</id>
                    <mainVersion>007</mainVersion>
                    <subVersion>049</subVersion>
                    <patchVersion>001</patchVersion>
                </partIdentification>
                <partIdentification>
                    <processClass>SWFL</processClass>
                    <id>00002720</id>
                    <mainVersion>007</mainVersion>
                    <subVersion>049</subVersion>
                    <patchVersion>001</patchVersion>
                </partIdentification>
                <partIdentification>
                    <processClass>SWFL</processClass>
                    <id>00002722</id>
                    <mainVersion>007</mainVersion>
                    <subVersion>049</subVersion>
                    <patchVersion>001</patchVersion>
                </partIdentification>
                <partIdentification>
                    <processClass>SWFL</processClass>
                    <id>00002723</id>
                    <mainVersion>007</mainVersion>
                    <subVersion>049</subVersion>
                    <patchVersion>001</patchVersion>
                </partIdentification>
                <partIdentification>
                    <processClass>SWFL</processClass>
                    <id>00002727</id>
                    <mainVersion>007</mainVersion>
                    <subVersion>049</subVersion>
                    <patchVersion>001</patchVersion>
                </partIdentification>

   

[duke99]

Hi,thanks.Will this work for ID4 upgrade ID6 black screen?

[painsage]

Hi, will this work for ID5/6 with Apix1 screen?

[superwofy]

Hi,thanks.Will this work for ID4 upgrade ID6 black screen?

Hi, will this work for ID5/6 with Apix1 screen?

It's all in the thread title, post and the screenshot.

What I've found is that it works for HW2.3 units (originally ID4) on the latest I-level using NBT (ID3) CIDs. I don't have other hardware available that I can use to confirm.

[painsage]

Just flashed my native ID6 HW 4.1 to 22-11, i want to use it with APIX1 for my E60. In var/opt/sys/ i don't see apix_vmon_off mentioned above. Any way to add the file and make it work?

[BusyBox]

How about reading VERY carefully the info provided?

[painsage]

How about reading VERY carefully the info provided?

It is said in OP, to create the file, i missed that. I'm still learning to do anything with EVO, can someone give exact instructions on how to do this?
EDIT: Please excuse my lack of knowledge, i just ran the command with putty through SSH, i'm gonna test out and let you know.

[painsage]

UPDATE: On my unit, native ID6, 4gb RAM, GPS, DAB. After doing the OMAP method, i have a file created in the mentioned directory. The file is 0kb in size, and is empty when opened with notepad. This did NOT fix the no signal/black screen issue. HU was powered on 4 times, 2 of those i got no signal. Very,very unfortunate, meaning i have to go back to 18-03 and hope that a reflash will fix my screen mirroring issue.

[superwofy]

UPDATE: On my unit, native ID6, 4gb RAM, GPS, DAB. After doing the OMAP method, i have a file created in the mentioned directory. The file is 0kb in size, and is empty when opened with notepad. This did NOT fix the no signal/black screen issue. HU was powered on 4 times, 2 of those i got no signal. Very,very unfortunate, meaning i have to go back to 18-03 and hope that a reflash will fix my screen mirroring issue.

No signal is a slightly different issue. Is your coding correct? For me, the ID3 screen is always black not in No Signal state without that file.

Post the output of these commands:

PHP Code:

on -f hu-jacinto -t 14 -r 41
on -f hu-jacinto -t 14 -r 42
on -f hu-jacinto -t 14 -r 43
on -f hu-jacinto -t 14 -r 44
on -f hu-jacinto -t 14 -r 45
on -f hu-jacinto -t 14 -r 46
on -f hu-jacinto -t 14 -r 47
on -f hu-jacinto -t 14 -r 48
on -f hu-jacinto -t 14 -r 49
on -f hu-jacinto -t 14 -r 4A
on -f hu-jacinto -t 14 -r 4B
on -f hu-jacinto -t 14 -r 4C
on -f hu-jacinto -t 14 -r 4E 


Also try running this a few times:

PHP Code:

on -f hu-jacinto apixconfig -t 14 -w 2F 01 


What CID are you using?

[painsage]

UPDATE: On my unit, native ID6, 4gb RAM, GPS, DAB. After doing the OMAP method, i have a file created in the mentioned directory. The file is 0kb in size, and is empty when opened with notepad. This did NOT fix the no signal/black screen issue. HU was powered on 4 times, 2 of those i got no signal. Very,very unfortunate, meaning i have to go back to 18-03 and hope that a reflash will fix my screen mirroring issue.

No signal is a slightly different issue. Is your coding correct? For me, the ID3 screen is always black not in No Signal state without that file.

Post the output of these commands:

PHP Code:

on -f hu-jacinto -t 14 -r 41
on -f hu-jacinto -t 14 -r 42
on -f hu-jacinto -t 14 -r 43
on -f hu-jacinto -t 14 -r 44
on -f hu-jacinto -t 14 -r 45
on -f hu-jacinto -t 14 -r 46
on -f hu-jacinto -t 14 -r 47
on -f hu-jacinto -t 14 -r 48
on -f hu-jacinto -t 14 -r 49
on -f hu-jacinto -t 14 -r 4A
on -f hu-jacinto -t 14 -r 4B
on -f hu-jacinto -t 14 -r 4C
on -f hu-jacinto -t 14 -r 4E 


Also try running this a few times:

PHP Code:

on -f hu-jacinto apixconfig -t 14 -w 2F 01 


What CID are you using?

Coding is good for apix1, it worked on 18-03 no problem, no signal/blackscreen didn't happen at all. I am using NBT ID3 8.8inch CID
I'm gonna try these commands tomorrow and let you know. Do i run them when i get a screen or when no signal is active?
This command: "

PHP Code:

on -f hu-jacinto apixconfig -t 14 -w 2F 01 


", what does it do? Am i supposed to run this everytime i get no signal? Is your apix_vmon_off file completely empty, 0kb in size?
EDIT: Forgot to mention, when i get no signal, a restart fixes the issue and the HU works perfectly.