My program has a GUI which the user can choose inputs and outputs, also time limits, and braking control.
Also I have started on assigning up to two outputs as lights, in case anyone wants to turn on an led while the monitor is rotating. You can also choose which action the light will take, such as blink or on steady..
I got a couple of bugs that need to be worked out, maybe now that Im back home I can pick up where I left off on it.
So your program is command line driven? Does "braking control" mean PWM? I guess my question goes more to "Should I withdraw my MALA Plugin?" Is sounds like yours is going to do everything mine does, be more flexible, will have a nice GUI (as opposed to my text file driven confg) and could be used with multiple emulators.. (Emulaxian/3Darcade would want to send you a 3x4 or a 4x3 instead of 0 and 90)
I would rather see the community settle on a "standard" method and having multiple programs that do the same thing would be detrimental to that.
p.s. Why do you want to turn on an LED during rotation? Just as a test mechanism? (I set one up on my bread board for that reason)
So your program is command line driven?
The following commands will do this:
mrotate = opens GUI, allows user to setup or change things.
mrotate 0 =runs the program in the background, rotating monitor to horizontal.
mrotate 90 =runs the program in the background, rotating monitor to vertical.
Does "braking control" mean PWM?
No, I decided not to go with PWM, although I could probably include if anyone wants it.
mrotate allows users to choose two ways of stopping the motor. (1) Apply both directions on for a set amount of time, and (2) turn off a relay which disconnects the motor from the drive and "shorts" the motor leads together, applying dynamic braking by using the motor as a generator while it is coasting.
"Should I withdraw my MALA Plugin?"
No, I dont think so. Your method works great with the small hobby motor that you guys use. Dont kill it just because there are other methods to do this. Let people decide what is best for them. It would be a shame to give up on the work you have put into it. This program was not made to take the place of yours. I have been working on this concept for a long time, it's just my baby I guess.
"(Emulaxian/3Darcade would want to send you a 3x4 or a 4x3 instead of 0 and 90)"
So are you saying instead of mrotate 0 I would need mrotate 4x3? I will need to modify my program to do this, but it shouldnt be a big deal. look for either 0 or 3x4 and either 90 or 4x3.
"I would rather see the community settle on a "standard" method and having multiple programs that do the same thing would be detrimental to that. "
Im all for that.
"Why do you want to turn on an LED during rotation?"
Well, it is purely optional, but someone may want an led to come on to indicate that the monitor is turning in the proper direction.
You can use one or two LEDs connected to the printer port outputs.
You can have each led flash in both directions, stay on solid in both directions, or do the same for just one direction, while the monitor is turning. It just adds a little pizazz to your control panel.
You can also alternately flash the two LEDS for a few seconds if you get an error, such as monitor timed out before making the limit switch.
Im not using this feature, but it's nice to know it's there if I want it.
In the GUI mode, you can also assign outputs for degauss and monitor off relays.
You can also assign a button on the control panel as a stop button, to turn off all outputs if something is not going right. Im using ESCAPE. (This was very handy while I was setting up the mechanics of the monitor.)
Here is a screen shot of the LED section: