Hijack v292 and "restore visuals"

Hi all,

is only my problem or the Hijack 'restore visuals' does not work in v292?

Make sure that you have set the in-car serial port rate to 115200, and make sure that you have selected the two desired info modes (say, Info:Track and Info:Transient) once from the main menu directly.

I was having similar troubles. You need all these lines in your config.ini

[output]
notify=1
[hijack]
suppress_notify=1
[serial]
car_rate=115200

I didn't have the notify=1 line I think.

How about this for a feature? In Hijack, if you try to turn on Restore Visuals, if the necessary settings aren't there, it just warns you on the screen. So no one else has this problem in the future.

Note that although notify=1 is required, only one of the other two (either suppress_notify or car_rate) is required.

Thanks tfabris and Shonky, I left the bbs for a while and sure I missed these settings.
Tomorrow I'll put it in my config.ini

Thanks

Isn't the requirement for these lines a hijack bug (no offense intended Mark ;-) ? What if you want to use a device on the serial port in the car that doesn't run at 115200 (gps for example)? You won't be able to with that config.

-Mike

What if you want to use a device on the serial port in the car that doesn't run at 115200 (gps for example)? You won't be able to with that config.

Incorrect. As I stated before, you only need either the suppress_notify option or the car_rate option.

If you have a slow serial device, then only do the first option.

In reply to:

---

Incorrect. As I stated before, you only need either the suppress_notify option or the car_rate option.

---

Actually that is not correct (at least not for me). I tried it with suppress_notify but not car_rate and it did not work. As soon as I added car_rate it started to work as expected. I am a few versions of hijack out of date though so maybe that got fixed already.

-Mike

Interesting.

Oh well, moot point now that he's redone the code again. Supposedly the new version doesn't require any particular config settings at all. We'll see how it pans out in long-term usage.

an interesting oddity that i've found. i'm running b13 and hijack293.

i use the long button press - menu button on the deck itself to switch between a visual and track info. if i turn on the (properly setup) restore visuals feature... even if i was on track info, it reverts to the visual. i can go back to track by doing the long button press...

instead of switching to visuals manually, gotta do the opposite and switch manually to track info. pretty funny once you think about it.

Okay so, maybe its just me but restore visuals in 293 with no config does NOT work. Has anyone else experienced the same?

Yes, this was discussed in another thread. Someone else said they still needed to speed up the in-car serial port to make it work.

Uhm, okay.
Dumb question. Open to all

Since I have NOT YET installed my player, I have yet to run it in 'DC' mode, so haven't had to mess with this part of the player yet.

In short, what the heck does the 'notify' and 'car_speed' have to do with the - ooh, lightening - Restore Visuals? I mean, why the link to begin with?

Me, typing in a storm.

As I understand it, notify was (is?) required so that Hijack can see when the player application has started enough to be able to send it a signal to ``restore visuals''. It does this by watching the notify data that the application spits out of the serial port. However, the default speed of the serial port in the car is 9600 bps, not the 115200 bps that it is on AC power, and that's slow. Sometimes slow enough to mess things up. Making the speed faster (or preventing that data from actually travelling out of the serial port, via suppress_notify) prevents that from happening.

Note that this is all conjecture on my part, but I'm pretty sure that it's at least close to the truth.

I've thought about this a lot at the Cincinnati meet, and I think I know what the dependency is. The serial routines discard data that arrives too quickly to be sent out the serial port, and hijack therefore misses such data. So if the serial rate is too slow, it never sees the patterns it is looking for.

By simply rearranging the code slightly, I can have hijack ALWAYS look at the data, before it gets discarded. Hopefully this will eliminate the dependency.

The theoretical untested fix is in now in for v295, to be released shortly.

Cheers