we have a costumer, which would like to make an CAN-Interface for different trucks by himself.
We would like to allow this only, if we can lock in our application all things, except CAN-Interface Module for Truck.
I have tried to make some locks in the application, but this is not possible as I needed. For example I cannot lock the Menu.
Is there a possibility to lock everything, except one software module?
If not, can you program something for us?
I have a problem with a system that uses APP in and out between three modules, one MD4, two MC3. I have found that one MC3 does not appear to be receiving APPIN's. When I monitor the modules in IQAN Run, all modules appear to be talking successfully. When I look at IQAN Design the APPIN's on the module that's faulting says Error, Timeout and its red not green. On the module that's sending the APPOUT, the function block APPOUT is green and OK. Its almost as if the modules are not starting at the same time and the timeout for the first APP in to be received is being reached?
Is there any way of finding out more information about this error?
The machine was working OK for some time and it just happened randomly and now im unable to recover the machine. We also have other machines running this software and same software version and it appears OK.
I have extended the 50ms cycle time to 100ms,on all three modules with no success. Is there any reason why this could have happened? Running Design 3.19.9.
I need 8 directional pulse count inputs... Is there any hope other than using 4 XA2s? Any plans for an IQAN expansion module that can do 4 or even 8 of this kind of input?
I can't find any 3rd party CAN modules that have this type of input. It seems to be all industrial modules.
I was hoping to get some feedback on an error I am encountering. One of our VREF channels is acting up an our MC43 controller. As soon as VBB is greater than 14.0 volts, the Vref goes immediately to 0.0v and throws an error. If VBB drops back down below 14v, the error goes away. The only thing on this Vref is a position sensor (500-4500mv) going into a VIN. Any thoughts on what could be causing this? I'm happy to provide more information if necessary, but I'm not sure what else would be of help.
I maintain 1 program for multiple machines that are very similar, one issue I have to dance around from time to time is if 1 program uses lets say C1:25 on an XA2 as a digital in, and in another program I want to use it as a voltage in, I can not switch it as in the system layout I can only define it as one thing. My workaround is enabling or disabling the XA2's based on my IO assignments, which creates tons of duplicate logic.
It would be nice if a warning showed up instead of locking this functionality out, giving me the flexibility of assigning IO anyway I choose. A way of safely doing this could be to force an SMC when doing this functionality. This could prevent user mistakes. I personally would rather just have the flexibility to do what I want and have my logic be the functionality decider, but with an SMC I could at least get rid of multiple modules doing 99% of the same tasks.
I have to suport old products that were originally programmed with V. 2.60. needless to say When an MD3 needs to be replaced, this causes me a problem.
Is there a way to bring a clone up to date? I do not have an old MD3 laying around any longer.
I have encountered a strange problem with a MD3/MC42 multi master system and cant't seem to resolve it "quickly".
The problem is that I cannot upload the software onto the system effectively. I have used MD3's and MC42's quite a lot in the past but never together like in this manner and this is the 1st time I encounter this issue (usually I have a MD3 with an expansion module or either a MC42 with a MD4 multi master system with no problems) so this time we wanted to use the MD3 and MC42 together for a project, so I thought it will be basically similar to using a MD4 with a MC42.
I have a 0T id tag on the MD3 and a 1T tag on the MC42, when trying to uplod the software via USB through the MD3 I get the message "incomplete system" and showing only the MD3(Safe mode). But the display also indicated wrong ID tag for some reason.
Then when disconnecting the 0T ID tag from the MD3 and try to upload the software, it works when I click yes after I get this message shown below, both controller get updated though, but then after uploading/startup a message appears on the display stating "CONTROLLER MC42 : NO CONTACT"
I work with a customer that uses system with MD3 to control forklift truck.It has worked well for quite long time and suddenly MD3 screen has gone blank (black) however all controls work fine (system works fine). Have you got any suggestions where to start trouble shooting.
Thanks in advance for your valuable support
You probably have a too high module temperature.
If i remember well, the backlight is switched off when the internal temperature exceeds a certain limit.
When the temp goes down, the backlight should be activated automatically
Maybe you can measure the temp with iqan run
Customer support service by UserEcho