GPIO en Cartwall problem
Re: GPIO en Cartwall problem
I'm not a pro about that, but as I tried (Michel maybe you can test that) If you press a lot of switch relatively fast, you can reproduce this issue, I tried that, with localip&port, with localhost&port, and most af all, with localhost&port, and network disconnected.. I reproduced this issue, with NO NETWORK, only while I was switching some buttons from the cartwall (local Library) and some local sounds from the hardrive. it doesn't seems to be a network issue.
ANd As I Got the same trouble using airence, I Don't think that the files From Benjamin are the problem (I Asked Him about this issue 2 days ago)
ANd As I Got the same trouble using airence, I Don't think that the files From Benjamin are the problem (I Asked Him about this issue 2 days ago)
Re: GPIO en Cartwall problem
I know now that when I do nothing at any given time the connection is gone, so not only by the cartwall buttons, I'm looking further.
Re: GPIO en Cartwall problem
and now at restart I had a message of error that was saying gpio config was maybe corrupt.. then after reboot GPIO It asked for the password again...
on the second computer password again too but no "corrupt error message"
on the second computer password again too but no "corrupt error message"
Re: GPIO en Cartwall problem
When your config file is corrupt it will loose the password! As the file cannot be read.
So why does your file get corrupt? Hard disk issue?
When you say 2 PCs - are on both running the GPIO service? Using the same port?
So why does your file get corrupt? Hard disk issue?
When you say 2 PCs - are on both running the GPIO service? Using the same port?
Bernd - radio42
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
Re: GPIO en Cartwall problem
Hopefully this is the solution: in the GPIO-client under the main tab, change the server address to "tcpex://localhost:9042/ProppFrexxRemoteService"
There was ip address computer instead of "localhost"
So far, that seems to have been the problem. The question now remains why all the cartwall buttons on the airlite are green when PF startup.
There was ip address computer instead of "localhost"
So far, that seems to have been the problem. The question now remains why all the cartwall buttons on the airlite are green when PF startup.
Re: GPIO en Cartwall problem
both running, and you're right same port... But I don't think it's the origin of the issue, cause I changed the port of the one running airlite earlier and it was still an issue.. I changed the second one this time, wait and see, stable at the moment, but it keept runnin yesterday for 12 hours before any trouble
Re: GPIO en Cartwall problem
They are maybe green because there might be a command send with the OnApplicationStartup event - see general settings.
E.g. when you send an LED command to the Aitlite with the id 255, this will change all to the given color.
Else I guess you must ask the developer of the Airlite mapping.
E.g. when you send an LED command to the Aitlite with the id 255, this will change all to the given color.
Else I guess you must ask the developer of the Airlite mapping.
Bernd - radio42
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
Re: GPIO en Cartwall problem
Unfortunately using "localhost:port" with different port on the 2 computers did not solve the problem, I still just got the issue.
Re: GPIO en Cartwall problem
Also here unfortunately
Re: GPIO en Cartwall problem
I still guess you will have a network issue somehow.
I am just testing it here on 3 PCs for over 4 hours now and have no issue. And as many other users also have no issues, I am not sure what it is, but it doesn't look like a general issue/bug.
However, we need to further see, what it is in your case, but what we figured out is, that on your systems:
- it seems unrelated to the version used (e.g. a .23 generates the same issue as a .29)
- it seems unrelated to the activity, as it also happens when you do nothing at all
Is the main 'connection slider' in the GPIO client also going to 'Not Connected', when you loose the connection?
I am just testing it here on 3 PCs for over 4 hours now and have no issue. And as many other users also have no issues, I am not sure what it is, but it doesn't look like a general issue/bug.
However, we need to further see, what it is in your case, but what we figured out is, that on your systems:
- it seems unrelated to the version used (e.g. a .23 generates the same issue as a .29)
- it seems unrelated to the activity, as it also happens when you do nothing at all
Is the main 'connection slider' in the GPIO client also going to 'Not Connected', when you loose the connection?
Bernd - radio42
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution