qlsdk2 0.1.0__tar.gz

qlsdk2-0.1.0/PKG-INFO

@@ -0,0 +1,107 @@
+Metadata-Version: 2.1
+Name: qlsdk2
+Version: 0.1.0
+Summary: SDK for quanlan device
+Home-page: https://github.com/hehuajun/qlsdk
+Author: hehuajun
+Author-email: hehuajun@eegion.com
+Classifier: Programming Language :: Python :: 3
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+Provides-Extra: dev
+
+# qlsdk project
+
+
+
+## Getting started
+
+To make it easy for you to get started with GitLab, here's a list of recommended next steps.
+
+Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
+
+## Add your files
+
+- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
+- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
+
+```
+cd existing_repo
+git remote add origin http://10.60.170.104/sw/qlsdk-project.git
+git branch -M main
+git push -uf origin main
+```
+
+## Integrate with your tools
+
+- [ ] [Set up project integrations](http://10.60.170.104/sw/qlsdk-project/-/settings/integrations)
+
+## Collaborate with your team
+
+- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
+- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
+- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
+- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
+- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
+
+## Test and Deploy
+
+Use the built-in continuous integration in GitLab.
+
+- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/)
+- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
+- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
+- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
+- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
+
+***
+
+# Editing this README
+
+When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
+
+## Suggestions for a good README
+
+Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
+
+## Name
+Choose a self-explaining name for your project.
+
+## Description
+Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
+
+## Badges
+On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
+
+## Visuals
+Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
+
+## Installation
+Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
+
+## Usage
+Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
+
+## Support
+Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
+
+## Roadmap
+If you have ideas for releases in the future, it is a good idea to list them in the README.
+
+## Contributing
+State if you are open to contributions and what your requirements are for accepting them.
+
+For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
+
+You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
+
+## Authors and acknowledgment
+Show your appreciation to those who have contributed to the project.
+
+## License
+For open source projects, say how it is licensed.
+
+## Project status
+If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.

qlsdk2-0.1.0/README.md

@@ -0,0 +1,93 @@
+# qlsdk project
+
+
+
+## Getting started
+
+To make it easy for you to get started with GitLab, here's a list of recommended next steps.
+
+Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
+
+## Add your files
+
+- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
+- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
+
+```
+cd existing_repo
+git remote add origin http://10.60.170.104/sw/qlsdk-project.git
+git branch -M main
+git push -uf origin main
+```
+
+## Integrate with your tools
+
+- [ ] [Set up project integrations](http://10.60.170.104/sw/qlsdk-project/-/settings/integrations)
+
+## Collaborate with your team
+
+- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
+- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
+- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
+- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
+- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
+
+## Test and Deploy
+
+Use the built-in continuous integration in GitLab.
+
+- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/)
+- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
+- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
+- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
+- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
+
+***
+
+# Editing this README
+
+When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
+
+## Suggestions for a good README
+
+Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
+
+## Name
+Choose a self-explaining name for your project.
+
+## Description
+Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
+
+## Badges
+On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
+
+## Visuals
+Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
+
+## Installation
+Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
+
+## Usage
+Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
+
+## Support
+Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
+
+## Roadmap
+If you have ideas for releases in the future, it is a good idea to list them in the README.
+
+## Contributing
+State if you are open to contributions and what your requirements are for accepting them.
+
+For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
+
+You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
+
+## Authors and acknowledgment
+Show your appreciation to those who have contributed to the project.
+
+## License
+For open source projects, say how it is licensed.
+
+## Project status
+If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.

qlsdk2-0.1.0/setup.cfg

@@ -0,0 +1,32 @@
+[metadata]
+name = qlsdk2
+version = 0.1.0
+author = Your Name
+author_email = your.email@example.com
+description = SQL SDK Library
+long_description = file: README.md
+long_description_content_type = text/markdown
+url = https://github.com/yourusername/qlsdk
+
+[options]
+package_dir = = src
+packages = find:
+python_requires = >=3.8
+install_requires = 
+	loguru>=0.6.0
+
+[options.packages.find]
+where = src
+exclude = 
+	tests*
+	examples*
+
+[options.extras_require]
+dev = 
+	pytest>=6.0
+	twine>=3.0
+
+[egg_info]
+tag_build = 
+tag_date = 0
+

qlsdk2-0.1.0/setup.py

@@ -0,0 +1,31 @@
+# setup.py
+import setuptools
+
+with open("README.md", "r") as fh:
+    long_description = fh.read()
+
+setuptools.setup(
+    name="qlsdk2",
+    version="0.1.0",
+    author="hehuajun",
+    author_email="hehuajun@eegion.com",
+    description="SDK for quanlan device",
+    long_description=long_description,
+    long_description_content_type="text/markdown",
+    url="https://github.com/hehuajun/qlsdk",
+    package_dir={"": "src"},
+    packages=setuptools.find_packages(where="src"),
+    classifiers=[
+        "Programming Language :: Python :: 3",
+        "License :: OSI Approved :: MIT License",
+        "Operating System :: OS Independent",
+    ],
+    python_requires='>=3.9',
+    install_requires=open("requirements.txt").read().splitlines(),
+    include_package_data=True,
+    # entry_points={
+    #     'console_scripts': [
+    #         'qlsdk-cli=qlsdk.cli:main',  # 如果有命令行工具
+    #     ],
+    # },
+)

qlsdk2-0.1.0/src/qlsdk/__init__.py

@@ -0,0 +1,15 @@
+__version__ = "0.1.0"
+
+# 暴露公共接口
+from .ar4m.ar4m import AR4M
+from .ar4m.ar4sdk import AR4SDK, AR4, Packet, AR4Packet
+
+__all__ = ['AR4M', 'AR4', 'AR4Packet']
+
+# from importlib import import_module
+# from pathlib import Path
+
+# _MODULES = [p.stem for p in Path(__file__).parent.glob("*.py") if p.stem != "__init__"]
+
+# for module in _MODULES:
+#     import_module(f".{module}", package="qlsdk")

qlsdk2-0.1.0/src/qlsdk/ar4m/__init__.py

@@ -0,0 +1,4 @@
+__path__ = __import__("pkgutil").extend_path(__path__, __name__)
+
+from .ar4m import AR4M
+from .ar4sdk import AR4SDK, AR4, Packet, AR4Packet

qlsdk2-0.1.0/src/qlsdk/ar4m/ar4m.py

@@ -0,0 +1,44 @@
+from ar4sdk import AR4SDK, AR4
+from time import sleep, time
+from threading import Lock, Timer
+from loguru import logger
+
+class AR4M(object):
+    def __init__(self):
+        self._lock = Lock()
+        self._search_timer = None 
+        self._search_running = False
+        self._devices: dict[str, AR4] = {}
+    
+    @property
+    def devices(self):
+        return self._devices
+    def search(self):
+        if not self._search_running:
+            self._search_running = True
+            self._search()
+        
+    def _search(self):
+        if self._search_running:
+
+            self._search_timer = Timer(2, self._search_ar4)
+            self._search_timer.daemon = True
+            self._search_timer.start()
+        
+        
+    def _search_ar4(self):
+        try:                        
+            devices = AR4SDK.enum_devices()
+            logger.debug(f"_search_ar4 devices size: {len(devices)}")
+            for dev in devices:
+                logger.debug(f"slot: {dev.slot}, mac: {dev.mac}-{hex(dev.mac)}, hub_name: {dev.hub_name.str}")
+                if dev.mac in list(self._devices.keys()):
+                    ar4 = self._devices[dev.mac]
+                    ar4.update_info()
+                ar4 = AR4(hex(dev.mac), dev.slot, dev.hub_name.str)
+                if ar4.init():
+                    self._devices[dev.mac] = ar4
+        except Exception as e:
+            logger.error(f"_search_ar4 异常: {str(e)}")
+        finally:
+            self._search()

qlsdk2-0.1.0/src/qlsdk/ar4m/ar4sdk.py

