Dontronics Message Board

What's New? - Super4 USB Relay Module

donmck — Fri, 09 May 2008 02:21:08 GMT

What's New at Dontronics?

9-May-08 TCTEC Pty Ltds Super4 USB Relay Module is a USB hub powered, modular relay control board. The super4 USB relay board is driven directly over USB via a dll. A virtual com port is not used, this avoids an extra layer of abstraction and gives the fastest response.It also eliminates the need to set baud rates, fifo buffers etc.
http://www.dontronics-shop.com/Super4-USB-Relay-Module-p-16730.html

Forum: Hardware

What's New? Micro Bus Modules

donmck — Tue, 29 Apr 2008 23:41:03 GMT

What's New at Dontronics?

28-Apr-08 Solid Fusion Technologies Micro Bus Modules are a modular, rapid prototype / development system using standard interface building blocks. The system is not tied to any particular CPU. The designer can use a PIC, 8051 or AVR today and switch to an ARM7 tomorrow simply by swapping CPU module. Standard interface modules exist for functions like I/O, data logging, debugging, communication, power supply etc. or design your own modules using the prototype board. Take plug and play to a whole new level.
http://www.dontronics-shop.com/Micro-Bus-p-1-c-414.html

Forum: Hardware

What's New? Droids SAS XBee Boards

donmck — Thur, 24 Apr 2008 10:00:19 GMT

What's New at Dontronics?

24-Apr-08 Droids SAS XBee Boards The XBee Boards have been designed to allow an easy and reliable connection between the Xbee modules and your application. XBee and XBeePRO modules are fully supported. Although we have sold the Simple and USB boards due to the popularity we now have more products available. Now shipped from Dontronics, Tullamarine, Australia. Don't wait for them to come from Italy!
http://www.dontronics-shop.com/home.php?cat=389

Forum: Hardware

u401 C# .DLL Exports

HowY — Thur, 03 Apr 2008 20:39:21 GMT

Well I see the list is dead but the device still rocks!

So here's the "Dll Commands" in C#

The "Class"

