Karel

My problem with SSEM messages was caused by me incorrectly filling the regional structures, of course. So that works correctly. However, I discovered another problem, there is a name collision...

I made renaming of `IssuerIdentifier_t` to pull request #180 on your new branch. I am able to encode/decode SREM, SSEM and IVIM messages on Craton/Secton devices now, so from my...

Note that `socktap` now does not work as stated [here](https://github.com/riebl/vanetza/issues/192#issuecomment-1671666667). After recent security changes, it cannot be compiled in the base repository either.

After your fix, I've tried `socktap` on Secton and Craton and it is working well.

asn1c version ebed0802c (https://github.com/mouse07410/asn1c/commit/ebed802c88b3049cfe67326e4df780cefc6da49e) (I noticed @riebl uses it) seems to work correctly, so I am closing this issue.

Sorry, I haven't used GPSD on Craton, but is it really necessary? I have created AutotalksGps module, that created a thread that was fetching the GPS data using the Autotalks...

No, it is not necessary. You can build socktap without support for GPSD. Does the example run when you try to use static position? I do not know what exact...

> I left `-p gpsd` out because after compiling with DSOCKTAP_WITH_GPSD=ON this is the default. Oh okay, I did not notice that, sorry. I think you should not use GPSD...

Hi @lo-hei, when I tested communication on a road with real devices, I recall that I encountered two problems that I could solve: - In the device, time must be...

@firolino Thanks for quick and hopeful response! I will look forward to the release.