Recent Posts

Pages: [1] 2 3 ... 10
1
General controls / Re: Module Viewer - Out of date view
« Last post by Mike on December 12, 2019, 10:04:19 PM »
Thanks, figured it was something simple that I was missing.
2
General controls / Re: Module Viewer - Out of date view
« Last post by acmall on December 12, 2019, 08:52:23 AM »
When you close the project to .p1p you pack all the files including the latest .scs into the .p1p. Does the .scs file that you are opening in he module viewer have a ~ at the start of the file name. This is a backup of a previous version.

If you want to view the current .scs in the viewer use Close Project instead of Close Project to P1P.  There are some settings in the Project Open/Close section that control what happens when a project is closed.

Alastair
3
General controls / Module Viewer - Out of date view
« Last post by Mike on December 11, 2019, 08:01:50 PM »
Currently I'm working on a program for a display and controller pair. It's useful to use the module viewer to compare and have both "open" at the same time. However one thing I've been running into is that the module viewer is not displaying the program as I last compiled it. There are multiple changes that I've made that don't show up. Is there a setting or something that I am missing when making changes that is supposed to update that file?

My typical process is make the change, save, close to p1p and open the other project. Then to reference; open the module viewer of the file I just changed and closed.

Thanks,
Mike
4
Displays / Re: Is there an easier solution - Menu navigation buttons
« Last post by oiltronic on December 03, 2019, 09:01:29 PM »
For quicker development I just direct the left & right buttons to an up/down counter that wraps around in both directions, and use another button (like 'O' on the DP700) to get back to the home screen.  Then the output of the counter just goes to list of "equals-to" components to activate a boolean flag, which then goes to each screen object.  I figure an operator can hit the right arrow button 10 times before he can activate a pop-up menu, scroll, then select a new screen.  And this way I don't need to make a menu.  It also makes it quick to enable extra screens for things like diagnostics.

I keep a permanent narrow menu at the bottom of the display to indicate what the buttons do.
5
Same as SJ & Tom.  Oldest machine still in service has been open to the damp weather for over 8 years without a single pin-corrosion problem.  Sealing plugs and tinned wire are much more important, in my opinion.
6
General controls / Debug Visualizer and Test Program
« Last post by Mike on December 02, 2019, 09:58:46 PM »
Has anyone used the debug visualizer or run through the test program inside guide?

Thought I would play around with it and see what's going on. The display of the each of the variables is nice (reminds me of CoDeSYS), easy to manipulate inputs to test out and see what happens.

Issue is that it doesn't seem to use timers properly. For example I have an oscillator and the output from it never switches on even though the input is continuous true. It is running as I can see the loop index number increasing.
7
I've made extensive usage of the non-gold contacts without issue.  The only time that I've insisted on the gold contacts is for a very, very long CAN bus.
8
Displays / Re: Is there an easier solution - Menu navigation buttons
« Last post by Mike on December 02, 2019, 03:33:23 PM »
There is a pretty decent video on the youtube page for the layout of a screen selection program.
https://www.youtube.com/watch?v=wlVSgQj6I6U

Essentially you need to use a state diagram to come up with what the buttons do when a certain screen is active. It will be important to lay it out beforehand to ensure that pressing a button cannot activate two separate screens at the same time.

9
PLUS+1™ Compliant Hardware / Re: EMD Speed Sensor
« Last post by G30RG3 on December 02, 2019, 02:52:22 PM »
If I had to program this sensor, I would suggest a modus of the CAN transmitter to send on the same position, not on constant time interval.
At higher speed it should send every 360 degrees 1 message for example.
At lower speed every 180 degrees, but on same positions.
The message should be the speed and then the pulses and time since last measurement.
Ok, I am dreaming.......

Wouldn't like this behavior myself, because that would mean very long intervals when the motor is close to standing still, or even no updates at all when the motor stops...  OTOH at high speed you would get lots of data on the CAN-bus. The actual interval period of the MA filter should be able to filter out variations in angular velocity, but the techinfo isn't clear about the base clock on the MA filter.  I expect it to be maximum 64 pulses of the encoder in its highest resolution (180 pulses per round, so about 1/3 of a round) but it could be anything.

What bothers me more:  It takes about 2 rounds of the motor/sensor before there is output after a power up. So to use the sensor as a position encoder means you need to get an initialisation setting after every power up..

10
PLUS+1™ Compliant Hardware / Re: EMD Speed Sensor
« Last post by G30RG3 on December 02, 2019, 02:15:08 PM »
Hi Nilla, Marbek ...

https://assets.danfoss.com/documents/DOC152886482077/DOC152886482077.pdf  Or google "L1017819 pdf"
See page 8 for info and 14 on instructions to set the parameter.

BR
G30RG3
Pages: [1] 2 3 ... 10