GPIO en Cartwall problem

You found a bug or have any issues? Please post them here!
User avatar
radio42
Site Admin
Posts: 8295
Joined: 05 Apr 2012 16:26
Location: Hamburg, Germany
Contact:
Re: GPIO en Cartwall problem

Post by radio42 »

Anyhow you might try to use the 'Previous Version' of ProppFrexx to see, if that changes the behavior?!

Then we are at least sure, if that caused the trouble or not.
User avatar
radio42
Site Admin
Posts: 8295
Joined: 05 Apr 2012 16:26
Location: Hamburg, Germany
Contact:
Re: GPIO en Cartwall problem

Post by radio42 »

Good news. Thanks for testing.
It seems the latest version of my remote lib had a small glitch. Now that we know what it is, I can work on this one.
User avatar
radio42
Site Admin
Posts: 8295
Joined: 05 Apr 2012 16:26
Location: Hamburg, Germany
Contact:
Re: GPIO en Cartwall problem

Post by radio42 »

An official v4.0.3.32 update is available.
It also contains a fix to the original issue, which was reverted in the .30.

However, I made both ways now configurable by a new 'Sync. Callback' option.
So if you find the time, please test both options .. they now should (hopefully) both work.

Use Synchronous Callbacks:
If enabled, GPIO command results as well as local macros are transmitted back to the server.
This is handled by invoking synchronous callbacks instead of asynchronous calls, which are more performant and non-blocking.
If you need to evaluate local GPIO client macros on the server side (i.e. within ProppFrexx ONAIR) you must enable this option, else you might leave it deactivated.
Changing this option requires a reconnect.
User avatar
Michel67
Posts: 166
Joined: 28 Nov 2016 19:53
Re: GPIO en Cartwall problem

Post by Michel67 »

If I enable Synchronous Callbacks then my Airlite does not enter any command in PF, so disabled and restart
User avatar
Michel67
Posts: 166
Joined: 28 Nov 2016 19:53
Re: GPIO en Cartwall problem

Post by Michel67 »

yes :D
User avatar
radio42
Site Admin
Posts: 8295
Joined: 05 Apr 2012 16:26
Location: Hamburg, Germany
Contact:
Re: GPIO en Cartwall problem

Post by radio42 »

So the default (not using the 'Sync. Callback' option) works fine again ?!
User avatar
Michel67
Posts: 166
Joined: 28 Nov 2016 19:53
Re: GPIO en Cartwall problem

Post by Michel67 »

I've found the OnDRAirliteStarted event and delete everything and after a restart the cartwall buttons no longer green, so resolved :D
moogwill
Posts: 420
Joined: 28 Feb 2016 12:31
Re: GPIO en Cartwall problem

Post by moogwill »

More news, but no good ones, for me, both are a complete fiasco. With synchronous callback the issue is back, with, in addition, many different little new issues... And if i unswitch its very Strange, First there's a huge latency then when I press a switch, the begining of each sound is missing and the autoplay switch is going mad. from one state to another as you press some starts switches, and finally starts blinking red/green like a strobe.
Note that when I woke up this morning still running yesterdays BETA, the Strobe blinking of the autoplay button issue was allready there (I restarted the GPIO to solve this).
User avatar
radio42
Site Admin
Posts: 8295
Joined: 05 Apr 2012 16:26
Location: Hamburg, Germany
Contact:
Re: GPIO en Cartwall problem

Post by radio42 »

A restart will clear all LEDs via a certain command you send, see the OnAirenceStarted event.
Even this is nothing I provided but a user, so better ask him.

I thought you now leave the new 'Sync. Callback' option unchecked (as it is per default) and this was working well, at lease it is for Michel.
So please use the default (unchecked).

However, the strobe like blinking LED (as you mailed me in an extra video) is nothing I can even implement in ProppFrexx. So this looks like a different issue.

As yesterday's BETA was even using the same function as in all previous version, I believe you have some other issue with your Airence.
Maybe an issue directly with your Airence.
Maybe time to call the D&R support?
moogwill
Posts: 420
Joined: 28 Feb 2016 12:31
Re: GPIO en Cartwall problem

Post by moogwill »

good news, so far, I just did a full reboot of everything, seems ok now

Post Reply