Jeremy Wood
- Total activity 33
- Last activity
- Member since
- Following 1 user
- Followed by 0 users
- Votes 1
- Subscriptions 12
Activity overview
Latest activity by Jeremy Wood-
Jeremy Wood commented,
Official comment Please refer to our updated documentation of `canSend` and `canMatch`, as well as new CAN interaction examples: CAN Interaction Examples CAN Send Command CAN Match Command
-
Jeremy Wood commented,
Thanks for pointing this out! We're updating our CAN command documentation to cover this, and include some examples. The piece we didn't explain in the docs is that the msgID and payload bytes can ...
-
Jeremy Wood commented,
You shouldn't rely on this behavior, because I think this is a bug. We don't intend to have this command PASS when expect isn't satisfied. My advice with this command at the moment would be to writ...
-
Jeremy Wood commented,
To clarify, was that a typo in your comment above, where you said "This is troubling in that the expected string ("RES 1") didn't come". Did you mean that "+RES 0" didn't come? I think this may be ...
-
Jeremy Wood commented,
Glad you got the first scenario working. For the second scenario, the PLT-300 cannot generally measure frequencies that high, because of signal limitations through the HD-78 cable and typical ICT f...
-
Jeremy Wood commented,
My mistake, when I looked up the value for ESC, I didn't realize I found the decimal value, not hex. 0x1B is equal to 27 in decimal.
-
Jeremy Wood commented,
Here's how to send out that key: - command: define sensorID "Nick\r\n"- uartcmd: uart UART0 send: "%sensorID%" timeoutms: 5000
-
Jeremy Wood commented,
There are a couple of different ways to send control characters over UART. One option: Send explicit bytes as a hex string: # Send Escape character (ASCII 0x27)- uartcmd: uart UART0 send: hex "27"...
-
Jeremy Wood commented,
Derek Cao I was able to reproduce this and find the issue. We've just released PLT-OS v1.9.11, which fixes it. Thanks again for reporting this!
-
Jeremy Wood commented,
Derek Cao Thank you for reporting this issue, we'll investigate!