\Cypress\PSOCDE~1\5.2\Common\CY110F~1\tools\make: *** No rule to make target `lib/G9FLE9~Y.INC'.Stop. C
2019-04-17 08:10
： 以表格的形式显示：上位机可以控制单片机(D4，D5)这2个LED的亮度和蜂鸣器的发不发声支持文本保存和数据库的形式保存数据：支持数据库的时间段查询：资料下载地址：http://pan.baidu.com/s/1FLE6E`
2015-08-26 20:56
ADC将这个输出值转换成整数。使用这个值，我想设置一个伺服，也就是显示一个符号的浓度。后来，我想通过FLE发送值到另一个PSoC，作为移动显示。不幸的是，它不起作用，我保存变量中的值，但是当读取这个
2019-10-22 07:11
：CBCharacteristicWriteType。我更新了我的FLE自定义配置文件的LED特性，使它现在看起来像这样（见下载IMG00327。JPG）：实际上只将类型更改为UIT16，以便它接受更多字符。我的理性是，CasSoice特性
2019-10-30 08:54
`采集智芯一号的三端电阻的值（R36，AD1),热敏电阻的值（AD2),主芯片STM32F103VC的温度和18B20的温度以图表和波形图的形式显示：以表格的形式显示：智芯一号STM32 labVIEW调试视频在线观看：[url=]http://www.iqiyi.com/w_19rtfck445.html[/url]`
2015-08-26 18:43
SigMoid函数怎么实现用以步进电机的控制方法？
2021-10-13 07:21
你好，我使用PSoC 4 BLE（CY8CKIT-042-BLE先锋套件）。有人能告诉我如何将Android手机和BLE软件狗加入到BLE模块的白名单中吗？ 以上来自于百度翻译 以下为原文Hi, I am using PSoC 4 BLE ( CY8CKIT-042-BLE PIONEER KIT ). Can anyone please guide me on how to add android phone and BLE dongle to the whitelist of BLE module?
2019-07-02 07:50
大家好，我试图实现以下场景：使用PSoC 4 BLE外围设备，我更新了隐私示例，并尝试在我的项目中使用它。我用一个公共地址启动外围设备，然后用一个Android智能手机连接到设备上，用固定的密钥配对，绑定设备，然后电话断开。在断开事件之后，我的外围设备的地址变成私有随机可解析，这是我想要的，甚至在没有连接或每次连接/断开事件到达时，即使在几分钟内它也会再次改变。一切都是好的，但我的问题是，在我与智能手机从外围设备断开，地址变为私有之后，我再也无法与我的智能手机重新连接。有没有人知道Android本身可以解决一个地址，或者应用程序应该每次扫描一个设备，并试图解决自己的地址？我想重新连接到一个保税设备没有扫描，但我不知道这是可能的。如果有人经历过这一点，那么暗示不仅仅是受欢迎的。谢谢您，玛丽安更新信息：我的设备的安全性被设置为模式1，认证加密配对，严格配对，显示为IO能力（即使这不是完全正确的，该设备没有I/O能力，但我想使用一个固定的密钥）。我观察到，由智能手机发起的绑定和密钥交换是可以的。在断开事件和地址变为私有之后，我可以扫描所有设备，找到我需要的定向地址，并且可以在没有任何绑定的情况下连接到它。现在的问题是：在连接和访问一个服务（例如电池级别）之后，我就不能再做任何事情了。如果我尝试阅读比配对WiNoW将再次弹出，无论我进入什么设备断开连接。更新信息2：这里是一个新的更新和项目附加。除了处理两个状态机来处理这些绑定和隐私任务之外，我消除了所有代码。请注意在BuffHordL.C中有些代码是注释的，因为它在这个测试项目中没有意义，尤其是通过按下一个按钮来完成绑定的事实，而在项目中它是在重置时完成的。SIG中的电池级别在读时已经加密和认证。因此，这可能再次触发配对窗口。我不是Android或IOS将如何处理这个问题的专家，但如果我删除加密，认证比一切都好。但我不想修改这个，而且我仍然希望在其他自定义特性上有一些隐私，即使在绑定之后，只有电话才能解决这个地址。其他信息：与CyPress软件和CyScript在PC上，当重新连接到私人地址，它会弹出配对，但OK后说，完成没有输入引脚完成。我的另一个问题是：我在外围处理这个过程有什么不对吗？Android上的应用程序有问题吗？我应该投资一些时间吗？如果有人能给我指出一个更正确的方向，那就太好了。谢谢您！消息编辑：Marian Emanuel Ionascu原型A2Test.Cyrj.CaseVo.01.Zip767 K 以上来自于百度翻译 以下为原文Hello everybody, I am trying to implement the following scenario: using a PSoC 4 BLE peripheral I updated the privacy example and I am trying to use it in my project. I start the peripheral using a public address; then I connect with an android smartphone to the device, pair it using a fixed passkey, bond the device and afterwards the phone disconnects. After the disconnecting event, the address of my peripheral becomes private random resolvable which is what I want, it even changes ones at a couple of minutes again if there is no connection or every time a connection/disconnection event arrived. Everything is good, but my problem is the following, after I disconnect with the smartphone from the peripheral and the address become private I am not able to reconnect with my smartphone again. Does anyone know if android itself can resolve an address or if the application should scan every time for a device and try to resolve itself the address? I would like to reconnect to a bonded device without scanning, but I do not know if this is possible. If anyone experienced this, a hint is more than welcomed. Thank you,Marian Update info: The security of my device is set to Mode 1, authenticated pairing with encryption, Strict pairing, Display as IO capability(even if this is not entirely correct, the device has no i/o capabilities but I want to use a fixed passkey for this). I observe that the bonding initiated by the smartphone and the exchange of keys is ok. After disconnect event and the address become private I can scan all devices, find the one I need with the orivate address and can connect to it without any bonding. The problem is now the following: after connection and accessing a service(ex. battery level) I am no longer able to do anything. If I try a read than the pairing winodw will pop up again and no matter what I enter the device disconnects. Update info 2: Here is a new Update and the project attached. I eliminate all the code except my two state machines that handle this bonding and privacy tasks. Please note in BLEHandler.c that some code is commented since it makes no sense in this test project, especially the fact that remove bonding is done by pressing a button and in the project it is done at reset. The battery level as it is in SIG has encryption and authenticated on Read. Therefore indeed that may trigger the pairing window again. I am not an expert in how Android or iOS will treat this but if I remove the encryption an authentication than everything is fine. But I do not want to modify this, and I still want some privacy on other custom characteristics, even if after a bonding only that phone can resolve the address. Other Info: with the cypress dongle and cysmart on PC, when reconnect to the private address, it will pop up the pairing but after ok it says paring completed without the entering pin. One of my other questions will be: Is there something wrong in how I handle this process in the peripheral? Is there a problem with the application on android and there I should invest some time? It would be great if someone can point me in a more correct direction. Thank you! Message was edited by: Marian-Emanuel Ionascu PrototypeA2_TEST.cyprj.Archive01.zip 767.0 K
2018-11-01 17:01
很抱歉在我还有一个问题的时候打开一个新的问题（“我炸了我的OP AMPS吗？”）但我必须在相当短的时间内找出很多事情。我想通过通知从我的PSoC设备向GATT客户端发送三个It16值数组。最终，我希望在GATT DB中更新这些值，用于客户端读取，但我只是尝试让通知工作。到目前为止，我所看到的所有示例只在通知上发送了一个UTIT8值（虽然我已经看到一些代码将UTI8数组写入GATT DB），但是当我试图修改这些以与我的It16数组一起工作时，我总是得到以下警告：从“It16（*）[ 3 ] ]分配给“Unt8*”（AKA“无符号char *”）的不兼容指针类型我翻遍了BLE生成的代码和API文档，但是我还没有找到这个问题的解决方案。我敢肯定，这跟我不了解指针（*），地址（&；）、处理等。我想我是设置在BLE组件的自定义特性窗口的数据的类型，但我现在明白我只是改变“新字段的数据格式。”我真的没有一个足够完整的后没有项目，但这是一段代码，我得到上面的警告。任何想法如何完成我所要做的将是最有帮助的。谢谢，唐CyBLY-GATSH-HANDLYVALIONE.NTFFETT通知句柄；如果（权重通知和0x01）{//用新数据更新通知NoTrimeActual.AtHuffRe= WebSythCARAL句柄；NoTimeCaldLe.ValueVal=和权重数组；NoTrimeChanel.ValueLe= Weethsl CalasDATAYLLN；/ /报告数据的组件通过通知发送数据cyble_gattsnotification（cyble_connhandle，&；notificationhandle）；} 以上来自于百度翻译 以下为原文Sorry to open a new question while I still have one open ("Did I Fry my Op Amps?"), but I have to figure out quite a few things in a relatively short period of time. I want to send an array of three int16 values from my PSoC device to a GATT client via a notification. I will eventually want to update these values in the GATT DB too, for client reads, but I'm just trying to get the notifications working for now. All the examples I've seen so far only send a single uint8 value over notifications (although I have seen some code for writing a uint8 array to the GATT DB), but when I try to modify these to work with my int16 array, I always get the following warning: incompatible pointer types assigning to 'uint8*'(aka 'unsigned char *') from 'int16 (*)[3]' I've dug around in the BLE generated code and API docs, but I haven't yet found the solution to this issue. I'm pretty sure it has to do with my poor understanding of pointers (*), addresses (&), handles and so forth. I thought I was setting the type of data in the custom characteristic window of the BLE component, but I now see that I was only changing the data format of "New field." I don't really have a project complete enough to post yet, but here is asnippet of code where I am getting the above warning. Any thoughts on how to accomplish what I am trying to do would be most helpful. Thanks, DonCYBLE_GATTS_HANDLE_VALUE_NTF_TnotificationHandle;if (weightsNotification & 0x01) { // update notification with new data notificationHandle.attrHandle = WEIGHTS_CHAR_HANDLE; notificationHandle.value.val = &weightsArray; notificationHandle.value.len = WEIGHTS_CHAR_DATA_LEN; // Report data to BLE component for sending data by notifications CyBle_GattsNotification(cyBle_connHandle, ¬ificationHandle);}
2019-01-14 08:50
Linux简单串口上网原理是什么？怎样去实现Linux串口上网？
2021-04-26 06:42