// needed to import the .dll
using System.Runtime.InteropServices;

    public class USBm
    {
        public static byte BitA0 = 0x00;
        public static byte BitA1 = 0x01;
        public static byte BitA2 = 0x02;
        public static byte BitA3 = 0x03;
        public static byte BitA4 = 0x04;
        public static byte BitA5 = 0x05;
        public static byte BitA6 = 0x06;
        public static byte BitA7 = 0x07;
        public static byte BitB0 = 0x08;
        public static byte BitB1 = 0x09;
        public static byte BitB2 = 0x0A;
        public static byte BitB3 = 0x0B;
        public static byte BitB4 = 0x0C;
        public static byte BitB5 = 0x0D;
        public static byte BitB6 = 0x0E;
        public static byte BitB7 = 0x0F;

// USBm.dll - C# pInvoke examples
// "Commands"
//

        public static extern bool USBm_FindDevices();

        public static extern int USBm_NumberOfDevices();

        public static extern bool USBm_DeviceValid(int Device);

        public static extern bool USBm_About(StringBuilder About);

        public static extern bool USBm_Version(StringBuilder Version);

        public static extern bool USBm_Copyright(StringBuilder Copyright);

        public static extern bool USBm_DeviceMfr(int Device, StringBuilder Mfr);

        public static extern bool USBm_DeviceProd(int Device, StringBuilder Prod);

        public static extern int USBm_DeviceFirmwareVer(int Device);

        public static extern bool USBm_DeviceSer(int Device, StringBuilder dSer);

        public static extern int USBm_DeviceDID(int Device);

        public static extern int USBm_DevicePID(int Device);

        public static extern int USBm_DeviceVID(int Device);

        public static extern bool USBm_DebugString(StringBuilder DBug);

        public static extern bool USBm_RecentError(StringBuilder rError);

        public static extern bool USBm_ClearRecentError();

        public static extern bool USBm_SetReadTimeout(uint TimeOut);

        public static extern bool USBm_ReadDevice(int Device, byte
        public static extern bool USBm_WriteDevice(int Device, byte
        public static extern bool USBm_CloseDevice(int Device);

    }

An "Example" of function calling

          if (!USBm.USBm_FindDevices()){ // No USBm device attached
      MessageBox.Show(string.Format("No Device Present"), "USBm Devices", MessageBoxButtons.OK,                         MessageBoxIcon.Information);
      return;
          } // implied else
//Walk the USBm.dll functions

// some containers
          StringBuilder sb = new StringBuilder(200);
          bool result = false; // return values

         // .DLL FindDevices returns the number of devices
         // public static extern bool USBm_FindDevices();
         result = USBm.USBm_FindDevices();

        // return the number of devices
        // public static extern int USBm_NumberOfDevices();
        int TotalDevices = USBm.USBm_NumberOfDevices();
        int Device = TotalDevices -1; // only One device is ever attached so ...

        // .DLL About info
        //public static extern bool USBm_About(StringBuilder about );
        result = USBm.USBm_About(sb);

        // .DLL Version info
        //public static extern bool USBm_Version(StringBuilder Version);
        result = USBm.USBm_Version(sb);

        // .DLL Copyright info
        //public static extern bool USBm_Copyright(StringBuilder Copyright);
        result = USBm.USBm_Copyright(sb);

        // Device Valid
        //public static extern bool USBm_DeviceValid(int Device);
        result = USBm.USBm_DeviceValid(Device);

        // Device Manufacturer
        //public static extern bool USBm_DeviceMfr(int Device, StringBuilder Mfr);
        result = USBm.USBm_DeviceMfr(Device, sb);

        // Device Product String
        // public static extern bool USBm_DeviceProd(int Device, StringBuilder Prod);
        result = USBm.USBm_DeviceProd(Device, sb);

        // Device Firmware Version
        // public static extern int USBm_DeviceFirmwareVer(int Device);
        int FirmVer = USBm.USBm_DeviceFirmwareVer(Device);

        // Device SerialNumber
        // public static extern bool USBm_DeviceSer(int Device, StringBuilder dSer);
        result = USBm.USBm_DeviceSer(Device, sb);

        // Device DiD
        // public static extern int USBm_DeviceDID(int Device);
        int DID = USBm.USBm_DeviceDID(Device);

        // Device PiD
        // public static extern int USBm_DevicePID(int Device);
        int PID = USBm.USBm_DevicePID(Device);

        // Device ViD
        // public static extern int USBm_DeviceVID(int Device);
        int VID = USBm.USBm_DeviceVID(Device);

        // Device Debug String
        // public static extern int USBm_DebugString(int Device);
        result = USBm.USBm_DebugString(sb);

        // Device Recent Error - always returns true
        // public static extern bool USBm_RecentError(void);
        result = USBm.USBm_RecentError(sb);

        // Device Clear Recent Error
        // public static extern bool USBm_ClearRecentError(void);
        result = USBm.USBm_ClearRecentError();

        // Device SetReadTimeout
        // public static extern bool USBm_SetReadTimeout(uint TimeOut);
        uint tOUT = 3000;
            result = USBm.USBm_SetReadTimeout(tOUT);

        // Device WriteDevice
        // public static extern bool USBm_WriteDevice(int Device, ref int OutBuf = { 0, 21, 3, 65, 8, 17, 60, 0 };
            result = USBm.USBm_WriteDevice(Device, OutBuf);

        // Device ReadDevice
        // public static extern bool USBm_ReadDevice(int Device, array);
            byte
        // public static extern bool USBm_CloseDevice(int Device);
            result = USBm.USBm_CloseDevice(Device);


Cheers!

HowY

Forum: USBmicro

What's New - 4dSys. OLED-320XX-PMD3

donmck — Mon, 31 Mar 2008 22:22:26 GMT

What's New at Dontronics?

31-Mar-08 4dSystems OLED-320XX-PMD3 The OLED-320XX-PMD3 series are compact & cost effective all in one SMART display modules using the latest state of the art Active Matrix OLED (AMOLED) technology with an embedded PICASO graphics controller that delivers stand-alone functionality to any project. The easy to learn and use 4D Graphics Language (4DGL) with its vast built in library functions will allow rapid application development.
http://www.dontronics-shop.com/4d-Micro-OLED-320-24-PMD3-Module-with-2.4-non-touch-screen-p-16696.html
http://www.dontronics-shop.com/4d-Micro-OLED-320-24-PMD3T-Module-with-2.4-with-touch-screen-p-16697.html
http://www.dontronics-shop.com/4d-Micro-OLED-320-28-PMD3-Module-with-2.83-non-touch-screen-p-16698.html
http://www.dontronics-shop.com/4d-Micro-OLED-320-28-PMD3T-Module-with-2.83-with-touch-screen-p-16699.html

Forum: Hardware

Olimex ICD2 Pocket

imsceptic — Mon, 03 Mar 2008 00:27:22 GMT

Hi

I recently purchased an ICD2 Pocket & have been experiencing problems.

Unit worked initially, was able to connect, program, erase & read target PIC. I was also able to run debug in MPLAB.

Now however, I am unable to connect to ICD2, even without target connected. MPLAB diagnostics suggest device access is OK.

Device Access Test: ICD2
Pass
Connection established. Device was seen.
Connection closed.
Device should be displayed in Windows Device Manager.

But when trying to connect using MPLAB IDE, I get the following...

Connecting to MPLAB ICD 2
...Connected
ICDWarn0054: MPLAB IDE has lost communications with the MPLAB ICD 2. Would you like to attempt to reconnect?
Connecting to MPLAB ICD 2
...Connected
ICD0286: Unable to communicate with ICD
ICDWarn0054: MPLAB IDE has lost communications with the MPLAB ICD 2. Would you like to attempt to reconnect?
Connecting to MPLAB ICD 2

Over and over. I have followed target header wiring instructions - have 10k pullup on MCRL. I have uninstalled & reinstalled firmware client to no avail. Can you please give me some suggestions to aid in a resolution. Any help you can provide would be greatly appreciated. I have noticed that if I set the device to a 16F84A & load an appropriate project (as opposed to 16F628A which is my current project), I still get the "unable to connect" message, but only once & then the MPLAB says it has connected.

ICDWarn0054: MPLAB IDE has lost communications with the MPLAB ICD 2. Would you like to attempt to reconnect?
Connecting to MPLAB ICD 2
...Connected
ICD0286: Unable to communicate with ICD
ICD0082: Failed MPLAB ICD 2 operation
MPLAB ICD 2 Ready

If I then attempt any MPLAB function such (program, erase etc), I get the "lost communication" error again (plus a bonus error) as below (suspect operation actually failed as no LED activity seen on target side)...

ICD0082: Failed MPLAB ICD 2 operation
...Erase Failed
ICD0024: Communications: Failed to write ('$7F00
' - 6 of 6 bytes - Windows::GetLastError() = 0x0, 'The operation completed successfully.
' - USBCOM = 0x1)
ICDWarn0054: MPLAB IDE has lost communications with the MPLAB ICD 2. Would you like to attempt to reconnect?
Connecting to MPLAB ICD 2
...Connected

I cannot determine where the problem is given that PIC device type selection in MPLAB has an impact on the type of error seen

Cheers

Forum: Hardware

PIC programmer question

justy — Fri, 15 Feb 2008 02:00:02 GMT

Hello there,

I've had a fair bit of experience with AVR programmers, but none with PIC. I have to program a PIC16LF88 for a project I'm working on. The chip is a SMD and will be programmed via in-circuit means. Am I right in thinking that this is a similar method that's used with AVR chips?

Specifically, I use the Arduino platform- there's a bootloader that waits for serial input, and if it's found, it uses this to load the code into the Flash RAM. Obviously a new PIC chip won't have this bootloader, so is it correct to assume that it's possible to do in-circuit programming that simply flashes the Flash on the chip with the desired code?

Finally, will I need to buy a PIC-specific programmer? I already have a DT-006 as well as several Arduino boards.

Thanks!

Forum: Hardware

uLCD - String display

CidVilas — Wed, 30 Jan 2008 10:38:38 GMT

Hello everyone! Woo! My first post. I purchased this screen, uLCD320PMD2, and i have been able to figure out Squares, lines, circles, and initializing. The one things which has eluded me some quite some time now is the String function. No matter what i do i just cant figure it out. So i decided to post. Hopefully someone can help sort me out. I am using a PIC16f690 uC. The screen works great, however, once i send the string command it assumes i am trying to start up the demo application on the screen which i don't understand since the letter 'd' is no where in the message. but help me out. I have posted the function below.

void LCD_STRING(int col, int row, int font, int16 colors, char str

The way i am calling up the function is like this:
LCD_STRING(1, 1, 0, 0xF0F0, &"Hello world");

Thanks for taking the time! Ill try to post some pictures later if someone feels it would help.

Forum: 4D Systems

What's New? - Olimex's LPC-E2214-1Mb

donmck — Thur, 17 Jan 2008 08:38:44 GMT

What's New at Dontronics?

17-Jan-08 Olimex's LPC-E2214-1Mb MCU: LPC2214 16/32 bit ARM7TDMI-St with 256K Bytes Program Flash, 16K Bytes RAM, EXTERNAL MEMORY BUS, RTC,4x 10 bit ADC 2.44 uS, 2x UARTs, I2C, SPI, 2x 32bit TIMERS, 7x CCR, 6x PWM, WDT, 5V tolerant I/O, up to 60MHz operation
http://www.dontronics-shop.com/LPC-E2214-1Mb-p-16695.html

Forum: Hardware

What's New? - Olimex's AVR-USB-162

donmck — Thur, 17 Jan 2008 08:37:52 GMT

What's New at Dontronics?

17-Jan-08 Olimex's AVR-USB-162 AT90USB162 is the easiest way to add USB functionality to your next device, Atmel provide free open source HID (mouse, keyboard) and CDC (USB-to-RS232) code and on top of this AT90USB162 cost is same as ATMega16, so what you are waitng for?
http://www.dontronics-shop.com/AVR-USB-162-p-16694.html

Forum: Hardware

What's New? - uDrive-USD-G1

donmck — Sat, 15 Dec 2007 05:36:39 GMT

What's New at Dontronics?

14-Dec-07 4dSystems uDrive-USD-G1 The uDRIVE-uSD-G1 is an extremely compact and an ideal companion module that can be easily interfaced to any microcontroller that requires a Disk Drive data storage system. Most microcontrollers are limited by the available onboard memory for those applications that require large volumes of data. The uDRIVE-uSD-G1 takes that burden away from the host controller by allowing data transfers to-and-from via a simple serial interface.
http://www.dontronics-shop.com/4d-uDRIVE-uSD-G1-Tiny-Disk-Drive-Data-Storage-Module-p-16692.html

Forum: 4D Systems

What's New? - uOLED-96-PROP

donmck — Sat, 15 Dec 2007 05:35:46 GMT

What's New at Dontronics?

14-Dec-07 4dSystems uOLED-96-PROP The OLED-96-PROP is an extremely compact and a cost effective ready to go 'drop in' embedded display module that will deliver stand-alone functionality to your project. The module represents a unique combination of a powerful micro controller, the Propeller chip from Parallax Inc, a 0.96 96x64 pixel 65K full colour OLED display and a micro-SD memory card socket capable of supporting up to 2GB of storage; all in an incredibly tiny 27mm X 23mm package. .
http://www.dontronics-shop.com/4d-Micro-OLED-96-PROP-0.96-Propeller-Powered-OLED-module-p-16687.html

Forum: 4D Systems

Whats' New? - uOLED-96-G1

donmck — Sat, 15 Dec 2007 05:34:39 GMT

What's New at Dontronics?

14-Dec-07 4dSystems uOLED-96-G1 The OLED-96-G1 is a compact (similar size to a postage stamp) & cost effective all in one SMART OLED Display with an embedded graphics controller that will deliver stand-alone functionality to your project. The simple to use embedded commands not only control background colour but can produce text in a variety of sizes as well as draw shapes (which can include user definable bitmapped characters such as logos) in 256 or 65,536 colours whilst freeing up the host processor from the processor hungry screen control functions. This means a simple micro-controller with a standard serial or USB interface can drive the OLED-96-G1 module with total ease.
http://www.dontronics-shop.com/4d-Micro-OLED-96-G1-0.96-Stamp-sized-Intelligent-OLED-module-p-16686.html

Forum: 4D Systems

uOLED

Simon_Ampleman — Mon, 26 Nov 2007 21:03:30 GMT

Hi,

I bought the uOLED-128 one year ago.. I saw that there is a new version GMD1... I would like to know if this one supports double buffering ? Or else, is there new commands to avoid screen flickering.. ?

My application is very simple, I want to draw a bar chart (16 bars of 8 pixels wide, 0 to 128 pixels height)... The value for each bar refresh 64 times by second. So I want the display to show as much as possible and without erasing the front buffer at each frame.

Thank you.

Simon

Forum: 4D Systems

READ ME FIRST: !!!!! Archives ONLY. DO NOT POST NEW MESSAGES. Please ask all 4d questions on 4d message board.

donmck — Thur, 22 Nov 2007 20:19:44 GMT

It is becoming increasingly difficult to answer questions on this board, as well as the 4d Systems board, so we have decided to do it all on the 4d Systems message board.

This will be better all round, as at this point, there are many more users there, and your questions can be answered by 4d direct, or by the other users as a self help group.

As it it now, I have to forward all messages to 4d, as they don't get a copy.

Just the way the forums have evolved, so we need to change it to make it better for all.

For any new new questions, please go direct to the 4d Systems forum at:
http://www.websitetoolbox.com/tool/mb/4d

Thanks

Cheers Don...

Forum: 4D Systems