We are trying to capturing data in "measure group" of iQAN mc2 & mdl2. We kept both the controller in "B" (master Bus). We kept diagnostics in "A". CAN communication terminate frequently, during data capture. Can anybody suggest the possible solution?
We wanted to leverage some of the new features of IQANdesign 4 but have found that the backup camera no longer displays properly once updated from IQANdesign 3 (system utilizes an AXIS F1005-E camera and AXIS F41 main unit).
In IQANdesign 3, the camera displayed correctly utilizing the following video stream URL; http://root:email@example.com/mjpg/video.mjpg?resolution=%1x%2
In IQANdesign 4 the camera has to be added as a generic module and no longer displays correctly.The following is the information entered into the generic modules property inspector;
IP Address: 192.168.129.10
Any help would be much appreciated!
Is there some possibility to change time and date directly in the program himself.
Hello. It would be interesting to have the chance to declare freely different touchscreen areas to our applicactions. As far as I know, the only way to use touch areas in display is with an image and declared it as a touch object, but there is not an "touch area" object available to asign it the action when you press. Here an example in other image edition tool. Regards. Diego.
I have been working with IQANdesign 4,01 and I am ver excited about adding the PDF files into my programme.
After loading all my PDF files and then assigning the action to the Text Labels and saving the file, the references are switched when I reopen the program. The text label that was assigned to open the Pump PDF file is now assigned to the Filter PDF and the Filter label is assigned to the Pressure sensor PDF etc...
I am not sure if I am doing something wrong or if I am doing something wrong.
Has anyone else noticed this issue?
I am currently working on a project that I need to control a number of high draw items. Years ago a Parker Rep had pointed me in the direction of the Cooper Bussmann mVEC power distribution module due to the CAN control capability.
I am finally getting around to working with it and am using a MD4 master module. I have basic understanding of J1939/CAN but am somewhat new to programming it on the Iqan.
Just wondering if anyone has experience with this and can help pointing me in the right direction, or maybe even has a base application they can share?
We were in the field with Marcel Colnot having blue screen issues with Iqan 3.19. We decided to update the program to 4.01 and try that and the program would not finish loading through an ASUS WL-330NUL when computer was connected wirelessly to the router (it would get to the end but after restart it went to blue screen - it appeared to be looking for an IP address). We had to take out the address tag and load it with a wired connection direct to an Ethernet port on his computer. I have a suface which has no Ethernet port - I have used the wireless adapter with no problems up to 4.01.
Marcel can give you more details if necessary.
Changes and new features
22588 Send J1939 identification framesA master will now respond to broadcast request for PGN 65242 and 65259 on a J1939 bus.
- Software Identification (65242) will contain 5 strings: Project name, version, id, checksum and vmAC version
- Component Identification (65259) will map the following strings: Make = empty, Model = module type (e.g IQAN-MC2), Serial number = module serial number, Unit number = module address
22547 Crash at startup on Windows XPFixed.
22555 Master crashes upon DM1 reception if no DM1 is definedFixed.
22574 MD4 stops working if external J1939 unit claims address 128Fixed.
22796 Remove "No contact" alarm for APPIN time-outBefore, a single lost APPOUT would trigger a warning message and log event saying 'No contact', even if all other APPOUTs from that module was received. The 'No contact' popup and log event has been removed. No change to the APPIN timeout and action.
Customer support service by UserEcho