@@ -0,0 +1,372 @@
+import ctypes
+from multiprocessing import Queue
+import platform
+from ctypes import (
+    c_int, c_int32, c_int64, c_uint32, c_uint64, 
+    c_char, c_char_p, c_void_p, 
+    Structure, POINTER, CFUNCTYPE
+)
+from loguru import logger
+from time import sleep, time
+
+# 加载 DLL
+if platform.system() == 'Windows':
+    _dll = ctypes.CDLL('./libs/libAr4SDK.dll')
+else:
+    raise NotImplementedError(f"不支持非Windows平台：{platform.system()}")
+
+#------------------------------------------------------------------
+# 基础类型定义
+#------------------------------------------------------------------
+class Ar4MacStr(Structure):
+    _fields_ = [("str", c_char * 17)]
+
+class Ar4Name(Structure):
+    _fields_ = [("str", c_char * 21)]
+
+class Ar4Device(Structure):
+    _fields_ = [
+        ("slot", c_int32),
+        ("mac", c_uint64),
+        ("hub_name", Ar4Name)
+    ]
+
+class Ar4NotifyData(Structure):
+    _fields_ = [
+        ("time_stamp", c_int64),
+        ("pkg_id", c_int64),
+        ("notify_id", c_int64),
+        ("eeg", POINTER(c_int32)),
+        ("eeg_ch_count", c_int32),
+        ("eeg_count", c_int32),
+        ("acc", POINTER(c_int32)),
+        ("acc_ch_count", c_int32),
+        ("acc_count", c_int32)
+    ]
+
+#------------------------------------------------------------------
+# 回调函数类型
+#------------------------------------------------------------------
+FuncAr4DataNotify = CFUNCTYPE(None, c_void_p, POINTER(Ar4NotifyData))
+FuncAr4TriggerNotify = CFUNCTYPE(None, c_void_p, c_int64, c_int32, c_uint32)
+FuncAr4RecorderDisconnected = CFUNCTYPE(None, c_void_p)
+FuncAr4RecorderConnected = CFUNCTYPE(None, c_void_p)
+FuncAr4RecorderTimeout = CFUNCTYPE(None, c_void_p, c_int64)
+FuncAr4RecorderPkgLost = CFUNCTYPE(c_int, c_void_p, c_int64, c_int64, c_int64)
+FuncAr4GetTime = CFUNCTYPE(c_int64)
+FuncAr4SDKPrint = CFUNCTYPE(None, c_char_p, ctypes.c_size_t)
+
+#------------------------------------------------------------------
+# SDK 函数定义
+#------------------------------------------------------------------
+# 设备枚举
+_dll.ar4_sdk_enum_device.restype = POINTER(Ar4Device)
+_dll.ar4_sdk_enum_hub.restype = POINTER(Ar4Name)
+_dll.ar4_sdk_enum_in_hub.argtypes = [Ar4Name]
+
+# MAC地址转换
+_dll.ar4_mac_to_str.argtypes = [c_uint64]
+_dll.ar4_mac_to_str.restype = Ar4MacStr
+_dll.ar4_str_to_mac.argtypes = [Ar4MacStr]
+_dll.ar4_str_to_mac.restype = c_uint64
+
+# 连接管理
+_dll.ar4_sdk_connect.argtypes = [c_uint64, c_void_p]
+_dll.ar4_sdk_connect.restype = c_void_p
+_dll.ar4_sdk_disconnect.argtypes = [c_void_p]
+
+# AR4信息查询
+_dll.ar4_sdk_get_box_name.argtypes = [c_void_p]
+_dll.ar4_sdk_get_box_name.restype = c_uint64
+
+# 数据采集控制
+_dll.ar4_sdk_start_acq.argtypes = [c_void_p]
+_dll.ar4_sdk_start_acq.restype = c_int
+_dll.ar4_sdk_stop_acq.argtypes = [c_void_p]
+_dll.ar4_sdk_stop_acq.restype = c_int
+_dll.ar4_sdk_get_record_sample_rate.argtypes = [c_void_p]
+_dll.ar4_sdk_get_record_sample_rate.restype = c_char_p
+_dll.ar4_sdk_get_acq_start_time.argtypes = [c_void_p]
+_dll.ar4_sdk_get_acq_start_time.restype = c_int64
+
+# 回调注册
+_dll.ar4_sdk_register_data_notify.argtypes = [c_void_p, FuncAr4DataNotify]
+_dll.ar4_sdk_register_data_notify.restype = None
+_dll.ar4_sdk_register_trigger_notify.argtypes = [c_void_p, c_void_p]
+_dll.ar4_sdk_register_conn_notify.argtypes = [c_void_p, FuncAr4RecorderConnected, FuncAr4RecorderDisconnected]
+_dll.ar4_sdk_register_record_state_notify.argtypes = [c_void_p, FuncAr4RecorderConnected, FuncAr4RecorderDisconnected]
+_dll.ar4_sdk_register_box_conn_notify.argtypes = [c_void_p, FuncAr4RecorderConnected, FuncAr4RecorderDisconnected]
+
+# _dll对外封装类
+class AR4SDK:
+    @classmethod
+    def enum_devices(cls):
+        """枚举可用设备"""
+        devices = []
+        ptr = _dll.ar4_sdk_enum_device()
+        
+        while ptr and ptr.contents.mac != 0:
+            devices.append(ptr.contents)
+            ptr = ptr[1]
+            if isinstance(ptr, Ar4Device):
+                logger.debug(f"enum_devices break with {ptr}")
+                break
+        return devices
+    
+    @classmethod
+    def enum_hubs(cls):
+        """枚举可用设备"""
+        devices = []
+        ptr = _dll.ar4_sdk_enum_hub()
+        sleep(5)
+        logger.debug(f"enum_hubs: {ptr}")
+
+    def __enter__(self):
+        return self
+
+    def __exit__(self, exc_type, exc_val, exc_tb):
+        pass
+  
+
+# 读取系统当前时间(ms)
+def _get_time():
+    cur_time = int(round(time()) * 1000)
+    logger.debug(f"_get_time is {cur_time}")
+    return cur_time  
+    
+# ar4设备对象
+class AR4(object):
+    def __init__(self, box_mac, slot, hub_name):
+        self._handle = None
+        self._box_type = None
+        self._box_mac = box_mac
+        self._box_id = None
+        self._box_soc = None
+        self._box_name = None
+        self._box_version = None
+        self._head_type = None
+        self._head_mac = None
+        self._head_version = None
+        self._head_conn_state = None
+        self._head_soc = None
+        self._net_state = None
+        self._hub_name = hub_name
+        self._slot = slot
+        self._connected = False
+        self._conn_time = None
+        self._last_time = None
+        # 回调函数
+        self._data_callback = FuncAr4DataNotify(self._wrap_data_accept())        
+        self._trigger_callback = FuncAr4TriggerNotify(self._trigger_accept)
+        
+        # 消息订阅
+        self._consumers: dict[str, Queue] = {}
+        
+    @property
+    def box_mac(self):
+        return self._box_mac
+    def init(self):
+        if not self._handle:
+            self._connected = self.connect()
+            if self._connected:
+                self._conn_time = _get_time()
+                self.get_box_name()
+                self.get_head_mac()
+                self.get_record_conn_state()
+                self._last_time = _get_time()
+            logger.debug(self)
+        return True
+
+    def update_info(self):
+        self._last_time = _get_time()
+        
+    # 设备连接
+    def connect(self)-> bool:
+        
+            if self._box_mac:
+                """连接设备"""
+                # callback = FuncAr4GetTime(self._get_time)
+                try:
+                    self._handle = _dll.ar4_sdk_connect(int(self._box_mac, 16), c_void_p(0))
+                    # logger.info(f"conn handle is {self._handle}")
+                    self._handle = c_void_p(self._handle)     
+                    logger.debug(f"ar4 {self._box_mac} 连接: {self._handle}")                   
+                except Exception as e:
+                    logger.error(f"ar4 {self._box_mac} 连接异常: {str(e)}")
+            return self._handle is not None
+    
+    # 读取盒子名称
+    def get_box_name(self):
+        if self._handle:    
+            try:        
+                self._head_mac = _dll.ar4_sdk_get_recoder_mac(self._handle)
+            except Exception as e:
+                    logger.error(f"ar4 {self._box_mac} 获取盒子记录子mac异常: {str(e)}")
+    # 读取记录子mac
+    def get_head_mac(self):
+        if self._handle:    
+            try:        
+                self._box_name = _dll.ar4_sdk_get_record_conn_state(self._handle)
+            except Exception as e:
+                    logger.error(f"ar4 {self._box_mac} 获取盒子名称异常: {str(e)}")
+    # 读取记录子连接状态
+    def get_record_conn_state(self):
+        if self._handle:    
+            try:        
+                self._head_conn_state = _dll.ar4_sdk_get_record_conn_state(self._handle)
+            except Exception as e:
+                    logger.error(f"ar4 {self._box_mac} 获取盒子记录子连接状态异常: {str(e)}")
+
+    # 数据采集启动
+    def start_acquisition(self):
+        logger.info(f"ar4 {self._box_mac} 启动数据采集...")
+        """启动数据采集"""
+        
+        if self._handle:
+            # 设置信号数据回调
+            try:
+                _dll.ar4_sdk_register_data_notify(self._handle, self._data_callback)
+            except Exception as e:
+                logger.error(f"ar4 {self._box_mac} 停止采集异常: {str(e)}")
+                
+            # 设置trigger数据回调
+            try:
+                _dll.ar4_sdk_register_trigger_notify(self._handle, self._trigger_callback)
+            except Exception as e:
+                logger.error(f"ar4 {self._box_mac} 停止采集异常: {str(e)}")
+            # 启动采集
+            try:
+                logger.debug(f"ar4 {self._box_mac} 启动采集: {self._handle}")
+                ret = _dll.ar4_sdk_start_acq(self._handle)
+                logger.debug(f"ar4 {self._box_mac} 启动采集结果: {ret}")
+                    
+                return ret == 0
+            except Exception as e:
+                logger.error(f"ar4 {self._box_mac} 停止采集异常: {str(e)}")
+        else:
+            logger.info(f"ar4 {self._box_mac} 启动数据采集失败， 设备未连接")
+            return False
+
+    def stop_acquisition(self):
+        """停止采集"""
+        if self._handle:
+            try:
+                return _dll.ar4_sdk_stop_acq(self._handle) == 0
+            except Exception as e:
+                logger.error(f"ar4 {self._box_mac} 停止采集异常: {str(e)}")
+        else:
+            return False
+
+    def disconnect(self):
+        """断开连接"""
+        if self._handle:
+            _dll.ar4_sdk_disconnect(self._handle)
+
+    def get_sample_rate(self):
+        try:
+            ret = _dll.ar4_sdk_get_record_sample_rate(self._handle)
+            logger.debug(f"ar4 {self._box_mac} 获取采样率: {ret.contents.decode('utf-8')}")
+        except Exception as e:
+            logger.error(f"ar4 {self._box_mac} 获取采样率异常: {str(e)}")
+            
+    def get_acq_start_time(self):
+        try:
+            ret = _dll.ar4_sdk_get_acq_start_time(self._handle)
+            logger.debug(f"ar4 {self._box_mac} 获取采样开始时间: {ret}")
+        except Exception as e:
+            logger.error(f"ar4 {self._box_mac} 获取采样开始时间异常: {str(e)}")
+       
+    # 订阅推送消息 
+    def subscribe(self, topic: str = None, q: Queue = Queue()):
+        if topic is None:
+            topic = f"msg_{_get_time()}"
+        if topic in list(self._consumers.keys()):  
+            logger.warning(f"ar4 {self._box_mac} 订阅主题已存在: {topic}")
+            return topic, self._consumers[topic]
+        self._consumers[topic] = q
+        
+        return topic, self._consumers[topic]
+    
+    def _wrap_data_accept(self):
+        
+        @FuncAr4DataNotify
+        def data_accept(handle, data_ptr):
+            self._data_accept(data_ptr)
+            
+        return data_accept
+            
+    def _data_accept(self, data_ptr):
+        # logger.info(f"_eeg_accept 被调用")
+        # logger.debug(f'handle:{self}, data_ptr:{data_ptr}')
+        # data = cast(data_ptr, POINTER(Ar4NotifyData)).contents
+        if len(self._consumers) > 0:
+            packet = AR4Packet().transfer(data_ptr.contents)
+            for consumer in self._consumers.values():
+                consumer.put(packet)
+            # logger.debug(f"EEG数据: {packet}")
+        
+    def _trigger_accept(self, time_ms, trigger_type, trigger_value):
+        logger.info(f"_trigger_accept 被调用")
+        logger.info(f"触发时间: {time_ms}, 触发类型: {trigger_type}, 触发值: {trigger_value}")
+                
+    def __str__(self):
+        return f"""
+                box mac: {self._box_mac}, 
+                box name: {self._box_name}, 
+                box soc: {self._box_soc}
+                head conn state: {self._head_conn_state}
+                head mac: {self._head_mac},
+                head soc: {self._head_soc} 
+                connected: {self._connected}
+                connect time: {self._conn_time}
+                last time: {self._last_time}
+            """
+            
+class Packet(object):
+    pass
+            
+class AR4Packet(Packet):
+    def __init__(self):
+        self.time_stamp = None
+        self.pkg_id = None
+        self.notify_id = None
+        self.eeg_ch_count = None
+        self.eeg_count = None
+        self.eeg = None
+        self.acc_ch_count = None
+        self.acc_count = None
+        self.acc = None
+    
+    def transfer(self, data: Ar4NotifyData):
+        self.time_stamp = data.time_stamp
+        self.pkg_id = data.pkg_id
+        self.notify_id = data.notify_id
+        self.eeg_ch_count = data.eeg_ch_count
+        self.eeg_count = data.eeg_count
+        self.acc_ch_count = data.acc_ch_count
+        self.acc_count = data.acc_count
+        # 读eeg数据
+        if self.eeg_ch_count and self.eeg_count:
+            self.eeg = [[] for _ in range(self.eeg_ch_count)]
+            for i in range(self.eeg_ch_count):
+                self.eeg[i] = [data.eeg[j + (i * self.eeg_count)] for j in range(self.eeg_count)]
+        # 读acc数据
+        if self.acc_ch_count and self.acc_count:
+            self.acc = [[] for _ in range(self.acc_ch_count)]
+            for i in range(self.acc_ch_count):
+                self.acc[i] = [data.acc[j + (i * self.acc_count)] for j in range(self.acc_count)]
+        
+        return self
+        
+    def __str__(self):
+        return f"""
+            time_stamp: {self.time_stamp}
+            pkg_id: {self.pkg_id}
+            notify_id: {self.notify_id}
+            eeg_ch_count: {self.eeg_ch_count}
+            eeg_count: {self.eeg_count}
+            acc_ch_count: {self.acc_ch_count}
+            acc_count: {self.acc_count}
+            eeg: {self.eeg}
+            acc: {self.acc}
+        """

