HX3 Flash for OEMs: Unterschied zwischen den Versionen

Aus KeyboardPartner Wiki
Zur Navigation springenZur Suche springen
(Die Seite wurde neu angelegt: „==Customizable updater== Due to some demand I changed the HX3 Flash updater app behaviour. Former versions of HX3 Flash looked what firmware was installed on…“)
 
Zeile 1: Zeile 1:
==Customizable updater==
==Customizable updater==


Due to some demand I changed the HX3 Flash updater app behaviour.
'''Information given here is intended for OEM use only.'''


Former versions of HX3 Flash looked what firmware was installed on HX3 board and tried to determine what might be adequate to install. That often lead to unwanted results if parameters in new firmware changed significantly. Or I had a lot of work implementing minor parameter changes for various OEM *.hex files.
Due to some demand I changed the '''HX3 Flash updater''' app behaviour.


The new HX3 Flash is customizable by OEMs like you, so it might be completely adapted to your needs. You might prepare a package for your customers like the Flash_*.ZIPs on
Former versions of '''[[HX3 Flash]]''' looked what firmware was installed on the HX3 board and tried to determine what might be adequate to install. That often lead to unwanted results if parameters in new firmware changed significantly. Or I had a lot of work implementing minor parameter changes for various OEM *.hex files.
 
The new '''HX3 Flash''' is customizable by OEMs like you, so it might be completely adapted to your needs. You might prepare a package for your customers like the Flash_*.ZIPs on


https://github.com/keyboardpartner/HX3/tree/master/LATEST
https://github.com/keyboardpartner/HX3/tree/master/LATEST


containing only the necessary files for a specific instrument. The behaviour of HX3 Flash is controlled by an INI file named "hx3_flash_config.ini" which is human-readable and may be edited by a simple text editor. Content of INI looks like this example:
containing only the necessary files for a specific instrument. The behaviour of HX3 Flash is controlled by an INI file named '''hx3_flash_config.ini''' which is human-readable and may be edited by a simple text editor. Content of INI looks like this example:


  / Configuration file for HX3 Standard Organ
  / Configuration file for HX3 Standard Organ
Zeile 19: Zeile 21:
  / The firmware_name is just shown in HX3 flash window.
  / The firmware_name is just shown in HX3 flash window.
  firmware_name=HX3 StandardOrgan
  firmware_name=HX3 StandardOrgan
 
  / Files to use. Must be present in same folder.
  / Files to use. Must be present in same folder.
  avr_filename=HX3mk3_std.hex
  avr_filename=HX3mk3_std.hex
Zeile 31: Zeile 33:
   
   
  / Disable buttons that should not be used
  / Disable buttons that should not be used
 
  restore_organ=false
  restore_organ=false
  restore_presets=true
  restore_presets=true
Zeile 88: Zeile 90:
  [End]
  [End]


As you see, you can decide which buttons are enabled and which parameters have to be tweaked after firmware was installed. Therefore, you may adjust parameters to your taste or to requirements of your instrument - without urging me to re-compile just for parameter issues.
As you see, you can decide which buttons are enabled and which parameters have to be tweaked '''after''' firmware was installed. '''User Name''' and '''Licences''' are always retained.  


All parameter numbers given in HX3 Remote pages are valid, so you may even change rotary params or MIDI CCs.
Therefore, you may adjust parameters to your taste or to requirements of your instrument - without urging me to re-compile just for some parameter issues. All parameter numbers given in HX3 Remote pages are valid, so you may even change rotary params or MIDI CCs.

Version vom 23. Dezember 2015, 23:00 Uhr

Customizable updater

Information given here is intended for OEM use only.

Due to some demand I changed the HX3 Flash updater app behaviour.

Former versions of HX3 Flash looked what firmware was installed on the HX3 board and tried to determine what might be adequate to install. That often lead to unwanted results if parameters in new firmware changed significantly. Or I had a lot of work implementing minor parameter changes for various OEM *.hex files.

The new HX3 Flash is customizable by OEMs like you, so it might be completely adapted to your needs. You might prepare a package for your customers like the Flash_*.ZIPs on

https://github.com/keyboardpartner/HX3/tree/master/LATEST

containing only the necessary files for a specific instrument. The behaviour of HX3 Flash is controlled by an INI file named hx3_flash_config.ini which is human-readable and may be edited by a simple text editor. Content of INI looks like this example:

/ Configuration file for HX3 Standard Organ
/ Disable lines with comment char '/' at start
/ Extend to other parameters at own discretion

[Files]=

/ The firmware_name is just shown in HX3 flash window.
firmware_name=HX3 StandardOrgan

/ Files to use. Must be present in same folder.
avr_filename=HX3mk3_std.hex
fpga_filename=fpga_20122015.bit
taper1_filename=taper_levels1.dat
taper2_filename=taper_levels2.dat
taper3_filename=taper_levels3.dat
taper4_filename=taper_levels4.dat

[ButtonEnables]=

/ Disable buttons that should not be used

restore_organ=false
restore_presets=true
restore_midi=true

[Parameters]=

/ parameters that must be restored to old value end with '=?'
/ Boolean on/off values are 255 or 0
/ Disable lines with comment char '/' at start

/ MIDI Channel:
433=?
/ Split default mode:
/436=?
/ Jack config A:
438=?
/ Jack config B:
439=?
/ ScanCore:
477=?
/ Analog input Enable:
478=?
/ Button mask PL7:
479=?
/ Button mask PL11:
480=?
/ Preset number to select second drawbar set:
483=?
/ No splitted Preset16 panel:
484=?
/ Save tabs to presets:
485=?

/ parameters to set do have a value
/ Boolean values are 0 or 255
/ Disable lines with comment char '/' at start

/ Jack config A:
/438=1
/ Jack config B:
/439=18
/ ScanCore:
477=0
/ Button mask PL7:
479=255
/ Button mask PL11:
480=240
/ Preset number to select second drawbar set:
483=1
/ No splitted Preset16 panel:
/484=0
/ Save tabs to presets:
/485=1

[End]

As you see, you can decide which buttons are enabled and which parameters have to be tweaked after firmware was installed. User Name and Licences are always retained.

Therefore, you may adjust parameters to your taste or to requirements of your instrument - without urging me to re-compile just for some parameter issues. All parameter numbers given in HX3 Remote pages are valid, so you may even change rotary params or MIDI CCs.