## 
  #####  
 ##  ##  
 #####   
  ##     
  #####  
 ##  ##  
 #####   

         
         
 #    #  
 #    #  
 #   ##  
  ### #  
      #  
  ####   

 _______ 
(  ____ )
| (    )|
| (____)|
|  _____)
| (      
| )      
|/       
         

  _   _ 
 | | | |
 | | | |
 | |_| |
  \___/ 
        

           
     /\    
    /  \   
   / /\ \  
  / ____ \ 
 /_/    \_\
           
           

IMPORTANT: enter the case-INsensitive alphabetic (no numbers) code AND WRITE SOME SHORT summary of changes (below) if you are saving changes. (not required for previewing changes). Wiki-spamming is not tolerated, will be removed, so it does NOT even show up in history. Spammers go away now.


Visit Preferences to set your user name
Summary of change:
'''Developer corner: find a good way for networking the AVR (mega88) boards''' This is rather hardware related. VemsFrontier/Networking is about software/logical issues. While the big ARM guys ( VemsFrontier/ArmEfi and IonSense ) will work nice with CAN, CAN is not feasible for ATMEGA88. ATMEGA88 has an UART (ATMEGA128 also, except it has 2): * FBUS point-2-point for very short distance * RS232 point-2-point for short distance * RS485 bus for upto 32 nodes network. The only cost efficient solution that allows several small boards (displays, dongles, ECMs) to communicate without a central HUB. While FBUS requires no transceivers, the RS232 and RS485 transceivers are the same cost (very cheap) and availability. '''Neither of the above can be used to talk to most notebooks directly: since majority of notebooks have neither of these ports, only USB'''. Fortunately, [http://zone.ni.com/devzone/conceptd.nsf/webmain/F9F58CBF78A3D1ED86256C06007AF286?opendocument&node=dz00000_us bridging ]either of these to USB is simple and cheap. It is normally just a "cable" with some circuitry inside. RS232 and FBUS not only needs bridging to notebook, but also needs a HUB when more than 2 nodes are used. [http://www.rs485.com/pfaq.html converters] * symmetric drive for twisted pair preferred ** [http://focus.ti.com/docs/prod/folders/print/sn65176b.html SN65176B] makes symmetric (shielded pair) serial bus possible apparently same as '''ST485A''' ** ST490A or other driver ** you can experiment with v3 midOPA if you have no other choice * physical ring * physical bus: ** with collision detection ** or sg. like a token-ring ** 1 master + N slave (good enough) * physical star: a board with many serial connections The '''RS-485''' is basically an update of the RS-422 specified for multipoint buses to be constructed. This standard meets and improves all the requirements of the RS-422 allowing, in addition, up to 32 drivers and 32 receivers can be connected to a single bus. [http://www.st.com/stonline/prodpres/standard/interfc/rs42285.htm ST] site. TI has many cost efficient transceivers. [http://www.modbus.org/ modbus] goes hand in hand (as a practical upper layer) with RS485, although RS485 is just the physical layer and modbus is not a requirement. ---- '''RS485 on VemsFrontier/ArmEfi''' * 2 UARTs with LPC... is costlier than we thought, because every UART robs 2 PWM channels, so 2 UARTS means 4 out of 8 PWM is lost. We are sortof short of PWM on VemsFrontier/ArmEfi (although 4 should be enough), but not on other boards: mostly softpwm is good, HW PWM is nice for: ** WBO2 pump (for each WBO2 channel) ** injector PWMing (2 preferred for 8 injectors) ** SMPS (switching supply, eg. for CDI) ** misc analog output (softpwm is usually OK, but soft+HW pwm can do 12+ bits with high freq). This is available everywhere, since VemsFrontier/ArmEfi has only 1 WBO2 and no SMPS and IonSense has no injector PWMing. * CAN to anything (RS485; or RS232 that is only used for PC; or parallel bus like LBUS that is only good onboard) is cheaper than we thought: http://caraca.sourceforge.net/candongle/index.html but software implemented CAN is very limited in baudrate and costs many CPU clocks. Johan, where did you upload the sch? '''Conclusion''' We probably want CAN on as many boards as possible, including the 9343 display. I'm afraid that 2 networks '''both CAN and RS485) would be costly to support originally'''. When we sell 10000 boards, we can maybe rethink this and invest in some development and use 2 networks from than on. The only difference this makes is that smaller sensor-controller boards (made from LPC2129) will have more IO than if they were atmega88 based. But the connector (and supply-connection!) costs dictate the same anyway. '''Also, CAN is a sales pitch''' ---- '''LIN protocol''' - an alternative * Transceiver like [http://ww1.microchip.com/downloads/en/DeviceDoc/21730d.pdf Microchip LIN transceiver] connects to UART with no other components needed (like RS485) * more expensive than RS485 - but still on the cheap side (unlike CAN) * lower bitrate than RS485 * shorter distance than RS485 (would not be showstopper) * similar, but even lower cost solution is a resistor for RX and an NPN (with internal base resistor) and slight pullup for TX. For above reasons, RS485 seems to be the most widely used interconnection standard in the industry for low cost controllers and sensors. I'd (sloppily) say that * '''LIN is a low cost version of Dallas 1-wire'''. But we only use 1-wire when we have no other choice (eg. authtication button). Between boards it's suboptimal, IMHO. * '''RS485 is a low cost version of CAN'''. Definitely a nice direction. Both are nice, depending on speed requirements and application cost (used uC: atmega88 or ARM). ----
Optional: Add document to category:
Wiki formatting: * is Bullet list ** Bullet list subentry ... '''Bold''', ---- is horizontal ruler, <code> preformatted text... </code> See wiki editing HELP for tables and other formatting tips and tricks.