Actions
Forum Thread Details
  • Replies 2 replies
  • Subscribers 57 subscribers
  • Views 399 views
  • Users 0 members are here
Related

moto mods sensor card not available

lllars

I'm getting the above error when trying to run the sensor card example, with firmware and android app compiled from source.  The sensor card works fine when running in example mode.

 

Looking a little deeper, these two conditions are failing:

personality.getModDevice().getVendorId() != Constants.VID_MDK
personality.getModDevice().getProductId() != Constants.PID_TEMPERATURE

 

Any idea what I'm doing wrong?

Parents

  • Figured it out, it appears to be a bug.  VID_MDK and PID_TEMPERATURE are for when the MDK is is example mode, and another set of constants: VID_DEVELOPER and PID_DEVELOPER are intended to be used when the MDK is in developer mode.  The problem is that the android app always uses the first constants regardless of MDK mode.  There is a function "isMDKMod", which would check if the MDK is in developer mode, but that function is never used.

     

    I just hacked the definitions of VID_MDK and PID_TEMPERATURE, in Constants.java, and that got it working:

     

    public static final int VID_DEVELOPER = 0x00000042;

    public static final int VID_MDK = VID_DEVELOPER; // 0x00000312;

    public static final int PID_DEVELOPER = 0x00000001;

    public static final int PID_TEMPERATURE = PID_DEVELOPER; // 0x00010503;

     

    Also, note that the directions for this example on the web have you use "hdk-temperature" as the manifest name in menuconfig, but i think it should actually be "temperature-example" to match the mnfs file they have you create earlier.

  • in reply to lllars

    Not a bug, actually.  In part because we don't want every MDK app trying to open up the Raw interface.  If you've gone the trouble to develop your own firmware, especially using Raw, you'll need your own app to handle that custom data/experience.  We may re-evaluate that decision in future updates.

     

    You're right about the manifest name on the Portal, that has been resolved.  Thank you!

Reply
  • in reply to lllars

    Not a bug, actually.  In part because we don't want every MDK app trying to open up the Raw interface.  If you've gone the trouble to develop your own firmware, especially using Raw, you'll need your own app to handle that custom data/experience.  We may re-evaluate that decision in future updates.

     

    You're right about the manifest name on the Portal, that has been resolved.  Thank you!

Children
No Data