Chief Delphi

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)
-   Electrical (http://www.chiefdelphi.com/forums/forumdisplay.php?f=53)
-   -   VEX 393 Encoder Issues (http://www.chiefdelphi.com/forums/showthread.php?t=112654)

cjlane1138 02-02-2013 22:42
VEX 393 Encoder Issues
 
Hello everyone,
We have successfully controlled a VEX 393 IME using the Digital Sidecar in C++, but we are currently having issues with the wiring of the encoder. We have the yellow wire as A and the white wire as B, yet we are not getting any values. Any help would be appreciated! Thanks!

Mark McLeod 02-02-2013 22:58
Re: VEX 393 Encoder Issues
 
Doesn't that use an I2C communication scheme?
Are you connecting it to the I2C header pins on the Digital sidecar?

cjlane1138 02-02-2013 23:04
Re: VEX 393 Encoder Issues
 
No, can you instruct us on how to wire that?

tuyauxtu 03-02-2013 10:02
Re: VEX 393 Encoder Issues
 
Hi, I went under the assumption that as an I2C bus device it could not be connected to the DIO portion of the DSC like a regular USDigital encoder.

The encoder cable has white (data), yellow (clock), red (+5V) and black (ground). We made up a female-female connector so that the red maps to the top I2C pin in the DSC (5V), the yellow to the next pin down (SCL), the white to the SDA and the black to ground. I'd appreciate it if you could post your c++ code if you are reading values from the I2C bus.

I can read the encoder in java by extending the SensorBase class (trying to mimic devices like the HiTechnicColorSensor and HiTechnicCompass), however the data is not making sense:
The returned values for the device information seem to be missing the last byte in each address (getting only 7 of the 8, first clue something's not right!), and when I read the addresses 0x40 upwards (per http://www.vexforum.com/wiki/index.p...Motor_Encoders, compensating for the unsigned integers, I get what looks like individual values in each address which follow the motor rotation but the MSB and LSB rotation tick bits 0x40 and 0x41 seem to be reversed (second clue). I doubt that I am using the I2C read method correctly in that I should be able to read, say 4 bytes in one go, starting at 0x40 and get the first rotation bytes, then combine them to an integer number that counts up and down as the motor moves. Comes out as garbage, third clue.

FRC Team 781's experience so far, I'll post if I make any progress.
Pat

eddie12390 16-02-2013 15:54
Re: VEX 393 Encoder Issues
 
Quote:
Originally Posted by tuyauxtu (Post 1226894)
Hi, I went under the assumption that as an I2C bus device it could not be connected to the DIO portion of the DSC like a regular USDigital encoder.

The encoder cable has white (data), yellow (clock), red (+5V) and black (ground). We made up a female-female connector so that the red maps to the top I2C pin in the DSC (5V), the yellow to the next pin down (SCL), the white to the SDA and the black to ground. I'd appreciate it if you could post your c++ code if you are reading values from the I2C bus.

I can read the encoder in java by extending the SensorBase class (trying to mimic devices like the HiTechnicColorSensor and HiTechnicCompass), however the data is not making sense:
The returned values for the device information seem to be missing the last byte in each address (getting only 7 of the 8, first clue something's not right!), and when I read the addresses 0x40 upwards (per http://www.vexforum.com/wiki/index.p...Motor_Encoders, compensating for the unsigned integers, I get what looks like individual values in each address which follow the motor rotation but the MSB and LSB rotation tick bits 0x40 and 0x41 seem to be reversed (second clue). I doubt that I am using the I2C read method correctly in that I should be able to read, say 4 bytes in one go, starting at 0x40 and get the first rotation bytes, then combine them to an integer number that counts up and down as the motor moves. Comes out as garbage, third clue.

FRC Team 781's experience so far, I'll post if I make any progress.
Pat
Is there any chance that you could post the code that you have so far? We'd like to look into it.

tuyauxtu 17-02-2013 10:02
Re: VEX 393 Encoder Issues
 
Certainly, I'll post this morning, there a just a couple of things I want to confirm first at the build site.
Pat

tuyauxtu 17-02-2013 16:53
Re: VEX 393 Encoder Issues
 
Well, morning turned into a build-related time dilation. Here is the VexIntegratedMotorEncoder.java code, which is certainly not as polished/complete as I would like! Please treat as a work in progress!

Next post will have some usage/warning info. Apologies for posting code this way.

Pat

Code:
/*----------------------------------------------------------------------------*/
/* Copyright (c) FIRST 2008-2012. All Rights Reserved.                        */
/* Open Source Software - may be modified and shared by FRC teams. The code  */
/* must be accompanied by the FIRST BSD license file in the root directory of */
/* the project.
/* This class based on WPILIBJ HiTechnic NXT Color Sensor
/*----------------------------------------------------------------------------*/

package sensorExtensions;

//import java.lang.Object;

import edu.wpi.first.wpilibj.DigitalModule;
import edu.wpi.first.wpilibj.I2C;
import edu.wpi.first.wpilibj.SensorBase;
import edu.wpi.first.wpilibj.Timer;
import edu.wpi.first.wpilibj.livewindow.LiveWindow;
import edu.wpi.first.wpilibj.livewindow.LiveWindowSendable;
import edu.wpi.first.wpilibj.parsing.ISensor;
import edu.wpi.first.wpilibj.tables.ITable;

/**
 * VEX Integrated Motor Encoder.
 *
 * This class allows access to a VEX Integrated Motor Encoder on an I2C bus.
 *
 * Details on the sensor can be found here:
 *  http://www.vexforum.com/wiki/index.php/Intergrated_Motor_Encoders
 *
 * our experience is that this cannot run at the same time as a HiTechnic Colour Sensor plugged into the NXT port
 *
 * the first physically connected IME has to be accessed using the default address, then have its address changed,
 * then unset it termination state so it can pass into to the next in the chain connected device. For the next device you
 * follow the same steps, but leave it terminated if it is last in the chain.
 *
 */
public class VexIntegratedMotorEncoder extends SensorBase implements ISensor, LiveWindowSendable {

    /**
    * An exception dealing with connecting to and communicating with the
    * device
    */
    public class IntegratedMotorEncoderException extends RuntimeException {

        /**
        * Create a new exception with the given message
        * @param message the message to pass with the exception
        */
        public IntegratedMotorEncoderException(String message) {
            super(message);
        }
     
    }
   

    private static final boolean mVerbose = false; // false to suppress development console messages
    private static final byte kDefaultAddress = 0x60;
    private byte m_address = kDefaultAddress;
    private static final byte kDeviceStatusRegister = 0x23;
   
    private static final byte kManufacturerBaseRegister = 0x08;
    private static final byte kManufacturerSize = 0x8;
    private static final byte kSensorTypeBaseRegister = 0x10;  // was 0x10 for color sensor;
    private static final byte kSensorTypeSize = 0x08;
   
    private static final byte kSignedVelocityRegisterMSB = 0x3e;
    private static final byte kSignedVelocityRegisterLSB = 0x3f;

    private static final byte kUnSignedVelocityRegisterMSB = 0x44;
    private static final byte kUnSignedVelocityRegisterLSB = 0x45;

    private static final byte kRotationRegisterLowLSB = 0x41;
    private static final byte kRotationRegisterLowMSB = 0x40;
    private static final byte kRotationRegisterMiddleMSB = 0x42;
    private static final byte kRotationRegisterMiddleLSB = 0x43;
    private static final byte kRotationRegisterHignMSB = 0x47;
    private static final byte kRotationRegisterHighLSB = 0x46;
       
    private static final byte kClearDeviceCounters = 0x4a;
    private static final byte kDisableTerminator = 0x4b; // so next device in chain can be seen
    private static final byte kEnableTerminator = 0x4c; // default, device is last in chain
    private static final byte kChangeDeviceAddress = 0x4d;
    private static final byte kLowestDeviceAddress = 0x20;
    private static final byte kHighestDeviceAddress = 0x5e;   
   
    // see http://www.vexforum.com/showthread.php?p=255691
    // says 39.2 times per output revolution for high torque and 24.5 times per output revolution high speed
    // also from http://www.vexrobotics.com/276-1321.html get
    // Measures 627.2 ticks per revolution of the output shaft. (High Torque Configuration)
    // Measures 392 ticks per revolution of the output shaft (High Speed Configuration)
    private static final double kTicksPerRevHighTorque = 627.2; // factor with normal high torque gearing
    private static final double kTicksPerRevHighSpeed = 392; // factor with optional high speed gearing
    private double m_TicksPerRev;
    private I2C m_i2c;
    private int m_Version;
    private int m_Type;
    private int m_BoardID;
    private byte m_DeviceStatus;
    private boolean m_Terminated;
    private boolean m_Overflow;
    private boolean m_Diagnostic;
    private int m_Direction;

    /**
    * Constructor.
    *
    * @param slot The slot of the digital module that the sensor is plugged into.
    * @param newAddress1 The new address of the first encoder.
    * @param newAddress2 The new address of the second encoder.
    * @param gearing Whether the gearing is set to standard high torque or optional high speed.
    */

        public VexIntegratedMotorEncoder(int slot, byte newAddress, String gearing, boolean setTerminated) {
        Timer myTimer = new Timer();
        myTimer.start();
        DigitalModule module = DigitalModule.getInstance(slot);
        //m_i2c = module.getI2C(kAddressRegister);
        m_i2c = module.getI2C(kDefaultAddress);
        System.out.println("initial device info ++++++++++++++++++++++++++++++++++++++++++++++++++++++");
        System.out.println("device is " + (m_i2c.addressOnly() ? "not " : "") + "present at address 0x" + Integer.toHexString(kDefaultAddress));
        System.out.println("+++ new device info ++++++++++++++++++++++++++++++++++++++++++++++++++++++");
        if (newAddress != kDefaultAddress) { // change address if not using the default address
            myTimer.delay(0.5); // put in a delay to see if we can get the second chain device to be connected
            setAddress(newAddress);
            m_i2c.free(); // release the previously addressed object
            m_i2c = module.getI2C(m_address);
            System.out.println("device is " + (m_i2c.addressOnly() ? "not " : "") + "present at address 0x" + Integer.toHexString(m_address));
        }
       
        setTicksPerRev(gearing); //
       
        // terminate device as required
        if (setTerminated) { // requesting device to be terminated
          setTerminated();
        }
        else { // requesting device to be un-terminated
            unSetTerminated();
        }
    }
       
    /**
    * Destructor.
    */
    public void free() {
        if (m_i2c != null) {
            m_i2c.free();
        }
        m_i2c = null;
    }

    public void reset() {
        m_i2c.write(kClearDeviceCounters, (int) 1); // can write any value to the register
    }

   
    public double getRaw() {
        byte[] buffer = new byte[1];
        m_i2c.read(kRotationRegisterLowMSB, (byte) buffer.length, buffer);
        byte low_msb = buffer[0];
        m_i2c.read(kRotationRegisterLowLSB, (byte) buffer.length, buffer);
        byte low_lsb = buffer[0];
        m_i2c.read(kRotationRegisterMiddleMSB, (byte) buffer.length, buffer);
        byte mid_msb = buffer[0];
        m_i2c.read(kRotationRegisterMiddleLSB, (byte) buffer.length, buffer);
        byte mid_lsb = buffer[0];
        return combine4Bytes(low_lsb, low_msb, mid_lsb, mid_msb);
       
    }
   
    public double getRawHigh() {
        byte[] buffer = new byte[1];
        m_i2c.read(kRotationRegisterHignMSB, (byte) buffer.length, buffer);
        byte high_msb = buffer[0];
        m_i2c.read(kRotationRegisterHighLSB, (byte) buffer.length, buffer);
        byte high_lsb = buffer[0];
        return combine2Bytes(high_lsb, high_msb);
    }
   
    public double combine4Bytes(byte low_lsb, byte low_msb, byte mid_lsb, byte mid_msb) {
        long m_low_lsb = (long) (low_lsb & 0xff);
        long m_low_msb = (long) ((low_msb << 8) & 0xff00);
        long m_mid_lsb = (long) ((mid_lsb << 16) & 0xff0000);
        long m_mid_msb = (long) ((mid_msb << 24) & 0xff000000);
        return (m_low_lsb | m_low_msb | m_mid_lsb | m_mid_msb);
    }
   
    public double combine2Bytes(byte mid_lsb, byte mid_msb) {
        short m_mid_lsb = (short) (mid_lsb & 0xff);
        short m_mid_msb = (short) ((mid_msb << 8) & 0xff00);
        return (m_mid_lsb | m_mid_msb);
    }
   
    /**
    * Set the Address of the encoder
    * This method is used to set the encoder to an even address within range of 0x20 to 0x5E,
    * from its initial default of 0x60 by writing to address 0x4D
    * @param mode The address to set
    */
    public void setAddress(byte address) {
        if (address < kLowestDeviceAddress || address > kHighestDeviceAddress) {
            throw new IntegratedMotorEncoderException("Encoder Address Out Of Range");
        }
        else if (address % 2 != 0) {
            throw new IntegratedMotorEncoderException("Encoder Address Must Be Even");
        }
        else {
            int m_old_address = m_address;
            m_i2c.write(kChangeDeviceAddress, (int) address);
            m_address = address;
            if (mVerbose) {
                System.out.println("setAddress(): Address changed from 0x" + Integer.toHexString(m_old_address) + " to 0x" + Integer.toHexString(m_address));
            }
        }
    }
 
   
    public boolean getTerminated() {
        byte[] address = new byte[1];
        m_i2c.read(kDeviceStatusRegister, (byte) address.length, address);
        m_Terminated = ((int) address[0] & 0x1) == 1 ? true : false;
        if (mVerbose) {
            System.out.println("getTerminated() kDeviceStatusRegister = : " + Integer.toHexString(address[0]) + " raw and m_Terminated is " + m_Terminated);
        }
        return m_Terminated;
    }

    public void setTerminated() {
        if (! this.getTerminated()) { // if device is not already terminated then write bytes to terminate
            m_i2c.write(kEnableTerminator, 1);
            m_Terminated = true;
            System.out.println("setTerminated(): device status changed to terminated");
        }
        else {
            System.out.println("setTerminated(): device status already set to terminated");
        }
    }
 
        public void unSetTerminated() {
        if (this.getTerminated()) { // if device is already terminated then write bytes to terminate
            m_i2c.write(kDisableTerminator, 1);
            m_Terminated = false;
            System.out.println("unSetTerminated(): device status changed to not terminated");
        }
        else {
            System.out.println("unSetTerminated(): device status already set to not terminated");
        }
    }
 
       
    public double getRevs() {
        return this.getRaw() / m_TicksPerRev;
    }
   
    public double get() {
        return (this.getRevs() % 1) * 360.0;
    }

    public void setTicksPerRev(String gearing) {
        // adjust ticks per revolution depending on gearing
        if (gearing.toLowerCase().equals("torque")) {
            m_TicksPerRev = kTicksPerRevHighTorque;
        }
        else if (gearing.toLowerCase().equals("speed")) {
            m_TicksPerRev = kTicksPerRevHighSpeed;
        }
        else {
            System.out.println("Invalid Gear Ratio Input As: " + gearing);
        }
        if (mVerbose) {
            System.out.println("setTicksPerRev(): " + gearing + " resulted in ticks per revolution set to " + m_TicksPerRev);
       
        }
    }

    /*
    * Live Window code, only does anything if live window is activated.
    * TODO: Should this have its own type?
    */
    public String getSmartDashboardType(){
        return "VexEncoder";
    }
    private ITable m_table;
   
    /**
    * {@inheritDoc}
    */
    public void initTable(ITable subtable) {
        m_table = subtable;
        updateTable();
    }
   
    /**
    * {@inheritDoc}
    */
    public ITable getTable(){
        return m_table;
    }
   
    /**
    * {@inheritDoc}
    */
    public void updateTable() {
        if (m_table != null) {
            m_table.putNumber("Rotation", get());
        }
    }
   
    /**
    * {@inheritDoc}
    */
    public void startLiveWindowMode() {}
   
    /**
    * {@inheritDoc}
    */
    public void stopLiveWindowMode() {}
}

tuyauxtu 17-02-2013 16:55
Re: VEX 393 Encoder Issues
 
Continuing the previous post with the Integrated Motor Encoder code:

You plug the first IME into the second (right) set of I2C pins using a jumper cable as mentioned previously. The constructor sets the digital sidecar module number, the address you want to use (there are restrictions on what is allowed), the gearing type ("speed" or "torque" which changes the ticks per revolution), and the desired termination state, true being terminated.

I set the first IME to address 0x50/un-terminated and the second to 0x52/terminated. You can see in the code the values which are allowed.

When you first plug in and power up the encoder(s), the led light(s) should be flashing orange showing that it is using the default address and is terminated.

After you run your Netbeans project, if things work, the first connected encoder should have a green flash every 3 seconds or so, and the second should double flash at about the same rate. This means the first has been readdressed and is not terminated, while the second is also readdressed but is terminated. You then read the encoders with a getRaw() for counts, a get() for degrees (wraps at 360°) and a getRevs for encoder revolutions. You can also reset the encoder to zero.

While loading the code, there should be some output messages that show the addresses and termination states as they are configured. Please note that unless you power down the encoders they will keep their last set addresses and termination states, and should still work after disabling and reenabling, as well a power cycle. You can of course comment out the messages.

We could not get the encoders to co-exist with a HiTechnic colour sensor plugged into the NXT port. It may work if the sensor connecting cable is short, but we found that that the encoders would not always read consistently with an NXT sensor plugged in.

We also found that there appears to be a wiring problem with one of the supplied cables that we are still trying to track down. These cables are now buried in the robot, so I suggest testing a harness ahead of time to attempt to preclude such a problem.

Pat

eddie12390 17-02-2013 21:28
Re: VEX 393 Encoder Issues
 
Quote:
Originally Posted by tuyauxtu (Post 1235110)
Continuing the previous post with the Integrated Motor Encoder code:

You plug the first IME into the second (right) set of I2C pins using a jumper cable as mentioned previously. The constructor

-cut out to save space-

Pat
Thanks a lot for posting that. I was thinking of a similar approach to yours but I haven't had the time to work on it. I really appreciate it :)

joelg236 17-04-2013 19:37
Re: VEX 393 Encoder Issues
 
We're having troubles with this code. When the encoder is not plugged in, it seems to pause forever when initialising. (prints "initial device info ++++++++++++++++++++++++++++++++++++++++++++++++++ ++++" and nothing more, freezing the entire code)

Any help?


All times are GMT -5. The time now is 11:19.

Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi