View Single Post
Old December 3rd, 2018   #5
shawn
Junior Member
 
Join Date: Nov 2018
Location: Oakland, CA, USA
Posts: 18
Default

I’m not sure I agree with that. The PID is known. I think the E1.37-2 reason, NR_ACTION_NOT_SUPPORTED, might be more appropriate (I found it after I asked). It specifically covers the case where the current setup doesn’t accommodate the request.

Update: I'll add: I'm working on a system where the device is programmable; also a library and API that can be incorporated into other embedded projects. It may change its footprint depending on how it's initialized and also on other external factors. i.e. the footprint is potentially dynamic.

Last edited by shawn; December 3rd, 2018 at 05:08 PM.
shawn is offline   Reply With Quote