Blue Melon
BlueSense

Products/BlueSense FAQ

From BlueMelon

Contents


Wireless modules

I often see green and/or red LEDs lit on my wireless modules, what do they mean?

  1. At normal operation;
    • the green LED is;
      • on - it means the device is powered.
    • the red LED is;
      • off - normal operation
      • blinking quickly - one of the wirelessly connected slaves is not responding (it could be out of range or turned off)
      • on (steady) - a communication error just occured
  2. When the button was just pressed;
    • the green LED is;
      • on - normal operation
      • off - reset
    • the red LED is;
      • on - indicating it is searching for a slave or master
      • blinking quickly - it has just found a slave or master


Max MSP(tm)

When I double click the BlueSenseMaster component nothing happens


When I check the table of available modules the type of the modules is displayed as "???"

  • The type of the module will only be displayed after at least one Max MSP(tm) object of the missing types has been placed in your patch..


I have placed a Max MSP(tm) BlueSenseXXX component in my patch, the component however does nothing at all

  • Is the connection activated? Double click the BlueSenseMaster component.
  • Did you use the correct id for your object? Double click the object. Verify that the message displays that the module was found.


The values which my analog ïnput module produces do not change

  • Is the sample delay configured?
  • Is the resolution configured?
  • Is the vref configured?
  • Is there a large enough voltage drop over your sensor? The voltage drop should be in correspondence with the vref value.

For an exmaple analog input patch see: Max Msp analogue inputs


The switch states are not measured by my BlueSenseSwitchInput object


I use a BlueSenseOCOutput to set an output from a Max patch, however my actuator is not switched


Linux

When I try to execute the list device example it does not find any device

  • To be able to use the USB device as a user you will need to have access to the /proc/bus/usb filesystem.
  1. Check if you are in the group usb by executing the command id.
    If you are not in this group make the administrator (root) add you to this group.
  2. Next check if the /proc/bus/usb is mounted and is also in the same group using the mount command.
    One of the lines in the output from mount should look like this:
    usbfs on /proc/bus/usb type usbfs (rw,devgid=85,devmode=0664)
  3. Make sure your Linux sees the device by executing: grep Product /proc/bus/usb/devices
  4. As a temporary test you might try executing the examples as root (if possible).


         

 

This page was last modified 09:05, 16 May 2006.