WunderLINQ
Quote from Gunter on 10.06.2021, 07:37Hi Guido,
I use Scenic for quite some years now and love its versatility.
I use it offroad with tracks and onroad with routes.
Recently I started using WunderLINQ for a hobby project.
During testing, we discovered some issues regarding the detection and use of WunderLINQ.
- The glow around the buttons only occurs when Scenic gets the foreground. E.g. after switching to a different app and back or going to the homescreen and back to Scenic. Scenic doesn’t enable the glow when WunderLINQ is detected.
- The message “WunderLINQ connected” is only displayed if you first start Scenic and then switch-on the device. When the device is switched on before Scenic is started, there is no mention that WunderLINQ is connected or working.
So basically, to get WunderLINQ working, I have to execute following steps:
- start Scenic
- power on WunderLINQ
- go to homescreen
- start Scenic again
Another issue concerns the timeout on the button-screen. The time to find the correct button is too short or maybe I’m too slow, it gives me stress. 🙂 Twice the time would be nice, or maybe reset the time on key press?
I’m using the latest Scenic version 2.3.9
Keep up the good work and looking foreward to version 3!
Gunter
Hi Guido,
I use Scenic for quite some years now and love its versatility.
I use it offroad with tracks and onroad with routes.
Recently I started using WunderLINQ for a hobby project.
During testing, we discovered some issues regarding the detection and use of WunderLINQ.
- The glow around the buttons only occurs when Scenic gets the foreground. E.g. after switching to a different app and back or going to the homescreen and back to Scenic. Scenic doesn’t enable the glow when WunderLINQ is detected.
- The message “WunderLINQ connected” is only displayed if you first start Scenic and then switch-on the device. When the device is switched on before Scenic is started, there is no mention that WunderLINQ is connected or working.
So basically, to get WunderLINQ working, I have to execute following steps:
- start Scenic
- power on WunderLINQ
- go to homescreen
- start Scenic again
Another issue concerns the timeout on the button-screen. The time to find the correct button is too short or maybe I’m too slow, it gives me stress. 🙂 Twice the time would be nice, or maybe reset the time on key press?
I’m using the latest Scenic version 2.3.9
Keep up the good work and looking foreward to version 3!
Gunter
Quote from Guido on 10.06.2021, 08:57Hi Gunter,
Thanks for letting me know. I didn't know about these issues, but will take a look as part of Scenic 3. For the timing... the timer restarts when you simply move to another button (you don't have to select it). So, if you're running out of time just push the wheel to the right and you'll have more time. Do you think that will help? I don't want to make this timer too long as it will block the map for all that time.
Cheers,
Guido
Hi Gunter,
Thanks for letting me know. I didn't know about these issues, but will take a look as part of Scenic 3. For the timing... the timer restarts when you simply move to another button (you don't have to select it). So, if you're running out of time just push the wheel to the right and you'll have more time. Do you think that will help? I don't want to make this timer too long as it will block the map for all that time.
Cheers,
Guido
Quote from Gunter on 10.06.2021, 15:03Thank you Guido for the quick response.
I was expecting that the timer would reset when moving to another button, but it doesn't. It's not that big of a problem, I'll wait till version 3...
To be fair, I'm not exactly using WunderLINQ but an own-made (actually my colleague's work) Bluetooth LE controller which emulates a WunderLINQ. Maybe someone who owns a WunderLINQ can confirm these findings?
Kind regards,
Gunter
Thank you Guido for the quick response.
I was expecting that the timer would reset when moving to another button, but it doesn't. It's not that big of a problem, I'll wait till version 3...
To be fair, I'm not exactly using WunderLINQ but an own-made (actually my colleague's work) Bluetooth LE controller which emulates a WunderLINQ. Maybe someone who owns a WunderLINQ can confirm these findings?
Kind regards,
Gunter
Quote from Guido on 10.06.2021, 15:13OK. Yes... that would be great if someone could confirm this. I haven't heard this before, so maybe it's because of the home-made version.
@steady-eddie, @jvloyola, @idebide, do you have this same problem that's described above?
OK. Yes... that would be great if someone could confirm this. I haven't heard this before, so maybe it's because of the home-made version.
@steady-eddie, @jvloyola, @idebide, do you have this same problem that's described above?
Quote from Gunter on 10.06.2021, 17:35Hi Guido,
Someone brought to my attention one of your video's in which you can see the time-out not resetting.
https://youtu.be/DfxxBqZB3AE?t=80
Maybe you changed the behavior and the video is a little dated?
Kind regards,
Gunter
Hi Guido,
Someone brought to my attention one of your video's in which you can see the time-out not resetting.
https://youtu.be/DfxxBqZB3AE?t=80
Maybe you changed the behavior and the video is a little dated?
Kind regards,
Gunter
Quote from Guido on 10.06.2021, 17:39Video is dated yes, but I got confused. The timer resets when you TAP/select a button (like the play/pause button). I will add for the next update that the time resets when you move to another button with the wunderlinq.
Video is dated yes, but I got confused. The timer resets when you TAP/select a button (like the play/pause button). I will add for the next update that the time resets when you move to another button with the wunderlinq.
Quote from Gunter on 10.06.2021, 18:04Great, that would be nice. Thank you Guido.
If you need a beta-tester, I have TestFlight installed 😉
Kind regards,
Gunter
Great, that would be nice. Thank you Guido.
If you need a beta-tester, I have TestFlight installed 😉
Kind regards,
Gunter
Quote from Guido on 12.06.2021, 13:15While I started working on this, I noticed it should already work like that. It shouldn't matter if you are using a "home-made Wunderlinq". As long as you see the selected button changing, the timer should reset as well whenever you the selected button is changed with WunderLINQ. See this screen capture:
Could you confirm this works for you as well? If not, check the Scenic version you are running (at the bottom of the Settings tab). Latest version is v2.3.9. If you're running an older version, update through the App Store.
In the upcoming update I will add a little bit more time just in case.
While I started working on this, I noticed it should already work like that. It shouldn't matter if you are using a "home-made Wunderlinq". As long as you see the selected button changing, the timer should reset as well whenever you the selected button is changed with WunderLINQ. See this screen capture:
Could you confirm this works for you as well? If not, check the Scenic version you are running (at the bottom of the Settings tab). Latest version is v2.3.9. If you're running an older version, update through the App Store.
In the upcoming update I will add a little bit more time just in case.
Quote from Gunter on 13.06.2021, 13:08Hi Guido,
I'm using Version 2.3.9
As you can see in the screen capture, the timer does not reset. You can also see that the glow is not appearing when WunderLINQ is connected. I need to go to the homescreen and and back in order to get it working.
Hi Guido,
I'm using Version 2.3.9
As you can see in the screen capture, the timer does not reset. You can also see that the glow is not appearing when WunderLINQ is connected. I need to go to the homescreen and and back in order to get it working.
Quote from Guido on 13.06.2021, 13:53Very weird it’s not working for you and it is for me 🤔 I’ll have another look before I release version 2.4.0.
Very weird it’s not working for you and it is for me 🤔 I’ll have another look before I release version 2.4.0.
Quote from Gunter on 15.06.2021, 03:57Yesterday I did a test with an iPad Mini.
I first update Scenic and iPadOS to the latest version. Then paired WunderLINQ with iPad and verified that the “keys” work in iPadOS.
Started Scenic and enable “I have a WunderLINQ”. Powered-up WunderLINQ and…
…nothing, I couldn’ get it to work, no “WunderLINQ connected” message, no glow around keys.
Just out of curiosity Guido, how do you test WunderLINQ? Is it with a real device or are you using a keyboard?
Yesterday I did a test with an iPad Mini.
I first update Scenic and iPadOS to the latest version. Then paired WunderLINQ with iPad and verified that the “keys” work in iPadOS.
Started Scenic and enable “I have a WunderLINQ”. Powered-up WunderLINQ and…
…nothing, I couldn’ get it to work, no “WunderLINQ connected” message, no glow around keys.
Just out of curiosity Guido, how do you test WunderLINQ? Is it with a real device or are you using a keyboard?
Quote from Guido on 15.06.2021, 04:21Since I don’t have my BMW anymore, like you, I use a device that emulates a keyboard. But, the strange thing is that I have not received any other feedback about this connectivity issue. And it also works for me all the time. So, I almost have to assume it’s something in your setup.
the timer not resetting is even weirder. Because, in the code, even before the focus is moved to the next button, the timer is reset. So, it doesn’t matter what device you are using for that. If the focus moves, the code to reset the timer was called, 100% sure.
yesterday Scenic 2.4.0 was released. Could have been after you tried this. Any luck with that? In any case I increased the timer there with 2 seconds more.
Since I don’t have my BMW anymore, like you, I use a device that emulates a keyboard. But, the strange thing is that I have not received any other feedback about this connectivity issue. And it also works for me all the time. So, I almost have to assume it’s something in your setup.
the timer not resetting is even weirder. Because, in the code, even before the focus is moved to the next button, the timer is reset. So, it doesn’t matter what device you are using for that. If the focus moves, the code to reset the timer was called, 100% sure.
yesterday Scenic 2.4.0 was released. Could have been after you tried this. Any luck with that? In any case I increased the timer there with 2 seconds more.
Quote from Gunter on 15.06.2021, 06:28I updated today to ver 2.4.0 and alas, same results.
Is there a way to get some sort of debug information?
I updated today to ver 2.4.0 and alas, same results.
Is there a way to get some sort of debug information?
Quote from Guido on 15.06.2021, 07:03No. Let me test with my neighbor’s actual WunderLINQ. He’s on holiday now so will take some time.
2.4.0 has a 2 second longer delay so that at least should give you a bit more time to select the right button.
There is one thing you can test… if you use the play/pause button or next/prev button, does the timer reset? It should.
No. Let me test with my neighbor’s actual WunderLINQ. He’s on holiday now so will take some time.
2.4.0 has a 2 second longer delay so that at least should give you a bit more time to select the right button.
There is one thing you can test… if you use the play/pause button or next/prev button, does the timer reset? It should.
Quote from Guido on 15.06.2021, 08:19OK. Thanks. I'll keep you posted.
OK. Thanks. I'll keep you posted.
Quote from idebide on 20.06.2021, 14:37Quote from Guido on June 10, 2021, 15:13OK. Yes... that would be great if someone could confirm this. I haven't heard this before, so maybe it's because of the home-made version.
@steady-eddie, @jvloyola, @idebide, do you have this same problem that's described above?
I tested scenic 2 wrt scenic reportedly not being connected if it is started after Wunderlinq and I don't see the behavior reported. I started Wunderlinq, noted the bluetooth was connected, and then started Scenic and the buttons highlighted normally and worked (with the bike selector in Nav mode). It is true that I did not see a "Wunderlinq detected" message when Scenic started but everything worked as expected.
Quote from Guido on June 10, 2021, 15:13OK. Yes... that would be great if someone could confirm this. I haven't heard this before, so maybe it's because of the home-made version.
@steady-eddie, @jvloyola, @idebide, do you have this same problem that's described above?
I tested scenic 2 wrt scenic reportedly not being connected if it is started after Wunderlinq and I don't see the behavior reported. I started Wunderlinq, noted the bluetooth was connected, and then started Scenic and the buttons highlighted normally and worked (with the bike selector in Nav mode). It is true that I did not see a "Wunderlinq detected" message when Scenic started but everything worked as expected.