Jump to content
AVIC411.com

morus

Members
  • Content count

    34
  • Joined

  • Last visited

About morus

  • Rank
    Member

Recent Profile Visitors

2905 profile views
  1. Thanks Ron, but it is not an issue with the parking brake. As I said, I did a lot of tests including direct access to the parrot module via AT-commands and it is all fine. It is just the communication with the Pioneer BT application software that does not work. Somehow the settings in USER\RW\SETUP\BT\BTUNIT.DAT got messed up. That's why I need this file from a working unit.
  2. I have the same issue with greyed-out BT settings as many others. I have tried a lot of things like flashing different firmware versions of the BT module, erasing its stored data and verifying that the module itself is working fine via supertestmode. My final conclusion is that not the module is faulty but the pioneer software that controls it. I am pretty sure that it could be fixed by replacing the files inside the folder USER\RW\SETUP\BT with the ones from a working unit. Does somebody have a backup copy of his unit available and could provide these files (esp. BTUNIT.DAT)? Or would somebody be so kind to copy them via supertestmode? Just put the attached file in the root of an SD-Card, navigate to \USER\RW\SETUP, mark BT for copy, navigate to \SD and select paste. TESTMODE.KEY
  3. I have exactly the same BT problem. I managed to update the BT firmware via the supertestmode but it did not solve the issue for me. It seems that some settings in the application software are messed up. It might have to do with the file in \SETUP\BT\BTUNIT.DAT . Can anyone provide a copy of this file from a working unit? Anyway, if someone wants to try to update the BT firmware via supertestmode, just put the 3 files that are contained in the latest map update in \FIRMWARE\BT on an SD-card in the folder \AVICZ110\BLUETOOTH and select update bluetooth firmware from the "forced firmware write" submenu in the supertestmode. Use the paths exactly as given even if you don't have an avic Z110. You can also check if your BT module is working from the testmode. Just go into the "Tel test" submenu. here you can open and init the connection to the module and pair with your phone. Once paired you can dial a phone number from this menu. My BT module works fine this way. Also the BT firmware update was successful, but in the settings BT is still greyed-out. So it definitely must be a problem of the Pioneer application SW and not of the Parrot bluetooth firmware.
  4. Bt firmware file

    I have exactly the same problem on my f30bt. I managed to update the BT firmware via the supertestmode though but it did not solve the issue for me. It seems that some settings in the application software are messed up. It might have to do with the file in \SETUP\BT\BTUNIT.DAT . Can anyone provide a copy of this file from a working unit? Anyway, if you want to try to update the BT firmware via supertestmode, just put the 3 files that are contained in the latest map update in \FIRMWARE\BT on an SD-card in the folder \AVICZ110\BLUETOOTH and select update bluetooth firmware from the "forced firmware write" submenu in the supertestmode. Use the paths exactly as given even if you don't have an avic Z110. With the supertestmode you can also check if your BT module is working. Just go into the "Tel test" submenu. Here you can open and init the connection to the module and pair with your phone. Once paired you can dial a phone number from this menu. My BT module works fine this way. Also the BT firmware update was successful, but in the BT settings most items are still greyed-out. So it definitely must be a problem of the Pioneer application SW and not of the Parrot bluetooth firmware.
  5. F9220BT Lost Bluetooth Firmware

    I have exactly the same problem. I managed to update the BT firmware via the supertestmode but it did not solve the issue for me. It seems that some settings in the application software are messed up. It might have to do with the file in \SETUP\BT\BTUNIT.DAT . Can anyone provide a copy of this file from a working unit? Anyway, if someone wants to try to update the BT firmware via supertestmode, just put the 3 files that are contained in the latest map update in \FIRMWARE\BT on an SD-card in the folder \AVICZ110\BLUETOOTH and select update bluetooth firmware from the "forced firmware write" submenu in the supertestmode. Use the paths exactly as given even if you don't have an avic Z110. You can also check if your BT module is working from the testmode. Just go into the "Tel test" submenu. here you can open and init the connection to the module and pair with your phone. Once paired you can dial a phone number from this menu. My BT module works fine this way. Also the BT firmware update was successful, but in the settings BT is still greyed-out. So it definitely must be a problem of the Pioneer application SW and not of the Parrot bluetooth firmware.
  6. AppRadio Extensions 2.0

    Don't know which version it is exactly but should be the lastest one. Pulled it in 2017 from Mike Decaro's repo shortly before it went down. Runs nicely on my Ipod touch 4 with IOS 6.1.6. Don't trust the filename. It was generated automatically by the redeb tool. Might very well be derived from a reference to an outdated version somewhere in the deb config files.
  7. Improved Hackmode with internal GPS

    New version with working virtual keyboard morushack_1.3.zip
  8. Improved Hackmode with internal GPS

    New version 1.2 with script optimizations and integrated port splitter for (hopefully) better stability of the internal GPS data stream. Use com9: at 115200 bps as the NMEA source in your preferred nav SW. Previous versions of the hack must be uninstalled before installing this version as the runscript intercepts now navi.exe instead of voice.exe. Long term goal is better integration with original SW (now you can switch back and forth between orig. SW and hack, but you cannot listen to mp3s or answer phone calls while in hackmode). I also plan to add a dab+ receiver (FS-Silicon verona with sermmi firmware) via com1: and an ODB trip computer (hobd-standalone is already running, just need to connect my ODB dongle via com6:). And finally I want to add support for WLAN SD-Cards and a VNC client. morushack_1.2.zip
  9. Improved Hackmode with internal GPS

    adzaM, On the f30bt I start Igo via the "APL exit" debug mode. In this mode av.exe is not running. I do not know how av.exe behaves if I replace navi.exe with igo. Maybe I will try that when I find some time. So far I cannot give you any advice. Sorry.
  10. hi morus dont know why the post is archive so i cant reply. i try yours morushack1.1 but on the mrz i cant find anyway to enable "poseidondbg" the navi software its different to f series also condihack no working on it i have last idea to replace full image from avic f30bt but i cant find it anywhere so i hope you can help with thisĀ 

  11. Now even with working internal GPS! See readme.txt for instructions. PW is avic411. For those that are trying to run Igo on japanese MRZ HUs: In order to get the internal GPS working you need to 1. kill gpsmc.exe 2. reload the com7: device driver using "reloaddrv.exe COM7:" 3. retart gpsmc.exe See Voice.mscr for mortscript commands to perform these steps. morushack_1.1.zip
  12. Improved Condi Hackmode

    I have made some progress in running Igo on my AVIC f30bt. This hack is heavily based on the Condi-Hackmode v. 1.4 and on the poseidondebug mode that has been found by pionara . It allows you to run Igo 8.3 and probably also other 3rd party nav software using an external GPS receiver with sound and even TMC working. This hack was tested only on my f30bt using the 2017 european map update. You might brick your device if you try this with older software versions. So please update your unit with the 2017 maps before you try to use this hack. Just put all the files within the morushack_1.0 folder in the root of an SD-Card. Put this into the HU, once the testmode screen is visible go to file maintenance and navigate to \NAND folder and check if you have a file called "PRG.FLG". If you have it, go to the \NAND\PRG1\Apl folder, otherwise go to the \NAND\PRG0\Apl folder. All files and subfolders from the folder "to_be_copied_in_APL_folder" must be copied here. But before you can do this, you must delete the file "Voice.exe", because in the testmode file maintenance mode one cannot overwrite any files. If you later on want to remove this hack, just delete all the files that have been copied to this folder and rename "Voice1.exe" in "Voice.exe". Before you restart the HU, delete both the "TESTMODE.KEY" and the "autorun.mscr" files from the root of the SD-Card usinf the file maintenance menu. Your HU should start as usual. Now you need to enable the hidden debug menu as follows (has to be done only once): 1. go to navigation menu, favorites. edit existing or add new favorite. (search method does not matter - just need to get to the "name" field) 2. while in "edit favorite" view, click on name button. you should now see the keyboard to edit the favorite name 3. here you type in "POSEIDONDBG ON", but then instead of hitting OK, press and hold the top center of the screen. 4. it should go back to map screen, and you have enabled debug mode. You will notice some debugging output overlayed on the map screen. Don't worry you can turn it off in the hidden debug menu. To enter the debug menu: go to navigation menu, then press and hold top center of screen. If you get a red text that reads "ERR" or a blue text "GPS", you can turn it off via the GPS debug entry in the hidden menu. Just go to log and disable GPS logging. You can now start the hackmode via this hidden debug menu. Open it and select "APL Exit" from the list and after 10-15 seconds you should see the windows ce desktop. Now you can launch any ce program you want. You can go back to the AVIC original software via the "restart" link on the desktop. If you want to get sound output from ce programs, you need to play an mp3 from either the sd-card or an USB drive while you chose "APL Exit". Otherwise you will have no sound other than the source that was selected while you got into the debug menu. If you want to start automatically any software (e.g. Igo) instead of the windows ce desktop, you can put the "autorun.mscr" file in the root of the sd-card (or a USB drive) and adjust its contents with a text editor accordingly. I run Igo 8.3 in this way using the following sys.txt file: [folders] app="%SDCARD%/iGO8" [interface] skin="ui_igo8" vga=0 mapfontscale=100 show_exit=1 [rawdisplay] class="landscape" highres=0 screen_x=800 screen_y=480 [tts] tts_buffer=131072 tts_logics=3 priority="HIGH" always_say_road_names=1 announce_street_name=1 expected_engine_delay=1400 [debug] skip_eula=1 enable_roadshadow=1 [map] auto_nightmode=1 [tmc] port=2 baud=38400 source="gns" [gps] port=1 baud=9600 source="nmea" Currently the internal GPS receiver is not working, but you can use an external receiver. See the end of the Condi Hackmode thread for an explanation how to connect an external GPS receiver. I already have an idea how to enable the internal GPS receiver. However, due to lack of time it is unlikely that I will succeed... morushack_1.0.zip
  13. No, not possible, because it's only an antenna. You need to connect a complete receiver. It does not need to be a M8N. You just need a GPS receiver that has a TTL UART output. M8N is attractive because it is highly sensitive, it supports GPS/GLONASS/BEIDOU/GALILEO, and it is relatively cheap because it is often used in chinese drones...
  14. AVIC-MRZ99 Custom Firmware / Testmode

    Take a look at the condi hackmode thread. I have explained there why you can't use the GPS port. It is already opened by "NPGPSENGINE.DLL" at the point when navi.exe is started and it cannot be opened twice. You either need the "Pioneerus" hack to get access to this port (ask forum user "Sanik") or you need to use an external GPS receiver as described in the condi hackmode thread.
  15. manio112, the mrzs seem to use the same AV-connector as the f30bt. So I am pretty sure that they will have the COM1 port available as well since it is used by the pioneer software developers as a debug port (debug output can be turned on with the "POSEIDONDBG ON" method as described by an old post of pionara here in the forum). Here are instructions to get you going: Connect the TX pin of the M8N to pin 24 (EXTOC) of the AV connector and the RX pin of the M8N to pin 12 (CTOEX). You can use the "KMODE" connection method for the handbrake signal detection override as described on youtube to make this connection despite missing leads on the AV connector plug. Alternatively, if you don't need any other signals from the AV connector, you can also remove the Plug and use so called "jumper cables" for breadborads to connect to the pins on the AV connector directly. That's how I did it. GND and VCC for the M8N can be taken from the USB port of the AVIC. Just use a USB Y-adapter cable that are used to power mobile USB harddisk and cut off the secondary USB plug to tap off GND and VCC. GND is usually the black wire and VCC the red one, but I recommend to double check with a multimeter. I am using a GY-GPSV3 M8N PCB-only module that I ordered from ebay, but you can also find M8N modules for drones that come complete with a housing and wires. BTW., the method you suggested to get audio working does not seem to work for the f30bt, because as soon as av.exe starts it will occupy the screen. So I do have to start Igo instead of av.exe and can't start it instead of navi.exe. This seems to be also the rootcause for the missing audio, because av.exe seems to be needed in order to initialize the audio path from the codec to the speakers.
×