qlsdk2-0.1.0/src/qlsdk/ar4m/example.py

@@ -0,0 +1,51 @@
+from time import sleep
+from loguru import logger
+import os
+from threading import Thread
+    
+from ar4m import AR4M
+
+#------------------------------------------------------------------
+# 日志文件配置
+#------------------------------------------------------------------
+LOG_DIR = os.path.expanduser("./logs")
+LOG_FILE = os.path.join(LOG_DIR, "app_{time}.log")
+if not os.path.exists(LOG_DIR):
+    os.mkdir(LOG_DIR)
+
+logger.add(LOG_FILE, rotation = "50MB")     
+
+def consumer(q):
+    t = Thread(target=deal_data, args=(q,))
+    t.daemon = True
+    t.start()
+        
+def deal_data(q):
+    while True:
+        data = q.get()
+        if data is None:
+            break
+        logger.info(data)
+
+# 主函数
+if __name__ == "__main__":
+    try:
+        ar4m = AR4M()
+        ar4m.search()
+        sleep(6)
+        for dev in list( ar4m.devices.values()):
+            ret = dev.start_acquisition()
+            topic, queue = dev.subscribe()
+            logger.info(f"启动{dev.box_mac}的数据采集{'成功' if ret else '失败'}")
+            
+        sleep(60)
+        
+        for dev in list( ar4m.devices.values()):
+            ret = dev.stop_acquisition()
+            dev.get_acq_start_time() 
+            logger.info(f"关闭{dev.box_mac}的数据采集{'成功' if ret else '失败'}")
+        sleep(1)
+    except Exception as e:
+        logger.error(f"程序运行异常: {str(e)}")
+    finally:        
+        logger.info("程序结束。")

