16
Mar
07

Ktechlab needs your help!

Hello everyone,

I have been using this electronic application called ktechlab for a while,i found that it is a pretty good application for electronic ppl,ppl who design circuits,ppl who write microcode and for ppl who want to build PIC.

KTechlab is a young open source electronic design automation software. It supports real-time electronics simulation and PIC microcontroller debuggin.

KTechLab includes a whole programming language called MicroBASIC and associated compiler for programming PICs. It can compile the flow diagrams into MicroBASIC and from there into an assembly language compatible with MPASM as used by the manufacturer of PICs. The assembly language can be compiled into a machine code suitable and compiler for feeding into PICs.


KTechLab uses the KMDI interface familiar to users of Kate or KDevelop. (You can change this layout but this seems to cause problems and KMDI is the most usable.) Diagrams and code are displayed as tabs and each diagram is saved as an XML file using a custom language and a file extention of .flowcode or .circuit. You can group together diagrams and code files into projects which makes a file with a .ktechlab extention that points to the other files but I wonder if it would be more intuitive to just have one file for all your diagrams and code.

Around the edge of the canvas you’ll find electrical components which can be dragged onto circuit diagrams and flow parts for flow chart diagrams. I usually find it best to keep this left hand sidebar open all the time when working, you can do this by clicking on the “Overlap” button (square icon) at the top of the sidebar. On the right hand side is an Item sidebar which gives information and lets you set properties of the currently selected item in the diagram. There is also a context help sidebar giving a helpful description of the currently selected item in the diagram. Many Free Software applications are criticised for their lack of documentation so it is refreshing to find one which goes out of its way to provide extra documentation.

Having worked on Umbrello which also draws diagrams I find myself jealous at the intelligent way the connections joining diagram items route themselves. You can also do manual connection routing if you are not happy with the automatic routing. Diagrams can not currently be resized or zoomed, maybe this will be added in future versions (although it is actually quite difficult to get QCanvas drawings to be resizable on the top and left hand sides).

Using KTechLab

A flowchart is probably the best place to start. In the top left or the diagram is a picture of the PIC chip, this show its initial settings, it is not part of the flowchart itself. You can change these initial settings by clicking on each connects of the PIC to turn it on or off, clicking and dragging left or right will set it to be an input or an output. Flowcharts need a start and end which you can drag in from the flow part sidebar. You can then drag in any of the other flowchar actions and connect them together. Dragging in a subroutine adds a large diagram item into which you can put other items.

 

Ktechlab_2Ktechlab_1

Once you have your flowchart you can convert it into microbasic, assembly code or directly into machine (hex) code by using the buttons on the right hand side of the toolbar (or from the Tools menu).

Now we can make a new circuit diagram. The Components sidebar contains assorted electrical items that can be dragged onto the diagram. At the very bottom is a PIC 18 Pin item. If you add this to a diagram it can be associated with the flowchart you just made (or one of its code representations). Click on the PIC and point it towards the file with your flowchart by editing the filename box in the toolbar. If you now run the PIC by clicking the play button below it the circuit should run according to your flow diagram, you can see the output in the gpsim box at the bottom of the diagram.

But alas Looks like the Developer is no longer working on the said application and no new releases have been issued so i believe that this application wont be going any further ,so it needs developers,geeks to help it start again.Pls guys dont let this appln go down the drain ,It needs Your help.

The sourceforge repository retuns nothing so if you want the packages you will have to download it from rpm.pbone.net.”A word of caution for opensuse users you will have to satisfy many dependencys before you can have it working” ,but it works i have it working on my opensuse 10.2 machine.

PLS HELP KTECHLAB.

Advertisements

