Forum Replies Created
-
AuthorPosts
-
in reply to: Missing information on MPU Digital Inputs #19906
Hi Craig,
Sorry for my delayed answer.
I investigated the last photo you sent and noticed a diode is missing on your board. This is the diode that is responsible for pulling up the MPU_DIs.
So, let me know if you are comfortable with doing the rework or if you want to send the device back, and we can fix it for you.
If you decide to do the rework, here is the simplified instruction:
1. Please probe both pads of the diode. You need to verify that one pad has V_Batt on it, and the other pad is connected to the dip switch.
2. The simple fix is to directly pour solder on pads and short them to have V_BATT for pull-up voltage. But remember, you will have a back-powering issue. (If VBATT is off and you put voltage on DIs, you can wake up the device)
3. The clean, but harder fix is to populate the diode on that footprint. (MPN: BAS516,135) Anode to VBATT and Cathode to dipswitch.Let me know what your decision is and how I can assist you further.
Amir
Attachments:
You must be logged in to view attached files.in reply to: Missing information on MPU Digital Inputs #19875Where are you measuring the 1.5V on DI? Is it measuring 1.5V on the external screw terminal pin?
Please make sure you activate only one of the Pull dip switches at any time.
Please also note that the dip switch controls the pull for the whole MPU digital input terminal. So, all of them can be set to either pull down or pull up. In case you need different pulls on MPU DI, you should add them externally.Attachments:
You must be logged in to view attached files.in reply to: Missing information on MPU Digital Inputs #19874The pull up voltage on MPU DI will be the same as the V_BATT. So if 12V is connected to V_BATT, the pull up will be 10K ohm to 12V.
This is the same as DI pull ups for MCU.in reply to: RS232 vs RS485 Settings #19872Hi Craig,
There has been an issue with the setup of RS232/RS485 on FCB1.2. However, I remember we did apply a fix on the FCB unit that was sent to you. So on your FCB1.2, the RS232 is active by default. You don’t need to change any dip switches on the board to make it available.(I have also attached a picture of that area of the board.)
Unfortunately, RS-485 won’t be accessible because of the hardware issue on FCB1.2. Sorry about that.
For RS232 communications on RPi-CM4, you can use the UART0 on pins 51 and 55.
Thanks,
AmirAttachments:
You must be logged in to view attached files.in reply to: Inputs multiplexed with PLC #19852Hi Mathew,
The control pilot pin on FCG is muxed with DI12(pin B45).
Also, ADC12(pin A26) acts as a Proximity Pilot with a 1/2 voltage divider ratio.
You don’t need any activation for either pins, which are activated by default.Cheers,
Amirin reply to: PWM on LSO affecting HSO output. #19341Hi Nikhil,
Thanks for your patience.
I would be able to have a more reasonable understanding if you could perform the voltage difference test I mentioned earlier.
Please redo the fault scenario and then 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 it is closed.Thanks,
Amirin reply to: PWM on LSO affecting HSO output. #19205Hi 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 6 months, 2 weeks 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 7 months, 1 week ago by
AmirF.
Attachments:
You must be logged in to view attached files. -
This reply was modified 6 months, 2 weeks ago by
-
AuthorPosts