HX3 Flash for OEMs - Versionsgeschichte

Bovist am 11. Januar 2016 um 07:33 Uhr

2016-01-11T07:33:57Z

← Nächstältere Version		Version vom 11. Januar 2016, 07:33 Uhr
Zeile 3:		Zeile 3:
	Due to some demand I changed the '''[[HX3 Flash Application]]''' behaviour.		Due to some demand I changed the '''[[HX3 Flash Application]]''' behaviour.

	Former versions of ''~~'[[~~HX3 Flash ~~Application]]'~~'' checked 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.		Former versions of ''HX3 Flash'' checked 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 our Github repository], 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 customized by a simple text editor or by HX3 Flash itself. Just raise ''HX3 Flash'' windows fully to the right (dragging its right border). The control script is visible now and may be edited directly. Click "Save Configuration INI" to make changes permanent. Content of ''hx3_flash_config.ini'' looks like this example:		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 our Github repository], 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 customized by a simple text editor or by HX3 Flash itself. Just raise ''HX3 Flash'' windows fully to the right (dragging its right border). The control script is visible now and may be edited directly. Click "Save Configuration INI" to make changes permanent. Content of ''hx3_flash_config.ini'' looks like this example:

Bovist am 11. Januar 2016 um 07:15 Uhr

2016-01-11T07:15:43Z

← Nächstältere Version		Version vom 11. Januar 2016, 07:15 Uhr
Zeile 3:		Zeile 3:
	Due to some demand I changed the '''[[HX3 Flash Application]]''' behaviour.		Due to some demand I changed the '''[[HX3 Flash Application]]''' behaviour.

	Former versions of [[HX3 Flash Application]] checked 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.		Former versions of '''[[HX3 Flash Application]]''' checked 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 our Github repository], 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 customized by a simple text editor. Content of ~~INI~~ looks like this example:		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 our Github repository], 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 customized by a simple text editor or by HX3 Flash itself. Just raise ''HX3 Flash'' windows fully to the right (dragging its right border). The control script is visible now and may be edited directly. Click "Save Configuration INI" to make changes permanent. Content of ''hx3_flash_config.ini'' looks like this example:

	/// Configuration file for HX3 MIDI Expander ///		/// Configuration file for HX3 MIDI Expander ///

Bovist am 25. Dezember 2015 um 22:35 Uhr

2015-12-25T22:35:15Z

← Nächstältere Version		Version vom 25. Dezember 2015, 22:35 Uhr
Zeile 13:		Zeile 13:
	[BoardInfo]=		[BoardInfo]=

	/// Disable update of user info or licences by commenting.		/// Disable update of user info or licences by commenting. WARNING: old licences will be overwritten if enabled.
	~~///~~ WARNING: old ~~licence numbers~~ will be overwritten if enabled.
	new_user_name=Hans Wurst		new_user_name=Hans Wurst
	/new_organ_licence=7654321		/new_organ_licence=7654321
Zeile 28:		Zeile 27:
	fpga_filename=fpga_20122015.bit		fpga_filename=fpga_20122015.bit

	/// If FPGA is updated, all taper_levels files,		/// If FPGA is updated, all taper_levels files, fir_coeff and dsp_rev must be activated as well.
	~~///~~ fir_coeff and dsp_rev must be activated as well.
	taper1_filename=taper_levels1.dat		taper1_filename=taper_levels1.dat
	taper2_filename=taper_levels2.dat		taper2_filename=taper_levels2.dat
Zeile 37:		Zeile 35:
	dsp_rev_filename=dsp_rev.bin		dsp_rev_filename=dsp_rev.bin

	/// If FPGA is updated, at least MIDI and the scan core		/// If FPGA is updated, at least MIDI and the scan core used in your instrument must be activated.
	~~///~~ used in your instrument must be activated.
	/scancore0_filename=HX_CHAIN.DAT		/scancore0_filename=HX_CHAIN.DAT
	scancore1_filename=HX_MIDI.DAT		scancore1_filename=HX_MIDI.DAT
Zeile 50:		Zeile 47:
	[ButtonEnables]=		[ButtonEnables]=

	/// Disable buttons that should not be used		/// Disable HX3 Flash buttons that should not be used

	restore_organ=false		restore_organ=false
Zeile 59:		Zeile 56:

	/// parameters that must be restored to old value end with '=?'		/// 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		/// Disable lines with comment char '/' at start