5 Responses to “Ktechlab needs your help!”


  1. 1 GoodLady
    March 23, 2007 at 10:08 am

    While I haven’t used KTechLab much, it is the first program that is easy to use and accessible. Surprisingly I’ve had a lot of problems finding suitable electronics tools on Linux that don’t require a month to learn how to use. This bucks the trend though. Shame I can’t find any

  2. 2 Ktechlab user
    March 27, 2007 at 2:15 am

    Somebody Please help Ktechlab!

    I am not a programer so i can not but I have used Ktechlab
    and love it it beats ALL including windows software.
    I first saw this when looking for a good electronic simulator and
    flow chart program for PIC’s, at the time I was runing Windown XP,
    win I found this I Downloaded Kubuntu and was runing this cool
    applacation and now pride myself in converting people from Micro$oft window$
    To Linux! I have already converted 4+ people to linux All from Ktechlab

  3. 3 Miguel Montiel Mtz
    July 25, 2007 at 7:32 am

    hi i from Mx, i ise ktechlan¿b, but in Debian i have asome problemas, u know, an overflow, or someting like that y read you know about programming, if you can help me this is the error when i load a program in pic

    SIGSEGV singnal 11

    (no debugging symbols found)
    Using host libthread_db library “/lib/tls/i686/cmov/libthread_db.so.1”.
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    [Thread debugging using libthread_db enabled]
    [New Thread -1243035968 (LWP 4827)]
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    [KCrash handler]
    #9 0xb7e16bf0 in ProcessorConstructor::ConstructProcessor ()
    from /usr/lib/libgpsim.so.0
    #10 0xb7e234db in CSimulationContext::add_processor ()
    from /usr/lib/libgpsim.so.0
    #11 0xb7e23578 in CSimulationContext::add_processor ()
    from /usr/lib/libgpsim.so.0
    #12 0xb7dc40a8 in PicCodProgramFileType::LoadProgramFile ()
    from /usr/lib/libgpsim.so.0
    #13 0xb7e1ee48 in ProgramFileTypeList::LoadProgramFile ()
    from /usr/lib/libgpsim.so.0
    #14 0x081db9ad in RegisterInfo::staticMetaObject ()
    #15 0x08239b89 in PICComponent::staticMetaObject ()
    #16 0x08239e6c in PICComponent::staticMetaObject ()
    #17 0xb66e9d4f in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
    #18 0xb66ea7e0 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
    #19 0x0825a39a in ProcessChain::staticMetaObject ()
    #20 0x0825e3fb in ProcessChain::staticMetaObject ()
    #21 0x0825eaa2 in ProcessChain::staticMetaObject ()
    #22 0xb66e9d4f in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
    #23 0x08256a0e in ProcessOptionsHelper::staticMetaObject ()
    #24 0x08258b11 in ProcessOptionsHelper::staticMetaObject ()
    #25 0x08270aa2 in ExternalLanguage::staticMetaObject ()
    #26 0x08271022 in ExternalLanguage::staticMetaObject ()
    #27 0xb66e9d4f in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
    #28 0xb6d5e081 in KProcess::processExited () from /usr/lib/libkdecore.so.4
    #29 0xb6d5e2af in KProcess::processHasExited () from /usr/lib/libkdecore.so.4
    #30 0xb6d59540 in KProcessController::slotDoHousekeeping ()
    from /usr/lib/libkdecore.so.4
    #31 0xb6d59652 in KProcessController::qt_invoke ()
    from /usr/lib/libkdecore.so.4
    #32 0xb66e9d4f in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
    #33 0xb66ea656 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
    #34 0xb6a73c7b in QSocketNotifier::activated () from /usr/lib/libqt-mt.so.3
    #35 0xb670c4fa in QSocketNotifier::event () from /usr/lib/libqt-mt.so.3
    #36 0xb6681c26 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
    #37 0xb6683a43 in QApplication::notify () from /usr/lib/libqt-mt.so.3
    #38 0xb6e33e0e in KApplication::notify () from /usr/lib/libkdecore.so.4
    #39 0xb6615421 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
    #40 0xb6673fd9 in QEventLoop::activateSocketNotifiers ()
    from /usr/lib/libqt-mt.so.3
    #41 0xb6629754 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
    #42 0xb669c179 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
    #43 0xb669bf9a in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
    #44 0xb66837bf in QApplication::exec () from /usr/lib/libqt-mt.so.3
    #45 0x0827ab63 in DPText::construct ()
    #46 0xb5f0eea8 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
    #47 0x0807f481 in ?? ()

    for your time thanks, i was reported this bug to bugd.kde
    thanks
    Miguel

    P.S. i U can write a letter please

  4. 4 Pierre
    October 30, 2008 at 9:37 am

    Hello,

    Ktechlab is the best free electronics software I found on the www.
    Practising electronics fore about 30 years, I appreciate the capacity to use both logic and analogic component.
    As I have now a new notebook with a lot of memory and a powerfull processor, I can say the simulation is excellent.
    I would enjoy to provide some help. For example to extend analog components library or to help some documentation translation.
    I also could make some “publicity” on Elektor magazine forum.
    Hoping to hear from you soon.
    Pierre

  5. 5 Mateus ml
    December 22, 2009 at 1:23 pm

    You are all right, we can not let this project end! I’m from Brazil and here fewer people relationated to the eletronic area know about this amazing software. I belive that’s because there is fewer material in portuguese about it, and the ones that start studing this go to other softwares, betters, but not free software. It is true that Ktechlab have a lot to things to improve, like his grafics (furier would be nice), wich is a little poor. But this all depends of us! I’m trying to make some videos showing how to use it for the brazilians, but I must learn a little bit about it before, especially in this part of the PIC programation.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

w

Connecting to %s


My Bookmarks on Del.icio.us

Advertisements

%d bloggers like this: