Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

how to avoid this? wireless pro transceiver OLED display goes crazy after an hour or two of processing events #127

Open
xanderalexx opened this issue Jun 11, 2022 · 2 comments

Comments

@xanderalexx
Copy link

xanderalexx commented Jun 11, 2022

brief context: an apple watch app allows me to send health data(my heart rate) every second to a few seconds (this varies) to a web server which is what this is. new_msg() is called when the server receives a new message. it checks if it includes my heart rate and if it does, it creates a game event as a dict object and sends it over to gamesense to handle as JSON. it also sets up and sends a screen handler (prePL) before the web server loop starts.

After handling game events just fine for an hour or two the screen goes crazy and wont fix itself unless I power cycle the transceiver.

Here's a couple of videos:

Vs8yFAN.mp4

This looks like a camera shutter/fps issue but exactly what you see in the video is what my eyes were seeing.

80L4Wel.mp4
8wP2lqH.mp4

did satan himself possess my transceiver?

RrfGI9P.mp4

keep in mind I'm not well versed in this, feel free to point out any obvious errors and oversights

Thanks!
python code:

import logging
from websocket_server import WebsocketServer
import requests
import json
import os

address = "http://" + json.load(open('C:\ProgramData\SteelSeries\SteelSeries Engine 3\coreProps.json'))['address']
i = 0
prePL = {
    "game":"HEARTRATE",
    "event":"HEARTBEAT",
    "handlers":[{
        "device-type":"screened",
        "zone":"one",
        "mode":"screen",
        "datas":[{
            "icon-id":38,
            "has-text": True,
            "length-millis":0,
            "context-frame-key": "custom-text"
        }]
    }]
}
prepost = requests.post(url=address + "/bind_game_event", json=prePL)
print(prepost.status_code)
print(prepost.content)

def new_msg(client, server, message):
    global i
    data = message.split(":")
    if data[0] == "heartRate":
        print(data[1])
        payload = {
            "game": "HEARTRATE",
            "event": "HEARTBEAT",
            "data":{
                "value":i,
                "frame":{
                    "custom-text":data[1]
                }
            }
        }
        r = requests.post(url=address + "/game_event", json=payload)
        i = i + 1
        print(r)
        print(r.content)

server = WebsocketServer(host='0.0.0.0', port=8080, loglevel=logging.INFO)
server.set_fn_message_received(new_msg)
server.run_forever()
@gemSquared
Copy link

gemSquared commented Jun 25, 2022

I have this SAME exact issue. I need to unplug and replug the device when it does this. Except mine does it sooner because I stream images at 15FPS heheheh. I've found a past issue though! Supposedly a hardware/firmware issue. #66

@xanderalexx
Copy link
Author

I have this SAME exact issue. I need to unplug and replug the device when it does this. Except mine does it sooner because I stream images at 15FPS heheheh. I've found a past issue though! Supposedly a hardware/firmware issue. #66

Yeah I did a bit more research after opening this issue and saw what the dev had to say about it. So unfortunate that there's nothing they can do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants