Forum Replies Created
-
AuthorPosts
-
in reply to: PWM on LSO affecting HSO output. #19205
Hi Nikhil,
Thanks for the detailed description of the issue.
I still have some questions regarding the issues happening. The answer will clear up the problem for us.
You stated that the LSOs are driving the solenoids. How much is the total current draw for the LSOs from all the LSOs?
If the overall current draw from all LSOs is 20A or more, can you measure the voltage difference between the GND_IN pin(J2-5/6) and the big GND pads on the PCB, or the enclosure itself if case is closed, when the FCG is in a faulty state?
Are the HSOs also driving inductive loads? Do you have an estimation of the inductance?
Have you utilized external flyback diodes in your setup?Hi Kantesh,
What is the signal you are reading with DI12?
Please keep in mind that low-level threshold on DI12 is 1.5V.
Have you tried the sample code on the website?
Let me know what are the exact upper/lower bands, frequency, and duty cycle of the signal you are trying to read on DI12?in reply to: PWM high side drive control #19177Hi David,
Is it possible that the power supply is limiting current and forcing the VCU to reset?
How inductive are the loads you are driving?
Which outputs are you using currently?- This reply was modified 3 weeks, 5 days ago by AmirF.
in reply to: PWM low side drivers #19176Hi David,
How much current draw each of the LSOs have?
Does the CAN communication completely go away? Or it starts missing some messages?Thanks,
AmirHi Omkar,
It seems like you were using the JTAg only for debugging over Freemaster. Is that right?
When you say JTAG stopped working, do you mean you cannot flash code on the MCU? Or you can’t debug it over Freemaster?
May I also know if you have already checked all the hardware connections? The cable and the PeMicro header can be the source of disconnection as well.
Furthermore, let me know what is the resource/MAP file you are using for Freemaster? Is it the same elf file generated with the binary code when you generate your code?
Thanks,
Amirin reply to: LIN communication in flexcase E #19147Hi Akhila,
There has been an error with the uploaded file. Could you please upload the file again?
Thanks.in reply to: LIN communication in flexcase E #19141Hi Akhila,
I didn’t see your mex file in the attached zip. If you have configured the pins correctly in the mex file, please consider checking the following points:
1. To enable the transceiver, you need to drive the LIN_EN pin(PTB19) HIGH. You also need to drive PTB18 high to have the transceiver in Master(commander) mode. If FlexCase is in LIN slave, there is no need to drive the PTB18.
2. Every LIN bus should have only one master. Slave devices can be more than one. You can use Peak-Lin in both Master and Slave modes.
3. Which MBDT version are you using? And how are you connecting to MCU for FreeMaster?Hi Kantesh,
You can read the DICP or DI12 in the same way you read all other digital inputs.
If you want to read the DI12 in GPIO mode, you need to define the pin in both Dio MCAL and in the pinout section in the config tool. For digital status read, you can use SIUL2.For PWM reads, you need to add a custom C code in your Simulink. Also, you need to set the pin in the config tool as input EMIOS, modify the pin in ICU MCAL, and set the clock reference, and interrupt setting.
You can take a look at the attached example for both GPIO and PWM applications.
Example file is compatible with MatlabR2022a and MBDT1.4. This is not part of our standard templates. Please use with caution.Thanks,
Amir- This reply was modified 1 month, 2 weeks ago by AmirF.
Attachments:
You must be logged in to view attached files.Hi Mobina,
Every time you build the code, Simulink tries to upload the generated files directly to the specified hardware(S32K3 in this case). So, this is an expected message, as Simulink can’t find the MCU, because this needs a direct connection to the MCU or some sort of onboard debugger. You are using another method to flash your binary files to the MCU over CAN using the FlexCase Flash software.
So, please ignore this message and select “abort” every time it pops up.- This reply was modified 1 month, 2 weeks ago by AmirF.
in reply to: FCE/G Configurations #18986Unfortunately, the feedback ADCs for high-side outputs from 8 to 10 are unusable on ADC_MA channels. This is a bug on FCE2.0 and is resolved in the next versions.
As a workaround for feedback for HSO9/10 ADC, you can use another ADC channel ID available on that pin(ADC1_S18). Just ensure the secondary channel ID is not being used on any other physical pin.
Unfortunately, there is no workaround for the feedback pin for HSO7/8.
Thanks,
AmirThanks for the clarification. Unfortunately, because of ASIL safety features JTAG flashing is disabled by default on FCE2.1 boards. Please get in touch with us directly to discuss this matter further.
Thanks,
AmirHi Kantesh. May I ask what are trying to achieve with JTAG flashing? And why aren’t you using flash over CAN?
In general, you won’t be able to flash over JTAG on FCE2.1, unless you have a special development board to do it.Amir
in reply to: FlexCase E Not Communicating over CAN #18946Could you confirm that you are writing to the same CAN that is connected to your PCAN device?
I believe that for flashing software you are using CAN2(CAN2L->pin C3, CAN2H->C4). Can you confirm that the CAN write block you are using in your Simulink is also for CAN2?
Also, please don’t remove the termination throughout the connection.
Please see the attached image.
Thanks,
AmirAttachments:
You must be logged in to view attached files.in reply to: Freemaster over CAN in FCE-G #18693Hello Rishabh,
We will work on this feature and let you know as soon as we have an update.
-
AuthorPosts