Zeile 73:		Zeile 69:
	/477=?		/477=?
	/ Analog input Enable:		/ Analog input Enable:
	478=?		/478=?
	/ Button mask PL7:		/ Button mask PL7:
	/479=?		/479=?
Zeile 81:		Zeile 77:
	/483=?		/483=?
	/ No splitted Preset16 panel:		/ No splitted Preset16 panel:
	484=?		/484=?
	/ Save tabs to presets:		/ Save tabs to presets:
	485=?		/485=?

	/// parameters to set must have a value behind '='		/// parameters to set must have a value behind '=', boolean values are 0 (off) or 255 (on)
	~~/// Boolean~~ values are 0 or 255
	/// Disable lines with comment char '/' at start		/// Disable lines with comment char '/' at start

Zeile 94:		Zeile 89:
	/439=18		/439=18
	/ ScanCore:		/ ScanCore:
	477=0		/477=1
	/ Button mask PL7:		/ Button mask PL7:
	479=255		/479=255
	/ Button mask PL11:		/ Button mask PL11:
	480=240		/480=240
	/ Preset number to select second drawbar set:		/ Preset number to select second drawbar set:
	483=1		/483=1
	/ No splitted Preset16 panel:		/ No splitted Preset16 panel:
	/484=0		/484=0
Zeile 112:		Zeile 107:
	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.		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.

	For your convenience, I left some parameters in which are disabled by '/' comment character. You may enable them just by removing the leading '/'. Please note: Valid parameter commands must start with a digit, no spaces or comments are allowed in a command line. Blank lines or comment lines may be inserted anywhere. '''Do not change''' the ''[xxx]='' lines.		For your convenience, I left some parameters in which are disabled by '/' comment character. You may enable them just by removing the leading '/' and change values to your needs. Please note: Valid parameter commands must start with a digit, no spaces or comments are allowed in a command line. Blank lines or comment lines may be inserted anywhere.

			'''Do not change''' the ''[xxx]='' section separator lines.

Bovist am 25. Dezember 2015 um 22:29 Uhr

2015-12-25T22:29:37Z

← Nächstältere Version		Version vom 25. Dezember 2015, 22:29 Uhr
Zeile 108:		Zeile 108:
	[End]		[End]

	Lines can be disabled by placing a comment character '/' in first column. As you see, you can decide which buttons are enabled and which parameters have to be tweaked '''after''' the new firmware was installed. '''User Name''' and '''Licences''' are always restored to old values. You may force ''HX3 Flash'' to write new user/licence info by ''new_user_name'', ''new_organ_licence='' and ''new_rotary_licence='' command.		Lines can be disabled by placing a comment character '/' in first column. As you see, you can decide which buttons are enabled and which parameters have to be tweaked '''after''' the new firmware was installed. '''User Name''' and '''Licences''' are always restored to old values. You may force ''HX3 Flash'' to write new user/licence info by ''new_user_name='', ''new_organ_licence='' and ''new_rotary_licence='' command. '''Warning:''' Existing licence numbers will be overwritten!

	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.		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.

	For your convenience, I left some parameters in which are disabled by '/' comment character. You may enable them just by removing the leading '/'. Please note: Valid parameter commands must start with a digit, no spaces or comments are allowed in a command line. Blank lines or comment lines may be inserted anywhere. '''Do not change''' the ''[xxx]='' lines.		For your convenience, I left some parameters in which are disabled by '/' comment character. You may enable them just by removing the leading '/'. Please note: Valid parameter commands must start with a digit, no spaces or comments are allowed in a command line. Blank lines or comment lines may be inserted anywhere. '''Do not change''' the ''[xxx]='' lines.

Bovist am 25. Dezember 2015 um 22:28 Uhr

2015-12-25T22:28:06Z

← Nächstältere Version		Version vom 25. Dezember 2015, 22:28 Uhr
Zeile 71:		Zeile 71:
	439=?		439=?
	/ ScanCore:		/ ScanCore:
	477=?		/477=?
	/ Analog input Enable:		/ Analog input Enable:
	478=?		478=?
	/ Button mask PL7:		/ Button mask PL7:
	479=?		/479=?
	/ Button mask PL11:		/ Button mask PL11:
	480=?		/480=?
	/ Preset number to select second drawbar set:		/ Preset number to select second drawbar set:
	483=?		/483=?
	/ No splitted Preset16 panel:		/ No splitted Preset16 panel:
	484=?		484=?
Zeile 112:		Zeile 112:
	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.		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.

	For your convenience, I left some parameters in which are disabled by '/' comment character. You may enable them just by removing the leading '/'. Please note: Valid parameter commands must start with a digit, no spaces or comments are allowed in a command line.		For your convenience, I left some parameters in which are disabled by '/' comment character. You may enable them just by removing the leading '/'. Please note: Valid parameter commands must start with a digit, no spaces or comments are allowed in a command line. Blank lines or comment lines may be inserted anywhere. '''Do not change''' the ''[xxx]='' lines.

Bovist am 25. Dezember 2015 um 22:25 Uhr

2015-12-25T22:25:20Z

← Nächstältere Version		Version vom 25. Dezember 2015, 22:25 Uhr
Zeile 85:		Zeile 85:
	485=?		485=?

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

Bovist am 25. Dezember 2015 um 22:22 Uhr

2015-12-25T22:22:35Z

← Nächstältere Version		Version vom 25. Dezember 2015, 22:22 Uhr
Zeile 108:		Zeile 108:
	[End]		[End]

	Lines can be disabled by placing a comment character '/' in first column. As you see, you can decide which buttons are enabled and which parameters have to be tweaked '''after''' the new firmware was installed. '''User Name''' and '''Licences''' are always restored to ~~olde~~ values. You may force ''HX3 Flash'' to write new user/licence info by ''new_user_name'', ''new_organ_licence='' and ''new_rotary_licence='' command.		Lines can be disabled by placing a comment character '/' in first column. As you see, you can decide which buttons are enabled and which parameters have to be tweaked '''after''' the new firmware was installed. '''User Name''' and '''Licences''' are always restored to old values. You may force ''HX3 Flash'' to write new user/licence info by ''new_user_name'', ''new_organ_licence='' and ''new_rotary_licence='' command.

	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.		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.

	For your convenience, I left some parameters in which are disabled by '/' comment character. You may enable them just by removing the leading '/'. Please note: Valid parameter commands must start with a digit, no spaces or comments are allowed in a command line.		For your convenience, I left some parameters in which are disabled by '/' comment character. You may enable them just by removing the leading '/'. Please note: Valid parameter commands must start with a digit, no spaces or comments are allowed in a command line.

Bovist am 25. Dezember 2015 um 22:20 Uhr

2015-12-25T22:20:55Z

← Nächstältere Version		Version vom 25. Dezember 2015, 22:20 Uhr
Zeile 24:		Zeile 24:
	firmware_name=HX3 Expander		firmware_name=HX3 Expander

	/// Disable loading/update of particular file by commenting.		/// Disable loading/update of particular file by commenting.
	/avr_filename=HX3mk3_expander.hex		avr_filename=HX3mk3_expander.hex
	/fpga_filename=fpga_20122015.bit		fpga_filename=fpga_20122015.bit

	/// If FPGA is updated, all taper_levels files,		/// If FPGA is updated, all taper_levels files,
	/// fir_coeff and dsp_rev must be activated as well.		/// fir_coeff and dsp_rev must be activated as well.
	/taper1_filename=taper_levels1.dat		taper1_filename=taper_levels1.dat
	/taper2_filename=taper_levels2.dat		taper2_filename=taper_levels2.dat
	/taper3_filename=taper_levels3.dat		taper3_filename=taper_levels3.dat
	/taper4_filename=taper_levels4.dat		taper4_filename=taper_levels4.dat
	/fir_coeff_filename=fir_coeff.dat		fir_coeff_filename=fir_coeff.dat
	/dsp_rev_filename=dsp_rev.bin		dsp_rev_filename=dsp_rev.bin

	/// If FPGA is updated, at least MIDI and the scan core		/// If FPGA is updated, at least MIDI and the scan core
Zeile 50:		Zeile 50:
	[ButtonEnables]=		[ButtonEnables]=

	/ Disable buttons that should not be used		/// Disable buttons that should not be used

	restore_organ=false		restore_organ=false
Zeile 58:		Zeile 58:
	[Parameters]=		[Parameters]=

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

	/ MIDI Channel:		/ MIDI Channel:
Zeile 85:		Zeile 85:
	485=?		485=?

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

	/ Jack config A:		/ Jack config A:
Zeile 108:		Zeile 108:
	[End]		[End]

	As you see, you can decide which buttons are enabled and which parameters have to be tweaked '''after''' the new firmware was installed. '''User Name''' and '''Licences''' are always ~~retained~~.		Lines can be disabled by placing a comment character '/' in first column. As you see, you can decide which buttons are enabled and which parameters have to be tweaked '''after''' the new firmware was installed. '''User Name''' and '''Licences''' are always restored to olde values. You may force ''HX3 Flash'' to write new user/licence info by ''new_user_name'', ''new_organ_licence='' and ''new_rotary_licence='' command.

	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.		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.

	For your convenience, I left some parameters in which are disabled by '/' comment character. You may enable them just by removing the leading '/'. Please note: Valid parameter commands must start with a digit, no spaces or comments are allowed in a command line.		For your convenience, I left some parameters in which are disabled by '/' comment character. You may enable them just by removing the leading '/'. Please note: Valid parameter commands must start with a digit, no spaces or comments are allowed in a command line.

Bovist am 25. Dezember 2015 um 22:15 Uhr

2015-12-25T22:15:05Z

← Nächstältere Version		Version vom 25. Dezember 2015, 22:15 Uhr
Zeile 14:		Zeile 14:

	/// Disable update of user info or licences by commenting.		/// Disable update of user info or licences by commenting.
	/// ~~Warning~~: old licence numbers will be overwritten if enabled.		/// WARNING: old licence numbers will be overwritten if enabled.
	new_user_name=Hans Wurst		new_user_name=Hans Wurst
	/new_organ_licence=7654321		/new_organ_licence=7654321
Zeile 47:		Zeile 47:
	/scancore6_filename=HX_TEST.DAT		/scancore6_filename=HX_TEST.DAT
	/scancore7_filename=HX_XB2.DAT		/scancore7_filename=HX_XB2.DAT

	[ButtonEnables]=		[ButtonEnables]=

Bovist am 25. Dezember 2015 um 22:14 Uhr

2015-12-25T22:14:07Z

← Nächstältere Version		Version vom 25. Dezember 2015, 22:14 Uhr
Zeile 7:		Zeile 7:
	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 our Github repository], 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 customized by a simple text editor. Content of INI looks like this example:		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 our Github repository], 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 customized by a simple text editor. Content of INI looks like this example:

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

			[BoardInfo]=

			/// Disable update of user info or licences by commenting.
			/// Warning: old licence numbers will be overwritten if enabled.
			new_user_name=Hans Wurst
			/new_organ_licence=7654321
			/new_rotary_licence=1234567

	[Files]=		[Files]=

	/ ~~The firmware_name~~ is ~~just shown~~ in HX3 ~~flash~~ window.		/// this name is showed in HX3 Flash window, nothing else.
	firmware_name=HX3 ~~StandardOrgan~~		firmware_name=HX3 Expander

			/// Disable loading/update of particular file by commenting.
			/avr_filename=HX3mk3_expander.hex
			/fpga_filename=fpga_20122015.bit

	/ ~~Files to use. Must be present in same folder.~~		/// If FPGA is updated, all taper_levels files,
	~~avr_filename=HX3mk3_std.hex~~		/// fir_coeff and dsp_rev must be activated as well.
	~~fpga_filename=fpga_20122015~~.~~bit~~		/taper1_filename=taper_levels1.dat
	taper1_filename=taper_levels1.dat		/taper2_filename=taper_levels2.dat
	taper2_filename=taper_levels2.dat		/taper3_filename=taper_levels3.dat
	taper3_filename=taper_levels3.dat		/taper4_filename=taper_levels4.dat
	taper4_filename=taper_levels4.dat		/fir_coeff_filename=fir_coeff.dat
			/dsp_rev_filename=dsp_rev.bin

			/// If FPGA is updated, at least MIDI and the scan core
			/// used in your instrument must be activated.
			/scancore0_filename=HX_CHAIN.DAT
			scancore1_filename=HX_MIDI.DAT
			scancore2_filename=HX_FATAR.DAT
			/scancore3_filename=HX_SR44.DAT
			/scancore4_filename=HX_SR49.DAT
			/scancore5_filename=HX_SR61.DAT
			/scancore6_filename=HX_TEST.DAT
			/scancore7_filename=HX_XB2.DAT

	[ButtonEnables]=		[ButtonEnables]=