Hi,

I have integrated the backup camera on our vehicle and I came across a lag issue with the camera and was wondering what the root cause was. Please see attached video (https://www.dropbox.com/s/0wgs5htr8moqyss/IMG_4580.MOV?dl=0) . Maybe you guys could help.

I chose to go with a 50 ft M12 cable, and there is not much loose considering the fact that the box is 20 ft long.

( https://www.digikey.ca/products/en?keywords=wm15300-nd). 

I played with the following parameters in IQAN for the SV Camera

• Enable HDR: No
• Max bitrate [mbps] : Toggled between 1 and 20. At 1, the image is really pixelized as on the attached photo. At 20, there is a lot of lag. The current setting is at 4, and the image quality is really poor with some lag. Considering the fact that this camera will be used to backup to a shipping dock, the small lag is a big concern for our customers.
• Dimensions: I toggled between Wide 800x600and Narrow 160x120 with no interesting improvement.

Is there something here that I am missing? My though is that the wire is too long, but it is impossible for me to shorten it.

Best regards,

Is it possible to limit an Event counter channel with a maximum and a minimum value?

Do I have to connect the ID-Tag to my Master module even though I'm using only one master module MD4 and one expansion XA2 will be connected to it, can anyone help me with this?

Thanks 

Starting and restarting of a simulation takes a lot of time and after every (re)start it starts in the same view so when you are working on large projects you need to a lot of clicking before you reach the part that you are testing. this is particularly annoying when testing  functions that run only just after boot up.

It would be nice if there was a function that you could do a restart without stopping the simulation and/or a or a function that when a simulation is started the program it stays in a pre- operational state so that you can navigate to the part of the program that you are testing and then start the program simulation. 

We have a multi master system with 1 x MD4, 3 x MC43 fitted to two identical machines. All 4 modules have multiple logs inside, we are able to get logs from all modules, however two logs on one of the MC43's only will refuse to download when using IQAN Run. Running Iqan Design 5.03. The logs are visible, and it displays how many logs are inside, however when double clicking to show the logs we get a blank white screen while its trying to populate the logs on screen then it times out after around 20 seconds with a message box saying no response from the controller. The controller remains active, no error flashes.

The controllers are not overloaded, and we are talking only a couple hundred logs inside each log, not thousands and thousands. Is there any known reasons why this could be happening? Its the same for both machines we have, so something common between the two...

We are using an application created in IQANDesign 5.03.11.5029 and when simulating the application I'm unable to login using credentials i configured within design on IQANRun 5.04.6.4873. Looking closer our password we set in design is 27 characters in length but IQANRun will only allow 25? IQAN Design notes state a password can be up to 40 in length, is this a bug or conflict between different versions?

Does this affect the tablet access as our customers use this length password to login, will IQANRun for tablets also limit the password length to 25 characters?

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.

When I upgraded to IQANDesign 5.04 from 5.03 my project now has 1183 errors, with 99% of them being 'Invalid Context'. I can't seem to find a pattern as to what is wrong with particular snips of code.

Here is one example.

Would like a use Internal Digital in to select different PDFs based on some internal criteria or selections of the type of machine.