qlsdk2-0.1.0/src/qlsdk2.egg-info/PKG-INFO

@@ -0,0 +1,107 @@
+Metadata-Version: 2.1
+Name: qlsdk2
+Version: 0.1.0
+Summary: SDK for quanlan device
+Home-page: https://github.com/hehuajun/qlsdk
+Author: hehuajun
+Author-email: hehuajun@eegion.com
+Classifier: Programming Language :: Python :: 3
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+Provides-Extra: dev
+
+# qlsdk project
+
+
+
+## Getting started
+
+To make it easy for you to get started with GitLab, here's a list of recommended next steps.
+
+Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
+
+## Add your files
+
+- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
+- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
+
+```
+cd existing_repo
+git remote add origin http://10.60.170.104/sw/qlsdk-project.git
+git branch -M main
+git push -uf origin main
+```
+
+## Integrate with your tools
+
+- [ ] [Set up project integrations](http://10.60.170.104/sw/qlsdk-project/-/settings/integrations)
+
+## Collaborate with your team
+
+- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
+- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
+- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
+- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
+- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
+
+## Test and Deploy
+
+Use the built-in continuous integration in GitLab.
+
+- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/)
+- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
+- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
+- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
+- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
+
+***
+
+# Editing this README
+
+When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
+
+## Suggestions for a good README
+
+Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
+
+## Name
+Choose a self-explaining name for your project.
+
+## Description
+Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
+
+## Badges
+On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
+
+## Visuals
+Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
+
+## Installation
+Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
+
+## Usage
+Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
+
+## Support
+Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
+
+## Roadmap
+If you have ideas for releases in the future, it is a good idea to list them in the README.
+
+## Contributing
+State if you are open to contributions and what your requirements are for accepting them.
+
+For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
+
+You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
+
+## Authors and acknowledgment
+Show your appreciation to those who have contributed to the project.
+
+## License
+For open source projects, say how it is licensed.
+
+## Project status
+If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.

