Firmware V1.1.2 – what’s new?
-
- Posts: 22
- Joined: Wednesday 11. May 2016, 21:27
Firmware V1.1.2 – what’s new?
Good morning together,
like mentioned on the H&W facebook page the new Firmware V1.1.2 is available now.
The update process was successfully but in the “readme.txt” is nothing listed or documented regarding new features, adaptions, ... - can you give a short overview?
Thanks in advance & best regards,
Chris
like mentioned on the H&W facebook page the new Firmware V1.1.2 is available now.
The update process was successfully but in the “readme.txt” is nothing listed or documented regarding new features, adaptions, ... - can you give a short overview?
Thanks in advance & best regards,
Chris
-
- Posts: 4376
- Joined: Sunday 13. May 2007, 18:07
Re: Firmware V1.1.2 – what’s new?
With firmware V1.1.2 including RTE 0.90 comes no big new feature to the OSTC4 this time.
There is an important fix for multiple gas changes in GF mode and the readLimits was improved for external (PC/Mac) software.
Furthermore the complete update process works without a reset again with RTE 0.90.
The only immediately noticeable feature is the individual configuration of the button sensitivity.
The tiny changes in the hardware layer are not visible for the user but improve overall performance.
Major steps forward might come with one of the next updates or as a continuation of step by step improvements.
kind regards,
Christian
There is an important fix for multiple gas changes in GF mode and the readLimits was improved for external (PC/Mac) software.
Furthermore the complete update process works without a reset again with RTE 0.90.
The only immediately noticeable feature is the individual configuration of the button sensitivity.
The tiny changes in the hardware layer are not visible for the user but improve overall performance.
Major steps forward might come with one of the next updates or as a continuation of step by step improvements.
kind regards,
Christian
Re: Firmware V1.1.2 – what’s new?
There is still a bug where battery shows as almost empty and red after updating firmware.
Best regards
gorcio
Best regards
gorcio
Kind regards,
Gorcio, OSTC MK2 828
Gorcio, OSTC MK2 828
-
- Posts: 4376
- Joined: Sunday 13. May 2007, 18:07
Re: Firmware V1.1.2 – what’s new?
The "RTE" part of the firmware tracks the battery level (What's being charged into it and what's drained for the electronics during use) to give an exact percent value what is actually left in the battery at any time. This information is currently lost when updating this RTE part (Which will be much less often happen in the future). With the next recharge this value is recalibrated and the OSTC4 shows the normal state again. The update process doesn't drain the battery so it was full before it will be calibrated on the charger again in a few minutes.
Regards,
Matthias
Regards,
Matthias
Re: Firmware V1.1.2 – what’s new?
[s][size=x-large]!! DO NOT UPDATE 1.1.2 !![/size]
Can't update RTE to 0.90 and alerts shows up in center of screen.
I already tried many time to update/reset settings&reboot rte&reboot firmware. FAILED!!!
[img]https://s14.postimg.org/67h2x9sw1/S_93429764.jpg[/img]
[img]https://s15.postimg.org/mj90vbcbf/S_93429765.jpg[/img]
[/s]
* via dctool[dctool --family ostc3 --model 0x3B --verbose --logfile dctool.log fwupdate --firmware OSTC4_update_160919_V1_1_2__RTE_0_90.bin ] // can't connect well
[pre]
[0.000373] DATETIME 2016-09-27T15:10:46Z (1474989046)
[0.000401] VERSION 0.5.0-devel (c506be93f94eb40d7b6802685074c496d546c202)
[0.000432] Opening the device (Heinrichs Weikamp OSTC 4, /dev/tty.OSTC4-00051-SPP).
[0.000444] INFO: Open: name=/dev/tty.OSTC4-00051-SPP
[6.197811] INFO: Configure: baudrate=115200, databits=8, parity=0, stopbits=0, flowcontrol=0
[6.198112] INFO: Timeout: value=3000
[6.198163] INFO: Sleep: value=300
[6.503333] INFO: Purge: direction=3
[6.503550] Registering the event handler.
[6.503565] Registering the cancellation handler.
[6.503575] Updating the firmware.
[6.503849] INFO: Write: size=4, data=AAABCDEF
[6.503861] INFO: Sleep: value=100
[6.609065] INFO: Read: size=5, data=4BABCDEF4C
[6.609353] INFO: Write: size=1, data=60
[6.647482] INFO: Read: size=1, data=60
[6.647513] INFO: Read: size=5, data=003B000043
[6.647521] INFO: Read: size=1, data=4C
[6.647605] ERROR: Failed to open the file. [in ../../source/src/hw_ostc3.c:1123 (hw_ostc3_firmware_readfile4)]
[6.647614] ERROR: Error updating the firmware. [in ../../source/examples/dctool_fwupdate.c:91 (fwupdate)]
[6.647794] INFO: Write: size=1, data=FF
[9.650834] INFO: Read: size=0, data=
[9.650878] ERROR: Failed to receive the echo. [in ../../source/src/hw_ostc3.c:210 (hw_ostc3_transfer)]
[9.650892] ERROR: Failed to send the command. [in ../../source/src/hw_ostc3.c:529 (hw_ostc3_device_close)]
[10.341540] ERROR: Input/output error
[/pre]
[s]
* via ostc companion = shows success(but actually RTE update failed, always part3 upload then reboots not to go RTE update/deco erase warning process)
[pre]
OSTC4 selected.
Connecting...
Found OSTC4 #0051, fw 66.08 (main 1.01.01/RTE 0.89.00/Font 0.09.00), blah
Disconnecting...
Disconnected.
Upgrading firmware...
Starting OSTC4 firmware upgrade...
uploading part 1: FW v1.01.02...
< timeout
< timeout
part 1: FW v1.01.02 uploaded.
part 2: Font v0.09.00 already up-to-date.
uploading part 3: RTE v0.90.00...
part 3: RTE v0.90.00 uploaded.
Please wait for OSTC4 to complete installation...
...
many time tried again again... always part3 upload then, reboots(doesn't enter RTE update/deco calculation erase warning and progress bars)
...
OSTC4 selected.
Upgrading firmware...
Starting OSTC4 firmware upgrade...
part 1: FW v1.01.02 already up-to-date.
part 2: Font v0.09.00 already up-to-date.
uploading part 3: RTE v0.90.00...
part 3: RTE v0.90.00 uploaded.
Please wait for OSTC4 to complete installation...
[/pre][/s]
# Solved
* U must reset settings, reboot firmware, reboot RTE few times. then follow
* Wait until idle time(2mins~, I tried when LCD turned off and wait almost 10mins later), then update part3 successfully(RTE successfully updated)
Can't update RTE to 0.90 and alerts shows up in center of screen.
I already tried many time to update/reset settings&reboot rte&reboot firmware. FAILED!!!
[img]https://s14.postimg.org/67h2x9sw1/S_93429764.jpg[/img]
[img]https://s15.postimg.org/mj90vbcbf/S_93429765.jpg[/img]
[/s]
* via dctool[dctool --family ostc3 --model 0x3B --verbose --logfile dctool.log fwupdate --firmware OSTC4_update_160919_V1_1_2__RTE_0_90.bin ] // can't connect well
[pre]
[0.000373] DATETIME 2016-09-27T15:10:46Z (1474989046)
[0.000401] VERSION 0.5.0-devel (c506be93f94eb40d7b6802685074c496d546c202)
[0.000432] Opening the device (Heinrichs Weikamp OSTC 4, /dev/tty.OSTC4-00051-SPP).
[0.000444] INFO: Open: name=/dev/tty.OSTC4-00051-SPP
[6.197811] INFO: Configure: baudrate=115200, databits=8, parity=0, stopbits=0, flowcontrol=0
[6.198112] INFO: Timeout: value=3000
[6.198163] INFO: Sleep: value=300
[6.503333] INFO: Purge: direction=3
[6.503550] Registering the event handler.
[6.503565] Registering the cancellation handler.
[6.503575] Updating the firmware.
[6.503849] INFO: Write: size=4, data=AAABCDEF
[6.503861] INFO: Sleep: value=100
[6.609065] INFO: Read: size=5, data=4BABCDEF4C
[6.609353] INFO: Write: size=1, data=60
[6.647482] INFO: Read: size=1, data=60
[6.647513] INFO: Read: size=5, data=003B000043
[6.647521] INFO: Read: size=1, data=4C
[6.647605] ERROR: Failed to open the file. [in ../../source/src/hw_ostc3.c:1123 (hw_ostc3_firmware_readfile4)]
[6.647614] ERROR: Error updating the firmware. [in ../../source/examples/dctool_fwupdate.c:91 (fwupdate)]
[6.647794] INFO: Write: size=1, data=FF
[9.650834] INFO: Read: size=0, data=
[9.650878] ERROR: Failed to receive the echo. [in ../../source/src/hw_ostc3.c:210 (hw_ostc3_transfer)]
[9.650892] ERROR: Failed to send the command. [in ../../source/src/hw_ostc3.c:529 (hw_ostc3_device_close)]
[10.341540] ERROR: Input/output error
[/pre]
[s]
* via ostc companion = shows success(but actually RTE update failed, always part3 upload then reboots not to go RTE update/deco erase warning process)
[pre]
OSTC4 selected.
Connecting...
Found OSTC4 #0051, fw 66.08 (main 1.01.01/RTE 0.89.00/Font 0.09.00), blah
Disconnecting...
Disconnected.
Upgrading firmware...
Starting OSTC4 firmware upgrade...
uploading part 1: FW v1.01.02...
< timeout
< timeout
part 1: FW v1.01.02 uploaded.
part 2: Font v0.09.00 already up-to-date.
uploading part 3: RTE v0.90.00...
part 3: RTE v0.90.00 uploaded.
Please wait for OSTC4 to complete installation...
...
many time tried again again... always part3 upload then, reboots(doesn't enter RTE update/deco calculation erase warning and progress bars)
...
OSTC4 selected.
Upgrading firmware...
Starting OSTC4 firmware upgrade...
part 1: FW v1.01.02 already up-to-date.
part 2: Font v0.09.00 already up-to-date.
uploading part 3: RTE v0.90.00...
part 3: RTE v0.90.00 uploaded.
Please wait for OSTC4 to complete installation...
[/pre][/s]
# Solved
* U must reset settings, reboot firmware, reboot RTE few times. then follow
* Wait until idle time(2mins~, I tried when LCD turned off and wait almost 10mins later), then update part3 successfully(RTE successfully updated)
-
- Posts: 18
- Joined: Saturday 6. August 2016, 13:47
Re: Firmware V1.1.2 – what’s new?
still cant get RTE to .90
PLEASE UPDATE RTE MSG STILL ON CENTER
any tips ?
thanks
PLEASE UPDATE RTE MSG STILL ON CENTER
any tips ?
thanks
Sulaiman OSTC3 OSTC4:73
Re: Firmware V1.1.2 – what’s new?
tanomogi Wrote:
-------------------------------------------------------
> * via dctool[dctool --family ostc3 --model 0x3B
> --verbose --logfile dctool.log fwupdate --firmware
> OSTC4_update_160919_V1_1_2__RTE_0_90.bin ] //
> can't connect well
> [pre]
> [0.000373] DATETIME 2016-09-27T15:10:46Z
> (1474989046)
> [0.000401] VERSION 0.5.0-devel
> (c506be93f94eb40d7b6802685074c496d546c202)
> [0.000432] Opening the device (Heinrichs Weikamp
> OSTC 4, /dev/tty.OSTC4-00051-SPP).
> [0.000444] INFO: Open:
> name=/dev/tty.OSTC4-00051-SPP
> [6.197811] INFO: Configure: baudrate=115200,
> databits=8, parity=0, stopbits=0, flowcontrol=0
> [6.198112] INFO: Timeout: value=3000
> [6.198163] INFO: Sleep: value=300
> [6.503333] INFO: Purge: direction=3
> [6.503550] Registering the event handler.
> [6.503565] Registering the cancellation handler.
> [6.503575] Updating the firmware.
> [6.503849] INFO: Write: size=4, data=AAABCDEF
> [6.503861] INFO: Sleep: value=100
> [6.609065] INFO: Read: size=5, data=4BABCDEF4C
> [6.609353] INFO: Write: size=1, data=60
> [6.647482] INFO: Read: size=1, data=60
> [6.647513] INFO: Read: size=5, data=003B000043
> [6.647521] INFO: Read: size=1, data=4C
> [6.647605] ERROR: Failed to open the file. [in
> ../../source/src/hw_ostc3.c:1123
> (hw_ostc3_firmware_readfile4)]
> [6.647614] ERROR: Error updating the firmware. [in
> ../../source/examples/dctool_fwupdate.c:91
> (fwupdate)]
This indicates it couldn't open the firmware file. That's not a failed firmware upgrade! Most likely you made a small typo in the filename.
Jef
-------------------------------------------------------
> * via dctool[dctool --family ostc3 --model 0x3B
> --verbose --logfile dctool.log fwupdate --firmware
> OSTC4_update_160919_V1_1_2__RTE_0_90.bin ] //
> can't connect well
> [pre]
> [0.000373] DATETIME 2016-09-27T15:10:46Z
> (1474989046)
> [0.000401] VERSION 0.5.0-devel
> (c506be93f94eb40d7b6802685074c496d546c202)
> [0.000432] Opening the device (Heinrichs Weikamp
> OSTC 4, /dev/tty.OSTC4-00051-SPP).
> [0.000444] INFO: Open:
> name=/dev/tty.OSTC4-00051-SPP
> [6.197811] INFO: Configure: baudrate=115200,
> databits=8, parity=0, stopbits=0, flowcontrol=0
> [6.198112] INFO: Timeout: value=3000
> [6.198163] INFO: Sleep: value=300
> [6.503333] INFO: Purge: direction=3
> [6.503550] Registering the event handler.
> [6.503565] Registering the cancellation handler.
> [6.503575] Updating the firmware.
> [6.503849] INFO: Write: size=4, data=AAABCDEF
> [6.503861] INFO: Sleep: value=100
> [6.609065] INFO: Read: size=5, data=4BABCDEF4C
> [6.609353] INFO: Write: size=1, data=60
> [6.647482] INFO: Read: size=1, data=60
> [6.647513] INFO: Read: size=5, data=003B000043
> [6.647521] INFO: Read: size=1, data=4C
> [6.647605] ERROR: Failed to open the file. [in
> ../../source/src/hw_ostc3.c:1123
> (hw_ostc3_firmware_readfile4)]
> [6.647614] ERROR: Error updating the firmware. [in
> ../../source/examples/dctool_fwupdate.c:91
> (fwupdate)]
This indicates it couldn't open the firmware file. That's not a failed firmware upgrade! Most likely you made a small typo in the filename.
Jef
--
libdivecomputer developer
http://www.libdivecomputer.org/
libdivecomputer developer
http://www.libdivecomputer.org/
Re: Firmware V1.1.2 – what’s new?
Jef,
Actually firmware not in same directory with current path(.)
I used '../../' with right file name(case sensitive). double checked.
Path name and filename not contains any other space or special characters.
I reviewed code again, It using just usual fopen in stdio.h ...
well... I believe its casual error in my case.
Actually firmware not in same directory with current path(.)
I used '../../' with right file name(case sensitive). double checked.
Path name and filename not contains any other space or special characters.
I reviewed code again, It using just usual fopen in stdio.h ...
well... I believe its casual error in my case.
Re: Firmware V1.1.2 – what’s new?
sadsani@gmail.com Wrote:
-------------------------------------------------------
> still cant get RTE to .90
>
> PLEASE UPDATE RTE MSG STILL ON CENTER
>
> any tips ?
>
> thanks
Same as my case in the above post. part3 loading fail/reboot.
In my case,
Reset configuration, Reboot firmware, Reboot rte
then, leave it alone for a wile until LCD off.(at least 2mins over, mine was 10mins later)
Then try it again, with OSTC Companion beta8.
U will see console message with below
"part 3: RTE v0.90.00 uploaded.
Please wait for OSTC4 to complete installation..."
Then, check the screen of OSTC4.
If successfully uploaded/verified, it will show about initializing tissue loading warning message.
-------------------------------------------------------
> still cant get RTE to .90
>
> PLEASE UPDATE RTE MSG STILL ON CENTER
>
> any tips ?
>
> thanks
Same as my case in the above post. part3 loading fail/reboot.
In my case,
Reset configuration, Reboot firmware, Reboot rte
then, leave it alone for a wile until LCD off.(at least 2mins over, mine was 10mins later)
Then try it again, with OSTC Companion beta8.
U will see console message with below
"part 3: RTE v0.90.00 uploaded.
Please wait for OSTC4 to complete installation..."
Then, check the screen of OSTC4.
If successfully uploaded/verified, it will show about initializing tissue loading warning message.
-
- Posts: 18
- Joined: Saturday 6. August 2016, 13:47
Re: Firmware V1.1.2 – what’s new?
thanks tanomogi its all good the problem was from my imac .. i tried macbook pro all good and working maybe the bluetooth wasnt working correctly or the file was corrupted dont know but the good news its working now
thanks
thanks
Sulaiman OSTC3 OSTC4:73
Re: Firmware V1.1.2 – what’s new?
I can confirm that the update on an iMac with Companion beta8 won't work.
Same issue with no RTE update here.
1. reset settings
2. reboot firmware
3. reboot RTE
4. wait until OSTC goes to sleep
5. start OSTC and enable Bluetooth
After I switched to my Macbook Pro it worked well with Companion beta 8.
So it seems something's going on with bluetooth on iMac which is different to Macbook Pro.
Cheers
Toby
sadsani@gmail.com Wrote:
-------------------------------------------------------
> thanks tanomogi its all good the problem was from
> my imac .. i tried macbook pro all good and
> working maybe the bluetooth wasnt working
> correctly or the file was corrupted dont know but
> the good news its working now
>
>
> thanks
Same issue with no RTE update here.
1. reset settings
2. reboot firmware
3. reboot RTE
4. wait until OSTC goes to sleep
5. start OSTC and enable Bluetooth
After I switched to my Macbook Pro it worked well with Companion beta 8.
So it seems something's going on with bluetooth on iMac which is different to Macbook Pro.
Cheers
Toby
sadsani@gmail.com Wrote:
-------------------------------------------------------
> thanks tanomogi its all good the problem was from
> my imac .. i tried macbook pro all good and
> working maybe the bluetooth wasnt working
> correctly or the file was corrupted dont know but
> the good news its working now
>
>
> thanks