Custom Firmware Thread: *RELEASED* Ver 1.1.1aE [DR500GW-HD]
- Thread starter jsan
- Start date
dashuser
Member
- Joined
- Jun 20, 2013
- Messages
- 64
- Reaction score
- 1
- Country
- Germany
- Dash Cam
- LS300W, 808 #16 v2 Lens D
Re: Custom Firmware Thread: *RELEASED* Ver 1.1.1aE [DR500GW-
I did not change this settings.
In manual there is not written that I need to set it to 0.
I think
is not working.
Could anyone please check this?
It take the setting from normal config.ini with the same name.
I did not change this settings.
Code:
Video=2I think
Code:
Volume=95%Could anyone please check this?
It take the setting from normal config.ini with the same name.
Re: Custom Firmware Thread: *RELEASED* Ver 1.1.1aE [DR500GW-
A proper setting is
, without the % symbol.
Did you safe your configuration (using _SAVECFG_) before entering to the FAST mode?dashuser said:
What do you mean, could you clarify please?dashuser said:
A proper setting is
Code:
VOLUME=95
mollydog
Well-Known Member
Re: Custom Firmware for DR500GW-HD | Higher bitrate | No sta
sure hope you guys will be paying him a good amount for all his hard work you are going to learn from.[/quote]
I hope so too, I was going to dump this DR500 as the image quality just wasn't up yo it for the price Blackvue were asking for it, I got hold of a $60 cheap DVR that produced images just as good as this DR500 for much less money, Blackvue should be paying Mio for all his R & D he's been doing for Blackvue
sure hope you guys will be paying him a good amount for all his hard work you are going to learn from.[/quote]
I hope so too, I was going to dump this DR500 as the image quality just wasn't up yo it for the price Blackvue were asking for it, I got hold of a $60 cheap DVR that produced images just as good as this DR500 for much less money, Blackvue should be paying Mio for all his R & D he's been doing for Blackvue
dashuser
Member
- Joined
- Jun 20, 2013
- Messages
- 64
- Reaction score
- 1
- Country
- Germany
- Dash Cam
- LS300W, 808 #16 v2 Lens D
Re: Custom Firmware Thread: *RELEASED* Ver 1.1.1aE [DR500GW-
No, I didn't safe the configuration with _SAVECFG_
Why should I do this? From where did you know?
I suggested that the % is wrong.
But it is part of the original file! Please open your rar archive and have a look at config-custom.ini.
You will see the % there.
Maybe they know about it and has to be there. Maybe not ... :?:
config-custom.ini
config.ini
//
I removed the % from config-custom.ini and started the camera. Its still loading the setting from config.ini
Why are there 2 "Volume" settings? Are they the same? One is in config.ini and one in config-custom.ini
No, I didn't safe the configuration with _SAVECFG_
Why should I do this? From where did you know?
I suggested that the % is wrong.
But it is part of the original file! Please open your rar archive and have a look at config-custom.ini.
You will see the % there.
Maybe they know about it and has to be there. Maybe not ... :?:
config-custom.ini
config.ini
//
I removed the % from config-custom.ini and started the camera. Its still loading the setting from config.ini
Why are there 2 "Volume" settings? Are they the same? One is in config.ini and one in config-custom.ini
ave123
New Member
Re: Custom Firmware Thread: *RELEASED* Ver 1.1.1aE [DR500GW-
Yes, really we didn't correct documentation. All settings, except settings of video are ignored, and everything, as for video - works. And that is why. The matter is that English-language firmware versions jumped at once with custom-1.005 on custom-1.1.1a, and Russian-language (intermediate) versions was at least two more: 1.1.0 and 1.1.1. In 1.1.0 FAST mode really sharply I accelerated loading time, but starting with version 1.1.1 all procedures were copied and optimized so special need for the FAST mode disappeared and practically nobody uses it. Documentation, unfortunately I didn't correct.
dashuser said:
Yes, really we didn't correct documentation. All settings, except settings of video are ignored, and everything, as for video - works. And that is why. The matter is that English-language firmware versions jumped at once with custom-1.005 on custom-1.1.1a, and Russian-language (intermediate) versions was at least two more: 1.1.0 and 1.1.1. In 1.1.0 FAST mode really sharply I accelerated loading time, but starting with version 1.1.1 all procedures were copied and optimized so special need for the FAST mode disappeared and practically nobody uses it. Documentation, unfortunately I didn't correct.
Mio
Active Member
- Joined
- Feb 4, 2013
- Messages
- 253
- Reaction score
- 2
- Country
- Ukraine
- Dash Cam
- Xiaomi Mijia Car DVR & Xiaomi 70Mai
Re: Custom Firmware Thread: *RELEASED* Ver 1.1.1aE [DR500GW-
dashuser I do not understand what you want
viewtopic.php?f=6&t=669&start=760#p17967
_SAVECFG_ - saves all of your settings.
When formatting flashcards, all these settings will be loaded on flashcards
dashuser I do not understand what you want
viewtopic.php?f=6&t=669&start=760#p17967
_SAVECFG_ - saves all of your settings.
When formatting flashcards, all these settings will be loaded on flashcards
Last edited by a moderator:
ave123
New Member
Re: Custom Firmware Thread: *RELEASED* Ver 1.1.1aE [DR500GW-
the "%" sign in the configuration file is established correctly! It isn't necessary to confuse the configuration config.ini and custom-config.ini files
dashuser said:
the "%" sign in the configuration file is established correctly! It isn't necessary to confuse the configuration config.ini and custom-config.ini files
Re: Custom Firmware Thread: *RELEASED* Ver 1.1.1aE [DR500GW-
dashuser ok, I see
RAGY just click on Mio name on the left from any of his post to see his profile, and use the PM:Send private message link to send a request for a custom firmware.
dashuser ok, I see
RAGY just click on Mio name on the left from any of his post to see his profile, and use the PM:Send private message link to send a request for a custom firmware.
dashuser
Member
- Joined
- Jun 20, 2013
- Messages
- 64
- Reaction score
- 1
- Country
- Germany
- Dash Cam
- LS300W, 808 #16 v2 Lens D
Re: Custom Firmware Thread: *RELEASED* Ver 1.1.1aE [DR500GW-
Bootup time with custom firmware is exactly 37 seconds.
What I mean:
Power on -> 37 secs later -> video beginns
Tested with a timer im front of the camera and startet both at the same time.
Bootup time with custom firmware is exactly 37 seconds.
What I mean:
Power on -> 37 secs later -> video beginns
Tested with a timer im front of the camera and startet both at the same time.
ave123
New Member
Re: Custom Firmware Thread: *RELEASED* Ver 1.1.1aE [DR500GW-
Business is so. In official firmware from the moment of inclusion of a food and until start of dashcam the minimum of diagnostic messages, including at the time of software updating is played. Thus the loudness of these messages is fixed and the VOLUME parameter from the config.ini file you can already regulate loudness when actually dashcam already works.
In castes of firmware the set of additional diagnostic reports, for example, at the time of the firmware updating is provided. Due to the ey the decision to regulate the loudness of these messages independently (in the config-custom.ini file) from what are lost by the supervisor of the dashcam was made.
dashuser said:
Business is so. In official firmware from the moment of inclusion of a food and until start of dashcam the minimum of diagnostic messages, including at the time of software updating is played. Thus the loudness of these messages is fixed and the VOLUME parameter from the config.ini file you can already regulate loudness when actually dashcam already works.
In castes of firmware the set of additional diagnostic reports, for example, at the time of the firmware updating is provided. Due to the ey the decision to regulate the loudness of these messages independently (in the config-custom.ini file) from what are lost by the supervisor of the dashcam was made.
RAGY
New Member
- Joined
- May 11, 2013
- Messages
- 27
- Reaction score
- 1
- Country
- Singapore
- Dash Cam
- BlackVue DR550GW
Re: Custom Firmware Thread: *RELEASED* Ver 1.1.1aE [DR500GW-
So do I format my SD card, unzip the file, copy and paste the blackvue folder into the SD card then boot it to my Blackvue?
So do I format my SD card, unzip the file, copy and paste the blackvue folder into the SD card then boot it to my Blackvue?
Re: Custom Firmware Thread: *RELEASED* Ver 1.1.1aE [DR500GW-
Help !!!
I faced this issue of occasional "hang" at after the initial power-up "chime" sound with just the blue GPS LED on. It does not reach the state where the voice says "blackvue is ready........" and orange led starts blinking and I need to do a reset.
It happens maybe once every 4 times I start the car.
Anyone knows what could be wrong? (Formated SD card, same..)
Mio: Is there any ssh or telnet that I can login to BV to see where it hang?
Thank everyone.
Help !!!
I faced this issue of occasional "hang" at after the initial power-up "chime" sound with just the blue GPS LED on. It does not reach the state where the voice says "blackvue is ready........" and orange led starts blinking and I need to do a reset.
It happens maybe once every 4 times I start the car.
Anyone knows what could be wrong? (Formated SD card, same..)
Mio: Is there any ssh or telnet that I can login to BV to see where it hang?
Thank everyone.
Re: Custom Firmware for DR500GW-HD | Higher bitrate | No sta
Getting my DR-500 hardwired tomorrow so haven't' installed it yet, Mio.
I think everyone should send Mio and his team a little contribution on PayPal for their hard work! :idea:
Welcome to the forum, Blackvue, and thanks for your participation!BlackVue said:
Getting my DR-500 hardwired tomorrow so haven't' installed it yet, Mio.
I think everyone should send Mio and his team a little contribution on PayPal for their hard work! :idea:
dashuser
Member
- Joined
- Jun 20, 2013
- Messages
- 64
- Reaction score
- 1
- Country
- Germany
- Dash Cam
- LS300W, 808 #16 v2 Lens D
Re: Custom Firmware Thread: *RELEASED* Ver 1.1.1aE [DR500GW-
I had two cameras before and they were not that warm/hot.
I know that 60°C are not extremely much. But for example a modern cpu from intel (core i5) has an specification of 72,6°C.
And the gab between 60 and 72 isnt that big.
I only what to know what part of the camera is causing the heat. My Samsung S3 has a quite good cpu and never gets so warm. Tough it has no ventilations holes.
//
Here are my suggestions for pittasoft about the dr500:
- the ring around the lens should be black (attracting attention is unwanted)
- the wide angle is too wide. thats too just to much. One quarter of the image is my dashboard and another quarter is the above sky.
- try to make the camera more efficient without producing so much heat (my two old cams (Aiptek X3, Rollei 110) were much cooler), the dr400 has a bad reputation because these problems.
- higher the bitrate! (a lot of people are complaining about the poor video quality, see amazon comments and other reviews at youtube and so on; there IS a reason why someone is making his own firmware) Try to learn from that.
- support sd-cards with higher capacity (in 2013 there should be no 32gb limit)
- license plates are hard to read (because the extrem wide angle?)
I can not understand why you set the bitrate to only 7,5 kbits. You know what people see:
They see that the video quality is very poor and will never buy a blackvue camera again. (Also they do not recommend your products and write negative reviews.)
Pittasoft can benefit from the users suggestions. Because they are the users (and they also buy your products).
Hillbilly said:
I had two cameras before and they were not that warm/hot.
I know that 60°C are not extremely much. But for example a modern cpu from intel (core i5) has an specification of 72,6°C.
And the gab between 60 and 72 isnt that big.
I only what to know what part of the camera is causing the heat. My Samsung S3 has a quite good cpu and never gets so warm. Tough it has no ventilations holes.
//
Here are my suggestions for pittasoft about the dr500:
- the ring around the lens should be black (attracting attention is unwanted)
- the wide angle is too wide. thats too just to much. One quarter of the image is my dashboard and another quarter is the above sky.
- try to make the camera more efficient without producing so much heat (my two old cams (Aiptek X3, Rollei 110) were much cooler), the dr400 has a bad reputation because these problems.
- higher the bitrate! (a lot of people are complaining about the poor video quality, see amazon comments and other reviews at youtube and so on; there IS a reason why someone is making his own firmware) Try to learn from that.
- support sd-cards with higher capacity (in 2013 there should be no 32gb limit)
- license plates are hard to read (because the extrem wide angle?)
I can not understand why you set the bitrate to only 7,5 kbits. You know what people see:
They see that the video quality is very poor and will never buy a blackvue camera again. (Also they do not recommend your products and write negative reviews.)
Pittasoft can benefit from the users suggestions. Because they are the users (and they also buy your products).