qlsdk2-0.1.0/src/qlsdk2.egg-info/SOURCES.txt

@@ -0,0 +1,14 @@
+README.md
+setup.cfg
+setup.py
+src/qlsdk/__init__.py
+src/qlsdk2.egg-info/PKG-INFO
+src/qlsdk2.egg-info/SOURCES.txt
+src/qlsdk2.egg-info/dependency_links.txt
+src/qlsdk2.egg-info/requires.txt
+src/qlsdk2.egg-info/top_level.txt
+src/qlsdk/ar4m/__init__.py
+src/qlsdk/ar4m/ar4m.py
+src/qlsdk/ar4m/ar4sdk.py
+src/qlsdk/ar4m/example.py
+test/test_ar4m.py

qlsdk2-0.1.0/src/qlsdk2.egg-info/dependency_links.txt

@@ -0,0 +1 @@
+

qlsdk2-0.1.0/src/qlsdk2.egg-info/requires.txt

@@ -0,0 +1,5 @@
+loguru>=0.6.0
+
+[dev]
+pytest>=6.0
+twine>=3.0

qlsdk2-0.1.0/src/qlsdk2.egg-info/top_level.txt

@@ -0,0 +1 @@
+qlsdk

qlsdk2-0.1.0/test/test_ar4m.py

@@ -0,0 +1,51 @@
+from time import sleep
+from loguru import logger
+import os
+from threading import Thread
+
+from qlsdk import AR4M
+
+#------------------------------------------------------------------
+# 日志文件配置
+#------------------------------------------------------------------
+LOG_DIR = os.path.expanduser("./logs")
+LOG_FILE = os.path.join(LOG_DIR, "app_{time}.log")
+if not os.path.exists(LOG_DIR):
+    os.mkdir(LOG_DIR)
+
+logger.add(LOG_FILE, rotation = "50MB")     
+
+def consumer(q):
+    t = Thread(target=deal_data, args=(q,))
+    t.daemon = True
+    t.start()
+        
+def deal_data(q):
+    while True:
+        data = q.get()
+        if data is None:
+            break
+        logger.info(data)
+
+# 主函数
+if __name__ == "__main__":
+    try:
+        ar4m = AR4M()
+        ar4m.search()
+        sleep(6)
+        for dev in list( ar4m.devices.values()):
+            ret = dev.start_acquisition()
+            topic, queue = dev.subscribe()
+            logger.info(f"启动{dev.box_mac}的数据采集{'成功' if ret else '失败'}")
+            
+        sleep(60)
+        
+        for dev in list( ar4m.devices.values()):
+            ret = dev.stop_acquisition()
+            dev.get_acq_start_time() 
+            logger.info(f"关闭{dev.box_mac}的数据采集{'成功' if ret else '失败'}")
+        sleep(1)
+    except Exception as e:
+        logger.error(f"程序运行异常: {str(e)}")
+    finally:        
+        logger.info("程序结束。")