0
Waiting for MC43 when sending to a single module of a multimaster system.
I have an issue with iQAN Run 7 when trying to program a single MC43 for use as a field replacement. When programming the module using a CAN adapter, the firmware and program go into the module, but after the restarting MC4[1], the process seems to get stuck at "Waiting for MC43[1]".
When I look at the MC43 it is now blinking a 3:1 CAN, no contact fault. Am I doing something wrong here?
Customer support service by UserEcho
I believe you would need to attach the MC43 to the multi-master system to program it otherwise you will get a system mismatch when you replace the module. That has been my experience.
When you are seeing 3:1 CAN no contact, that is a good indication that you have successfully loaded your application to the module. A module that isn't connected to any other module will show this if the application contains other modules with a defined timeout. So that it is a single master from an IQAN multi-master system explains this.
The same blink would be seen in case of no contact with IQAN expansion modules, or J1939 or generic CAN modules with a timeout defined.
I'm not sure why I was having issues, as when I tried again today everything worked as expected. I figured it might have had something to do with my diagnostic bus being on a different CAN network than the one I had my adapter going to, but that wasn't an issue today. Only thing I can think of that changed was I didn't have power applied to C2:73, so the address tag wasn't seen so the module would have been in safe mode.