Recent Posts

Pages: 1 ... 6 7 [8] 9 10
71
Controllers / MC018 C1p11 error 23 and 665
« Last post by macbahi on May 01, 2024, 11:57:59 PM »
Hi Guys,

It's my first time I use MC018. I will use all output. Every think it's OK.
All setting output are the same way.
But when I compile the program, I get error only for C1P11.
You find enclosed the pictures of errors

I had update my plus+1 to 2024.1.5.

Thanks in advance

With best regards
Mac bahi
72
Do you really need to store the state of the sequence in a NVmem? NVmem have a limited number of write cycles. If your sequence is actuated lot of times per day, you could end with a non functionning NVmem block and need to replace the controller.

I would prefer this sequence to be done with Set/Reset components. At Power-On, maybe you could do a kind of "homing" sequence that sets all the cylinder to the original position so the sequence always starts at a known good position.

Sam
73
PLUS+1 Autonomy Hardware / Re: About XM100 and OUSTER Lidars
« Last post by cvandestroet on April 29, 2024, 01:59:20 PM »
Hello ibrahim!
It is mainly a question of processing power. With an OSx-32 at 2048x10, you will likely be able to hook up to 3 or possibly 4 LiDARs to one XM (it depends on what else is going on in the application). If you lower the data rate, you will be able to hook up more. However, using an OSx-64 at 2048x10 has twice as much information, and therefore, the XM can only support half as many lidars. There are a few knobs to tailor to what you need!
74
Displays / Re: DP720 Touchscreen Inactivity Timer
« Last post by Camox on April 29, 2024, 08:54:22 AM »
Hi, there,
If we look at the touchscreen inputs, I would test the X and Y values in the State bus to check that the touchscreen is not being used.



Have a nice day
75
 :oI solved the problem, but I don't understand why it worked, I just put a checkpoint in the routine and the sequence continued.

Does anyone know why the error occurred and why it was "resolved", I still don't understand.
Is it possible that the check points force the controller to read or pay attention to the routines?
76
Displays / DP720 Touchscreen Inactivity Timer
« Last post by gregbosma on April 25, 2024, 07:30:10 PM »
Hi all!

On a DP720 touchscreen program, I have a customer who would like a timer that logs people out of a password-protected page after a certain amount of inactivity. What's the best way to define inactivity?

Tying this timer to the navigation buttons is no problem, but what about touchscreen taps? Is there a quick and easy way to see if anywhere on the screen has been touched?
77
PLUS+1 GUIDE / Re: How to stop automatically generating ports on page interface
« Last post by Tor on April 24, 2024, 08:11:20 AM »
Hello gregbosma,

I guess you are talking about "Add page port matching".
You can find the setting in the options menu in the CAD segment.  See Image and/or the User Manual.


Have a nice day.
78
PLUS+1 GUIDE / How to stop automatically generating ports on page interface
« Last post by gregbosma on April 23, 2024, 08:32:47 PM »
Hi there!

Whenever I go to Page Interface Editor, I notice it automatically adds a bunch of bus ports and wire ports that I don't need. Is there a setting somewhere to disable this feature?

Screenshot:
https://imgur.com/a/GR36kRe
79
Communication / Messages from e Wheel
« Last post by SuperVinay on April 23, 2024, 09:53:37 AM »
Hello PLUS +1 Community,

I am completely new to this controller and CAN.
I am trying to control an electric motor using Plus +1 and Danfoss e-Wheel, I have MC024-120 controller.
I want to read CAN messages from e-Wheel and after some logic send an Analogue signal which will control the electric motor.
The firs issue is CAN messages from e-Wheel, as for example it is U16 signal for steering position, where values 0-4095 contains information of the steering position and 4096-65535 means no information. But when i read messages of specified Bytes using CAN explorer, it fluctuates a lot from 0 to 65000. It gives the correct values also but it fluctuates to point 0 and 65000.
I don't understand what to do now. I am attaching a screenshot here, in that the Red line is steering position, which gives correct value for most of the time stamps but then you can see it just fluctuates. Same happens with Velocity signal. As per e-Wheel catalogue, it sends message in 50ms, so i have same as Log Period in Service tool. Even if is limit the output it does not solve the problem as there will be an output corresponding to maximum the messages of 65000 value should be excluded completely, but also there is 0 which is not correct value but is there. I tried decoding the bits and only taking 12 bits, but of course it does not solve the issue.

I will be hugely grateful if anyone can help me here. Ultimately I need analogue signals to control an electric drive.

Thanks in advance.
Vinay

 
80
I am developing an application that activates on/off valves sequentially, a pulse starts the sequence, write true to activate valve 1, cylinder 1 activates sensor 1 and turns off memory 1 (write false), I use the lowering button of the memory 1 so that memory 2 writes tru and activates valve 2 and so on until the entire sequence is executed. all memories have the same connection and configuration (bool). The problem occurs in memory 45, the name assigned to the first memory is MT1_B1 for routine 1, MT2 _B2 for routine 2, etc. The problem occurs to me in step MT45_B4. Is there any restriction on the names used for these components? Another possible problem is that I develop the application using an hwd file for mc012_110 (it is the hardware that I have available to run and monitor in servicetool), then I copy the routines and paste them into the program to use on the machine, which is a mc050_110, both files are compiled without errors, the drivers can be loaded into the controllers, both drivers can be monitored without problem using service tool, but on the field hardware (mc050) the routine is interrupted at step MT45_B4. Is there any restriction on the maximum number of memories and/or their names?
Pages: 1 ... 6 7 [8] 9 10