Recent Posts

1

Kilobot / Re: Kilobots not responding to OHC

« Last post by kteam on June 19, 2018, 08:14:23 AM »

Hi,

if the Robot didn't respond even after an firmware install means that the IR calibration has been erased (during update) or is not more correct.
in Both case, the only solution is to send back the robot to K-team for calibration.

Best regards
K-Team

2

Kilobot / Real Time coding of kilobots from eclipse and matlab

« Last post by pradyum2104 on May 31, 2018, 07:03:51 PM »

I want to use the real time data of Matlab variables in Eclipse and want to generate the hex file from eclipse so as to burn it to the kilobots. Is there a way to send real time data from Matlab variables to eclipse environment?  and also is there a possibility to code kilobots with hex files from eclipse instead of using the kilogui application?

3

Kilobot / Kilobots not responding to OHC

« Last post by Amaya on February 27, 2018, 03:55:04 PM »

Hi,

I am actually working with Kilobots on Debian. I have followed the instructions here : https://www.kilobotics.com/documentation.
Some kilobots work perfectly, while others do not repond at all to the OHC (when I use the kiloGUI interface), even though I have correctly updated the firmware on these kilobots, and they are turned on (green light flashing).
Is there any explanation for this issue? What should I do?

Thanks.

4

Khepera IV / ssh connection- response too slow

« Last post by Firhanh on November 11, 2017, 02:31:16 AM »

Hi,

I'm able to connect my PC to khepera IV via ssh connection, the problem is the connection response is too slow..
 
I've tried to ping khepera IV IP adress from my PC and the result is shown below

Firhan@Hz:~$ ping 10.42.0.134
PING 10.42.0.134 (10.42.0.134) 56(84) bytes of data.
From 10.42.0.1 icmp_seq=14 Destination Host Unreachable
From 10.42.0.1 icmp_seq=15 Destination Host Unreachable
64 bytes from 10.42.0.134: icmp_seq=9 ttl=64 time=18131 ms
64 bytes from 10.42.0.134: icmp_seq=13 ttl=64 time=8056 ms
64 bytes from 10.42.0.134: icmp_seq=20 ttl=64 time=907 ms
64 bytes from 10.42.0.134: icmp_seq=21 ttl=64 time=4929 ms
64 bytes from 10.42.0.134: icmp_seq=22 ttl=64 time=3912 ms
64 bytes from 10.42.0.134: icmp_seq=23 ttl=64 time=2888 ms
64 bytes from 10.42.0.134: icmp_seq=24 ttl=64 time=1864 ms
64 bytes from 10.42.0.134: icmp_seq=25 ttl=64 time=840 ms
The ping is too high

but when I tried to ping my PC from khepera IV the response is great
root@khepera4_1118:~$  ping 10.42.0.1                                           
PING 10.42.0.1 (10.42.0.1) 56(84) bytes of data.                               
64 bytes from 10.42.0.1: icmp_seq=1 ttl=64 time=5.73 ms                         
64 bytes from 10.42.0.1: icmp_seq=2 ttl=64 time=5.73 ms                         
64 bytes from 10.42.0.1: icmp_seq=3 ttl=64 time=5.70 ms                         
64 bytes from 10.42.0.1: icmp_seq=4 ttl=64 time=5.70 ms                         
64 bytes from 10.42.0.1: icmp_seq=5 ttl=64 time=2.86 ms                         
64 bytes from 10.42.0.1: icmp_seq=6 ttl=64 time=6.65 ms                         
64 bytes from 10.42.0.1: icmp_seq=7 ttl=64 time=6.47 ms                         
64 bytes from 10.42.0.1: icmp_seq=8 ttl=64 time=5.64 ms                         
^C                                                                             
--- 10.42.0.1 ping statistics ---                                               
8 packets transmitted, 8 received, 0% packet loss, time 7015ms                 
rtt min/avg/max/mdev = 2.868/5.565/6.652/1.085 ms       


Have anyone face this problem before? any solution?
I need your advice,

Thank you

Firhan

5

Khepera IV / Installing Robot Operating System (ROS) on khepera IV

« Last post by Firhanh on November 08, 2017, 08:37:07 AM »

Hi,

I want to install ROS in Khepera IV to make it easier to communicate with my PC.
The problem is I don't know if ROS is compatible with Khepera IV or not.
Does anyone have experience in doing this? Is it possible to install ROS on Khepera IV?

I'm looking for advice..
Thank you.

6

Khepera IV / Peoblem with SSH

« Last post by DrIsrael on September 11, 2017, 02:46:57 PM »

I have problems to connect with SSH
It appears "write failed: broken pipe" as message
when I try ssh root@IP
However Ping process works fine.

7

Khepera III / Khepera III in morse simulator

« Last post by pedroosi on August 14, 2017, 11:44:45 AM »

Hello

I am a university student and I am working with khepera III robot.
I need to define this robot in the Morse simulator.
Has anyone already done this?
Is there any place where I can download the configuration for the morse simulator?

Thank you

8

Kilobot / Re: OHC Resetting

« Last post by kteam on June 01, 2017, 08:30:40 AM »

Have you tried to reflash the OHC using AVRstudio? Normally it solve the problem of corrupted Flash.

But, in your case, if the device manager did not find the AVRispII on the OHC, you won't be able to reflash it.

Try again with AVRstudio, if it doesn't solve the problem, please contact K-Team and return the OHC for repair.

Best regards

9

Kilobot / Re: OHC Resetting

« Last post by Dasto on May 31, 2017, 02:22:57 PM »

The drivers were installed and working, in fact I was able to flash the OHC successfully. Only after the failure to flash the Kilobot did it start to behave this way, and no changes were made to Windows. It was literally a few seconds between unplugging the OHC to plugging it in again.

I tried a new Win7 machine as per your instructions, however as the OHC is in some weird mode, so it is not possible to connect to it as per step 2.

As soon as I plug in the OHC, the lights appear as in my video. The 2 read lights are permanently on, and the green ones flashing. Device Manger is refreshing every 4 seconds. Usually when Device Manager refreshes it's because it detects a new device. In this case, as it refreshes every 4 seconds, it detects the OHC then loses it, detects it, loses it etc. so I presume the OHC is restarting.

What else can I try?

 

10

Kilobot / Re: OHC Resetting

« Last post by kteam on May 31, 2017, 09:19:25 AM »

Hello,

you have certainly not correctly change the driver with Zadig. Please refer to our procedure to update the Kilobot here:
http://ftp.k-team.com/kilobot/user_manual/kilobot_update.pdf

Best regards
K-Team