Deleted
Deleted Member
Posts: 0
|
0.9.4
Jun 20, 2018 20:42:48 GMT
Post by Deleted on Jun 20, 2018 20:42:48 GMT
Manuals builder (Can create own manuals) LINKYou are now able to build you own manual - not sure if its shared with other users - Admin can you confirm please In the old version under garage and your car you had an option called manuals but it normally said your car does not have any. Now it can I will create a how to document during the week.
Wallet (View credit transactions history) linkI will update the Credit Process document during the week but as you can see what used to be the credit screen now shows you the above. If you hit the green plus sign then you will get the old (buy credits or apply for free credits) - more later
Account management (now can change email, password and link accounts)
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jun 21, 2018 8:13:24 GMT
One small change that has been added as part of the Wallet function If you have got your daily number of credits on the previous version you hit the no more free credits today option and it just closed the screen Now you get an error message Time Not Passed, dont see the need for that warning as i have already selected the option. please note this is not a major issue just pointing it out, there are still Climatronic ECU connection issues from 0.9.3.7 along with tomtee issue from 0.9.3.4
|
|
Deleted
Deleted Member
Posts: 0
|
0.9.4
Jun 21, 2018 8:33:48 GMT
Post by Deleted on Jun 21, 2018 8:33:48 GMT
New Manual feature is very helpful thanks, however if you check out the attached vid you will see if you enter lots of data or go to update the manual then the save button is no longer shown, if you scroll to top of the screen it comes back but it would be helpful if it stayed on the screen and maybe move the position so that it does not hide the text box. Also if you do get round to doing any changes can you enable hyperlinking please, we all have lots of info that is already saved on the web and it would be good to just link to that data.
Low Priority change - fix the outstanding bugs please
|
|
|
0.9.4
Jun 21, 2018 13:52:03 GMT
Post by Martynas Šileika on Jun 21, 2018 13:52:03 GMT
New Manual feature is very helpful thanks, however if you check out the attached vid you will see if you enter lots of data or go to update the manual then the save button is no longer shown, if you scroll to top of the screen it comes back but it would be helpful if it stayed on the screen and maybe move the position so that it does not hide the text box. Also if you do get round to doing any changes can you enable hyperlinking please, we all have lots of info that is already saved on the web and it would be good to just link to that data.
Low Priority change - fix the outstanding bugs please
Hi cupra280, You dont have to go to top of the screen to see save button, you have to swipe up just a little for button to appear
|
|
|
0.9.4
Jun 21, 2018 13:59:24 GMT
Post by Martynas Šileika on Jun 21, 2018 13:59:24 GMT
Today we have found a car with the same issue on Climate Control units from 0.9.3.7 so we are working on it. For tomtee issue, we are still looking for similar control unit to check what is going wrong. We have to have control unit ourselves to check deeper. We cant check what is going on just with app logs. Maybe tomtee can test his car with other diagnostic tool? Maybe there is an issue with car itself?
|
|
Deleted
Deleted Member
Posts: 0
|
0.9.4
Jun 21, 2018 15:15:19 GMT
Post by Deleted on Jun 21, 2018 15:15:19 GMT
^^^^thanks for the updates
Re the save button, ok get that its just not a very user friendly screen design from my perspective.
|
|
|
0.9.4
Jun 21, 2018 16:00:49 GMT
Post by tomtee on Jun 21, 2018 16:00:49 GMT
Today we have found a car with the same issue on Climate Control units from 0.9.3.7 so we are working on it. For tomtee issue, we are still looking for similar control unit to check what is going wrong. We have to have control unit ourselves to check deeper. We cant check what is going on just with app logs. Maybe tomtee can test his car with other diagnostic tool? Maybe there is an issue with car itself? There are no issues with my car's OBD. The OBD-11 app worked fine until after installing the version 0933 updates. After this update, the app would not connect to either the Engine or ABS modules. You fixed the ABS connection problem which is appreciated. I am still waiting the fix for the Engine module. While I do understand that you do not have a similar control module for testing your fixes there is a work around. That being I am willing to test your fixes on my own car provided there would be no damage to the control unit. It will be much quicker than waiting forever for a similar control unit. I am willing to do whatever it takes to speed the process up including sending another error report. Please think about this and let me know how to proceed. Thank you. Tom
|
|
|
0.9.4
Jun 25, 2018 5:04:18 GMT
Post by Martynas Šileika on Jun 25, 2018 5:04:18 GMT
There are no issues with my car's OBD. The OBD-11 app worked fine until after installing the version 0933 updates. After this update, the app would not connect to either the Engine or ABS modules. You fixed the ABS connection problem which is appreciated. I am still waiting the fix for the Engine module. While I do understand that you do not have a similar control module for testing your fixes there is a work around. That being I am willing to test your fixes on my own car provided there would be no damage to the control unit. It will be much quicker than waiting forever for a similar control unit. I am willing to do whatever it takes to speed the process up including sending another error report. Please think about this and let me know how to proceed. Thank you. Tom Tom, we appreciate your help, but in this situation we need to check what's happening directly on diagnostic data line before our device and it requires specific hardware to do it.
|
|
|
0.9.4
Jun 25, 2018 12:37:15 GMT
Post by tomtee on Jun 25, 2018 12:37:15 GMT
There are no issues with my car's OBD. The OBD-11 app worked fine until after installing the version 0933 updates. After this update, the app would not connect to either the Engine or ABS modules. You fixed the ABS connection problem which is appreciated. I am still waiting the fix for the Engine module. While I do understand that you do not have a similar control module for testing your fixes there is a work around. That being I am willing to test your fixes on my own car provided there would be no damage to the control unit. It will be much quicker than waiting forever for a similar control unit. I am willing to do whatever it takes to speed the process up including sending another error report. Please think about this and let me know how to proceed. Thank you. Tom Tom, we appreciate your help, but in this situation we need to check what's happening directly on diagnostic data line before our device and it requires specific hardware to do it. Martynas, I understand completely. But you must understand that it was your code that was introduced with 0933 which caused the problems in the first place. It has been over two months now with no way to scan the Engine module. It is frustrating to purchase a working product then to not have it work anymore. Please make the old version available here for me and me only to download. At least this will get the app working so I can move forward with my scans. Thank you. Tom
|
|
|
0.9.4
Jun 26, 2018 10:57:13 GMT
Post by Martynas Šileika on Jun 26, 2018 10:57:13 GMT
Today we have released a firmware update which should fix issue regarding to Climate Control units. Also tomtee could you try to connect to your vehicle? We have done a little change and want to know you response.
|
|
|
Post by tomtee on Jun 26, 2018 12:35:11 GMT
Today we have released a firmware update which should fix issue regarding to Climate Control units. Also tomtee could you try to connect to your vehicle? We have done a little change and want to know you response. Martynas - was this update posted and available at the Play Store?
|
|
Deleted
Deleted Member
Posts: 0
|
0.9.4
Jun 26, 2018 12:49:07 GMT
Post by Deleted on Jun 26, 2018 12:49:07 GMT
tomtee, Just log on and you will get the following screen
There is no version release just the interface.
|
|
|
0.9.4
Jun 26, 2018 13:46:40 GMT
Post by tomtee on Jun 26, 2018 13:46:40 GMT
Today we have released a firmware update which should fix issue regarding to Climate Control units. Also tomtee could you try to connect to your vehicle? We have done a little change and want to know you response. I updated my device but the software still shows no faults in the Engine module. Either the updates were not successful or the one fault disappeared. Please let me know how to proceed from here. Thanks for the support!
|
|
|
0.9.4
Jun 27, 2018 5:59:18 GMT
Post by Martynas Šileika on Jun 27, 2018 5:59:18 GMT
I updated my device but the software still shows no faults in the Engine module. Either the updates were not successful or the one fault disappeared. Please let me know how to proceed from here. Thanks for the support! If update were failed you wont be able to proceed further. Yesterday and today we have tested a lot vehicles which using K-Line for diagnostics and no problems found. Could you confirm that the fault is still present in your vehicle? Maybe there is no fault and we are looking for nothing?
|
|
|
0.9.4
Jun 27, 2018 13:37:37 GMT
Post by tomtee on Jun 27, 2018 13:37:37 GMT
I updated my device but the software still shows no faults in the Engine module. Either the updates were not successful or the one fault disappeared. Please let me know how to proceed from here. Thanks for the support! If update were failed you wont be able to proceed further. Yesterday and today we have tested a lot vehicles which using K-Line for diagnostics and no problems found. Could you confirm that the fault is still present in your vehicle? Maybe there is no fault and we are looking for nothing? I created a fault by disconnecting the throttle position sensor connector from the sensor with the engine running. This should have produced VAG code 00518. Despite several attempts of a scan with OBDEleven, the software was still showing no faults when at least the 00518 error code should have been displayed on the OBD11 app. IMO you still have a bug in your software. It worked fine until version 0933 was downloaded and installed. Update for you. I was able to pull the OBD blink codes by using an LED light plugged into the ABS light cluster. One of the error codes was 2212 which corresponds to VAG fault code 00518 - Throttle Position Sensor. By displaying the blink codes it rules out anything wrong with the K-line diagnostics in the car. Therefore the problem with OBDEleven showing no faults in the Engine Module is due to a bug in the OBDEleven app. Update #2 After clearing the app data and cache from my mobile device, another scan attempt was made with the same result. Therefore I generated an error report titled "Engine Module". Perhaps this new report will shed a little more light into the cause of the problem accessing the engine module. Please let me know if you need more info and thanks again for your support. Update #3 Live data from the Engine Module is working. So it is the diagnostic error codes that are not displaying on the app.
|
|
|
0.9.4
Jun 28, 2018 7:19:20 GMT
Post by Martynas Šileika on Jun 28, 2018 7:19:20 GMT
I created a fault by disconnecting the throttle position sensor connector from the sensor with the engine running. This should have produced VAG code 00518. Despite several attempts of a scan with OBDEleven, the software was still showing no faults when at least the 00518 error code should have been displayed on the OBD11 app. IMO you still have a bug in your software. It worked fine until version 0933 was downloaded and installed. Update for you. I was able to pull the OBD blink codes by using an LED light plugged into the ABS light cluster. One of the error codes was 2212 which corresponds to VAG fault code 00518 - Throttle Position Sensor. By displaying the blink codes it rules out anything wrong with the K-line diagnostics in the car. Therefore the problem with OBDEleven showing no faults in the Engine Module is due to a bug in the OBDEleven app. Update #2 After clearing the app data and cache from my mobile device, another scan attempt was made with the same result. Therefore I generated an error report titled "Engine Module". Perhaps this new report will shed a little more light into the cause of the problem accessing the engine module. Please let me know if you need more info and thanks again for your support. Update #3 Live data from the Engine Module is working. So it is the diagnostic error codes that are not displaying on the app. Thank you for you response. the fact that you can blink error codes doesn't mean that it can be read with diagnostics. We have checked entire faults reading routine prior 0.9.3.3 version and current version and don't see much differences. Could you try enter faults menu and try refresh faults multiple times with few seconds pause between refresh? Maybe the request made to fast after initiating diagnostics and control unit is not ready to provide fault list. Another assumption maybe something went wrong to your engine control module and it cant provide faults list, some internal failure? This is just my assumption. It is very strange behavior even that you can connect to it normally and see info and live data. It would be very helpful if you could try read faults with other diagnostic tool.
|
|
|
0.9.4
Jun 28, 2018 16:57:08 GMT
Post by tomtee on Jun 28, 2018 16:57:08 GMT
I created a fault by disconnecting the throttle position sensor connector from the sensor with the engine running. This should have produced VAG code 00518. Despite several attempts of a scan with OBDEleven, the software was still showing no faults when at least the 00518 error code should have been displayed on the OBD11 app. IMO you still have a bug in your software. It worked fine until version 0933 was downloaded and installed. Update for you. I was able to pull the OBD blink codes by using an LED light plugged into the ABS light cluster. One of the error codes was 2212 which corresponds to VAG fault code 00518 - Throttle Position Sensor. By displaying the blink codes it rules out anything wrong with the K-line diagnostics in the car. Therefore the problem with OBDEleven showing no faults in the Engine Module is due to a bug in the OBDEleven app. Update #2 After clearing the app data and cache from my mobile device, another scan attempt was made with the same result. Therefore I generated an error report titled "Engine Module". Perhaps this new report will shed a little more light into the cause of the problem accessing the engine module. Please let me know if you need more info and thanks again for your support. Update #3 Live data from the Engine Module is working. So it is the diagnostic error codes that are not displaying on the app. Thank you for you response. the fact that you can blink error codes doesn't mean that it can be read with diagnostics. We have checked entire faults reading routine prior 0.9.3.3 version and current version and don't see much differences. Could you try enter faults menu and try refresh faults multiple times with few seconds pause between refresh? Maybe the request made to fast after initiating diagnostics and control unit is not ready to provide fault list. Another assumption maybe something went wrong to your engine control module and it cant provide faults list, some internal failure? This is just my assumption. It is very strange behavior even that you can connect to it normally and see info and live data. It would be very helpful if you could try read faults with other diagnostic tool. After scanning it again & with no faults displayed I went into the faults menu in the Engine Module. After a few attempts of hitting the green button at the bottom right of the screen it finally loaded/displayed engine faults. This finally shows that the controller in the car is working. Perhaps it is slow but still functioning. I was also able to delete the error codes. I ran a few more tests and found that after pressing the green button to reload the Engine Module faults always showed no faults first time through, then after waiting at least 5 seconds, reloading it again would display faults. This was very consistent. The problem of not viewing engine faults could be a timing issue. I noticed several things during my scans including the Engine scan being much much faster than the ABS/Brake scan. The engine scan takes about 5 seconds tops to complete while the ABS/Brake scan takes about 13 seconds to complete. I also noticed that after reloading the engine scans in the faults menu the green light on the OBD11 dongle kept blinking like it was attempting to send data even though the app was idle. The app also hung a few times making it necessary to start over. About your review of the code prior to 0933, as a computer programmer, I can tell you that even the most minute change in a program can lead to unintended consequences. By you saying "don't see much differences" is not the same as no differences. In the prior releases of the app was there any code to deal with slow controllers? What about code to take into account various timing differences between the different modules? My guess is something was omitted in the later releases for some reason. Keep in mind that when I pull the blink codes the two connectors under the shift boot need to be jumped with a wire between 2.5 & 4 seconds to initiate the controller to send blink codes to the MIL lamp. So not only is there a timing to get any faults there is a timing requirement to initiate the controller. Let me know what you think about this & how to proceed. Thank you.
|
|
|
Post by Martynas Šileika on Jun 29, 2018 5:18:33 GMT
After scanning it again & with no faults displayed I went into the faults menu in the Engine Module. After a few attempts of hitting the green button at the bottom right of the screen it finally loaded/displayed engine faults. This finally shows that the controller in the car is working. Perhaps it is slow but still functioning. I was also able to delete the error codes. I ran a few more tests and found that after pressing the green button to reload the Engine Module faults always showed no faults first time through, then after waiting at least 5 seconds, reloading it again would display faults. This was very consistent. The problem of not viewing engine faults could be a timing issue. I noticed several things during my scans including the Engine scan being much much faster than the ABS/Brake scan. The engine scan takes about 5 seconds tops to complete while the ABS/Brake scan takes about 13 seconds to complete. I also noticed that after reloading the engine scans in the faults menu the green light on the OBD11 dongle kept blinking like it was attempting to send data even though the app was idle. The app also hung a few times making it necessary to start over. About your review of the code prior to 0933, as a computer programmer, I can tell you that even the most minute change in a program can lead to unintended consequences. By you saying "don't see much differences" is not the same as no differences. In the prior releases of the app was there any code to deal with slow controllers? What about code to take into account various timing differences between the different modules? My guess is something was omitted in the later releases for some reason. Keep in mind that when I pull the blink codes the two connectors under the shift boot need to be jumped with a wire between 2.5 & 4 seconds to initiate the controller to send blink codes to the MIL lamp. So not only is there a timing to get any faults there is a timing requirement to initiate the controller. Let me know what you think about this & how to proceed. Thank you. Thats good news. now we are clear that it is some timing issues, not communication problems. There are no such timing definitions in protocol standards which deals specifically with such slow controllers. We have done all timing specified in protocols but there are some exceptions like yours which are not documented. In the next update we will fix this problem.
|
|
|
0.9.4
Jun 29, 2018 12:22:32 GMT
Post by tomtee on Jun 29, 2018 12:22:32 GMT
"Thats good news. now we are clear that it is some timing issues, not communication problems. There are no such timing definitions in protocol standards which deals specifically with such slow controllers. We have done all timing specified in protocols but there are some exceptions like yours which are not documented. In the next update we will fix this problem."
I do recall you were surprised of the slow baud rate of my controller. We discussed this in another thread. If you'd like I can post the rate again if it will help.
|
|
|
0.9.4
Jul 2, 2018 5:06:05 GMT
Post by Martynas Šileika on Jul 2, 2018 5:06:05 GMT
I do recall you were surprised of the slow baud rate of my controller. We discussed this in another thread. If you'd like I can post the rate again if it will help. This is not related to the baud rate. If there would be an issue with baud rate you wont be able to communicate at all. By meaning slow controller don't mean slow baud, I mean slow in general. For such controllers normally baud rate is 9600, yours is 9523 which is just a little lower than standard baud. This is why I have been surprised.
|
|