Need ONS Random Counter

I am making a Safe Cracking Program for Class on a SLC500, 4 card Chassis.

I need to generate a random number using a timer that counts at .01sec Pre 10 Accum 0 Resetting continuously. Then within a CTU Pre 3, the User will then press a button grab the number from the timer with a ONS to move in into the integers N:7/0, N:7/1, & N:7/2. I had this figured out on paper but lost it.

The next step I think I can get. I want to use an Analog input to find the random numbers.

[kamenges]

NightCraver-
The hard part's done. You have the concept. And it's a good one, by the way. It looks like you listed all the functions you need, too. If you have any specific questions on implementing an instruction or a rung, post them here and we'll help you out. But just go down the path you outlined in your post and you shouyld be golden.


Keith

[Steve Bailey]

I had this figured out on paper but lost it.

I translated that statement to Spanish, then to French, then to German, then back to English, and the result was "The dog ate my homework". If you figured it out once, then presumably you can figure it out again.

You'll need to read up on indexed addressing techniques, because that's how you'll move the timer ACC value you snagged into a different register. The counter ACC value will be your index.

The next step I think I can get. I want to use an Analog input to find the random numbers.

I'm glad that you're sure of yourself on this one, because I'm not. Interesting concept though: an analog input as a search engine for random numbers.

[jdbrandt]

I've used the 'actual scan time' as a seed to a random number
generator before.

Take actual scan time, add the r.t. seconds then limit it for
a two digit number (1-99), then do a 'center squared' routine.
Look up 'center squared' in an old FORTRAN book... or ask
me (and old FORTRAN programmer).

[NightCraver]

This is the Basic Code line I'm attempting to make work
I'm away from my software at the moment so please don't laugh to hard.

|-----|-----|I:3/0|---|-------------------(B:3/0)
|.......|-----|B:3/0|---|
|
|-----|B:3/0|--------|T:4/DN|---------[Ton T:4.0]
|................................................. 0.01Sec
|................................................. Pre 9
|................................................. Accum 0
|
|-----|I:3/2|--------|ONS|------------[CTU C:5.0]
|................................................. Pre 3
|................................................. Accum 0
|
|----|ONS|-----------------------------(MOV)
|................................................. .T:4.ACCUM
|................................................. .N:7.1

I will try to use a light to insure that N:7.1 has a value assigned to it. Most likely will have to use a greater than less than Statement

|----|N:7.1|--------------------------(0:4.0)

[kamenges]

OK. Good start. You are pretty close but you missed a couple of the details you listed in your forst post.

You seem to go through the trouble of setting up a method to start your random number generator (B3/0). But you have no method to stop it once it starts. I suggest either leaving this out or putting in a stop mechanism. The stop conditions are up to you.

The general idea on the free-running timer looks good. Just make sure your sense on the timer contact is what you want (NO versus NC).

The counter increment looks good. But remember the details. This will only work once the way you are set up now.

I think you forgot something at the beginning of your move rung. Oneshots on the power rail don't do much good. Also you are missing a filing concept that you stated from your original post. In your current example, where will the timer accumulated value go every time you store it?

This is personal opinion but don't use the value in N7:1 to drive your light. Really consider what it is you want the operator to know and drive it that way. Do you really care that any given value is in any given location? That does the operator actually need to know?

By the way, your address definitions need a bit of polish. Input and output image table references are a special case as the I and O define both a data type and a file number. This is why they are addressed as I:XX/XX. All other files have separate file type and file number designators. So you get N7:1 for an integer reference and N7:1/0 for a bit reference. Just remember:
<file type><file number>:<element number>/<bit number>

Keep goin'. Don't bail now.

Keith

[NightCraver]

Still Not quit there.


Thanks everyone for your help and I try to do that stuff next post Keith.

[NightCraver]