Sponsored Content
Full Discussion: Arduino Robot Tank Project
Special Forums Hardware Arduino Robot Tank Project Post 303043242 by Neo on Wednesday 22nd of January 2020 05:04:57 AM
Old 01-22-2020
Some FYI on this project.

I'm currently waiting on KeyeStudio, the supplier of this RobotTank kit, to come off their Chinese New Years holiday and provide us with the basic "demo" Arduino sketches for this, instead of the Mixly graphical "code" they provide.

There are a few reasons for this. First, I'm personally not into graphical programming (like Mixly, which seem like a child's programming toy to me) and strongly prefer the C++ like Arduino IDE coding. Second, when I downloaded the mixly archive file provided by KeyeStudio, my Avast anti-virus scanner complains the archive contains some malware; and I'm just too busy to debug and "de-virus" the KeyeStudio Mixly archive.

KeyeStudio has kindly informed me they would get me the actual Arduino demo sketches for this robot kit after the Chinese New Years holiday is past, sometimes in February. I was going to make a video on the "virus alert" when unarchiving the mixly archive from KeyeStudio, but I've just been busy and making a "look at this virus alert" video for a supplier has not been a priority here. KeyeStudio was not satisfied with my photos of the virus alert(s) and requested a video!


I imagine, however, I'll start coding this robot long before I get the demo Ardunio sketches from KeyeStudio, but let's see what happens. My plan is to go beyond the kit and add some other sensors plus some other command and control boards. Let's see how long this kit can hold our attention. We have been playing with the kit little by little, not in a hurry, since we are waiting on supplier to get us the Arduino demo sketches before diving too far into this.

More later as we progress......

Note: The spelling is correct. It is KeyeStudio, not KeyStudio.
 

6 More Discussions You Might Find Interesting

1. Windows & DOS: Issues & Discussions

Adding robot and drives

Hi All Im running veritas netbackup 6.5.5, on MWindows 2003 master server. Ive just added a Quantum PX500 with 2 drives, the problem im facing is that now under the storage unit tab on console all the storage unit types for NDMP have the new robot listed and not the original one. The set up i... (0 Replies)
Discussion started by: blossy786
0 Replies

2. Programming

Arduino-cli - Uploading to Unknown Chinese Arduino Boards using the Arduino Command Line Interface

In my further exploration of Arduino, today I decided to install the arduino-cli on my mac today. https://github.com/arduino/arduino-cli I followed the instructions for macOS but when I got to this part: arduino-cli board list I got the dreaded "Unknown" Fully Qualified Board Name... (1 Reply)
Discussion started by: Neo
1 Replies

3. Programming

More Arduino Stuff...

HI all... (Apologies for any typos.) To add to Neo's Arduino subject matter I have decided to upload this in ".zip" format. Ignore "*.info" files these are AMIGA icons only and also the "HAM" drawer as these are photos in ancient AMIGA HAM modes. I have noticed that there are current... (6 Replies)
Discussion started by: wisecracker
6 Replies

4. Programming

Arduino UNIX Time - Syncing Computer UNIX Time to Arduino Time with Python

Just finished a quick Python script to send the current unix time over to the Arduino from macOS, so in the absence of GPS or some other way to get the unix timestamp (epoch time) to the Arduino, I can get my macOS and Arduino UNO synced to within a second. Normally, when the Arduino starts... (9 Replies)
Discussion started by: Neo
9 Replies

5. Programming

Arduino Project with NB-IoT (3GPP) and LoRa / LoRaWAN

My favorite projects are always related to the "latest" tech in command and control, networking and network communications. This Elecrow GSM/GPRS/EDGE SIM5360E 3G Shield seems to be the "latest and the greatest" as far as 3G and GPS, as far as I can see so far, but I has it drawbacks for sure.... (6 Replies)
Discussion started by: Neo
6 Replies

6. Programming

Arduino Project: iPhone to HM-10 BLE to NB-IoT Shield to NB-IoT Network to Internet to Linux Server

This post describes a "work in progress" project I started today. Here is the High Level Overview: Currently, this project sits on my desk as an Arduino UNO (on the bottom), an NB-IoT Shield (sandwiched in the middle), a Sensor Shield (on top) with a HM-10 BLE Module (in the little... (13 Replies)
Discussion started by: Neo
13 Replies
MAKEDIST(1)						      General Commands Manual						       MAKEDIST(1)

NAME
makedist - a distribution kit maker SYNOPSIS
makedist [ -dhqvV ] [ -c dir ] [ -s size ] [-f manifest ] DESCRIPTION
Makedist is a rather simpleminded shar program that knows how to pack files into multiple kits of approximately 50000 bytes each. The shar scripts produced assume very little about the target machine; there is correspondingly little error checking done compared to other shar programs. Alternatively, with the -c option, you can create a directory containing the whole source tree, and then pack it up using your own shell archiver. If you are using the copyright expansion feature (as determined by packinit), then you have to pack your distribution using this program to ensure the copyright is correctly set. In order to run makedist you have to do two things: 1) Create a .package file in the package's top-level directory by running packinit. This program will ask you about your package and remember what you tell it so that all the dist programs can be smart. 2) Create a MANIFEST.new file in your top-level directory that lists all the files in your package. The filename should be the first field on each line. After some whitespace you can add a comment describing your file (briefly). After running makedist, you will have a set of kits in your top-level directory. If your package name is "foo", they will be named foo.kit1, foo.kit2, etc. The file created PACKLIST file is automatically added to the distribution and tells which files come with which kits. If you used the -c option, you will end-up with a single directory instead, containing the whole distribution, ready to be sent to the end-user. If a file is too large to be packed as-is in one archive, it will be automatically split in smaller parts. Only the first 11 characters of the file will be kept though, and makedist will abort if two distinct files are to be split and have the same 11 first characters in their names. The split files will automatically be reconstructed at the end of the archive extraction by runnning a script generated in PAC- KNOTES. You may then mail your kits via kitsend or post them with kitpost. OPTIONS
The following options are handled by makedist: -c dir Tell makedist that the distribution should be copied (mirrored) in the specified directory, instead of producing shell archives. Compatible with the -q option. -d Turn on debug mode. Probably not useful. -f file Use file as manifest. By default, MANIFEST.new is used. -h Print help message and exit. -q Quick production of the kits: the checked-out version of the files is used, instead of using the RCS file to actually get the latest checked-in version. This will save some considerable time, but you have to be sure the checked-out version is up-to-date or you might end up with an inconsistent package. -s size Set maximum kit size to size bytes. -v Verbose mode: trace kit building process or tree mirroring. -V Print version number and exit. AUTHORS
Larry Wall <lwall@netlabs.com> (version 2.0) Raphael Manfredi <ram@hptnos02.grenoble.hp.com> FILES
Creates ./$package.kit* unless -c option is used. PACKLIST and PACKNOTES are also temporarily created. SEE ALSO
kitsend(1), kitpost(1), metaconfig(1), patcol(1) LOCAL MAKEDIST(1)
All times are GMT -4. The time now is 09:04 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy