Email: Password: Remember Me | Create Account (Free)

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
???
11/18/09 21:16
Read: times


 
#170950 - Why not byte-coded?
Responding to: ???'s previous message
Use a byte-coded solution.

Start with some global configration bytes informing about inputs and outputs etc.

Then transfer an array of bytes, where the bytes represents commands and each command can take optional bytes for parameters.

Take 8 pins to be arbitrary inputs or outputs
Take one byte internally as 8 virtual state cells
Take 8 bytes internally as 8-bit counters/accumulators

Send configuration, telling which pins you expect to be inputs and outputs. Possibly configuring delay timers etc.

Send array of commands.

Let the program continuously loop through the byte-coded commands, performing calculations and producing results.

By adding new byte-coded commands, you can make the processing as complex as you like.

List of 12 messages in thread
TopicAuthorDate
PLC using 89S52            01/01/70 00:00      
   BEWARE industrial PLC can take an awful lot of abuse            01/01/70 00:00      
      reply            01/01/70 00:00      
         do you not know what a PLC is            01/01/70 00:00      
            Why not byte-coded?            01/01/70 00:00      
            Reply            01/01/70 00:00      
               think it through            01/01/70 00:00      
                  Reply            01/01/70 00:00      
                     C# programming            01/01/70 00:00      
   RE: I'm not sure if this is the correct way for starting...            01/01/70 00:00      
   I tried to build one...            01/01/70 00:00      
      Reply            01/01/70 00:00      

Back to Subject List