Due to site maintenance, Forum interaction has been disabled until August 13. For support, please search existing forum posts or check the support page.
WunderLINQ
Quote from Gunter on June 15, 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 June 15, 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 June 15, 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 June 15, 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 Gunter on June 15, 2021, 07:19Yes, using play/pause does indeed reset the timer.
Yes, using play/pause does indeed reset the timer.
Quote from Guido on June 15, 2021, 08:19OK. Thanks. I'll keep you posted.
OK. Thanks. I'll keep you posted.
Quote from idebide on June 20, 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.
