Firmware 2.5


#1

Hi DI-Team,
I am new in this forum. I have a Problem with the Firmware 2.5 you have put to Git yesterday.

The File BrickPiFW_Compressed_Communication.cpp.hex is not in Git available.

In the BrickPiFW_UC1.bat you tests the BrickPi_EEPROM_UC2.hex, must be UC1.

I am from Germany an I bought the BrickPi a few weeks ago in France. But I must change the Firmware??? I am very surprised!

Thomas


#2

Hi Thomas. You should NOT change the firmware. We put that up for research / developers only. I recommend you leave the firmware as it is.

I am from America.

John


#3

Hi John,
where do I get the information that a firmware version is for customer’s?
Thomas


#4

Hey Thomas, I’m not sure I understand. Do you want to be able to figure out the version of the firmware that’s on the BrickPi+?


#5

Hi John,
no, for that you have a Testprogram in your distribution.
You told me, that the Firmware 2.5 is now only for developers. In the download there are no hints to see that.
To a appointment in the future, the Firmware 2.5 will be for customers.
So, my question is, how can I get the information, that the Firmware 2.5 can used by customers. At the moment, I can not use EV3 Sensors. So I have to change the firmware. On which date is it possible?
Sorry, my english is not so good. I hope you understand me now.
Thomas


#6

Hi Thomas, can you post a picture of your BrickPi? I want to verify that it’s a BrickPi+.

Have you tried running this program: https://github.com/DexterInd/BrickPi_Python/blob/master/Sensor_Examples/EV3-Touch.py
You should place an EV3 touch sensor on Port 2 to see it run. What are the results?

Also, which version of Raspbian for Robots are you using?
And, on your operating system have you enabled BrickPi communications? http://www.dexterindustries.com/howto/enable-or-disable-brickpi-communications/
Have you been able to make the motors move?

Thanks,

John


#7

Hi John,

thank you for your feedback.

You get a picture of my BrickPi+ as an attachment.
The Raspbian Version is: 2016.01.05_Dexter_Industries_wheezy.img
I have disabled the IR-Communication.

Here are the results of my Tests:
The Firmware seems to be ok.
All the motors moves.
The Touch-Sensor can be used but the results of the Infrared-sensor and the Color-sensor seems to be random.

Thomas

EV3-Firmware-Check.py

Trying to communicate with firmware.
PASS: Serial line setup.

Setup sensors returns: 0
Checking Firmware Version of BrickPi.
Firmware version is: 2
GREAT! Firmware is up to date!
You should be able to run EV3 sensors!


NXT-Motor moves
EV3-BigMotor moves
EV3-MiddleMotor moves


EV3-Touch.py

Button reads: 1023 -> Button pressed
Button reads: 1023
Button reads: 1023
Button reads: 1023
Button reads: 1023
Button reads: 1023
Button reads: 1023
Button reads: 1023
Button reads: 1012 -> Button not pressed
Button reads: 1013
Button reads: 1006
Button reads: 1003
Button reads: 1002
Button reads: 1002
Button reads: 1003
Button reads: 1002
Button reads: 1002
Button reads: 1002
Button reads: 1006
Button reads: 1006

EV3-Infrared.py

128
0
0
73
73
65535
65535
65535
65535
65535
65535
65535
65535
65535
65535
65535
65535
93
100
83
100
87
87
99
88
88
92
100
92
100
100
82
59
47
51
65535
65535
51
49
50
53
54
100
65535
65535
65535
65535

EV3-ColorSensor.py

65535
65535
65535
65535
65535
65535
65535
65535
65535
65535
6
6
6
6
6
6
6
6
1
1
1
0
0
0
0
0
0
0
0
0
1
1
1
1


#8

It brings up a really good point. The 65535 reading is clearly an error. You might need to write a quick filter program to filter out these results, they’re just errors from the sensor.