argtrak

Thanks for the info SmashTV... I guess I didn't read the links well enough, plus I never worked with comparators. My mistake. :-/ So... Moebius, (or anyone...) how many steps does a HD stepper usually have per turn? I'm curious. :) Pascal

yin (party-yin... chicks ;) )

Hmm, low voltage at low speed, doesn't that raises a potential issue of high voltage at high speed? Â I'm not sure what kind of maximum voltage could come out of a stepper motor at high speed, but it might be more than the 5 volt the DIN are supposed to receive... or maybe even outside the maximum the DIN can handle? Going to fast with a belt trainy might generate pulses too quickly for mios to handle correctly if the stepper has enough steps per turn. And (excluding HD steppers from what I read)at high enough rotation speed the stepping noise created may become an issue if you need a noiseless setup. Â All the stepper motors (not-HD)I have move with a feel similar to detented encoders(just a little softer), and if I turn them fast do they get somewhat noisy. It's true that HD feel different but then I'm not sure about how many steps per turn, they've got.. Â For my part, I'll be going with optical. Mouse optical encoders on the other hand should provide a very stable voltage, low or high speed. Â About the tight feel, that all depends on your construction. Â As mentionned earlier, modifying a pot for continuous rotation should give you a nice enough feel. Â All that's left is the actual construction of the device which shouldn't be too complicated if you use your imagination... Â ;) My 2 cents... Pascal

spider

(For the DINX4) Another option I like to use for those bridges is this: 1. Drill that particular IC pin hole a little bigger.(big enough to fit the IC pin and the size of wire used for the bridge) 2. Put the bridge on the component side of the board (center wirepad - IC pin) 3. Put the socket over the bridge with IC pin and bridge in the same hole. 4. Apply heat on bridge pin that is in the same hole as the IC pin while applying some pressure on the socket so it melts a little grove in the socket so the IC socket can sit flat against the board. (just don't burn yourself in the process ;D) This both hides the bridge and saves you the trouble of messing with tiny lengths of insulation... ;) Pascal :)

Me like 40 pin 8)

I actually bought 5 of those (and a few others w/backlight) back in... november if I remember well. :) That's what I'm using on my SID right now ;D They work pretty good. (for me at least) 8) Pascal

Hi Thorsten, The update works good, the demo application says "Hello World!" :) I have yet one more problem/question... Â I put the modified app_lcd.inc in the sid_v1.5b_18f_stepC project, it compiles without any problem. Â But I can't seem to be able to convert the hex to sysex. Â Is the application too big to contain a custom IIC LCD driver? I keep getting errors of this type: [tt]... Block 007800-007BFF allocated - Checksum: 4E ERROR: you are trying to overwrite the OS address range Use the -os_upload flag if this was your intention![/tt] I tried to rem almost all the stuff in the LCD driver and it converts, but as soon as I unrem more than 2 or 3 mov instructions, it gives me that error message. I tried deactivating the control surface of the SID firmware and that gave me enough space to leave unremmed all of the LCD driver code but that's kind of going backwards if you see what I mean. Â I'm kind of stuck. :'( Pascal

Hi Thorsten, Tried the 1.2b version, with and without the 1k resistor, and the results stayed the same... I found out something else though. Kind of puzzling, but you can probably make sense out of it. USER_LCD_init seems to work fine, it adjusts the contrast and I can turn on or off the backlight. I found that strange since I couldn't see any understandable text displayed on the LCD (hello world message...) so I went out in the app_display.inc file, in the USER_DISPLAY_Tick function and I put some code that would send characters to the screen and it works so my IIC connection seems to be working okay. Here's the code. IRQ_DISABLE call MIOS_IIC_Start movlw USER_LCD_IIC_DEVICE_ADDRESS call MIOS_IIC_ByteSend movlw 65 ; A call MIOS_IIC_ByteSend movlw 66 ; B call MIOS_IIC_ByteSend movlw 67 ; C call MIOS_IIC_ByteSend call MIOS_IIC_Stop IRQ_ENABLE of course, being in the tick function, the text is sent over and over, and wraps around the screen, but it displays okay. I tried to put a call to MIOS_LCD_PrintHex2 in the same function: movlw 66 ; 'B' call MIOS_LCD_PrintHex2 That doesn't work. (gives me the same weird u on its side) Can you deduce anything with this information? Best regards, Pascal

TK, I'm testing it out, and I end up getting something on screen, but it's all parenthesis... Â ))))))))))))))))) Â it seems every characters get sent as ) instead of the actual character... Â any clue why that would be? It's almost like MIOS_IIC_ByteSend would reinitialize the byte to send before sending it. Gotta leave to work, it's 7:30am here... Pascal UPDATE: I changed the address in app_lcd.inc, and the address on the device itself to something different and the characters on the screen are a different character, (they look like weird u on the side) It looks like the bytes received by the LCD have something to do with the address??? I'm a bit puzzled... any clue? Pascal

Hi TK, You're making my day here! 8) And about the testing, just let me know one way or another, and I'll gladly do some testing for you! About the next release of MIOS, any approximate date in mind? I'm just curious... Thanks a lot, :) Pascal

Hi, I'm new here, I just finished building my CORE and SID module ;D Both work gooood :) still need a control surface, (working on that). My question: I have an LCD here made by Matrix Orbital (LK20425) that already has a RS232/I2C interface built on it, and I was wondering if it would be possible to make a custom LCD drive that would use the bankstick port to reach the LCD's I2C address that is in the 0x50-0x6E range... (bankstick if I remember well seems to be I2C compatible) Any hints, clues, sample code?! ;) would be appreciated. Thanks.