Author Topic: SBC65EC with the IOR5E  (Read 10313 times)

shm267

  • Newbie
  • *
  • Posts: 2
    • View Profile
SBC65EC with the IOR5E
« on: August 28, 2005, 05:32:12 PM »
I have tried to get the web site up on the sbc65ec when plugged into the IOR5e and it seems to fail. I get no web pages, I have the latest load from the download page. If I unplug the 65ec board from the IOR board, the board works fine. I thought that the clock chip may be conflicting with the EE prom so I pulled the clock chip. This did not correct the problem. Any ideas on what to try next?

Administrator

  • Hero Member
  • *****
  • Posts: 171
    • View Profile
    • http://www.modtronix.com
Re: SBC65EC with the IOR5E
« Reply #1 on: August 29, 2005, 10:16:34 PM »
Hi

Before plugging the SBC65EC into the IOR5E, please ensure that all pins on the SBC65EC are configured as inputs, except B6 which can be configured as an output. This is done via the SBC65EC's web configuration page. This is the default configuration for the SBC65EC at delivery.

And, as you mentioned, the RTC might also cause trouble, so for initial testing remove it (if fitted). After plugging the SBC65EC into the IOR5E, you can power up the SBC65EC (12V only, seeing that the IOR5E relays are 12V!!!!!), and you will be able to access it via the network. If not, there has to be a unusual error. Are you getting any responce from the SBC65EC when plugged into the IOR5E? Is the light still flashing? Is the serial port still working?

I have included some sample code for testing all LEDs and relays on the IOR5E. Simply add this code to your mxwebsrvr.c file of the SBC65EC source code download. This code will sequentially turn all LEDs and Relays on and off.
Code: [Select]
//Latch pins
#define LATCH_SER       PORTC_RC0
#define LATCH_SCLK      PORTC_RC1
#define LATCH_RCLK      PORTC_RC2
#define LATCH_OE        PORTC_RC5
#define TRIS_LATCH_SER  TRISC_RC0
#define TRIS_LATCH_SCLK TRISC_RC1
#define TRIS_LATCH_RCLK TRISC_RC2
#define TRIS_LATCH_OE   TRISC_RC5

/**
 * Write the given value to the 595s internal register. It is not latched to it's output register.
 * Important!! After calling this function, the output register must still be latched:
 *
 *   //Latch the 595's internal register to it's output register
 *   LATCH_RCLK = 1;
 *   LATCH_RCLK = 0;
 *
 */
void setLatch595(BYTE c) {
    BYTE mask = 0x80;

    LATCH_RCLK = 0;
   
    //Shift all 8 bits into latch
    for (;;) {
        //Shift out next bit
        LATCH_SCLK = 0;
        if (c & mask)
            LATCH_SER = 1;
        else
            LATCH_SER = 0;
        LATCH_SCLK = 1;

        //Break if all 8 bits have been shifted out
        if (mask == 0x01) break;
        mask = mask >> 1;
    }
    LATCH_SCLK = 0;
}

/*
 * Main entry point.
 */
void main(void)
{
    BYTE latchRly, latchLED1, latchLED2;
    .....

    //Reset all outputs to 0
    TRIS_LATCH_SER  = 0;
    TRIS_LATCH_SCLK = 0;
    TRIS_LATCH_RCLK = 0;
    setLatch595(0);
    setLatch595(0);
    setLatch595(0);
    //Clock 595's internal register
    LATCH_RCLK = 1;
    LATCH_RCLK = 0;

    //Now (after all output have been initialized with 0, Enable output latches
    TRIS_LATCH_OE = 0;
    LATCH_OE = 0;

    //Initialize Relay and Latch outputs
    latchRly = 0x01;
    latchLED1 = 0x01;
    latchLED2 = 0x01;

    while(1)
    {
        ........

        /*
         * Increment Relay, LED latches every 500ms
         */
        if ( TickGetDiff(TickGet(), tTest) >= TICK_SECOND/4 )
        {
            tTest = TickGet();
           
            //Rotate values by one
            latchRly <<= 1;
            latchLED1 <<= 1;
            latchLED2 <<= 1;
            if (latchRly == 0) {
                latchRly = 0x01;
                latchLED1 = 0x01;
                latchLED2 = 0x01;
            }

            //Shift out all latches
            setLatch595(latchLED2);
            setLatch595(latchLED1);
            setLatch595(latchRly);

            //Clock 595's internal register
            LATCH_RCLK = 1;
            LATCH_RCLK = 0;
        }

        ...........
    }

    .........
}



*** Modtronix Engineering Support ***

Bob_H

  • Newbie
  • *
  • Posts: 5
    • View Profile
Re: SBC65EC with the IOR5E
« Reply #2 on: December 14, 2005, 01:27:45 PM »
Is there any code or is anyone working on any code to integrate the IOR5E with SBC65EC in such a way that there is web control and readout of the IOR5E???????

modtro2

  • Administrator
  • Hero Member
  • *****
  • Posts: 564
    • View Profile
Re: SBC65EC with the IOR5E
« Reply #3 on: December 16, 2005, 05:13:23 AM »
Hello

The SBC65EC network bootloader is next to be released, and is now finally at a stage where it will be released within the next couple of days. First prototypes have already been sent out. Next will be a program for the SBC65EC that will integrate it with the IOR5E.

steves

  • Sr. Member
  • ****
  • Posts: 34
    • View Profile
