We have had multiple issues using ratiometric sensors that end up sending voltages below the 0.5 threshold. If the input drops to 0.250 then the system throws a VIN low error. The error value only exists for an instant. The sensor output is jumpy. I wish we could add some averaging, signal stabilization or add a delay on the error to filter out these events. Or maybe we could define the low error value instead of using the minimum/2. 

In retrospect, it realize I could have set the range to 0 V and extrapolated the value of the output to keep the calibration the same, but I cannot do this on an existing program because the min and max outputs are not part of the calibration. 

I'm using a math channel to add a value stored in an adjustable integer parameter to the measured brightness value to control the backlight. I would like the ability to hide the backlight adjustment in the display preferences menu as this will cause confusion since customers familiar with the MD4 will go there to adjust the backlight, instead of the adjust group.

Or you could just add an ambient lighting adjust mode to the preferences screen so the operator can easilly chose how they want the backlight to operate. That'd probably be a better option.

Customers would like us to export a list of all message channels that can pop up on the interface.

Does Parker IQAN team has any plan/interest to implement CAN-FD (Flexible Data Rate) capability in the future ? 

We are starting to get a large fleet of equipment out in the field. currently to update a md4/mc43 pair we need to wire to the md4 and push the software. This is not convenient because the machines are all over USA. When I use the G11/12  locally we may get 7 of 10 to complete and update, the other 3  lock up the md4.  Doing an update remotely i think would be asking for trouble.  is there an easy way to push updates to people? currently the reliability isn't there. Thanks

Request to add ability to open more than one measure file at once. Useful when comparing two or more measure files.

It appears that it is not possible to mirror an actual connected iQAN display in iQAN simulate. I'm trying to capture images of what certain portions of our program would look like given different conditions on the machine. For the majority of items I'm able to use simulate on its own, but for heavily CAN driven display pages it's much harder, if not impossible, to simulate. It'd be very easy to create the different conditions on the machine itself, but taking pictures of the MD4 for user documentation just doesn't look as professional as screenshots.

with XA2/XS2 as legacy models in IQANdesign 6 and 7 would we be able to have added legacy support for the XC10 to allow software support. this would help with avoiding rewriting software from newer versions to IQANDesign 5 as units get redesigned to phase out outdated controllers. Additionally with the release of the MD5 what would the legacy support of the MD4 when it is eventually phased out. 

Hi!

I want to put a IQAN MC42 to control crane on a timber truck that previously had Olsbergs CAN joystick controls.

I remember that older Olsbergs joysticks were tuned to use 165Hz PWM.

Maybe somone here has experience and is willing to share a correct PWM frequency to control Olsbergs valves with MC42 module COUT?

Maybe you have some tips on things to watch out for?

Thanks in advance.

When you first take a trend using measure in IQANRun 7.01, you have access to a menu with the features:

- Show status bar

- Zoom to extend

- Auto Scale Split

- Auto Scale Join 

- View Cursor Range

- Comment

This menu goes away when you open a measure file that was saved. This makes analyzing measure files later very difficult.