Problem with canny 5.2 can gateway (Page 1 of 2)

I just thought of something.  Does the 5.2 need termination resistors on either side?

Thank you!!

I never would have looked for the resistor.  My 5.2 is now happily passing messages.

Changing the IDL on 0x271 messages to 273 is working

For 0x351 messages, it appears that the change for the reverse signal is always being applied no matter what the state of IO channel 8 and I'm not sure why you're resetting the Gateway configuration, but I will figure those out.  You shouldn't have to debug my logic.

Your response was much appreciated.

Okay, I have this working.  My problem was that the default state for DIO channels 8 and 9 is +12v and they have pull up resistors to reset the level for an open circuit.  Just using my brake light line for the reverses signal put 12v on a DIO channel that was already at 12v and without the brake lights the input wire is just open so the channel is still at 12v.  No change is ever detected.

Two viable solutions.
Use the brake signal to close a relay that grounds the DIO channel.  This works.
Use channel 10 in ADC mode.  I haven't tried this yet because there are no RED or FED registers in ADC mode and it will change the logic a little.  I'll try it later...just for the exercise.

You missed nothing. Wiki page for it was poor and not translated. Now fixed: http://wiki.cannylogic.com/index.php?ti … ADC_Driver

I am also interested in whether the Canny can perform a pulse frequency measurement function, as many older cars also use this method for speed signalling.  It could be useful for adapting dashboards and speed sensors that were not intended to work together.

It just depends on the electrical properties of the signal and the sensor attached, which will vary by vehicle. My old Audi runs off a transmission sensor that I think generates 8 pulses per transmission revolution but I'm not positive. it may also send a lighting signal on the same wire.  If I had a scope it would be easy to see what going on.  I don't, so I dropped the question in here.

Technically, the pulses are sending distance information and are used to drive the odometer first and then converted to speed and mapped to drive a stepper motor for the speedo.  I just want to sense the pulses, count them and generate a hex pulses per second to stick in a can message for my nav system.   

To translate transmission pulses to speed, you also have to know the differential ratio and the tire circumference, then do the math.  Newer cars store that conversion factor in the instrument cluster ecu and many allow the the tire circumference to be modified.  Most new cars also eliminate the transmission sensor and just pick up pulses from one of the ABS wheel sensors, which eliminates the need to know the differential ratio.

Here's what I had.  I didn't use the built-in counter but I think the result should be the same.  I have no idea which would be the most efficient.

Thank you.  Based on how I think the speed wire in my car works, I'd start losing pulses at around 20 mph?

After bench testing the logic, I finally installed the Canny5.2  in my old Audi.  I'm isolating the
instrument cluster on the infotainment bus (100k FT), so I put the cluster on Can1 and set as FT.  The rest of the car is on Can0 (Radio/Nav, Phone and and Audi gateway).

The only things I'm trying to do at this point are (1) switch the ID for the ignition message and (2) add the reverse signal to the speed message.

It didn't go well.  I will try to do some monitoring in the car later today or tomorrow, but the Can0 side is not playing well with the rest of the vehicle.  It appears to be dragging the bus way down .  Radio cycles on and off.  Steering wheel buttons get through only occasionally. Phone powers up but doesn't execute  pairing cycle. The phone and steering wheel signals don't even go through the Canny.   I suspect it is either the Canny isn't fast enough  or more likely that it is just creating problems for the FT on Can0.. Any suggestions?

If I'm right one suggestion for the 7.2 may be to allow both can ports to be set as fault tolerant.   

I'm sure it will get sorted out so all that aside....Happy New Year to everyone watching.

I  am using the gateway function  with some very simple additional logic.  I change the ID for one message and use the 12v line from my back up lights  on the ADC port to add reverse information to one other message.  I agree that speed is probably not the problem.  My logic file is attached.

My 2001 Audi has three networks.  The powertrain network is just like your car, 500k standard CAN.  The other two are 100k fault tolerant networks.  Without going into a lot of detail, those networks are idesigned so that if one wire is lost the network will continue to function.  The signal levels utilized are different than standard.

Colleagues, it seems that there must be an inversion before Sleep Mode register. Without it, your diagram is constantly trying to fall asleep.

cubic_nz
The perfect advice! Also, you can do without updating the CAN GW settings when it is not necessary.

Using an ADC can be justified in your case and will not noticeably affect the controller's speed.

You have set the  "CAN GW Selector 0 Linked CAN IF" = 1, and "CAN GW Selector 1 Linked CAN IF" = 1. This means that messages going in the direction from panel (CAN1) to car (CAN0) will changed. It is correct?

As for CANNY 5.2 duo and FT-CAN: When the CANNY is connected to the FT-CAN network of two or more FT-CAN devices, it is not necessary to switch on the transmitter mode. So, you can safe connect CAN0 interface to car network. When the CANNY is connected to a single CAN-FT device, you must to enable FT-CAN mode of CANNY CAN interface for for proper CAN Sleep Mode functioning. You can enable FT-CAN mode only on the CAN1 interface. So your hardware configuration when the car is connected to the CAN0 and the panel to the CAN1 is correct. CANNY 5.2 duo  are widely and successfully used on VAG with 100k FT-CAN. The situation you described with inadequate car equipment behaviour is typical for improper connection or a faulty on-board CAN network. I am sure that you will be able to resolve this issue. You can count on our help.