fischertechnik community forum

Ok, actually the base of the problem is getCameraFrame(). The path is correct, I just made a slight mistake commenting out the creation of filename. So because getCameraFrame doesn't work anymore, this code: pic = None while pic == None: pic = txt.getCameraFrame() print("pic") gives this output: <sn...

All errors I could get: 1: using txt.getCameraFrame() Exception in thread Thread-1: Traceback (most recent call last): File "/wheel/SSDSpace/devel/ftcommunity-TXT-0.9.3/output/target/usr/lib/python3.5/threading.py", line 914, in _bootstrap_inner File "/wheel/SSDSpace/devel/ftcommunity-TXT-0.9.3/outp...

More info. First: the error I get now: $ ./run_python Mirft2.py Connected to TX2013 firmware version 4.2.4 Camera connected Traceback (most recent call last): File "Mirft2.py", line 41, in <module> videv = ftrobopytools.camInit(fps, width, height, 0, 0) ftrobopytools.error: error set pixel format in...

@Richard,

Can you tell me how much of OpenCV is actually implemented in the cfw? I tried to create a gray image using a standard OpenCV instruction which was unknown during execution. Also, with all errors it shows a path inside /home/Richard/..... missing something.

hvn

You're welcome!

Hi,

This is a compilation video of 45 minutes recorded in full-HD of the convention in Schoonhoven at 28-10-2017: https://youtu.be/2Qv9NLs5KVA.
Pictures of the convention: https://www.flickr.com/photos/89022424@ ... 8501780514

I hope you enjoy.

hvn

Now I really get puzzled. In my code (a part which has nothing to with OpenCV) I use: while pic == None: pic = txt.getCameraFrame() Where it used to work, apart from getting quite a few 0 byte images, now the code hangs on this line. The final error I get after ^C is "struct.error: ubyte format requ...

The error I first got was: "ftrobopytools.error: error set pixel format in cam_init Now I get another error: "undefined symbol: Py_InitModule4". What I used from you ftDigiCam.py is the initialization: import ftrobopytools fps = 15 width = 320 height = 240 videv = ftrobopytools.camInit(fps, width, h...

I installed ftrobopytools and get a pixel error using .initCam(fps, width, height, 0, 0) while partly following your github example, actually on both firmwares. Any idea why?

I'm using OpenCV from my code, and I just find that the errors occur using Python 2.7 and not Python 3. And I'm still having the habit to use my Python 2.7 script so I guess I better remove that. But I've used OpenCV with Python 2.7 as well in the past. So is this for the TXT indeed only to be used ...

Hi Richard, Is there an example on how to use opencv with cfw? The usual way using import cv2 import numpy as np image = cv2.imread(filename) gives errors on cv2, numpy and imread: ImportError on both cv2 and numpy and NameError: global name 'imread' is not defined (after removing cv2). So can you t...

Hi Torsten,

Thank you for the answer. Didn't know about that project and will give it a try.

Regards,

hvn

@Torsten as discussed in http://forum.ftcommunity.de/viewtopic.php?f=33&t=4470, is it possible to add OpenCV to ftrobopy somehow so it can be used on the original firmware?

Thank you.

hvn

Of course, if someone else wants to beat me to it: Pull requests are always welcome

Since OpenCV is present, I'm fine waiting for it

Hi Richard,

That great news. This means I can already make a start, and on the original firmware would be a very nice addition as well, so I'll ask Torsten. When do you think OpenCV 3.3 will be included?

Regards,

hvn

Hi,

Before I make any attempt to do so: would it be possible to install OpenCV on the controller to use with Python?

Thanks

hvn

Hi, Recently I've tried again with ROBOPro and for me things haven't changed. So with the newest version of ROBOPro I still don't have a live-camera image via wine. I plan to do some experiments to use OpenCV for object detection in combination with copying grabbed images to a computer (which alread...

Ok, I found the interpreter and the FtLoader.exe in storage. Thomas advised me to use FtLoader with wine, so I tried with the result that with USB selected, "No ft-devices found / keine ft-Geraete gefunden". This isn't promising.

Ok, I knew something was different from what I remembered. My directory is Roboint_Compiler-1-01 and missing "interpreterV1.01.rom". I unzipped this directory straight from what I still had in storage...

Ok, that was an oops. I was convinced I had... it has built successfully now, but I find another problem. I can't run any .hex file unless I have interpreter.hex and the windows version of ftupload(er). I've searched for both (for ftupload(er) also inside the ROBOPro directory) and unable to find th...