fred
New Member
Posts: 2
|
Post by fred on Jan 27, 2019 7:24:51 GMT -7
Hi,
I would like to try using OpenDobot instead of the "official sdk and examples" propose by dobot.cc
I'm currently on Windows with python 3.7 - 32 bits
I'm trying to use the "FPGA" version for the moment.
I fixed first classical installation issue but now I stuck on that "Cannot get board version. Giving up" errog message.
I'm able to use the dobotclient 1.3 version everything works like a charm on port COM6.
I had a look into the DobotDriver.py file and try to comment a little bit:
def BoardVersion(self):
'''
Checks board version.
Returns (success, version), where version=0 is FPGA and version=1 is RAMPS.
'''
self._lock.acquire()
result = self._read1(CMD_BOARD_VERSION)
# print(result)
self._lock.release()
return result
As a result I can see 200 time (0,0) meaning I guess there is no success to _read the board version.
How could I fixe this?
Thx in advance
Fred
|
|
|
|
Post by Max on Jan 27, 2019 13:44:32 GMT -7
That likely means a timeout waiting for response from the board. There may be a number of reasons.
But the more important question is why do you need to use open-dobot instead of original firmware that is now open-source?
Open-dobot was created to enable features that were not in the original firmware, the firmware was too unstable and dobot developers announced that they will not open the source code.
Since the original firmware is now open it can be extended. There is not many use cases left for open-dobot apart from educational.
|
|
fred
New Member
Posts: 2
|
Post by fred on Jan 28, 2019 2:55:12 GMT -7
Ok thanks for your quick answer. Meaning, now if I want to stay on FPGA, you advise to use the "dobot open software" they are sharing. Do you have a same advice for Ramps 1.4?
I'm looking for something easy to progam, I don't want to "spend" time on the low level programmation of the arm.
|
|
|
|
Post by timinmb on Jan 28, 2019 11:13:12 GMT -7
I am still interested in your software because of the ability to use a ramps 1.4. My dobot arm is a clone, and thus didn't come with the fpga. Or is it possible to clone the fpga board that came with the dobot?
|
|
|
|
Post by Max on Jan 29, 2019 18:38:14 GMT -7
Ok thanks for your quick answer. Meaning, now if I want to stay on FPGA, you advise to use the "dobot open software" they are sharing. Do you have a same advice for Ramps 1.4? I'm looking for something easy to progam, I don't want to "spend" time on the low level programmation of the arm. That depends on what kind of programming you're planning to do. If it is just to control the moves of arm and the actuator, then you can use existing API that sends the coordinates and control sequences to the original firmware. If you're looking to extend arm's capabilities then, inevitably, you'd need to change the firmware, whether it is open-dobot or the original firmware. The issue you're referring to is usually observed when accelerometers cannot be reached by the firmware. I suggest to read other threads here that discuss that: open-dobot.boards.net/thread/46/next-make-own-dobotopen-dobot.boards.net/thread/49/dobot-mpu-6500-communication-issuesopen-dobot.boards.net/thread/47/start-stepopen-dobot.boards.net/thread/48/open-dobot-write-commands-returnI am still interested in your software because of the ability to use a ramps 1.4. My dobot arm is a clone, and thus didn't come with the fpga. Or is it possible to clone the fpga board that came with the dobot? Is it possible to clone? - Yes. Does it make sense to try - probably only if you're into microelectronics. If you have the same problem as fred , then see the threads I mentioned above. |
|
