- #Flashcode encoder install#
- #Flashcode encoder update#
- #Flashcode encoder code#
- #Flashcode encoder trial#
It does sound like a hardware problem to me.
#Flashcode encoder install#
I don’t really want to get into a tutorial on ConVEX in this thread, my normal recommendation would be to install on top of PROS so you can use their downloader.
Don’t forget to remove any motors that may be different.
#Flashcode encoder code#
Getting ConVEX up and running may take some time of you have not done that before, however, if you are able to get it installed, ConVEX will initialize the IMEs when it runs, the user code does not matter, I suggest you just compile and download one of the demos. In the meantime - do you have any sample code for the IME’s in ConVEX?
#Flashcode encoder update#
I’ll give you an update when I test it in ConVEX once it installs.
#Flashcode encoder trial#
I think I already used up the Eas圜 trial so I’ll install ConVEX right now to test the IME’s in there. The fw version is 9.68, so the same firmware is the same. The only other thing I can think of is a problem with the termination on the IME, but that’s very unlikely. The only other thing I can think of is a problem with the termination (and I mean the pass through switch) on the IME, but that’s very unlikely.Īny chance you have Eas圜 (or ConVEX) installed anywhere so we could check them with that ? I will install 3.62 later and test if you have not sorted this out by then. It’s probably nothing to do with firmware but best to check. what is the fw version shown on the ROBOTC startup screen ? (ROBOTC 3.60 uses firmware 9.68). I though that they were the same firmware, but perhaps not. To be honest I never upgraded from 3.60 to 3.62. The IMEs should initialize even if you don’t use them in the code. Your code has nothing to do with initialization, it happens when the cortex is powered and the ROBOTC firmware runs. Each of the three different wires each work with the first IME.Ĭorrect. I have tried three different 4-way wires (not sure of the specific name of the wires) so that shouldn’t be the issue. I read that if they are that color they are not initializing, but I initialized the first one the same way I initialize the second one. The second IME on the chain is a red/orange color with a slight tint of green. The LED on the first IME (no matter if I plug the left one or right one in first) is going to be slowly blinking green and reading correctly. I tried it multiple times and the cable plastic ends are flush with each other pushed fully into the module. Yes the cables are plugged in all of the way. What are the leds doing ? (orange, green, flashing). I just get tired of saying Eas圜 or ROBOTC (but there, you made me type it anyway).Īre you sure you plugged the cables in all the way, they can be quite hard to install. Integrated development environment (IDE). What can you see in the ROBOTC motor debug window when running the motors? You would access these three sensors using nMotorEncoder as follows. If the led does not turn on when running the motor perhaps you forgot to change the motor gear to the encoded gear. When you run the motors the led should flash green at a faster rate until it stays on constantly at the maximum motor speed. In general, if the LED is red/orange then the I2C sensor has not been initialized, check the cables are plugged in correctly.Ī working sensor should flash the led green occasionally, the last sensor in the chain will have a double flash.
Indicating which encoder had which color leds would have been better information, anyway… #pragma config(Motor, port5, rightArmGear, tmotorVex393, openLoop, reversed) #pragma config(Motor, port4, leftArmGear, tmotorVex393, openLoop, encoder, encoderPort, I2C_3, 1000) #pragma config(Motor, port3, LeftMotor, tmotorVex393, openLoop, encoder, encoderPort, I2C_2, 1000) #pragma config(Motor, port2, RightMotor, tmotorVex393, openLoop, encoder, encoderPort, I2C_1, 1000) #pragma config(Sensor, I2C_3, ArmEnc, sensorQuadEncoderOnI2CPort,, AutoAssign) #pragma config(Sensor, I2C_2, driveEncLeft, sensorQuadEncoderOnI2CPort,, AutoAssign) #pragma config(Sensor, I2C_1, driveEncRight, sensorQuadEncoderOnI2CPort,, AutoAssign) #pragma config(Sensor, dgtl1, Red_Or_Blue, sensorTouch) #pragma config(I2C_Usage, I2C1, i2cSensors) It looks like you missed configuring I2C_3, add that to the arm motor and you have this. This is how the motors/sensors are configured:
0 kommentar(er)