Re: SBC65EC with the IOR5E
« Reply #4 on: December 16, 2005, 09:01:11 AM »
Having just ordered an IOR5E for use with my SBC65EC I'd be interested in any version of the firmware that allows access to the RTC. ISTR reading a thread where the I2E code had been disentangled from the EEPROM code. Does the forthcoming release do this? If not can  someone give me a clue?

Thanks,

Steve

kangus

  • Jr. Member
  • **
  • Posts: 7
    • View Profile
Re: SBC65EC with the IOR5E
« Reply #5 on: January 06, 2007, 01:16:00 PM »
Hello

The SBC65EC network bootloader is next to be released, and is now finally at a stage where it will be released within the next couple of days. First prototypes have already been sent out. Next will be a program for the SBC65EC that will integrate it with the IOR5E.

It's been over a year now, have you finished the CODE?

I purchased $400 worth of your hardware just to watch it grow dust while I waited on the code to make the I/O work with the SBC computers.

I really do NOT want to beg users for code to make your product functional.

simond-7

  • Jr. Member
  • **
  • Posts: 9
    • View Profile
Re: SBC65EC with the IOR5E
« Reply #6 on: February 27, 2007, 06:58:57 AM »
I have had my SBC's and enclosures for a couple of weeks now and am very very impressed with what they can do and be programmed to do.  They function best when powered & don't require much dusting at all.  I have also found the best way to solicit a response from anyone is to ask nicely.

Bishop2K

  • Sr. Member
  • ****
  • Posts: 38
    • View Profile
Re: SBC65EC with the IOR5E
« Reply #7 on: May 05, 2007, 02:02:48 PM »
Has anyone ever got the attached main.c to work?  After tracking down the mpfs support files (why it needs them for a demo application I have no idea) ajd fixing relative path errors to source files, now I'm getting a heap of compiler errors...

\src\mxwebsrvr.c:154:Warning [2074] location .tmpdata specified in the interrupt save list is redundant
\src\mxwebsrvr.c:291:Error [1105] symbol 'AnsiEscClearScreen' has not been defined
\src\mxwebsrvr.c:291:Warning [2054] suspicious pointer conversion
\src\mxwebsrvr.c:346:Error [1205] unknown member 'Flags' in '_APP_CONFIG'
\src\mxwebsrvr.c:346:Error [1205] unknown member 'bIsDHCPEnabled' in '_APP_CONFIG'
\src\mxwebsrvr.c:346:Error [1122] scalar operand expected for '!' operator
\src\mxwebsrvr.c:353:Error [1117] scalar type expected in 'if' statement
\src\mxwebsrvr.c:490:Error [1205] unknown member 'Flags' in '_APP_CONFIG'
\src\mxwebsrvr.c:490:Error [1205] unknown member 'bFreezeADCBuf' in '_APP_CONFIG'
\src\mxwebsrvr.c:490:Error [1122] scalar operand expected for '!' operator
src\mxwebsrvr.c:511:Error [1105] symbol 'AdcValues' has not been defined
\src\mxwebsrvr.c:511:Error [1129] [] operator requires a pointer and an integer as operands
\src\mxwebsrvr.c:511:Error [1101] lvalue required
\src\mxwebsrvr.c:518:Error [1105] symbol 'AdcValues' has not been defined
\src\mxwebsrvr.c:518:Error [1129] [] operator requires a pointer and an integer as operands
\src\mxwebsrvr.c:518:Error [1101] lvalue required
\src\mxwebsrvr.c:518:Error [1117] scalar type expected in 'if' statement
\src\mxwebsrvr.c:709:Error [1205] unknown member 'SerialNumber' in '_APP_CONFIG'
\src\mxwebsrvr.c:709:Error [1205] unknown member 'Val' in '_APP_CONFIG'
\mxwebsrvr.c:709:Error [1146] type mismatch in argument 1
\src\mxwebsrvr.c:717:Error [1205] unknown member 'SerialNumber' in '_APP_CONFIG'
\src\mxwebsrvr.c:717:Error [1205] unknown member 'Val' in '_APP_CONFIG'
\src\mxwebsrvr.c:717:Error [1131] type mismatch in assignment
\src\mxwebsrvr.c:719:Error [1205] unknown member 'SerialNumber' in '_APP_CONFIG'
\src\mxwebsrvr.c:719:Error [1205] unknown member 'v' in '_APP_CONFIG'
\src\mxwebsrvr.c:719:Error [1129] [] operator requires a pointer and an integer as operands
\src\mxwebsrvr.c:719:Error [1131] type mismatch in assignment

Programming support documentation for this combination of hardware is woeful.  None of the examples posted in this forum appear to give any insight into getting these two devices to work.
« Last Edit: May 05, 2007, 03:51:08 PM by Bishop2K »

javierdc

  • Jr. Member
  • **
  • Posts: 9
    • View Profile
Re: SBC65EC with the IOR5E
« Reply #8 on: January 31, 2008, 10:59:09 PM »
Hello

The SBC65EC network bootloader is next to be released, and is now finally at a stage where it will be released within the next couple of days. First prototypes have already been sent out. Next will be a program for the SBC65EC that will integrate it with the IOR5E.

Any news on this? I'm having issues trying to program the IOR5E :(

Thanks in advance

D.Drody

  • Full Member
  • ***
  • Posts: 10
  • [url=http://tierussianwoman.w-ru.com/]russian bikini bride[/url]
    • View Profile
    • russia marriage dating
SBC65EC with the IOR5E
« Reply #9 on: November 19, 2009, 12:31:22 PM »
post some pix and the serial number. I may need a mag for a SBC soon